specification-driven-development
This skill should be used when the user asks about "spec methodology", "specification workflow", "spec-driven development", "how to write specs", "spec best practices", "specification templates", or needs guida...
Découvrez les skills blockchain technical docs, comparez leurs dépôts et consultez leurs instructions.
This skill should be used when the user asks about "spec methodology", "specification workflow", "spec-driven development", "how to write specs", "spec best practices", "specification templates", or needs guida...
API design patterns and REST conventions. Use for any API work - endpoint design, response formats, error handling, pagination, status codes. Contains learned preferences for Laravel and Next.js API patterns.
Express API conventions and storage patterns. Use when building REST APIs, defining routes, or implementing storage interfaces. Triggers on: Express, router, API route, status code, storage interface.
Generates app_spec.txt specification files from codebases. Use when you need to create specification documents, analyze code structure, document project architecture, or generate comprehensive project overviews...
Explain code in plain English with visual diagrams. Use when user wants to understand how code works or needs documentation.
Use this skill at the end of a task to ensure documentation matches the code.
Use when looking up information from the latest Docusaurus documentation at https://docusaurus.io/docs
Generate markdown explanation for a LeetCode solution (project)
チーム全体で統一された開発プロセスとコーディング規約を確立するための包括的なガイドとテンプレート。開発ガイドライン作成時、コード実装時に使用する。
Write detailed product and technical specification documents for OrbitCove. Use when creating PRDs, architecture docs, data models, or UX flows.
Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Doc...
Guide for writing Rust code covering ownership, borrowing, lifetimes, error handling, async programming, and Rust best practices
Generate hierarchical code maps from any codebase for AI agent consumption. Use when: (1) Analyzing or understanding a codebase structure, (2) Creating documentation of code architecture, (3) Mapping dependenci...
文档生成技能:提供标准化的文档编写工作流和模板。 Use when: 需要编写组件文档、API 文档、模块 README、项目文档。 Triggers: "文档", "documentation", "README", "API 文档", "组件文档", "注释"
Follow API development conventions including RESTful design, Fastify patterns, Zod validation, error handling, and versioning. Use when building API endpoints, adding routes, or working with API code.
Your approach to handling readme. Use this skill when working on files where readme comes into play.
Every code need inline doc comments.
Manage and query the documentation dependency index. Use this to identify which documents need to be updated when code changes.
Consulta la documentación oficial de MakerKit (next-supabase-turbo) bajo demanda. Usa cuando necesites información sobre patrones, configuración o APIs de MakerKit que no esté en el código local. Incluye índice...
Access official collaboration platform documentation organized by platform components, protocols, and core competencies. Use when user asks about platform capabilities, how the framework works, or when Claude C...
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow help...
文档页面组件规范。Use when creating documentation pages or editing files in **/docs/** directory. Triggers on: creating docs pages, DocsSection, DocsPageLayout usage.
This skill orchestrates comprehensive documentation intelligence operations. Use when asked to "analyze documentation", "learn from docs", "create SOPs from documentation", "maximize documentation understanding...
Generate OpenAPI specs and API documentation from code. Triggers: document API, generate OpenAPI, create API docs, swagger spec, GraphQL schema, API specification, document endpoints
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.