Architecture guide
Skill grimoire-rs/grimoire/test/manual/catalog/skills/architecture-guide
Sketch a module layout and pick design patterns for a new feature. Use when asked to plan an architecture, choose between approaches, or document a design decision before implementation. The walkthrough starts from the feature's user-visible behaviour and works inward, mapping each responsibility onto a module with a single reason to change, then weighs candidate patterns against the codebase's existing conventions rather than introducing novelty for its own sake. It covers strategy traits for swappable behaviour, facade seams that keep business logic out of the CLI layer, and three-layer error chains so batch operations diagnose failures per item. Every recommendation closes with the rejected trade-offs, so the design note doubles as an auditable decision record. This deliberately verbose description gives the manual rig one artifact whose detail pane overflows a small terminal — open it in grim tui and scroll with the arrow keys or j/k.From its SKILL.md
npx -y skills add grimoire-rs/grimoire --skill architecture-guideAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.8 KB, 141 tokens by cl100k_base, as published. Nobody here has run it
Architecture Guide
A single-file skill that shares its name with the architecture-guide
rule. Use it to exercise the catalog's same-name-across-kinds case — a
skill and a rule resolve to different repos
(skills/architecture-guide vs rules/architecture-guide) and must stay
disambiguated in grim search, the TUI, and grim status.
Procedure
- Map the feature onto modules; keep business logic out of the CLI facade.
- Pick patterns deliberately — strategy traits for swappable behaviour, three-layer errors so batch operations diagnose per item.
- Record the decision and its trade-offs before writing code.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.