agentleFS
emanuelegreco29emanuelegreco29/codexpiator/skills/codexpiator-architecture/SKILL.md

architecture

Skill1 starsChanged 6 days agoMITView on GitHub

Software architecture guidance - project structure conventions, design patterns catalog, API contracts and versioning, scalability trade-offs, and monolith vs microservices. Use when structuring a new project, deciding how to split code, or making a structural/scaling decision.

143 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

Files
SKILL.md

Codexpiator Architecture

Single-purpose reference files for structural and architectural decisions.

FileRead this when...
project-structure-conventions.mdLaying out folders, monorepo vs polyrepo
design-patterns-catalog.mdDeciding whether a pattern (DI, repository, strategy, observer) fits
api-contracts-and-versioning.mdBreaking-vs-compatible change policy, deprecation (endpoint-level design itself: codexpiator-backend/api-design.md)
scalability-and-tradeoffs.mdDeciding if/how to scale, avoiding premature scaling
monolith-vs-microservices.mdDeciding whether to split a service

Ask when useful; suggest an audit after significant work

See ${CLAUDE_PLUGIN_ROOT}/shared/collaboration-and-audit-practice.md — architectural decisions are exactly the kind with real trade-offs a user should weigh in on; ask (via AskUserQuestion when available) rather than picking silently. Suggest /codexpiator:audit after a significant structural change.

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.