Skill files
Templates that ship on ana init. Each has four sections: Detected (machine-populated), Rules (actionable constraints), Gotchas (stack-specific traps), Examples (code snippets). Core skills install for every project. Conditional skills install when the scan detects their triggers.
Skills · 8Template path · .claude/skills/{name}/SKILL.md
Core skills
Installed for every project regardless of stack.
coding-standardscoreInvoke when implementing features, writing code, or reviewing code quality. Contains project-specific naming conventions, error handling patterns, import style, and deviations from standard practices.
7 rules
deploymentcoreInvoke when working on deployment configuration, CI/CD pipelines, environment variables, or release processes. Contains project-specific deploy platform conventions.
0 rules
git-workflowcoreInvoke before any git operations — branching, committing, merging, or creating pull requests. Contains project-specific branch naming, commit format, and merge strategy.
3 rules
testing-standardscoreInvoke when writing tests, reviewing test quality, or setting up test infrastructure. Contains project-specific testing framework conventions, fixture patterns, and coverage expectations.
5 rules
troubleshootingcoreInvoke when debugging failures, diagnosing unexpected behavior, or investigating test failures. Contains project-specific failure modes, diagnostic workflows, and known issues.
0 rules
Conditional skills
Installed only when the scan detects their trigger — an AI SDK, a database ORM, or an API framework.
ai-patternsconditionalInvoke when building features that call LLM APIs, handling AI responses, managing prompts, or integrating AI SDKs. Contains error handling, security, prompt management, and observability patterns.
7 rules
api-patternsconditionalInvoke when implementing API routes, request handling, middleware, or error responses. Contains validation, error format, route architecture, and authorization patterns.
4 rules
data-accessconditionalInvoke when working with database queries, schema changes, migrations, or data models. Contains project-specific ORM conventions and data access patterns.
5 rules