Results for “dom-components”

Run web code in a webview on native platforms and as-is on web, enabling use of web-only libraries like recharts and react-syntax-highlighter in Expo apps.

Builds fast, standard-compliant web components with Lit, reactive properties, and Shadow DOM. Use for framework-agnostic UI.

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

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

Create or update standardized object-oriented component documentation by analyzing source code and following a shared template with mode-specific guidance.

Converts Stitch designs into modular Vite and React components, or syncs existing components to match updated designs.

Descriptions component for displaying key-value pairs in a structured layout. Invoke when user needs to display item details, configuration info, or form-like read-only data in Naive UI.

frontend-components

List component for displaying structured list items with headers, footers, and dividers. Invoke when user needs to implement list layouts, item lists, or content lists in Naive UI.

Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships. Creates component diagrams and documentation. Use when synthesizing code-level documentation into logical components.

Card component for displaying content in a contained, organized manner. Invoke when user needs to implement content cards, panels, or customizable containers in Naive UI.

Menu component for navigation and actions. Invoke when user needs to implement navigation menus, sidebars, dropdown menus, or hierarchical navigation in Naive UI.

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

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

BOM (Bill of Materials) management for electronics projects — the primary orchestrator skill that coordinates DigiKey, Mouser, LCSC, element14, JLCPCB, PCBWay, and KiCad skills into a unified workflow. Create, update, and maintain BOMs with part numbers, costs, quantities stored as KiCad symbol properties. ALWAYS trigger this skill for any task involving component sourcing, pricing, ordering, distributor searches, BOM export, or fabrication preparation — even if the user names a specific distributor or fab house (e.g. "search DigiKey for...", "generate JLCPCB BOM", "order from Mouser"). This skill decides which distributor/fab skills to invoke and in what order. Also trigger on phrases like "what parts do I need", "order components", "how much will this cost", "export for JLCPCB", "find parts for this board", "cost estimate", "compare pricing", or "check stock".

Modal component for displaying dialog boxes and content overlays. Invoke when user needs to implement modal dialogs, confirmations, or floating panels in Naive UI.

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

Use Light DOM in LWC when third-party libraries or global CSS require document-level access, with guidance on scoped styles and managed-package constraints.

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

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.

Build custom PCB structures with pcbComponent, shapes, Boolean ops, feeds, and multi-layer stackups for non-catalog geometries. TRIGGER: user asks to build, modify, or customize a pcbComponent — add/remove shapes, edit polygons, place feeds, add metal layers, cut slots, or create non-catalog RF structures. Also when modifying geometry of an existing catalog-designed component (e.g., adding pads, removing elements, editing vertices). Invoke BEFORE writing pcbComponent code — layer/shape/feed API is non-obvious. SKIP: designing catalog components like filters/couplers/txlines (use the specific matlab-design-pcb-* skill), material/stackup definition only (use matlab-manage-pcb-material), EM analysis (use matlab-analyze-em), importing PCB files (use matlab-read-pcb-layout).

Theme Salesforce Lightning base components and custom LWCs using SLDS Styling Hooks, covering global and component hooks, shadow DOM considerations, Experience Cloud theming, and SLDS 2 migration.

Statistic component for displaying statistical values with labels, prefixes, and suffixes. Invoke when user needs to implement statistics displays, metrics dashboards, or data summaries in Naive UI.

Migrate LWC components from fragile querySelector lookups to typed lwc:ref handles, with guidance on lifecycle timing, shadow boundaries, and iterator limitations.

Migrate an existing web React app to a native iOS/Android app with Expo, screen by screen, using a strangler fig pattern.