Maintains Grimoire's technical documentation using structured narrative standards.
Install
mkdir -p .claude/skills/docs-grimoire-rs && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14725" && unzip -o skill.zip -d .claude/skills/docs-grimoire-rs && rm skill.zipInstalls to .claude/skills/docs-grimoire-rs
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when authoring or editing Grimoire documentation — user guide, reference pages, doc pages under `docs/`, or doc narrative structure.Key capabilities
- →Read source code before documenting.
- →Read product context from `.claude/rules/product-context.md`.
- →Search real-world examples from other ecosystems.
- →Draft documentation narratively: idea → problem → solution → depth.
- →Verify internal links point to existing sections.
- →Use custom anchors on every heading.
How it works
This skill guides the creation of Grimoire documentation by enforcing a structured workflow that includes reading source code and product context, drafting narratively, and adhering to specific formatting and linking standards. It emphasizes problem-solution-depth structures.
Inputs & outputs
When to use docs
- →Write user guide sections
- →Draft technical reference pages
- →Verify documentation links
- →Maintain product context in docs
About this skill
Grimoire Documentation
Role: write user-facing docs for Grimoire (Markdown under docs/).
Workflow
- Read source code — no memory docs
- Read product context —
.claude/rules/product-context.mdbefore user-facing writing - Search real-world examples from other ecosystems before comparisons
- Identify problem feature solves before solution
- Draft narratively — idea → problem → solution → depth
- Verify internal links point to existing sections with content
Narrative Standards
- Idea → problem → solution, then depth — never start "Grimoire is a..."
- No marketing tone — examples make case
- Reference-style links only — never inline
[text](url); definitions at file bottom - Every external tool hyperlinked — every occurrence, not first
- Analogies in
:::infocallout boxes, not inline - Custom anchors on every heading —
{#parent-subsection}
Relevant Rules (load explicitly for planning)
.claude/rules/docs-style.md— narrative + linking + anchor conventions.claude/rules/product-context.md— positioning and product identity
Tool Preferences
- WebFetch / WebSearch — real-world examples from other tools before comparisons
Constraints
- NEVER inline links — reference-style only
- ALWAYS read source before documenting; never from memory
Handoff
- To /hex-architect — docs revealing design ambiguity
- To Builder — code changes uncovered while writing docs
$ARGUMENTS
When not to use it
- →When documenting non-Grimoire projects.
- →When writing marketing copy.
- →When not using Markdown for documentation.
Limitations
- →Documentation must be Markdown-based.
- →Links must be reference-style only.
- →Custom anchors are required on every heading.
How it compares
This skill provides a structured, product-specific documentation workflow with strict narrative and formatting rules, unlike general documentation practices.
Compared to similar skills
docs side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| docs (this skill) | 0 | 3mo | No flags | Beginner |
| ml-paper-writing | 48 | 6mo | Review | Advanced |
| docs-review | 10 | 8mo | No flags | Beginner |
| claude-md-improver | 21 | 7mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
ml-paper-writing
davila7
Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.
docs-review
metabase
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
claude-md-improver
anthropics
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project memory optimization".
write-docs
tldraw
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.
update-docs
vercel
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
wiki-architect
microsoft
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.