foundation

Subagent-configuration audit methodology preloaded by the subagent-auditor agent. Dispatch subagent-auditor to audit subagent configuration files; the main conversation reaches this audit only through that agent.

ALWAYS invoke this skill when creating, editing, or configuring subagents. NEVER create subagents without this skill.

Skill authoring standards enforced across all creating and auditing skills. Loaded by other skills, not invoked directly.

Agent prompt writing conventions enforced across all creator and auditor skills. Loaded by other skills, not invoked directly.

SKILL.md audit methodology preloaded by the skill-auditor agent. Dispatch skill-auditor to audit SKILL.md files; the main conversation reaches this audit only through that agent.

ALWAYS invoke this skill when creating, editing, or improving SKILL.md files.

ALWAYS invoke this skill when designing or building web components, pages, or dashboards. NEVER design or build web UI without this skill.

ALWAYS invoke this skill when writing reader-facing documents such as public docs, web pages, and product messages for outside readers like developers and customers. NEVER invoke for chat responses to the user (no matter how long), operational prose like code comments, commit messages, or agent-facing instructions like SKILL.md.

ALWAYS invoke this skill when auditing or reviewing internal team documents for cleanup. Use this whenever the user asks to review, audit, clean up, or check the writing of a Notion page, runbook, hiring rubric, scorecard, internal policy, decision record, design spec, competency model, onboarding guide, or any other doc that lives in a workspace and is read by colleagues. NEVER invoke for external-facing prose like READMEs, blog posts, web copy, customer release notes, or marketing material — use audit-prose for those instead. NEVER invoke for responses to the user, including long research summaries delivered in chat, or for agent-facing instructions like SKILL.md.

ALWAYS invoke this skill when auditing reader-facing documents such as public docs, web pages, and product messages for outside readers like developers and customers. NEVER invoke for chat responses to the user (no matter how long), operational prose like code comments, commit messages, or agent-facing instructions like SKILL.md.

ALWAYS invoke this skill when writing or editing internal team documents that live in a workspace: Notion pages, runbooks, hiring rubrics and scorecards, internal policies, decision records, design specs, competency models, onboarding guides, status pages, internal wiki content. Use this skill whenever the user is creating a doc intended for colleagues who already have context, not for strangers reading it for the first time. NEVER invoke for external-facing prose like READMEs, blog posts, web copy, customer release notes, or marketing material — use write-prose for those instead. NEVER invoke for chat replies, commit messages, code comments, or agent-facing instructions like SKILL.md.

Catalog of anti-patterns and positive patterns for internal team documents (Notion pages, runbooks, scorecards, hiring rubrics, internal policies, decision records, design specs, competency models). Reference skill loaded by other internal-doc skills, not invoked directly. Use write-internal-docs to write, or audit-internal-docs to review.

Prose anti-patterns enforced across all skills. Loaded by other skills, not invoked directly.