agent-rules-skill-authorlisted

# Agent Rules And Skill Author ## Purpose Create or revise repo-local agent rules and `.agents`-compatible skill packages without leaking project-specific instructions into the wrong layer. ## When To Use - The user asks to create, evaluate, rename, delete, or edit skills. - The user asks to change `AGENTS.md`, manifests, validators, `common/**`, `project/**`, or `skills/**`. - The user explicitly asks for user-facing README documentation changes. - The screenshot-to-frontend pipeline rules, tool contracts, or skill routing need maintenance. ## When Not To Use - The user asks to write a design implementation spec from screenshots. Use `design-screenshot-spec`. - The user asks to implement a frontend layout from a spec. Use `frontend-layout-implementer`. - The user asks to visually verify rendered UI. Use `frontend-visual-qa`. - The user asks to adapt a new project in Plan Mode. Use `project-onboarding-adapter`. ## Required Context 1. Read `AGENTS.md`. 2. Confirm the classified task is `skill-documentation-refactor`, `documentation`, or another `.agents` rule-maintenance task. 3. Read `common/documentation-maintenance.md`. 4. Read affected `common/**`, `skills/**`, `project/**`, manifests, validators, templates, examples, and root pointer files for the requested change. 5. Apply `common/readme-policy.md`: read targeted README sections when the request concerns README, public setup guidance, or docs/implementation drift; verify technical claims through higher evidence.