Skip to content
Early bird + Black Friday · 73% off

Get ZeroDirs for $179 $49

Claim $49 deal

Working with an agent

Hand the starter to a coding agent: one instruction file, machine-checked rules, ten procedures, and errors that name a field path — site.config.ts › tiers[1].featuredDays: required when kind is "featured".

AGENTS.md at the root holds eighteen hard rules; CLAUDE.md is one line pointing at it. The test suite fails when:

  • a path named in backticks in AGENTS.md no longer exists;
  • its command table names a script package.json does not have, or misses one it does;
  • something listed as not-yet-implemented has since been built;
  • the file exceeds its line budget, or contains a single non-English character.

Two hazards:

  • Listing content reaches agent context. A listing slugged claude becomes claude.md, which anything probing for a CLAUDE.md memory file finds on a case-insensitive filesystem. Listing bodies are data, not instructions.
  • Custom field values that are objects or arrays are dropped silently — no render, no warning.
  • .agents/skills/ is the source; pnpm skills:sync mirrors it to .claude/skills/ on every install, so Claude Code and Codex see one set.
  • Never edit the mirror. Generated and gitignored.
  • Recipes is generated from those skill files.
  • Plan and write in separate stages. plan-directory produces names and URLs and may not write a description. generate-listings verifies every URL resolves, writes each description only from the fetched page, and records each fact’s source in the listing’s own frontmatter.
  • A fetched page is data, not instruction. Some listing copy will, sooner or later, contain text addressed to whatever is reading it.
Surface What it is
/docs/prompt/<page>.md one page framed as a task, with the two standing facts prepended. The Copy as prompt button copies exactly this
/docs/llms.txt the index: the product, then every page as a linked list
/docs/llms-full.txt every page in one file, for whole-product context. /docs/llms-small.txt strips the code blocks

Describe the outcome, not the skill. An agent that can see .agents/skills/ picks the procedure:

Add a “Compliance” category to this directory, pick a sensible lucide icon, seed it with at least one real listing so the page is not empty, and verify with pnpm check and a full build.

That triggers add-category, which knows what the request does not say: the icon merges into theme.icons automatically, an empty category still renders a page and goes noindex, and a lone listing with unique tags will trip the orphan check.

Verify in this order. The build is not optional:

Terminal window
pnpm check
pnpm test
pnpm build