docs
Skill245 starsChanged 9 months agoMITView on GitHub
Generate or update documentation for Terrae components
- Reads credentials
171 other projects use a version of this.
Adopted by
Most recently taken up by
- AngeloDotNet/claude-configtheir own version, first seen Nov 16, 2026
- lenhatthanh20/natamuxtheir own version, first seen Nov 16, 2026
- RLinf/RLinftheir own version, first seen Nov 15, 2026
- cpoder/claude-apple-plugintheir own version, first seen Nov 15, 2026
- Canonry/agent-readinesstheir own version, first seen Nov 15, 2026
- automagik-si/genietheir own version, first seen Nov 15, 2026
Used with
Projects with it also use import-memory, build-fix and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
amirbironSkillimport-memory
Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.
Also in 3 projects that use this
diego-tobalinaSkillbuild-fix
Fix build and compilation errors systematically. Run when build fails.
Also in 3 projects that use this
JkudjoSkillincident
Production incident response — structured triage, hypothesis tree, safe remediation, incident record
Also in 4 projects that use this
vbrevikSkillwork
Use when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.
Also in 7 projects that use this
mbwsimsSkillimpact
This skill should be used when the user asks to "check the impact", "what will break if I change this", "blast radius", "impact analysis", "what depends on this", "who imports this", "is it safe to change this", mentions "/impact", or wants to understand the consequences of modifying a specific file or function before making changes.
Also in 3 projects that use this
AnthropicSkilldebug
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.
Also in 19 projects that use this
Other versions171 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 171
- remotion-dev/remotion★ 73ksame name
- PrefectHQ/fastmcp★ 29ksame name
- jlowin/fastmcp★ 29ksame name
- ccusage/ccusage★ 19ksame name
- ryoppippi/ccusage★ 19ksame name
- micronaut-projects/micronaut-core★ 6.4ksame name
- RLinf/RLinf★ 5.7ksame name
- latitude-dev/latitude-llm★ 4.8ksame name
- samuelgursky/davinci-resolve-mcp★ 4.1ksame name
- TanStack/ai★ 3.4ksame name
161 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 11 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 134 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Use src/app/docs/lines-animated/page.tsx as the reference for component documentation structure and patterns.
- Distinctive: line 18
Ask the user what they need:
- Distinctive: line 35
Use Cases grid (exactly 2 use cases, not more)
- Very specific: line 39
Use h-full w-full for the container div (NOT fixed heights like h-[400px])
- Distinctive: line 41
Always get accessToken from environment variable
- Distinctive: line 61
Add new entries at the top with:
- Distinctive: line 67
Use code blocks with proper syntax highlighting
- Distinctive: line 70
Document all props with types and defaults
- Distinctive: line 71
Add visual examples where helpful
- Distinctive: line 72
Use DocsCode for inline code references
- Distinctive: line 73
Use DocsLink for external links
- Distinctive: line 77
Ask for feedback and adjustments
- Distinctive: line 78
Only save after user approval
“Common” is measured: kept by at least 6 in 10 of the 134 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Docs Skill
Generate or update documentation for Terrae components.
Reference
Use src/app/docs/lines-animated/page.tsx as the reference for component documentation structure and patterns.
Instructions
- Determine Documentation Type
Ask the user what they need:
- Component documentation page
- Weeklog entry
- README update
- API reference
For Component Documentation Location:
src/app/docs/{component-name}/page.tsxExamples Location:src/app/docs/_components/examples/{example-name}.tsxStructure:
- Title and description (in DocsLayout)
- Installation section
- First example (directly after installation, NO title/description)
- Additional examples (each with DocsSection title and description)
- Animation Modes or similar feature explanations (if applicable)
- Properties table
- Use Cases grid (exactly 2 use cases, not more)
- Performance Tips
- Example Component Patterns
- Use
h-full w-fullfor the container div (NOT fixed heights likeh-[400px]) - The ComponentPreview wrapper handles sizing
- Always get accessToken from environment variable
Example structure:
export const ExampleName = () => { const accessToken = process.env.NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN || "" return ( <div className="h-full w-full"> <Map accessToken={accessToken} center={CENTER} zoom={10}> {/* Component here */} </Map> </div> ) }
- Use
For Weeklog Entries Location:
src/app/docs/weeklog/page.tsxAdd new entries at the top with:
- Date
- Summary of changes
- Links to relevant components
- Documentation Patterns
- Use code blocks with proper syntax highlighting
- Include working examples
- Show both basic and advanced usage
- Document all props with types and defaults
- Add visual examples where helpful
- Use DocsCode for inline code references
- Use DocsLink for external links
- Review Process
- Show the documentation to the user before saving
- Ask for feedback and adjustments
- Only save after user approval
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

