Frontend UI Development
Builds big-tech style (Stripe, Vercel, Apple) frontend UI from planning to implementation in one go.
Workflow
/frontend [requirements]
|
1. Write design specification (planning)
|
2. User confirmation
|
3. Implement in the frontend-developer context
|
4. Verify results
Phase 1: Planning
Design Style Selection
| Style | Characteristics | Suitable For |
|---|---|---|
| Stripe | Gradients, bright tones, subtle animations | Payments, SaaS, landing |
| Vercel | Dark mode, minimal, monotone | Developer tools |
| Apple | Wide margins, typography emphasis | Product showcase |
| Linear | Dark, purple accents | Productivity apps |
| Notion | Bright tones, icon usage | Docs/collaboration |
Specification Template
## [Project Name] Design Spec
### Style: [Selected Style]
### Colors
- Primary: #[hex]
- Background: #[hex]
- Text: #[hex]
- Border: #[hex]
- Accent: #[hex]
### Typography
- Display: [font] / [size]
- Body: [font] / [size]
### Components
1. [Component1]: [description]
2. [Component2]: [description]
### Layout
- Max width: [px]
- Main structure: [description]
Phase 2: Implementation
This skill runs in the frontend-developer context (via context: fork + agent in the frontmatter). Proceed with the implementation directly — do not spawn the agent again.
Implementation Order
- CSS variables (globals.css)
- Utilities (lib/utils.ts)
- UI components (components/ui/)
- Layout (components/layout/)
- Feature components
- Page assembly
- Animations
Required Dependencies
npm install tailwindcss @tailwindcss/typography
npm install clsx tailwind-merge
npm install framer-motion
npm install lucide-react
npx shadcn@latest init
Phase 3: Verification
After implementation:
- No TypeScript errors
- Build succeeds
- Responsive verified
- Accessibility verified
Usage Examples
/frontend Create a login page. Vercel style, with email/password input form and social login buttons.
/frontend Create a dashboard. Stripe style, with sidebar + main content area + chart cards.