Index of every page on this site: llms.txt
All skills
amanktyr avatar

/architecture

@5711aad
by Aman Ktyramanktyr/tailor6 stars
Run it yourself

Governs software architecture design, modular monolith patterns, layer boundary enforcement, and Architecture Decision Record (ADR) lifecycle management.

Use this Skill: https://skilld.dev/gh/amanktyr/tailor/architecture

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈42 tokens for metadata: the name and description. ≈921 when used: this file.

Description uses 2.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈168 characters, or 2.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Architecture Skill

Activate this skill when evaluating system boundaries, designing new subsystems, structuring directory layouts, resolving modular coupling, or maintaining Architecture Decision Records (ADRs).

Architectural Law: Make boundaries clear, keep modules cohesive, and defer distributed complexity until verifiable scale demands it.


1. Clean Architecture & Layer Boundary Enforcement

Maintain strict separation of concerns across application layers:

┌────────────────────────────────────────────────────────┐
│ 1. Presentation / Transport Layer                      │
│    - HTTP Controllers, Route Handlers, CLI Commands    │
│    - Responsibility: Parse inputs, validate payload,   │
│      map HTTP status codes, serialize responses.       │
├────────────────────────────────────────────────────────┤
│ 2. Domain / Application Service Layer                  │
│    - Business Services, Use Cases, Workflows           │
│    - Responsibility: Pure business logic, permissions, │
│      orchestration, domain events. Zero HTTP details.  │
├────────────────────────────────────────────────────────┤
│ 3. Infrastructure & Persistence Layer                  │
│    - Database Repositories, Third-Party API Clients    │
│    - Responsibility: SQL queries, ORM calls, network   │
│      transports, cache storage.                        │
└────────────────────────────────────────────────────────┘

Boundary Violations to Reject

  • Writing raw SQL or database queries inside React components or HTTP controllers.
  • Importing HTTP request/response objects (req, res) into domain service classes.
  • Allowing circular module dependencies across domain boundaries.

2. Modular Monolith vs Distributed Microservices

  • Default Choice: Modular Monolith. Group code into feature domains (src/features/billing/, src/features/auth/) with clear public API barriers (index.ts).
  • Reject Premature Microservices: Do not split applications into separate microservices, message queues, or distributed transactions unless:
    1. Independent teams require isolated deployment pipelines.
    2. Distinct microservices have vastly different scaling and compute profiles (e.g. CPU-intensive video encoding vs lightweight CRUD).

3. Architecture Decision Record (ADR) Standard (.ai/DECISIONS.md)

When an architectural decision is adopted, document it using this format:

## ADR-00X — [Short Descriptive Title]
**Status:** Accepted | Proposed | Deprecated | Superseded by ADR-YYY  
**Date:** YYYY-MM-DD  
**Deciders:** [Architects / Team Members]

### Context & Problem Statement
What technical challenge or product requirement are we addressing? What constraints exist?

### Decision
What specific architecture, technology, library, or pattern are we committing to?

### Rationale & Tradeoffs Considered
- **Option A (Chosen):** Key benefits, accepted trade-offs, and operational risks.
- **Option B (Rejected):** Why this alternative was considered and ultimately rejected.

### Evidence & Verification
References to benchmarks, documentation, or prototype results validating this decision.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    This skill provides structured templates for architectural decision-making and best practices for system design. No security risks or malicious behaviors were detected.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at 5711aad. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 3 months ago

README badge

README badge for amanktyr/tailor/architecture