agentleFS
Sign inStart free
DongDuong2001DongDuong2001/pudo-code-system/skills/plan/architecture/SKILL.md

architecture-plan

Skill5 starsChanged 5 months agoMITView on GitHub

Planning scalable system designs and architectural patterns

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    When starting a greenfield project or conducting a major refactor.

    line 11
  2. Distinctive:

    When deciding between Monolith, Microservices, Serverless, or Event-Driven architectures.

    line 12
  3. Distinctive:

    When preparing risk assessments and scaling strategies.

    line 13
  4. Distinctive:

    Consider both synchronous (API) and asynchronous (Pub/Sub, Queues) communication paths.

    line 18
  5. Distinctive:

    Ensure data ownership is clear (which service owns which data).

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Architecture Planning Skill

This skill is pivotal during the PLAN phase for determining system boundaries, deployment topologies, and core technologies.

When to use this skill

  • When starting a greenfield project or conducting a major refactor.
  • When deciding between Monolith, Microservices, Serverless, or Event-Driven architectures.
  • When preparing risk assessments and scaling strategies.

Guidelines

  • Prioritize simplicity. Do not over-engineer for traffic that doesn't exist yet (YAGNI).
  • Map out clear domain boundaries (Domain-Driven Design) to ensure separation of concerns.
  • Consider both synchronous (API) and asynchronous (Pub/Sub, Queues) communication paths.
  • Ensure data ownership is clear (which service owns which data).

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