agentleFS
Sign inStart free
Data-WiseData-Wise/craft/skills/architecture/SKILL.md

system-architect

Skill4 starsChanged 12 days agoMITView on GitHub

This skill should be used when the user asks to "design a system", "architect a solution", "review architecture", "plan a refactoring", "evaluate technical trade-offs", or discusses software architecture patterns. Provides expert guidance on system design, architecture patterns, and technical decision-making.

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use database-architect, webapp-testing and 3 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.
  • xfstudioSkill

    database-architect

    Expert database architect specializing in data layer design from

    Also in 3 projects that use this

  • JetBrainsSkill

    webapp-testing

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    Also in 4 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 5 projects that use this

  • MicrosoftSkill

    mcp-builder

    Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 12

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

Expert in software architecture, system design, and technical decision-making.

When to Use

Use this skill when:

  • Designing new systems or features
  • Making architectural decisions
  • Reviewing architecture changes
  • Planning refactoring or migrations
  • Evaluating technical trade-offs

Capabilities

Architecture Patterns

  • Microservices vs monolith decisions
  • Event-driven architecture
  • Domain-driven design (DDD)
  • Clean/hexagonal architecture
  • CQRS and event sourcing

System Design

  • Scalability planning
  • Performance optimization
  • Security architecture
  • Data modeling
  • API design

Technical Leadership

  • Technology selection
  • Build vs buy decisions
  • Technical debt management
  • Migration strategies
  • Documentation standards

Pattern Recognition

  • Anti-pattern detection
  • Coupling/cohesion analysis
  • SOLID principle application
  • Design pattern recommendations

Example Prompts

"Design a scalable architecture for a real-time chat application"
"Should we use microservices or stay with our monolith?"
"Review this architecture for potential bottlenecks"
"How do I refactor this tightly coupled code?"
"What's the best pattern for handling async operations here?"

Outputs

  • Architecture diagrams (Mermaid)
  • Design documents
  • Trade-off analyses
  • Implementation recommendations
  • Migration plans

Integration

Works with:

  • /craft:arch:analyze - Codebase analysis
  • /craft:arch:plan - Architecture planning
  • /craft:arch:review - Architecture review
  • /craft:arch:diagram - Diagram generation

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