Back to catalog
Human reviewedDevelopment

Skill dossier

architecture-designer

Source declaration

Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.

The author's original description, preserved in English. It describes intent, not verified performance.

Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

Helps with high-level system design and architecture review, producing requirements summaries, Mermaid diagrams and Architecture Decision Records with explicit trade-offs.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Gathers functional, non-functional and constraint requirements and checks coverage.
  • Matches requirements to architectural patterns using reference files.
  • Produces an architecture diagram, with Mermaid preferred.
  • Writes ADRs for key decisions and returns to design if stakeholder review fails.

Limitations & scope

  • Stakeholder review is a human step the skill can only prompt for, not perform.
  • Distinct from code-level design patterns and database-only design, which it explicitly excludes.
  • Recommendations are not validated against real load or cost data.

Relevant for

  • Architects and tech leads
  • Teams documenting decisions as ADRs
  • Engineers comparing monolith and microservice options

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
20.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/architecture-designer/references/adr-template.mdReference2.7 KB
skills/architecture-designer/references/architecture-patterns.mdReference4.5 KB
skills/architecture-designer/references/database-selection.mdReference2.5 KB
skills/architecture-designer/references/nfr-checklist.mdReference3 KB
skills/architecture-designer/references/system-design.mdReference2.9 KB
skills/architecture-designer/SKILL.mdInstruction4.8 KB

SKILL.md frontmatter

{
  "name": "architecture-designer",
  "description": "Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.1",
    "domain": "api-architecture",
    "triggers": "architecture, system design, design pattern, microservices, scalability, ADR, technical design, infrastructure",
    "role": "expert",
    "scope": "design",
    "output-format": "document",
    "related-skills": "fullstack-guardian, devops-engineer, secure-code-guardian, microservices-architect, code-reviewer"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Understand requirements

    Gather functional, non-functional and constraint requirements and verify full coverage.

  2. 02
    Action

    Design with trade-offs

    Create the architecture with trade-offs explicitly documented and produce a diagram.

  3. 03
    Decision

    Review with stakeholders

    If review fails, return to the design step with recorded feedback.

  4. 04
    Output

    Deliver design package

    Provide the requirements summary, diagram, key decisions, technology rationale and risks.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

20 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

5 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 5 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

15 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 15 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Confirm that the security considerations it lists are reviewed by someone qualified, as the skill only reminds you not to skip them.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/architecture-designer # .claude/skills/architecture-designer
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/architecture-designer/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Install the skill into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Confirm architecture-designer/SKILL.md exists at the destination, then ask Claude Code to use the architecture-designer skill on a small test task.

Prerequisites

  • Stakeholder review is a human step the skill can only prompt for, not perform.
  • Distinct from code-level design patterns and database-only design, which it explicitly excludes.
  • Recommendations are not validated against real load or cost data.

Example prompts

Representative task

Use the architecture-designer skill to propose an architecture for an order-processing platform with an API gateway, auth and notification services, include a Mermaid diagram and ADR-001 for the datastore choice.

Inspect before use

Read the architecture-designer skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/architecture-designer/SKILL.md and its referenced files. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Requires trade-offs, failure modes and operational cost to be considered, not only benefits.
  • Provides concrete Mermaid and ADR templates.

Considerations

  • The persona claims 15+ years of experience, which is role framing rather than a capability.
  • Output quality depends on how complete the supplied requirements are.
Research conclusion

A disciplined template for architecture documentation, useful when the real constraints are provided up front.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/architecture-designer
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.