01
Find
Search by the problem, target, language, framework, runtime, or architecture term you already know.
$ patterns find "replace database safely"00Why patterns exists
Architecture that stays legible
Code generators can give a project a starting shape. They do not explain which decisions must survive its next hundred changes.
A pattern is a small, versioned architecture guide for people and coding agents: responsibilities, dependency direction, extension recipes, decisions, and the boundaries a deterministic tool can verify.
AWhat it is
Reusable architectural knowledge
Patterns install under .patterns/. They route an agent from a compact manifest to the one structure, rule, recipe, or decision needed for a task.
BWhat it is not
Not a starter or source scaffold
Adding a pattern never creates controllers, components, repositories, or configuration. The coding agent applies guidance in the context of your code; the CLI handles distribution and checks only.
CThe consumer workflow
02
Evaluate
Read the human title, use and avoid cases, technical requirements, relationships, and source before installing.
03
Add
Install a pinned knowledge bundle directly from Git. Your application files remain untouched.
$ patterns add owner/repo/path#tag04
Check
Let agents follow the same guide humans can read, then enforce explicitly declared import boundaries in CI.
$ patterns checkDTwo halves, one ref
Discovery here. Distribution in Git.
patterns.directory is a searchable, rebuildable index. The repository remains the source of truth and the CLI installs directly from it. Publishing registers a verified ref and metadata; it does not upload the pattern files.