design-brieflisted

Create a design brief through an interactive interview, codebase exploration, and experience design decisions. Saved as a markdown file in the project. Use when user wants to write a design brief, plan a new feature or page, define a UI direction, or mentions "brief".
muzalee/claude-atelier · ★ 0 · Web & Frontend · score 62

Install: claude install-skill muzalee/claude-atelier

This skill creates a design brief through structured conversation. You may skip steps if they are not necessary. ## Example prompts - "Write a brief for the onboarding flow" - "I need to plan a settings page before I start building" - "Help me define the direction for a marketing landing page" - "Brief this: a dashboard that shows project health metrics" ## Process 1. Ask the user for a detailed description of what they want to build, who it is for, and any constraints or ideas they already have. 2. Explore the existing codebase to understand the current state. Scan for each of the following specifically: - **CSS variables / tokens**: files named `tokens.css`, `variables.css`, `theme.css`, or `:root` declarations with custom properties - **Tailwind config**: `tailwind.config.js` or `tailwind.config.ts`, check `theme.extend` for custom values - **UI framework themes**: Material UI `createTheme`, Chakra `extendTheme`, shadcn `globals.css` and `components.json` - **Component directories**: `components/`, `ui/`, `shared/`, or any folder containing reusable UI pieces - **Storybook**: `.storybook/` directory or `*.stories.*` files indicating a documented component library - **Design token files**: JSON token files (Style Dictionary format, Figma token exports) - **Package.json UI dependencies**: tailwindcss, @mui/material, @chakra-ui/react, @radix-ui, lucide-react, framer-motion, etc. - **Font loading**: Google Fonts links in HTML, `@font-face` declarat