agentleFS
Sign inStart free
o2alexanderfedino2alexanderfedin/strategic-research-automation-template/.claude/skills/solution-architect/SKILL.md

solution-architect

Skill19 starsChanged 12 months agoMITView on GitHub

Designs system architecture, component specifications, and technical integration strategy. Use when: designing solutions, system architecture, technology stack, or integration approaches.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow industry best practices, consider trade-offs, document decisions with rationale.

    line 31
  2. Distinctive:

    Never combine multiple numbered items in one line

    line 56
  3. Distinctive:

    Use appropriate Mermaid diagram types:

    line 63
  4. Very specific:

    Always use double quotes: A["Label"] not A[Label]

    line 89
  5. Distinctive:

    Test diagram rendering in markdown preview before finalizing

    line 99

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Solution Architect Skill

Role

Design comprehensive system architecture and technical solution for strategic opportunities.

Design Areas

  1. System Architecture: High-level design, components, interfaces
  2. Technology Stack: Languages, frameworks, platforms, tools
  3. Component Specifications: Detailed specs for major components
  4. Integration Strategy: APIs, data flows, external systems
  5. Scalability & Performance: Growth planning, performance requirements
  6. Security Architecture: Authentication, authorization, data protection

Output Files (in temp/sprint-XX/03-architecture/)

  • system-architecture.md - Overall system design
  • component-specifications.md - Detailed component specs
  • technology-stack.md - Technology choices and rationale
  • integration-strategy.md - Integration approach
  • security-architecture.md - Security design
  • scalability-plan.md - Growth and performance

Design Principles

Follow industry best practices, consider trade-offs, document decisions with rationale.

Formatting Requirements

Proper List Syntax - CRITICAL

NEVER use inline manual numbering - it renders as dense paragraph text.

INCORRECT:

Key Architectural Decisions: 1. Item one 2. Item two 3. Item three

CORRECT:

**Key Architectural Decisions**:

1. **Item One**: Description here
2. **Item Two**: Description here
3. **Item Three**: Description here

Rules:

  • Blank line before list starts
  • One item per line with proper markdown syntax (1. or - )
  • Bold the item label for emphasis
  • Never combine multiple numbered items in one line

Visualization Standards

Always Use Mermaid

  • ALWAYS use Mermaid diagrams for all architecture visualizations
  • NEVER use ASCII art diagrams (unprofessional and hard to read)
  • Use appropriate Mermaid diagram types:
    • System architecture → graph TD (flowchart) or C4 diagram
    • Component relationships → classDiagram or graph LR
    • Data flows → flowchart or sequenceDiagram
    • State machines → stateDiagram-v2
    • Database schemas → erDiagram

Label Quoting - CRITICAL

ALWAYS quote all labels in Mermaid diagrams to prevent rendering failures.

INCORRECT (may fail):

graph TD
    A[API Gateway] --> B[Processing Engine]
    B --> C[Database]

CORRECT (always works):

graph TD
    A["API Gateway"] --> B["Processing Engine"]
    B --> C["Database"]
    C --> D["Cache Layer"]

Rules:

  1. Always use double quotes: A["Label"] not A[Label]
  2. Quote edge labels: -->|"Success"| not -->|Success|
  3. Quote even simple labels to ensure consistency
  4. Escape internal quotes: A["Label: \"quoted\""]

Why: Prevents parsing errors with special characters, spaces, reserved words, ensuring diagrams render in all viewers (GitHub, HTML, PDF).

Best Practices

  • Include diagrams in all architecture files for visual clarity
  • Mermaid renders beautifully in GitHub, VS Code, and most markdown viewers
  • Test diagram rendering in markdown preview before finalizing

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free