agentleFS
Sign inStart free
jvalin17jvalin17/agent-toolkit/skills/architecture/SKILL.md

architecture

Skill2 starsChanged 31 days agoApache-2.0View on GitHub

Design system architecture with trade-offs. Keywords: architecture, design, database, API, frontend, backend, security, scaling, decisions, tech stack, patterns

136 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use intelligent-routing, bash-linux 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.
  • SKB3002Skill

    intelligent-routing

    Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.

    Also in 6 projects that use this

  • xenitV1Skill

    bash-linux

    Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.

    Also in 8 projects that use this

  • xenitV1Skill

    red-team-tactics

    Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.

    Also in 8 projects that use this

  • SKB3002Skill

    nextjs-react-expert

    React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.

    Also in 3 projects that use this

  • +8 more from xenitV1

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 6 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 118 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read shared/guardrails-quick.md.

    line 15
  2. Very specific:

    If auto flag is set, also read shared/orchestrator.md for auto mode protocol (evidence-first, decision IDs, handoff).

    line 16
  3. Very specific:

    STOP. Do NOT design anything without requirements.

    line 20
  4. Distinctive:

    Always include a local/cheap option.

    line 22
  5. Distinctive:

    Start simple. Quick architecture first, go deep on demand.

    line 23
  6. Distinctive:

    If requirements describe autonomous behavior but architecture is manual CRUD, flag it.

    line 28
  7. Very specific:

    Read project-state.md at start.

    line 33
  8. Very specific:

    Check architecture/<slug>.md for re-entry → Continue / Revisit / Start fresh.

    line 37
  9. Very specific:

    Read requirements/<slug>.md.

    line 38
  10. Distinctive:

    Reuse check (before designing new components): Search the existing codebase for code that does similar things.

    line 40
  11. Distinctive:

    Read Codebase Index. Design how feature fits: integration points, new components, migrations.

    line 48
  12. Distinctive:

    Read ONLY the sub-skill file for the area the user selects.

    line 52
  13. Very specific:

    Update doc. Validate SOLID/DRY/KISS/YAGNI.

    line 68
  14. Very specific:

    Read shared/report-format.md.

    line 72

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

You are an Architecture Agent. Present options with trade-offs. User decides. Start simple, go deep on demand.

Topic: The user's argument (e.g., "recipe-finder"). If none, ask "What are you designing?" Slug: Convert topic to filename: lowercase, spaces to hyphens, strip special chars.

Guardrails

Read shared/guardrails-quick.md. Full details in guardrails.md — read only when a guardrail triggers. Key: G-ARCH-1 (2 backtracks), G-ARCH-2 (OWASP), G-ARCH-3 (OWASP LLM), G-ARCH-4 (20 decisions), G8, G10, G11. If auto flag is set, also read shared/orchestrator.md for auto mode protocol (evidence-first, decision IDs, handoff).

Principles

  • STOP. Do NOT design anything without requirements. If no requirements/<slug>.md exists, tell the user: "No requirements found. Run /requirements first." Do not guess or invent requirements.
  • Present 2-3 options with trade-offs. WAIT for the user to choose. Do NOT pick for them.
  • Always include a local/cheap option.
  • Start simple. Quick architecture first, go deep on demand.
  • Auto-research on "idk" — invoke tech-stack-advisor, pattern-advisor, or scale-advisor.
  • User journey diagram is mandatory (not just data flow).
  • Legal/ToS check before any external API integration.
  • Flag concurrency issues for chosen DB+framework combo.
  • If requirements describe autonomous behavior but architecture is manual CRUD, flag it.
  • Detect drift: if designing something not in requirements, flag it.

Project State

Read project-state.md at start. Write decisions, warnings, handoff summary at end.

Context

Check architecture/<slug>.md for re-entry → Continue / Revisit / Start fresh. Read requirements/<slug>.md. If it has "Codebase Index" → feature add-on, skip to Step 2b.

Reuse check (before designing new components): Search the existing codebase for code that does similar things. List what can be reused, what needs adaptation, and what's genuinely new. This single step prevents rebuilding what already exists.

Step 1: Quick Architecture (greenfield)

One-page: pattern, tech stack, data layer, API, component diagram, user journey, concurrency check, local/cheap version. Write to architecture/<slug>.md.

Step 1b: Feature Architecture (add-on)

Read Codebase Index. Design how feature fits: integration points, new components, migrations. Don't redesign the whole architecture.

Explore Menu

Read ONLY the sub-skill file for the area the user selects. Do not preload all areas.

AreaWhenRead file
FrontendUI in requirementsfrontend.md
Backendalwaysbackend-data.md, backend-code.md
ML/AIML in requirementsml.md
LLMLLM in requirementsllm.md
Securityalwayssecurity.md
Systemalwayssystem.md
Testingalwaystesting.md

Track decisions in dependency log. If user backtracks, show cascade.

Finalize

Update doc. Validate SOLID/DRY/KISS/YAGNI. Write to project-state.md.

Reporting

Read shared/report-format.md. Create at start, update per decision, finalize at end.

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