learn-grimoire
Learn Grimoire
Orient a new or existing user on what grimoire is, why it exists, its core concepts, and how to actually use it day to day.
Why This Is Best Practice
Adopted by: Structured tool onboarding — why it exists, then core concepts, then a first real task, in that order — is standard practice in developer-tool adoption design, documented in Stripe's and GitHub's own developer-onboarding writing. Leading with purpose before mechanics is the consistent pattern across CLI tools with high sustained adoption. Impact: Developer tools that lead new users with a clear "why does this exist" step before mechanics see measurably higher sustained usage than tools that start users directly on commands — a consistent finding in developer-tool adoption research. A user who installs a tool but never understands why it exists or how its pieces fit together tends to under-use it, or abandon it for the familiar default (here, ad hoc prompting) even after installing it. Why best: Starting a new user directly on mechanics (command syntax, file formats) without first establishing why the tool exists produces surface-level compliance without genuine adoption — the user can follow a command but doesn't know when to reach for the tool unprompted. Orientation on purpose and mental model first, followed immediately by a first real task, is what converts installation into actual habitual use.
Sources: Stripe and GitHub developer-onboarding design documentation; grimoire's own STANDARD.md and README.md
Steps
Step 1: What grimoire is, in one paragraph
State plainly: grimoire is a package manager and curated, peer-reviewed library of best-practice skills for AI assistants, working across many agents (Claude Code, GitHub Copilot CLI, Gemini CLI, and others), organized into domains → subdomains → individual skills.