React Component Architecture
Design React components around stable identity, explicit ownership and composable behavior; preserve focus and local state while making feature boundaries easier to change.
19 CANONICAL SKILLS · V0.1.0
React and Next.js boundaries, TanStack Query, forms, Tailwind, design-system composition, accessible icons and complete frontend states.
Run from a full toolkit checkout. This prints a file manifest, not an installer.
node tools/bundle.mjs resolve modern-reactExplore the frontend worked guide →
Design React components around stable identity, explicit ownership and composable behavior; preserve focus and local state while making feature boundaries easier to change.
Identify the actual cause of slow React interactions and reduce unnecessary work using measured state boundaries, subscriptions, scheduling and justified memoization.
Assign each UI value one authoritative owner across local state, URL state, form drafts, server caches and shared client stores, with explicit reconciliation rules.
Implement React Query data access with complete query identities, explicit freshness, cancellation, mutation reconciliation and isolated server-rendering caches.
Plan App Router features around route ownership, server/client execution, loading and failure boundaries, cache semantics and the actual deployment target.
Keep server-only data and execution out of client graphs while composing small interactive React islands with explicit serialization and hydration contracts.
Build maintainable utility-based interfaces with version-correct tokens, statically discoverable variants, responsive behavior and tested component composition.
Establish a small versioned system of semantic tokens, accessible primitives and feature compositions with clear ownership and migration criteria.
Implement layouts that adapt to container space, content length, input mode and zoom without hiding required actions or masking overflow.
Implement and verify accessible frontend interactions through native semantics, meaningful names, keyboard/focus behavior and explicit assistive-technology limits.
Build React forms with a deliberate native or React Hook Form lifecycle, accessible errors, stable field identity and authoritative server validation.
Use a validated URL as the authority for shareable frontend state while preserving browser history, unrelated parameters and safe navigation boundaries.
Convert untrusted transport data into deliberate frontend view models without leaking service details, precision errors or unauthorized fields throughout the component tree.
Design initial, empty, refreshing, partially failed and mutation-pending UI states that preserve useful data and offer safe, attributable recovery.
Choose unit, component and browser checks around user-visible frontend contracts, with independent network fixtures and explicit integration coverage.
Use reproducible visual evidence to detect frontend regressions while preserving independent interaction, accessibility and content checks.
Keep untrusted content, navigation, credentials and server effects behind explicit boundaries while testing the real browser-to-server trust model.
Select and integrate a coherent icon family using React Icons, Lucide or an existing library with accessible meaning, bounded imports and preserved upstream license information.
Compose installed headless primitives and shadcn/ui source components without breaking keyboard semantics, local changes or version-specific APIs.
Pick the skill needed for the current task. A private adapter supplies project-specific roots, command IDs, accepted contracts, and policy. It should pin and verify the public revision before exposing guidance to an internal agent.
Skill effectiveness remains experimental. Package validation and content hashes do not establish host compatibility, artifact authenticity, or permission to execute.
Read the private-adapter boundary ↗