Keep one rule source per package and project it into the filename each coding agent expects, with a lint for rule documents that have started holding something else.
Plugin agent-rule-projection from marketplace modootoday in modootoday/marketplace. Commands read from the repo's manifest — 23 days ago.
agents-md-budget-trimCut a package's thin rules file (AGENTS.md or CLAUDE.md) under its byte budget by keeping only constraints there and moving everything else verbatim to the long-form document, settling any contradiction between the two by measuring the code, and keeping links from the thin file to the long form. Use
instruction-token-auditMeasure agent instruction files - root and per-package AGENTS.md or CLAUDE.md, rule files, skill metadata - in tokens through the provider's token-counting endpoint, report the distribution and the bytes-per-token spread, and convert existing byte budgets to token equivalents. Use when sizing or bud
monorepo-package-rules-scaffoldLay out agent rules across a monorepo - a root AGENTS.md under 12 KB and 200 lines that points to path-scoped .agents/rules/*.md files, one per-package AGENTS.md of constraints only under 4 KB with the long form in .agents/PACKAGE.md under 200 lines, the CLAUDE.md and GEMINI.md links each package ne
rule-layeringKeep one source of rules per package and project it into the filename each coding agent expects, splitting always-loaded constraints from the document read on demand. Use when a repository is read by more than one agent, or when rule files have started to disagree.
Your own Naver blog, Place, Smart Store, shopping, search ad and news comment data read through the datalab.tools browser extension, plus card news, short-form video, tutorial posts and social copy built in its editors, with no invented numbers and no change made without asking.
31 skills
Numbers that mean what they say: ClickHouse SQL that reads the key and deduplicates correctly, Naver trend data read as ratios, metrics defined once, experiments designed before launch, retention read by cohort, and open survey responses grouped with every response id kept.
16 skills
Reading passages that hit a measured grade level, language drills, and teacher-side checks for coverage, answer keys, lesson timing, study calendars and rule-valid puzzles, with the numbers and logs shown.
14 skills
Growth and community work: store listings written for the people searching that store, Discord servers run with structure and consistent moderation, newsletters readers open and finish, a month of social posts a small team can ship, launch emails that lead with what changed, and sites submitted to Google, Naver and IndexNow engines from a pipeline.
13 skills
Early product-planning steps done carefully: spar on an idea, frame the problem behind a request, synthesize feedback without overstating it, rank a backlog while saying where the ranking is fragile, write a Korean PRD with testable acceptance criteria, and put a decision on one page with the recommendation first.
13 skills
Korean content that reads well and stays true: product copy fixed to the Toss writing principles, Naver blog posts planned for search, persona tone measured with markers, and ghostwriting that never invents the author's facts.
11 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.