All skills
page-component-decomposition
FoundationJIT onlyanalysis-agent/task-agent: use when page components, props, state ownership, reuse, or decomposition boundaries change; skip when no component-structure decision exists.
- Group
- Frontend engineering
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- decompose page into components responsibilities props and reusable boundaries
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local page component decomposition decision is required
Required inputs
What must be supplied before this skill can decide anything
- current task contract
- selected primary Professional Skill
- task-local trigger evidence
Output contract
What this skill owes the next role
- component decomposition decision with responsibility boundaries, state and effect owners, semantic contracts, reuse rationale, rendering consequences, integration evidence, and residual risks
Escalation signals
When this skill must hand the decision back
- Poor decomposition creates brittle components and unclear state ownership
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | responsibility state ownership reuse or orchestration admits competing decompositions | one existing component boundary fully owns the changed behavior | TaskAnalysis |
| checklist.mddecision-checklist | page change mixes workflow state side effects rendering or permissions | local component change preserves established responsibilities and state ownership | TaskAnalysis |
| evidence-patterns.mdevidence-pattern | reuse ownership accessibility or decomposition claims need current proof | current consumers stories tests and source prove each claim | TaskAnalysis |