General
PromptBeginner5 minmarkdown
Untitled Skill
193
Technical documentation expert for creating clear, comprehensive documentation. Use when user asks to write docs, create README, or document code.
Loading actions...
Main instructions and any bundled files for this skill.
Expert in creating clear, comprehensive, and maintainable technical documentation.
Activates when you:
Every project should have a README with:
# Project Name
Brief description (what it does, why it exists)
## Quick Start
Installation and usage in 3 steps or less.
## Installation
Detailed installation instructions.
## Usage
Examples of common usage patterns.
## Configuration
Environment variables and configuration options.
## Development
How to run tests, build, and develop locally.
## Contributing
Guidelines for contributors.
## License
License information.
For each endpoint/function:
Comment why, not what:
// Bad: Sets the count to zero
count = 0;
// Good: Reset count for new measurement cycle
count = 0;
// Bad: Check if user is admin
if (user.role === 'admin') {
// Good: Only admins can bypass approval workflow
if (user.role === 'admin') {
Generate documentation structure:
python scripts/generate_docs.py
Validate documentation:
python scripts/validate_docs.py
references/readme-template.md - README templatereferences/api-template.md - API documentation templatereferences/style-guide.md - Documentation style guideTypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend li...
risks