Loading...
Loading...
Found 2,113 Skills
Generate API documentation from OpenAPI specs or code.
Agent-first project documentation. Scaffolds and maintains a documentation architecture designed for AI agents — ROADMAP, design-docs, logs, and more. Use when the user says "/docs", asks to set up project documentation, wants to update docs, or when starting a new project that lacks documentation structure. Also use when the user asks to plan a feature (creates a design doc) or review what's been done (updates logs/roadmap).
OpenAPI documentation skill for Rust APIs using utoipa with Axum framework. Use when building REST APIs with automatic OpenAPI spec generation and Scalar UI. Covers: (1) ToSchema derive for request/response types, (2) #[utoipa::path] for endpoint documentation, (3) OpenApi derive for combining specs, (4) Security schemes (JWT, API keys), (5) IntoParams for query/path params, (6) Scalar UI integration, (7) Response and error handling patterns. Triggers: utoipa, openapi, scalar, axum api, ToSchema, IntoParams, rust api docs.
OpenAPI/Swagger specification standards and API documentation best practices
Creates pull requests with bilingual documentation updates. Use when user asks to create PR, make a pull request, or submit changes for review. Automatically updates both English and Chinese README files.
Drizzle ORM documentation covering queries, CRUD operations, schema definitions, migrations, caching (50 topics), custom types, and database connections. Includes integrations for PostgreSQL (Neon, Vercel, Supabase, AWS Data API, PlanetScale, Prisma), MySQL (AWS Data API, PlanetScale, TiDB), and SQLite (Bun, Cloudflare D1/Durable Objects, Expo, Turso, OP SQLite). Use when working with Drizzle queries, database schemas, migrations, type-safe SQL, ORM patterns, or connecting to supported databases.
Find and remove dead code and stale documentation. Covers unused functions, orphaned files, dead links, and outdated references. Use for maintenance, pre-release cleanup, or codebase hygiene. Triggers: clean, dead code, unused, orphan, stale, cruft, maintenance.
Use Case 2.0 methodology by Ivar Jacobson. Covers use case slices, lightweight documentation, user story derivation, and value-driven prioritization. Modern approach to use case modeling for agile teams.
Create structured documents from conversations, summaries, or content in open formats (markdown, PDF, text). Use when the user requests document creation, report generation, content export, conversation summaries, or structured documentation. Triggers include "create a document", "make a report", "summarize this conversation", "export to PDF/markdown", or any request to formalize content into a document. Works independently or integrates with design-assistant skill for polished visual output.
A skill is documentation that learned to do things.
Professional documentation writing skills. Used for creating technical documents, READMEs, API documents, user manuals, etc. This skill is applied when users need to write or improve documents.
Standards and guidelines for organizing, structuring, and maintaining documentation in the PRPM repository - ensures consistency across user docs, development docs, and internal references