Results for “system-design”

Designs and structures the Movemental living SSOT dashboard (HTML/CSS/JS), aligning docs into a docs-first, token-based, agent-friendly dashboard.

Converts Stitch designs into modular Vite and React components, or syncs/updates existing React components to align with the latest Stitch designs, using system-level networking and AST-based validation.

Render a proposed redesign of a page as a self-contained static HTML file, then iterate via chat-driven commands until approved.

Generate production-quality React + Tailwind CSS code using the Rayden UI component library with correct props, design tokens, and layout patterns.

Data-driven modularity specialist - Masters ScriptableObjects, decoupled systems, and single-responsibility component design for scalable Unity projects

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, information architecture, visual style direction, design systems/tokens, component specs, copy/microcopy, accessibility, or to generate/critique/refine frontend UI (HTML/CSS/JS, React, Next.js, Vue, Svelte, Tailwind). Includes workflows for (1) generating new UI layouts and styling, (2) improving existing UI/UX, (3) producing design-system tokens and component guidelines, and (4) turning UX recommendations into concrete code changes.

CSS Grid-based responsive grid system component. Invoke when user needs to implement grid layouts, responsive designs, or column-based layouts in Naive UI.

Migrates a Stitch screen to production React: fetches and caches wireframes, archives existing pages, converts to shadcn/ui components with semantic tokens, and documents the design system layers.

Extrai e documenta o sistema de design do projeto legado — paleta de cores, tipografia, espaçamentos, tokens e componentes a partir de CSS, arquivos de tema e screenshots. Use quando arquivos de estilo ou screenshots de interface estiverem disponíveis.

Trigger: clean architecture, hexagonal architecture, domain model, state machine, boundary decoupling. Scope: Software modular design, dependency boundaries, architectural layering. Boundary: Excludes frontend aesthetic styling.

Use when the team needs reusable UI component patterns, component responsibilities, states, props, and interaction behavior for React, Next.js, or Tailwind-based interfaces. Trigger on requests to design a component system or define a component before coding it.

Automated visual design review — screenshot V0 demo URLs or local HTML, analyze rendered output, and validate against brand system. Works with both V0 live previews and Stitch-generated HTML.

Design and implement accessible UI motion systems for React, Next.js, and frontend interfaces. Use for animation, transitions, gestures, drag and drop, page transitions, staggered reveals, SVG motion, loaders, motion tokens, reduced-motion behavior, or the old motion-foundations/motion-patterns/motion-advanced/motion-ui skills.

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.

Trigger: web performance, slow load, bundle size, lazy loading, LCP, CWV optimization, fetch priority. Scope: Frontend optimization, loading speeds, asset minimization. Boundary: Excludes backend database indexing or visual design systems.

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.

Provides Kelvin Garr's fixed AICA brand identity and Next.js 14 implementation guide for building his personal sites and AICA-branded projects.

Audits colour decisions on a screen for contrast ratios, palette coherence, semantic meaning, and accessibility, flagging deviations and recommending specific corrections.

Use when designing or implementing product-grade web motion like Stripe, Linear, Apple, and Vercel. Covers motion principles, easing/duration defaults, choreography patterns, scroll/hover interactions, performance, accessibility (reduced motion), and implementation guidance.

Audits any movemental.com page across UI, content, architecture, UX, and conversion, then writes a markdown report and a standalone fix prompt.

Use when the team needs to understand how data moves through frontend, backend, database, jobs, auth, and external integrations. Trigger on requests to map data flow, event flow, or state transitions across the system.

Plan the frontend application structure for a product or feature. Use when the team needs route structure, feature modules, state boundaries, design-system needs, and frontend delivery sequencing based on defined screens and flows.

Use this skill when creating, redesigning, critiquing, reducing, polishing, hardening, or making design decisions for a user-facing interface, brand surface, product UI, component, dashboard, flow, app shell, onboarding, empty state, or visual system. Applies Mies van der Rohe-inspired restraint, the Interface Craft workflow, and anti-generic design discipline. Not for backend-only work.

Applies Kelvin Garr's fixed AICA brand identity—black glass, gold circuits, Space Grotesk—and Next.js 14 implementation guide for his personal sites and AICA-branded projects.

Use when the team needs route structure, feature modules, design-system boundaries, and frontend responsibilities for a React, Next.js, or Tailwind application. Trigger on requests about frontend architecture, app structure, pages, modules, or client-side delivery planning.

Use when the request is broad and spans idea evaluation, MVP planning, UX, frontend, backend, database, auth, integrations, and launch strategy. Trigger on asks like "build this app", "turn this idea into a product", "design the whole system", or "plan everything end to end".

Use when designing or auditing the evaluation of an ASE (IEEE/ACM Automated Software Engineering) paper, covering real subject systems, fair runnable tool baselines, task-matched effectiveness metrics, ablations that isolate a learned component, oracle and correctness validation, contamination-aware LLM handling, and provenance for mining.

Capture exact React element context from a live browser UI and hand it to an AI coding agent as component name, source file path, line number, and HTML. Use when the user wants `react-grab`, element-context copy, component-source lookup from the browser, clipboard-to-agent React debugging, or MCP-backed element selection for React apps. Not for generic browser automation or login/session reuse (`browser-harness`, `playwriter`), broad UI annotation/review (`agentation`), React performance audits (`react-best-practices`), or general design-system work (`design-system`). Triggers on: react-grab, grab element context, copy component to AI, browser component picker, React component inspector, clipboard component source, get element context from browser, grab UI element.

Polishes UI primitives one at a time using research-backed patterns: adds loading and icon states to buttons, replaces inline skeletons with primitives, adds secondary actions to errors, ensures 48px touch targets and visible focus indicators, and applies a standard motion token ladder.

Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style), not a decorative one. Encodes the discipline — columns + modules + baseline, grotesque type, flush-left ragged-right, restrained black/white/red — AND the front-end engineering that makes the grid load-bearing: one CSS-variable source of truth, a grid-toggle overlay that lives in the SAME content box as the content, subgrid 'bands' so every element snaps to a column line, an 8px baseline lock, and runtime optical alignment that puts display type's ink (not its box) on the line. Ships a scaffold generator and a Puppeteer harness that proves 0px adherence. Use when: building any editorial, magazine, report, or longform page that must read as rigorously grid-aligned, Swiss, International Typographic Style, or 'Müller-Brockmann'. Triggers: magazine spread, grid system, Swiss design, editorial layout, show the grid, grid overlay toggle, baseline grid, modular grid, 12-column layout, 瑞士网格, 版面网格.