Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- Documentapply documentation philosophy — explain why, not what. use for jsdocs, READMEs, inline comments.Votes: 0GitHub stars: 64
- Design DocumentationUse when 编写或修改特性 RFC、架构、系统、功能或详细设计说明书；普通实验报告用 cinderx-optimization-report。Votes: 0GitHub stars: 2
- Common DocumentationAssumption: each TODO represents a real follow-up rather than intentionally deferred work. 1. Inventory every TODO and assign an owner. 2. Create or link a ticket for each actionable item. 3. Rewrite comments using the required format: ```ts // TODO(alice): Explain why retry jitter is required to prevent the thundering herd. // Ticket: PROJ-123 ``` 4. Make comments explain `why`, not mechanics or obvious code behavior. 5. Convert public API comments to JSDoc, including `Args`, `Returns`, and ...Votes: 0GitHub stars: 549
- Project DocumentationWrite documentation, a brief, PRD, PCD, or implementation plan; fix documentation checks or retire a docs publisher.Votes: 0GitHub stars: 3
- DocumentationDocumentation. Use when writing docs or reviewing documentation.Votes: 0GitHub stars: 105
- Common DocumentationWrite effective code comments, READMEs, and technical documentation following intent-first principles. Use when adding comments, writing docstrings, creating READMEs, or updating any documentation.Votes: 0GitHub stars: 549
- Common DocumentationWrite effective code comments, READMEs, and technical documentation following intent-first principles. Use when adding comments, writing docstrings, creating READMEs, or updating any documentation.Votes: 0GitHub stars: 549
- CollectionUse when looking up information from the latest Docusaurus documentation at https://docusaurus.io/docsVotes: 0GitHub stars: 24
- Files<%= description %>Votes: 0GitHub stars: 76
- CollectionUse when looking up information from the latest Docusaurus documentation at https://docusaurus.io/docsVotes: 0GitHub stars: 24
- DocumentationWrite and maintain the project documentation.Votes: 0GitHub stars: 316
- Documentation CriteriaDetermines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each is stored. Use when deciding documentation scope or creating or reviewing a technical document.Votes: 0GitHub stars: 231
- Docs WritingUse when asked to write, restructure, or audit documentation with Diataxis types, or to draft a feature docs page or diagram source. Not for ADRs or architectural rationale.Votes: 0GitHub stars: 52
- DocumentAfter implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.Votes: 0GitHub stars: 2
- CollectionApply rigorous technical writing standards when creating architecture documentation, system descriptions, component descriptions, API documentation, or any technical specification text. Use when writing descriptions for systems, actors, externals, modules, components, relationships, or interfaces.Votes: 0GitHub stars: 24
- Documentation StandardsTemplates for issue docs, ADRs, roadmap entries, changelogs and Mermaid diagrams. Use when drafting an ADR, a changelog entry or a known-issue doc, updating the roadmap after a feature ships, or diagramming a system.Votes: 0GitHub stars: 80
- Technical WritingCreate architectural decision records (ADRs), system documentation, API documentation, and operational runbooks. Use when capturing design decisions, documenting system architecture, creating API references, or writing operational procedures.Votes: 0GitHub stars: 511
- Documentation That SlapsExpert in writing documentation that developers actually read. Covers README craft, API docs, tutorials, and internal docs. Understands that docs are a product—they need UX, marketing, and user empathy. Use when "documentation, readme, write docs, api docs, tutorial, how to document, explain this, " mentioned.Votes: 0GitHub stars: 137
- Diataxis WritingDiataxis documentation framework practice guide. Provides diagnosis, classification, templates, and quality assessment for four documentation types (Tutorial/How-to/Reference/Explanation).Votes: 0GitHub stars: 14
- DocumentAfter implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.Votes: 0GitHub stars: 150