dotagents

Create, update, audit, and maintain AGENTS.md, CLAUDE.md, .cursorrules, GEMINI.md, copilot-instructions, or similar coding-agent instruction files, using evidence-based best practices. This covers setting up or bootstrapping such a file for a repo or service ("set up a CLAUDE.md", "bootstrap agent docs", "init"); cleaning up, trimming, shortening, or fixing a bloated file the agent seems to ignore; advice on what content belongs in these files; deciding between one root file vs. per-package files in a monorepo; and consolidating drifting per-tool files (Cursor, Claude Code, Codex, Copilot) into one canonical file with symlinks or imports. Also use when the user never names a file but wants coding agents to know repo-specific commands, conventions, or gotchas — they say "document this for the agent", "make sure Claude knows about X", "add this to the project instructions", the agent keeps guessing commands wrong or repeating a mistake, or a change added commands, env vars, or conventions agents must know. Hand

Write new prose or rewrite existing text so it doesn't read as AI-generated. Use whenever producing content a human will read as writing — blog posts, emails, READMEs, LinkedIn posts, docs, announcements, marketing copy — and always when the user says "humanize", "make this sound less like AI", "this sounds robotic", "rewrite this in my voice", or asks you to edit a draft for tone. Apply it even when the user doesn't mention AI: if the output is prose meant to sound like a person wrote it, this skill applies.