Menú
Generate a professional architecture diagram from codebase analysis
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Automatically implement all sub-issues of an epic in dependency order
Implement a GitHub issue with automated PR creation
End-of-session retrospective. Captures knowledge from any working session (debug, implementation, config, deployment) as reusable scripts, CLAUDE.md procedures, or skill proposals. Run before ending a session to prevent knowledge loss.
Decompose a large GitHub issue into sub-issues and create a tracking draft PR
OWASP-guided security code review for a specific domain or issue
Project kickoff checklist based on lessons learned from previous projects. Generates a tailored checklist and optionally creates GitHub issues.
| name | architecture-diagram |
| description | Generate a professional architecture diagram from codebase analysis |
| argument-hint | [output-path] [-- description] |
| user-invocable | true |
Generate a professional architecture diagram as a standalone HTML/SVG file by analyzing the current codebase.
Arguments via $ARGUMENTS:
architecture-diagram.html in project rootpath/to/output.html: custom output path-- description text: skip codebase analysis, use the provided description insteadpath/to/output.html -- description text: both custom path and descriptionSpawn the architecture-diagram agent with the following prompt, adapted based on arguments:
Analyze the codebase in the current working directory and generate an architecture diagram.
Output file: [resolved output path]
Follow your full Discovery → Generation workflow:
1. Explore the codebase to identify all components (frontend, backend, databases, infrastructure, external services)
2. Map relationships and data flows between components
3. Present the component inventory to the user and ask for confirmation
4. After confirmation, generate the HTML diagram file
5. Report the output file path
If docker-compose.yml or similar orchestration files exist, use them as the primary source of truth for services and their relationships.
Generate an architecture diagram from this description:
[user's description]
Output file: [resolved output path]
Skip codebase analysis. Parse the description to identify components and relationships, then:
1. Present the component inventory to the user and ask for confirmation
2. After confirmation, generate the HTML diagram file
3. Report the output file path
architecture-diagramReport the output path and suggest:
/architecture-diagram again with feedback to iterate