From armor
Mines a codebase's recurring solutions into a named pattern language, or applies existing patterns to new problems with local adaptation. Useful for documenting conventions, onboarding, or asking how things are usually done.
How this skill is triggered — by the user, by Claude, or both
Slash command
/armor:pattern-languageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A set of proven solutions, named and written down, that you reuse with
A set of proven solutions, named and written down, that you reuse with adaptation. The Gang of Four patterns are the famous example. It is the constraint system that keeps taste from wandering. The other skills in this set lean on it.
Lightest of the set. Most of its value overlaps with a good conventions doc or ADR. Keep it if your repo has strong habits but no written record of them. Skip it if your conventions are already documented.
Pick one recurring concern: error handling, data fetching, validation, module layout.
Find three or more places the codebase already solves it. Use ast-grep for
structure, rg for text.
If they agree, that is a pattern. Name it. Write: the name, when to use it, the
shape, and one real example at file:line.
If they disagree, that is not a pattern. It is drift. Flag it. Do not enshrine an accident as a convention.
Name the problem.
Match it against the documented patterns. If none exist, mine on the fly from the three nearest examples.
Surface the matching pattern and the adaptation this context needs. Patterns get reused with changes, not copy-pasted. The change is the point.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub markacianfrani/armor --plugin armor