Instructions
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add longbridge/gpui-component --skill generate-component-documentationCompatible with
Supported agents
When generating documentation for a new component:
Follow existing patterns : Use the documentation styles found in the docs folder (examples: button.md , accordion.md , etc.)
Reference implementations : Base the documentation on the same-named story implementation in crates/story/src/stories
API references : Use markdown code blocks with links to docs.rs for component API references when applicable
Examples
The generated documentation should include:
C
No content available.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongenerate-component-documentationExecute the skills CLI command in your project's root directory to begin installation:
epx add longbridge/gpui-component --skill generate-component-documentationFetches generate-component-documentation from longbridge/gpui-component and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/generate-component-documentation
Restart Cursor to activate generate-component-documentation. Access via /generate-component-documentationin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
simple-english
AminBlg/SimpleEnglish · other · tag: documentation
ui-component-patterns
supercent-io/skills-template · Frontend · tag: component
spring-boot-openapi-documentation
giuseppe-trisciuoglio/developer-kit · Backend · tag: documentation
official-document-writing
kagurananaga/official-document-writing-skill · Documents · same category
pdf-compress
claude-office-skills/skills · Documents · same category
nano-pdf
steipete/clawdis · Documents · same category
Solid pick for teams standardizing on skills: generate-component-documentation is focused, and the summary matches what you get after install.
generate-component-documentation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added generate-component-documentation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in generate-component-documentation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
generate-component-documentation has been reliable in day-to-day use. Documentation quality is above average for community skills.
generate-component-documentation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend generate-component-documentation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend generate-component-documentation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
generate-component-documentation has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added generate-component-documentation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 56