technical-docs
2
github-readme
Fetch the README content from a GitHub repository. Use when the user asks for a repository README, documentation, or wants to read the repo's main documentation file.
Mearman
documentation
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
technical-docs
2
go-dev
General Go development guide. Use when writing Go code, implementing best practices, formatting code, writing tests, using mocks, handling errors, or understanding Go coding conventions. Covers code style, testing patterns, dependency injection, interface design, and performance optimization. Project-agnostic guidelines applicable to any Go codebase.
MrPointer
documentation
technical-docs
2
reverse-engineering-documentation
Creating documentation from legacy code when none exists, focusing on what future maintainers need to know
spacholski1225
documentation
technical-docs
2
documentation
Creates concise, behavior-focused documentation for humans and AI. Use after feature implementation OR bug fixes to document HOW THE PRODUCT BEHAVES. NOT a changelog - documents current behavior, not change history.
buzzdan
documentation
technical-docs
2
create-step-guide-skill
Creates comprehensive implementation guides for individual steps from implementation plans, breaking down complex steps into granular tasks with clear acceptance criteria and developer context
shsrams
documentation
technical-docs
2
api-documentation
Use when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.
troykelly
documentation
technical-docs
2
crafting-effective-readmes
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
joshuadavidthomas
documentation
technical-docs
1
generate-constitution
Derive technical development principles FROM user needs in product.md using evidence-based reasoning. Creates constitution.md with architecture decisions, tech stack choices, and development constraints - all traced back to specific user needs. Use when user mentions "technical principles", "constitution", "architecture decisions", or after creating product.md.
yangsi7
documentation
technical-docs
1
example-standard-skill
This skill should be used when the user asks to "perform standard task", "follow best practices", "implement common pattern", or needs comprehensive guidance. Demonstrates recommended skill structure with progressive disclosure.
helmecke
documentation
technical-docs
1
architecture
Design technical architecture from a PRD. Use when user wants to create an architecture document, define system design, plan technical implementation, or needs to translate product requirements into buildable technical specs. Reads from docs/PRD.md and outputs docs/ARCHITECTURE.md.
Porkbutts
documentation
technical-docs
1
documentation-standards
This skill should be used when the user asks to "write documentation", "create docs", "document code", "improve documentation", "documentation best practices", "diataxis", "technical writing", "API documentation", "user guide", mentions documentation quality, documentation structure, or needs guidance on software documentation standards and frameworks.
hculap
documentation
technical-docs
1
writing-plans
Create comprehensive implementation plans with bite-sized tasks. Use after brainstorming produces a design, before touching code. Documents exact files, complete code, commands, expected output.
geobrowser
documentation
technical-docs
1
doc-coauthoring
Structured workflow for co-authoring documentation, PRDs, technical specs, and decision docs. Use when writing substantial documentation, creating proposals, drafting specifications, or any structured content that benefits from iterative refinement. Provides context gathering, section-by-section building, and reader testing.
5dlabs
documentation
technical-docs
1
game-design-doc-creator
Create design documents for Stapledons Voyage game features. Use when user asks to create a design doc, plan a feature, or document game mechanics. Handles both planned/ and implemented/ docs.
sunholo-data
documentation
technical-docs
1
diataxis
Create and evaluate documentation using the Diátaxis framework. Use when writing, organizing, or auditing documentation to ensure it serves distinct user needs through four systematic categories (Tutorials, How-to Guides, Reference, Explanation). Ideal for diagnosing documentation problems, separating mixed content, and ensuring each piece serves a single, clear purpose.
arisng
documentation
technical-docs
1
meta-sdk-patterns-eng
Foundational SDK development patterns that domain-specific SDK skills extend. Use when building SDKs for APIs or specifications, creating SDK development skills, or establishing SDK architecture standards across languages.
aRustyDev
documentation
technical-docs
1
zenn-article-writer
Write technical articles for Zenn in Oikon's distinctive writing style. This skill should be used when creating articles about AI tools, development workflows, tool integrations, updates/new features, or technical reports. The skill provides detailed writing guidelines, article structure patterns, and reference materials based on Oikon's existing articles.
oikon48
documentation
technical-docs
1
chouzz-blog-writer
Personalized blog writing assistant for chouzz. Helps transform technical practice snippets into well-structured, progressive blog posts suitable for Medium, Zhihu, and similar platforms. Triggers when chouzz provides code snippets, practice records, or technical notes and wants to organize them into a blog post. Core workflow: (1) Understand source material and extract key information, (2) Interact to determine outline and style, (3) Expand each section incrementally with user feedback, (4) Organize code presentation and prompt for screenshot placements, (5) Check for typos and formatting consistency.
chouzz
documentation
technical-docs
1
writing-technical-docs
Guides technical documentation and report writing. Applies the 7 Cs principle (Clear, Concise, Correct, Coherent, Concrete, Complete, Courteous). Use for writing technical documents, reports, and code comments.
sumik5
documentation
technical-docs
1
diataxis-documentation
Write comprehensive, user-focused documentation following the Diataxis framework. Use this skill when creating or improving tutorials, how-to guides, reference documentation, or explanatory content. Helps identify the right documentation type and apply best practices for each.
abatilo
documentation
technical-docs
1
thematic-doc-generator
Generate comprehensive, publication-quality technical manuals with thematic storytelling using multi-agent orchestration. Use when user asks for themed documentation, narrative technical guides, memorable training materials, or mentions themes like Victorian, steampunk, art deco, medieval, pharmaceutical, or nautical combined with technical topics. Triggers on phrases like "create themed manual", "documentation with storytelling", or requests to make docs "more engaging" or "memorable".
delorenj
documentation