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.

Applies design engineering principles to polish UI components, covering typography, surfaces, animations, and performance with concrete CSS values and review checklists.

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

Composition Patterns

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

A design system has three token layers, and conflating them is what makes systems

SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles.

Guides module boundaries, dependency direction, and domain structure. Do not use for local edits that leave architecture unchanged.

Find a unifying insight that eliminates multiple components, collapsing complexity by abstracting common patterns.

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.

Trigger: writing style, copy editing, simple copy, prose check, text clarity. Scope: Writing clear, direct, and concise English copy. Boundary: Excludes code formatting or marketing value propositions.

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.

Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract to build systems that are easy to change, understand, and trust.

Explain and apply core ML/AI concepts — model types, training pipelines, evaluation metrics, and neural architectures.

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.

Find a single insight that eliminates multiple components by recognizing when seemingly different systems share a common underlying pattern.

Angular core patterns: standalone components, signals, inject, control flow, zoneless. Trigger: When creating Angular components, using signals, or setting up zoneless.

Design motivation systems for products and teams using Autonomy, Mastery, and Purpose (AMP) to drive intrinsic engagement.

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.

Manage software complexity through deep modules, information hiding, and strategic programming, with a scoring framework for evaluating design quality.

Provides a structured checklist of design principles and rules to produce grounded, non-generic UI/HTML/slide outputs by gathering context, offering multiple variants, and avoiding AI-slop patterns.

Dotnet Patterns

Compare tradeoffs and recommend architectural patterns — dependency injection, service-oriented architecture, repository, domain events, circuit breaker, and anti-corruption layer. Use when choosing between design patterns, planning microservices boundaries, evaluating system design alternatives, or asking 'which pattern should I use' for a specific coupling or resilience problem.

CSS design system standards — custom properties, BEM naming, spacing/typography/color scales, no build tools

Define a set of actionable design principles that guide decision-making and resolve trade-offs.

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.