technical-writing
Guide for writing effective technical documentation, specs, and markdown files. Use when creating or editing specs, documentation, READMEs, AGENTS.md files, or any markdown content in the codebase.
Datos de origen
- Repositorio
- cashew-labs/libretto
- Última actividad en el origen
- 4 de marzo de 2026 a las 23:18
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 899
- Forks
- 69
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- technical-writing
- description
- Guide for writing effective technical documentation, specs, and markdown files. Use when creating or editing specs, documentation, READMEs, AGENTS.md files, or any markdown content in the codebase.
# Technical Writing
## Audience
Assume readers are at least as smart as you, so do not over-explain. State information once and move on.
## Style
Write concise, complete sentences using active voice and present tense. Each paragraph or bullet should express a single idea.
## Formatting
- Do not use emojis.
- Do not use bold or italics.
- Use headings, lists, and code blocks only when they add clarity.
- Use fenced code blocks with language identifiers.
## Paths
Always use relative file paths: `docs/testing.md`, not `/Users/name/project/docs/testing.md`.
## Do Not Repeat
Link to existing resources instead of duplicating content. Reference other docs, web pages, or files rather than restating their information.
Ver en GitHub