component-designlisted
Install: claude install-skill lx-wnk/skills
# Component Design (Detail Level)
Design the internals of one module: classes, interfaces, patterns, method contracts. Output a design doc plus optional diagrams when they earn their place.
## Scope
**In scope:** class responsibilities, interfaces/abstract types, design patterns (Strategy, Factory, Adapter, …), aggregate roots and invariants, method signatures, collaboration, data-shape contracts, testability seams.
**Out of scope:** module/context boundaries (→ `architecture-design`), feature requirements, infrastructure choices outside the module.
## Examples
```bash
# Design a specific component
/component-design OrderService
# Design a new component from scratch
/component-design payment-retry handler
```
## Workflow
```mermaid
flowchart TD
A["Locate target module"] --> B["Read existing code"]
B --> C["Detect stack + idioms"]
C --> D["Research framework patterns"]
D --> E["Clarify contract with user"]
E --> F["Propose 2-3 designs"]
F --> G["User picks design"]
G --> H["Write design doc"]
H --> I["Summarize"]
```
## Phase 1: Locate the Target
From `$ARGUMENTS`, find the module via `Glob` / `Grep`. If nothing matches, ask the user to confirm path/name.
Always read **at minimum**:
- The target module's current files (or parent directory if new)
- Nearby sibling modules for convention parity
- Existing tests — they reveal the real contract
## Phase 2: Detect Stack & Idioms
- Language, framework, version
- Framework-native building blocks (Symfon