react-component-design
React Component Design
Overview
Use this skill to build React components that are composable, testable, and stable under evolving UI requirements.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Rendering and hooks rules:
references/rendering-and-hooks-rules.md
Templates And Assets
- Component boundary template:
assets/react-component-boundary-template.md
- State flow checklist:
assets/react-state-flow-checklist.md
Inputs To Gather
- UI and interaction requirements.
- Reuse boundaries and design-system constraints.
- State ownership and data-flow expectations.
- Performance and accessibility requirements.
- Prop and state shape contracts (explicit type/interface/schema expectations).
Deliverables
- Component boundary and prop/state contract.
- Effect and async-behavior policy.
- Rendering-risk and accessibility checks.
Workflow
- Define component boundaries with
assets/react-component-boundary-template.md. - Apply state/effect rules from
references/rendering-and-hooks-rules.md. - Define explicit prop/state contracts; avoid
any/opaque object bags for component boundaries. - Validate state ownership and transitions.
- Review loading/empty/error/accessibility behavior.
- Finalize with
assets/react-state-flow-checklist.md.
Quality Standard
- Component responsibilities are single-purpose and explicit.
- State ownership is minimal and predictable.
- Effects are scoped and cleanup-safe.
- Performance choices are evidence-driven.
- Data shape mismatches are handled at boundary adapters, not via repeated casts in render/effect logic.
Failure Conditions
- Stop when component boundaries are ambiguous or cyclic.
- Stop when effect logic substitutes for missing state design.
- Escalate when state ownership cannot be resolved cleanly.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9