agentleFS
Sign inStart free
PURPLE-ORCAPURPLE-ORCA/skills/pragmatic-architecture/SKILL.md

pragmatic-architecture

Skill2 starsChanged 5 months agoMITView on GitHub

The master architectural gatekeeper. Enforces Vertical Slices, Hexagonal boundaries, and CQRS Lite. Use whenever structuring a new feature, planning a refactor, or deciding where code belongs. Triggers on "new feature", "architecture", "refactor", "how should I structure", or "where do I put this". MUST use this skill before writing feature code.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. ITS-MSW/skills★ 2100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    If you build monolithic horizontal layers or tightly couple external infrastructure to the core logic, the system will fail.

    line 11
  2. Distinctive:

    Before scaffolding any feature, identify the architectural requirement and strictly adhere to its corresponding module:

    line 15
  3. Distinctive:

    Copying is Better Than the Wrong Abstraction: Do not extract "shared" logic into a global helper folder until at least three separate …

    line 29
  4. Distinctive:

    No Anemic Data: Do not pass generic associative arrays between architectural layers.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Pragmatic Architecture Guide

You are an expert software architect. Before you write a single line of framework-specific code, you must enforce these high-level structural invariants.

If you build monolithic horizontal layers or tightly couple external infrastructure to the core logic, the system will fail.

Architectural Directives (Mandatory Reading)

Before scaffolding any feature, identify the architectural requirement and strictly adhere to its corresponding module:

  1. Feature Structuring & Folder Layout: → READ references/vertical-slice.md (Bans global Controllers/ and Services/ folders. Mandates grouping all related files into a single feature folder).
  2. External API & Third-Party Integrations: → READ references/hexagonal-boundaries.md (Bans direct HTTP calls inside business logic. Mandates defining Interfaces/Ports in the core and pushing third-party SDKs into Adapters).
  3. Complex Dashboards & Data Pipelines: → READ references/cqrs-lite.md (Bans using ORMs for heavy analytical reads. Enforces strict separation between Read queries and Write commands).

The 3 Golden Rules of Execution

  1. No Dogma: Do not over-engineer simple CRUD. If an operation is just taking a name and saving it to a database, don't build a 5-layer Hexagonal abstraction. Use the framework's native tools. Save the heavy architecture for external boundaries (Payments, CRMs) and complex features.
  2. Copying is Better Than the Wrong Abstraction: Do not extract "shared" logic into a global helper folder until at least three separate features require it.
  3. No Anemic Data: Do not pass generic associative arrays between architectural layers. Data must be typed using DTOs, Zod schemas, or native language structs at the boundary.

Acknowledge and apply these structures before querying the framework-specific skills (modern-laravel, modern-nextjs, nextjs-core, etc.).

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