clean-architecture

Malicious tool definition detected

Tool: SKILL.md [1/3] Description: --- name: clean-architecture description: 'Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", or "use case boundary".

Tool: SKILL.md [2/3] Description: defined by Use Cases -- the Use Case defines the contract, the gateway fulfills it - The database is a detail: business rules don't need to know whether data is stored in SQL, NoSQL, or flat files - The web is a detail: business rules don't know they're being delivered over HTTP - Treat frameworks with suspicion -- they want you to couple to them; keep them at arm's length - Plugin architecture: the system should be structured so that frameworks plug into busine

Tool: SKILL.md [3/3] Description: just a monolith with network calls - The Main component is a plugin: it creates all factories, strategies, and dependencies, then hands control to the high-level policy - Test boundaries: tests are the most isolated component; they always depend inward and nothing depends on them - Premature boundaries are expensive, but so are missing boundaries -- draw them when the cost of crossing is less than the cost of not having them **Code applications:** | Context | Pa

Malicious tool definition detected

Tool: references/adapters-frameworks.md [1/3] Description: # Interface Adapters and Frameworks Interface Adapters and Frameworks & Drivers form the two outermost circles of Clean Architecture.

Tool: references/adapters-frameworks.md [2/3] Description: |-------------------|-----------------|-------------------| | **Routing** | Business logic in route handlers | Route handlers call Controllers; Controllers call Use Cases | | **ORM** | Domain entities ARE ORM models | Separate domain entities; map to/from ORM models in gateways | | **Validation** | Framework validation decorators on entities | Validation in Use Case or domain layer using plain code | | **Dependency injection** | `@Inject

Tool: references/adapters-frameworks.md [3/3] Description: or `json.dumps()`.

Malicious tool definition detected

Tool: references/boundaries.md [1/3] Description: # Boundaries and Boundary Anatomy Boundaries are the lines that separate software elements.

Tool: references/boundaries.md [2/3] Description: read/write operations | Logic that decides what to read/write | | Clock/Random | System clock, random generator | Logic that uses injected clock/random | ## Partial Boundaries ### When Full Boundaries Are Too Expensive Full boundaries require interfaces on both sides (Input Port and Output Port), separate DTOs, and careful dependency management. Sometimes the anticipated need for a boundary doesn't justify the cost.

Tool: references/boundaries.md [3/3] Description: **Instantiate use case interactors** with injected dependencies 4.

Malicious tool definition detected

Tool: references/component-principles.md [1/2] Description: # Component Principles Components are the units of deployment -- the smallest entities that can be independently deployed.

Tool: references/component-principles.md [2/2] Description: stable if many other components depend on it (making it hard to change without breaking things). **Measuring stability:** - **Fan-in (Ca):** Number of classes outside the component that depend on classes inside the component (incoming dependencies) - **Fan-out (Ce):** Number of classes inside the component that depend on classes outside the component (outgoing dependencies) - **Instability (I):** I = Ce / (Ca + Ce), where I ranges from

Malicious tool definition detected

Tool: references/dependency-rule.md [1/2] Description: # The Dependency Rule and Concentric Circles The Dependency Rule is the single most important concept in Clean Architecture. It states that source code dependencies can only point inward.

Tool: references/dependency-rule.md [2/2] Description: | Communicating between bounded contexts | `OrderPlaced(order_id, timestamp)` emitted by inner circle | | **Data maps (dicts)** | Crossing boundaries where type safety is less critical | Acceptable in dynamic languages; prefer typed DTOs in static ones | ### What Must Not Cross Boundaries - **ORM entities or database rows**: These are outer circle artifacts. Never pass an ActiveRecord model into a Use Case.

Malicious tool definition detected

Tool: references/entities-use-cases.md [2/2] Description: and implemented by the outer circles.

Malicious tool definition detected

Tool: references/solid-principles.md [1/3] Description: # SOLID Principles The SOLID principles are five design principles for managing dependencies at the class and module level.

Tool: references/solid-principles.md [2/3] Description: | Callers rely on the method doing something | The class hierarchy is wrong; use composition or a different abstraction | | Subclass strengthens preconditions | Callers that work with base type fail with subtype | Subtypes may weaken preconditions, never strengthen them | | Subclass weakens postconditions | Callers expect guarantees the subtype doesn't provide | Subtypes may strengthen postconditions, never weaken them | ### LSP and Interfa

Tool: references/solid-principles.md [3/3]