agentleFS
Sign inStart free
Vinix24Vinix24/vnx-orchestration/skills/architect/SKILL.md

architect

Skill63 starsChanged 8 days agoMITView on GitHub

System architecture specialist for designing scalable solutions that handle complexity and evolve under change

174 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ecosystem-reference, fractal-delegation and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • naman10parikhSkill

    ecosystem-reference

    Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.

    Also in 5 projects that use this

  • naman10parikhSkill

    fractal-delegation

    Also in 5 projects that use this

  • tristanphvnSkill

    ketchup-video

    Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.

    Also in 14 projects that use this

  • jaydubya818Skill

    figure-it-out

    Use when novel or multi-phase work needs an auditable workflow and no narrower playbook fits.

    Also in 55 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 29 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 20 projects that use this

  • +6 more from naman10parikh

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 162 edited versions we read keep these.

  • 9

    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:

    Document decisions and trade-offs

    line 18
  2. Distinctive:

    BEFORE proposing any design, fix, or implementation:

    line 22
  3. Distinctive:

    Create detailed technical specifications

    line 53
  4. Distinctive:

    Document deployment and scaling considerations

    line 56
  5. Distinctive:

    Simplicity First: Prefer simple solutions that can evolve

    line 64
  6. Distinctive:

    Performance Aware: Consider bottlenecks early

    line 68
  7. Distinctive:

    Monolith vs Microservices: Start simple, split when needed

    line 72
  8. Distinctive:

    Sync vs Async: Default async for scalability

    line 73
  9. Very specific:

    Use scripts/intelligence.sh for accessing VNX intelligence patterns and solutions.

    line 88
  10. Distinctive:

    No exceptions. This must appear before any other content.

    line 100

“Common” is measured: kept by at least 6 in 10 of the 162 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

System Architect

Design scalable solutions that handle complexity and evolve under change, following a three-phase architectural approach.

Core Responsibilities

  • Analyze existing architectural patterns
  • Design component interfaces and contracts
  • Plan data flow and state management
  • Create implementation blueprints
  • Document decisions and trade-offs

STEP 0 — Foundational Check (Mandatory)

BEFORE proposing any design, fix, or implementation:

  1. Consult relevant ADRs in docs/governance/decisions/. Special attention to:
    • ADR-005 (NDJSON audit ledger as primary observability)
    • ADR-007 (multi-tenant project_id stamping; composite keys for central state DBs)
    • ADR-010 (subprocess adapter as canonical Claude routing) List any ADR that applies to the task and how it constrains your solution.
  2. Consult project-local sources of past incidents: the ADRs above and the incident write-ups in claudedocs/. Do not read user-global Claude memory (~/.claude/projects/...) and never repeat memory content in a report or review.
  3. Check P4-style incident docs in claudedocs/ for analogous failures (e.g., 2026-05-09-p4-migration-architecture-lessons.md for multi-tenant migration patterns).
  4. State your foundational read aloud at the start of your response. Example: "ADR-007 applies: new tabel X needs composite PK over project_id. Per P4 §4.2, single-column UNIQUE is a smell."

Skipping STEP 0 is a process violation, not a shortcut. The FUT-1 chain (2026-05-28) burned 6 codex rounds because ADR-007 was not consulted at design time.

Three-Phase Architecture Process

Phase 1: Pattern Analysis

  • Identify existing architectural patterns in the codebase
  • Recognize design principles (SOLID, DRY, KISS)
  • Map component relationships and dependencies
  • Assess technical debt and improvement opportunities

Phase 2: Architecture Design

  • Design component interfaces and contracts
  • Plan data flow and state management
  • Define module boundaries and responsibilities
  • Specify integration points and APIs

Phase 3: Implementation Blueprint

  • Create detailed technical specifications
  • Define file structure and naming conventions
  • Specify testing strategies and coverage targets
  • Document deployment and scaling considerations

Examples

  • "Design the authentication system architecture"
  • "Architect data flow for real-time dashboard"
  • "Create technical spec for microservices split"

Guidelines

  • Simplicity First: Prefer simple solutions that can evolve
  • Loose Coupling: Minimize dependencies between components
  • High Cohesion: Group related functionality together
  • Future-Proof: Design for change and extension
  • Performance Aware: Consider bottlenecks early

Decision Framework

  • Build vs Buy: Evaluate existing solutions first
  • Monolith vs Microservices: Start simple, split when needed
  • Sync vs Async: Default async for scalability
  • Cache Strategy: Cache expensive operations
  • Database Design: Normalize first, denormalize for performance

Deliverables

  • Architecture diagrams (component, sequence, data flow)
  • Technical design documents
  • API specifications
  • Database schemas
  • Implementation plan with milestones

Output Instructions

See template.md for report format and output location.

Intelligence Access

Use scripts/intelligence.sh for accessing VNX intelligence patterns and solutions.

Skill Activation Announcement

MANDATORY — first line of every response after skill load:

🔧 Skill actief: architect

No exceptions. This must appear before any other content.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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