frontend-product-design-architect

Designs frontend information architecture, responsive layouts, and UI states for product surfaces.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/Scardubu/SwarmXQ --skill frontend-product-design-architect-scardubu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-product-design-architect
Source: https://github.com/Scardubu/SwarmXQ/tree/main/.ai/skills/frontend-product-design-architect
Command: npx skills add https://github.com/Scardubu/SwarmXQ --skill frontend-product-design-architect-scardubu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend surfaces often ship as functional but unstructured screens with weak hierarchy, missing states, and unclear calls to action. This Skill structures the design process before any component code is written, covering information architecture, responsive breakpoints, and all six UI states. ## Core Features & Use Cases - Information Architecture: Defines reading paths with primary content, proof, one dominant CTA, and trust signals so hierarchy drives the product decision. - Responsive & State Design: Specifies mobile-first Tailwind breakpoint patterns (320px to 1440px+) and designs default, loading, empty, error, degraded, and success states for every surface. - Section Composition Patterns: Provides TSX patterns for heroes, dashboards, forms, and empty states, plus vertical-specific guidance for TaxBridge tax UX, SabiScore analytics dashboards, and SwarmX agent UI. - Use Case: When asked to design a Nigerian SME tax filing form, the Skill produces a chunked fieldset layout with Naira currency inputs, FIRS trust signals, inline validation, and a single dominant submit action. ## Quick Start Ask the assistant to design the layout and information architecture for your landing page, dashboard, or form before writing any component code.

Frequently Asked Questions about frontend-product-design-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a dashboard layout with good information hierarchy?

Lead with a KPI row of scannable summary numbers, follow with trend and breakdown charts, and place detail tables last for deep readers. Use a persistent sidebar so users always know where they are, and keep one dominant action per section.

How to structure a multi-step form for better conversion?

Chunk related fields into fieldsets with clear legends, use inline validation with specific recoverable error messages, and place the primary submit action at the end in a persistent footer. Add progress indicators for multi-step flows like tax filings.

What responsive breakpoints should I design for in Tailwind?

Design explicitly for mobile (320-767px, single column), tablet (768-1023px, two-column max), desktop (1024px+, full layout), and ultra-wide (1440px+, max-width container). Always build mobile-first using Tailwind's sm, md, lg, and xl prefixes.

Should empty states be designed before implementation?

Yes, all six states (default, loading, empty, error, degraded, success) should be designed before any component is written. Empty states should teach and invite action rather than display a bare 'No data found' message.

When should this design skill run relative to writing components?

Always before any component code is written, since structure precedes code. Pair it with a design token system for colors and spacing, then run accessibility review after the layout is set.