@theproductguy/create-mission-control 1.0.3 → 1.0.4

package/src/template/design-system/.claude/commands/design-os/design-tokens.md

@@ -1,166 +0,0 @@
-# Design Tokens
-
-You are helping the user choose colors and typography for their product. These design tokens will be used consistently across all screen designs and the application shell.
-
-## Step 1: Check Prerequisites
-
-First, verify that the product overview exists:
-
-Read `/product/product-overview.md` to understand what the product is.
-
-If it doesn't exist:
-
-"Before defining your design system, you'll need to establish your product vision. Please run `/product-vision` first."
-
-Stop here if the prerequisite is missing.
-
-## Step 2: Explain the Process
-
-"Let's define the visual identity for **[Product Name]**.
-
-I'll help you choose:
-1. **Colors** — A primary accent, secondary accent, and neutral palette
-2. **Typography** — Fonts for headings, body text, and code
-
-These will be applied consistently across all your screen designs and the application shell.
-
-Do you have any existing brand colors or fonts in mind, or would you like suggestions?"
-
-Wait for their response.
-
-## Step 3: Choose Colors
-
-Help the user select from Tailwind's built-in color palette. Present options based on their product type:
-
-"For colors, we'll pick from Tailwind's palette so they work seamlessly with your screen designs.
-
-**Primary color** (main accent, buttons, links):
-Common choices: `blue`, `indigo`, `violet`, `emerald`, `teal`, `amber`, `rose`, `lime`
-
-**Secondary color** (complementary accent, tags, highlights):
-Should complement your primary — often a different hue or a neutral variation
-
-**Neutral color** (backgrounds, text, borders):
-Options: `slate` (cool gray), `gray` (pure gray), `zinc` (slightly warm), `neutral`, `stone` (warm gray)
-
-Based on [Product Name], I'd suggest:
-- **Primary:** [suggestion] — [why it fits]
-- **Secondary:** [suggestion] — [why it complements]
-- **Neutral:** [suggestion] — [why it works]
-
-What feels right for your product?"
-
-Use AskUserQuestion to gather their preferences if they're unsure:
-
-- "What vibe are you going for? Professional, playful, modern, minimal?"
-- "Any colors you definitely want to avoid?"
-- "Light mode, dark mode, or both?"
-
-## Step 4: Choose Typography
-
-Help the user select Google Fonts:
-
-"For typography, we'll use Google Fonts for easy web integration.
-
-**Heading font** (titles, section headers):
-Popular choices: `DM Sans`, `Inter`, `Poppins`, `Manrope`, `Space Grotesk`, `Outfit`
-
-**Body font** (paragraphs, UI text):
-Often the same as heading, or: `Inter`, `Source Sans 3`, `Nunito Sans`, `Open Sans`
-
-**Mono font** (code, technical content):
-Options: `IBM Plex Mono`, `JetBrains Mono`, `Fira Code`, `Source Code Pro`
-
-My suggestions for [Product Name]:
-- **Heading:** [suggestion] — [why]
-- **Body:** [suggestion] — [why]
-- **Mono:** [suggestion] — [why]
-
-What do you prefer?"
-
-## Step 5: Present Final Choices
-
-Once they've made decisions:
-
-"Here's your design system:
-
-**Colors:**
-- Primary: `[color]`
-- Secondary: `[color]`
-- Neutral: `[color]`
-
-**Typography:**
-- Heading: [Font Name]
-- Body: [Font Name]
-- Mono: [Font Name]
-
-Does this look good? Ready to save it?"
-
-## Step 6: Create the Files
-
-Once approved, create two files:
-
-**File 1:** `/product/design-system/colors.json`
-```json
-{
-  "primary": "[color]",
-  "secondary": "[color]",
-  "neutral": "[color]"
-}
-```
-
-**File 2:** `/product/design-system/typography.json`
-```json
-{
-  "heading": "[Font Name]",
-  "body": "[Font Name]",
-  "mono": "[Font Name]"
-}
-```
-
-## Step 7: Confirm Completion
-
-Let the user know:
-
-"I've saved your design tokens:
-- `/product/design-system/colors.json`
-- `/product/design-system/typography.json`
-
-**Your palette:**
-- Primary: `[color]` — for buttons, links, key actions
-- Secondary: `[color]` — for tags, highlights, secondary elements
-- Neutral: `[color]` — for backgrounds, text, borders
-
-**Your fonts:**
-- [Heading Font] for headings
-- [Body Font] for body text
-- [Mono Font] for code
-
-These will be used when creating screen designs for your sections.
-
-Next step: Run `/design-shell` to design your application's navigation and layout."
-
-## Reference: Tailwind Color Palette
-
-Available colors (each has shades 50-950):
-- **Warm:** `red`, `orange`, `amber`, `yellow`, `lime`
-- **Cool:** `green`, `emerald`, `teal`, `cyan`, `sky`, `blue`
-- **Purple:** `indigo`, `violet`, `purple`, `fuchsia`, `pink`, `rose`
-- **Neutral:** `slate`, `gray`, `zinc`, `neutral`, `stone`
-
-## Reference: Popular Google Font Pairings
-
-- **Modern & Clean:** DM Sans + DM Sans + IBM Plex Mono
-- **Professional:** Inter + Inter + JetBrains Mono
-- **Friendly:** Nunito Sans + Nunito Sans + Fira Code
-- **Bold & Modern:** Space Grotesk + Inter + Source Code Pro
-- **Editorial:** Playfair Display + Source Sans 3 + IBM Plex Mono
-- **Tech-forward:** JetBrains Mono + Inter + JetBrains Mono
-
-## Important Notes
-
-- Colors should be Tailwind palette names (not hex codes)
-- Fonts should be exact Google Fonts names
-- Keep suggestions contextual to the product type
-- The mono font is optional but recommended for any product with code/technical content
-- Design tokens apply to screen designs only — the Design OS app keeps its own aesthetic

package/src/template/design-system/.claude/skills/frontend-design/SKILL.md

@@ -1,42 +0,0 @@
----
-name: frontend-design
-description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
-license: Complete terms in LICENSE.txt
----
-
-This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
-
-The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
-
-## Design Thinking
-
-Before coding, understand the context and commit to a BOLD aesthetic direction:
-- **Purpose**: What problem does this interface solve? Who uses it?
-- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
-- **Constraints**: Technical requirements (framework, performance, accessibility).
-- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
-
-**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
-
-Then implement working code (HTML/CSS/JS, React, Tailwind, etc.) that is:
-- Production-grade and functional
-- Visually striking and memorable
-- Cohesive with a clear aesthetic point-of-view
-- Meticulously refined in every detail
-
-## Frontend Aesthetics Guidelines
-
-Focus on:
-- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
-- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
-- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
-- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
-- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
-
-NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
-
-Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
-
-**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
-
-Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.