Results for “component-principles”

Create or review Blazor components (.razor files) with correct architecture, covering parameters, EventCallback, RenderFragment, lifecycle, async patterns, disposal, and CSS isolation.

Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices.

Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices.

Provides idiomatic React 18/19 patterns for hooks, server/client components, Suspense, error boundaries, forms, data fetching, state management, and accessibility-first composition.

React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.

Creates detailed component specifications for design systems, covering anatomy, variants, states, accessibility, and usage guidelines.

Provides React composition patterns to avoid boolean prop proliferation, build flexible component libraries, and design reusable APIs, including React 19 changes.

Plan complex Blazor UI features by decomposing them into focused, composable components with clear data flow and implementation order.

Share state between Blazor components across render mode boundaries using cascading values, scoped services with change events, or CascadingValueSource via DI.

frontend-components

Provides reusable React and Next.js patterns for component composition, state management, data fetching, and performance optimization.

Provides idiomatic React 18/19 patterns for hooks, server/client components, Suspense, error boundaries, forms, data fetching, state management, and accessibility-first composition.

Atomic-design guidance for UI Atoms — the smallest single-purpose building blocks (buttons, inputs, icons, labels). Use when authoring or reviewing components under ui/atoms, components/atoms, or when deciding whether a component belongs at the atom level.

Frontend architecture and UI design — component hierarchies, accessibility, performance, state management. Use when designing frontend architecture, building component hierarchies, making something accessible, optimizing Core Web Vitals, or choosing a state management approach.

Converts Stitch designs into modular Vite and React components using system-level networking and AST-based validation.

C4 Component Level: [Component Name]

React composition and performance optimization patterns from Vercel. Use when building component libraries, refactoring components with prop proliferation, optimizing React/Next.js performance, or designing scalable component architectures. Covers composition patterns, React 19 APIs, performance optimization across waterfalls, bundle size, server/client rendering, and re-render optimization.

Provides React composition patterns to avoid boolean prop proliferation, covering compound components, state management, and React 19 API changes.

Use this when the team needs a component breakdown for a screen or feature that may or may not be React-specific. Trigger on requests to plan component responsibilities, composition, states, and boundaries before implementation.

Use when writing or editing a React component. Covers preferred patterns for functional components, prop types, and styling.

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

Container/presentational component split — "smart" containers connect to the store, fetch data, and orchestrate loading/error/empty states; "dumb" children just render props. Use when extracting data logic from views, introducing custom hooks, or reviewing `*Container` components.

Converts Stitch designs into modular Vite and React components, using MCP networking and AST-based validation to ensure code quality.

Composite skill — design, scaffold, build, and verify a UI in one workflow. Chains ui-ux-pro-max or web-design-guidelines (audit/principles) → shadcn or tailwind-design-system (component scaffold) → impeccable or frontend-design (build) → webapp-testing (verify). Use when the task is "build this page", "design and implement X", or any new UI surface.

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", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.