recipe-reverse-engineer
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow
Verify and update documentation examples to match a component's current public API
Guidelines for creating and editing Umbraco documentation content. Use when writing new articles, editing existing docs, or making structural changes (adding, moving, renaming, deleting articles). Covers style guide, markdown conventions, code samples, images, SUMMARY.md entries, and .gitbook.yaml redirects.
Guides writing clear, well-structured technical documentation following Mintlify's best practices (Diátaxis framework, audience awareness, style/tone, navigation, SEO/AEO). Use when writing, reviewing, or improving documentation, guides, tutorials, API references, or any user-facing technical content.
Fetch source code for npm, PyPI, or crates.io packages and GitHub/GitLab repos to provide AI agents with implementation context beyond types and docs. Use when needing to understand how a library works internally, debug dependency issues, or explore package implementations.
Add or modify Dokan backend PHP code following project conventions. Use when creating new classes, methods, hooks, REST controllers, or modifying existing backend code. Invoke before writing PHP unit tests.
Backend conventions for NestJS projects: modules, controllers, services, DTOs, migrations, structure. Use when implementing or reviewing code in NestJS backends.
Syncs MCP Apps documentation with the @apollo/client-ai-apps changelog. Always use this skill whenever: (1) the user wants to update or sync the mcp-apps-*.mdx docs based on a new release or version range, (2) phrases like "sync docs from version X", "update docs from changelog", "what changed since v0.x.x", "docs are out of date", or "check the changelog" appear in context of MCP Apps documentation, (3) checking whether mcp-apps-*.mdx files reflect recent releases. The changelog URL and doc file paths are pre-configured — the user only needs to provide the minimum version to sync from.
Guides creation of UI/UX designs, interactive prototypes, reusable components, and design specs in Adobe XD. Use when the user asks about Adobe XD artboards, prototype links, repeat grids, component states, design tokens export, or developer handoff.
Generates structured technical documentation including API docs (OpenAPI/Swagger), README files, user guides, developer guides, and changelogs. Use when the user needs to create or improve project documentation, generate API reference docs, write onboarding guides, or structure documentation for a codebase.
Adds JavaDoc comments to Java code following industry standards. Covers class-level, method-level, and field-level comments for Controller, Service, ServiceImpl, Mapper, Entity, BO, DTO, VO, and other component types. Use when the user wants to add comments to Java code, generate JavaDoc documentation, or systematically document a Java codebase.
Provides comprehensive guidance for Docker including container creation, images, Dockerfile, docker-compose, and container management. Use when the user asks about Docker, needs to create Docker containers, build Docker images, or manage containerized applications.
Generate API documentation by scanning Controller classes, extracting endpoint URLs, HTTP methods, parameters, and response structures, then producing standardized docs from templates. Use when the user explicitly mentions generating API documentation, creating API docs, scanning interfaces, or documenting REST APIs. Do not trigger for generic documentation requests without explicit API mention.
Guide users through a structured three-stage workflow for co-authoring documentation: context gathering, iterative refinement, and reader testing. Use when the user wants to write documentation, proposals, technical specs, decision docs, PRDs, or RFCs. Trigger when user mentions writing docs, creating proposals, drafting specs, or collaborative document creation.
Open or create a design document. Use when you need to initialize design tasks, create new files, or switch to specific designs.
Generate a technology-agnostic feature specification by analyzing existing source code, extracting user stories, functional requirements, and acceptance criteria from code patterns. Use when the user needs to document an existing or legacy codebase, create a spec before refactoring, or reverse-engineer requirements from source files.
Generate a technical implementation plan from a feature spec by filling the plan template, resolving unknowns via research, producing data-model.md, API contracts, and quickstart.md artifacts. Use when the feature spec is ready and the user needs architecture decisions, data models, API schemas, or a structured plan before task generation.
Guides uni-app mini program development including configuration, component usage, API compatibility, and conditional compilation for WeChat, Alipay, Baidu, and other mini program platforms. Use when the user wants to build uni-app mini programs, configure mini program settings, or handle platform-specific differences.