Prompt file imported from ProsperousHeart/Basics-Boot-Camp (.github/prompts/create-architecture-diagram.prompt.md). Copyright stays with the author.

Prompt: Create Architecture Diagram

Name: create-architecture-diagram
Author: ProsperousHeart

Purpose: Generate architecture diagram using Mermaid Input: Requirement or specification document path Output: Architecture diagram in docs/diagrams/ References:

.github/instructions/architecture-diagrams.instructions.md
Relevant CodeGuard instruction files

Prompt

Create an architecture diagram for {document_path}.

Instructions:
1. Read the requirement or specification document
2. Follow guidance in .github/instructions/architecture-diagrams.instructions.md
3. Create appropriate Mermaid diagrams:
   - System architecture (component interactions)
   - Sequence diagrams (if workflow-heavy)
   - ERD diagrams (if database-intensive)
   - Component diagrams (if modular architecture)
4. Include:
   - Component descriptions
   - Technology choices
   - Security annotations (trust boundaries, encryption, auth points)
   - References to relevant CodeGuard files
5. Save to docs/diagrams/ with appropriate prefix:
   - architecture-{name}.md
   - sequence-{name}.md
   - erd-{name}.md
   - component-{name}.md
6. Optionally create separate .mmd file if requested
7. Update docs/SPEC-CROSS-REFERENCE.md
8. Log execution details to docs/output-logs/{timestamp}-architecture-diagram.md

Note: When updating existing diagrams, create a new version file rather than editing the original.

Example Usage

With Claude Code

Use the create-architecture-diagram prompt for docs/specifications/spec_api.md

With GitHub Copilot

@workspace Create architecture diagram for @docs/specifications/spec_api.md using Mermaid following @.github/instructions/architecture-diagrams.instructions.md

Expected Output

Architecture diagram: docs/diagrams/architecture_{name}.md
Optional: docs/diagrams/architecture_{name}.mmd
Updated: docs/SPEC-CROSS-REFERENCE.md
Log: docs/output-logs/{timestamp}-architecture-diagram.md

TODO: Add complete architecture diagram example

# Prompt: Create Architecture Diagram **Purpose**: Generate architecture diagram using Mermaid **Input**: Requirement or specification document path **Output**: Architecture diagram in `docs/diagrams/` **References**: - `.github/instructions/architecture-diagrams.instructions.md` - Relevant CodeGuard instruction files ## Prompt ``` Create an architecture diagram for {document_path}. Instructions: 1. Read the requirement or specification document 2. Follow guidance in .github/instructions/architecture-diagrams.instructions.md 3. Create appropriate Mermaid diagrams: - System architecture (component interactions) - Sequence diagrams (if workflow-heavy) - ERD diagrams (if database-intensive) - Component diagrams (if modular architecture) 4. Include: - Component descriptions - Technology choices - Security annotations (trust boundaries, encryption, auth points) - References to relevant CodeGuard files 5. Save to docs/diagrams/ with appropriate prefix: - architecture-{name}.md - sequence-{name}.md - erd-{name}.md - component-{name}.md 6. Optionally create separate .mmd file if requested 7. Update docs/SPEC-CROSS-REFERENCE.md 8. Log execution details to docs/output-logs/{timestamp}-architecture-diagram.md Note: When updating existing diagrams, create a new version file rather than editing the original. ``` ## Example Usage ### With Claude Code ``` Use the create-architecture-diagram prompt for docs/specifications/spec_api.md ``` ### With GitHub Copilot ``` @workspace Create architecture diagram for @docs/specifications/spec_api.md using Mermaid following @.github/instructions/architecture-diagrams.instructions.md ``` ## Expected Output - Architecture diagram: `docs/diagrams/architecture_{name}.md` - Optional: `docs/diagrams/architecture_{name}.mmd` - Updated: `docs/SPEC-CROSS-REFERENCE.md` - Log: `docs/output-logs/{timestamp}-architecture-diagram.md` **TODO**: Add complete architecture diagram example

{ "prompt": "# Prompt: Create Architecture Diagram\n\n**Purpose**: Generate architecture diagram using Mermaid\n**Input**: Requirement or specification document path\n**Output**: Architecture diagram in `docs/diagrams/`\n**References**:\n- `.github/instructions/architecture-diagrams.instructions.md`\n- Relevant CodeGuard instruction files\n\n## Prompt\n\n```\nCreate an architecture diagram for {document_path}.\n\nInstructions:\n1. Read the requirement or specification document\n2. Follow guidance in .github/instructions/architecture-diagrams.instructions.md\n3. Create appropriate Mermaid diagrams:\n - System architecture (component interactions)\n - Sequence diagrams (if workflow-heavy)\n - ERD diagrams (if database-intensive)\n - Component diagrams (if modular architecture)\n4. Include:\n - Component descriptions\n - Technology choices\n - Security annotations (trust boundaries, encryption, auth points)\n - References to relevant CodeGuard files\n5. Save to docs/diagrams/ with appropriate prefix:\n - architecture-{name}.md\n - sequence-{name}.md\n - erd-{name}.md\n - component-{name}.md\n6. Optionally create separate .mmd file if requested\n7. Update docs/SPEC-CROSS-REFERENCE.md\n8. Log execution details to docs/output-logs/{timestamp}-architecture-diagram.md\n\nNote: When updating existing diagrams, create a new version file rather than editing the original.\n```\n\n## Example Usage\n\n### With Claude Code\n\n```\nUse the create-architecture-diagram prompt for docs/specifications/spec_api.md\n```\n\n### With GitHub Copilot\n\n```\n@workspace Create architecture diagram for @docs/specifications/spec_api.md using Mermaid following @.github/instructions/architecture-diagrams.instructions.md\n```\n\n## Expected Output\n\n- Architecture diagram: `docs/diagrams/architecture_{name}.md`\n- Optional: `docs/diagrams/architecture_{name}.mmd`\n- Updated: `docs/SPEC-CROSS-REFERENCE.md`\n- Log: `docs/output-logs/{timestamp}-architecture-diagram.md`\n\n**TODO**: Add complete architecture diagram example", "variables": [], "notes": "Instructions: 1. Read the requirement or specification document 2. Follow guidance in .github/instructions/architecture-diagrams.instructions.md 3. Create appropriate Mermaid diagrams: - System architecture (component interactions) - Sequence diagrams (if workflow-heavy) - ERD diagrams (if database-intensive) - Component diagrams (if modular architecture) 4. Include: - Component descriptions - Technology choices - Security annotations (trust boundaries, encryption, auth points) - References to relevant CodeGuard files 5. Save to docs/diagrams/ with appropriate prefix: - architecture-{name}.md - sequence-{name}.md - erd-{name}.md - component-{name}.md 6. Optionally create separate .mmd file if requested 7. Update docs/SPEC-CROSS-REFERENCE.md 8. Log execution details to docs/output-logs/{timestamp}-architecture-diagram.md", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/ProsperousHeart/Basics-Boot-Camp", "path": ".github/prompts/create-architecture-diagram.prompt.md", "ref": "4f544a1bd59ceb95e27d0c81274ba1bf46bfa763", "url": "https://github.com/ProsperousHeart/Basics-Boot-Camp/blob/4f544a1bd59ceb95e27d0c81274ba1bf46bfa763/.github/prompts/create-architecture-diagram.prompt.md", "key": "ProsperousHeart/Basics-Boot-Camp/.github/prompts/create-architecture-diagram.prompt.md" } } }

create-architecture-diagram

About

Prompt: Create Architecture Diagram

Prompt

Example Usage

With Claude Code

With GitHub Copilot

Expected Output

Use it

Manifest

Reviews