From 25f4df03f7c434addeece0c46067d8f206895cd8 Mon Sep 17 00:00:00 2001 From: Paul Bakaus Date: Thu, 8 Jan 2026 15:14:49 -0800 Subject: [PATCH] Strip context gathering from frontend-design skill Remove the MANDATORY: Context Gathering section since it never works when the skill is invoked from commands. Context gathering is now handled by the commands themselves (bolder, quieter, colorize, animate, delight, simplify). The skill is now leaner and focused on design principles and anti-patterns, matching the original Anthropic skill structure. Co-Authored-By: Claude Opus 4.5 --- .claude/skills/frontend-design/SKILL.md | 21 ------------------- .../.claude/skills/frontend-design/SKILL.md | 21 ------------------- .../.claude/skills/frontend-design/SKILL.md | 21 ------------------- .../.codex/skills/frontend-design/SKILL.md | 21 ------------------- .../.codex/skills/frontend-design/SKILL.md | 21 ------------------- .../.cursor/skills/frontend-design/SKILL.md | 21 ------------------- .../.cursor/skills/frontend-design/SKILL.md | 21 ------------------- .../.gemini/skills/frontend-design/SKILL.md | 21 ------------------- .../.gemini/skills/frontend-design/SKILL.md | 21 ------------------- source/skills/frontend-design/SKILL.md | 21 ------------------- 10 files changed, 210 deletions(-) diff --git a/.claude/skills/frontend-design/SKILL.md b/.claude/skills/frontend-design/SKILL.md index 8f564d157..c78cca7e0 100644 --- a/.claude/skills/frontend-design/SKILL.md +++ b/.claude/skills/frontend-design/SKILL.md @@ -6,27 +6,6 @@ license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md f 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. -## MANDATORY: Context Gathering (Do This First) - -Before ANY design work, complete these steps in order: - -### Step 1: Scan the codebase for context -Search for and read: README, brand guidelines, design tokens, existing components, style files, color variables. - -### Step 2: Answer these questions (from codebase OR by asking user) -- Who is the target audience? -- What is the brand personality or tone? -- Are there existing design tokens, colors, or fonts to use? - -### Step 3: If ANY question is unclear, STOP and ask -If you cannot confidently answer ALL three questions from the codebase, STOP and call the AskUserQuestionTool to clarify. Do NOT proceed to design work until all three are answered. Guessing leads to generic AI slop. - ---- - -**Only after completing the above, proceed to design work below.** - ---- - ## Design Direction Commit to a BOLD aesthetic direction: diff --git a/dist/claude-code-prefixed/.claude/skills/frontend-design/SKILL.md b/dist/claude-code-prefixed/.claude/skills/frontend-design/SKILL.md index 8f564d157..c78cca7e0 100644 --- a/dist/claude-code-prefixed/.claude/skills/frontend-design/SKILL.md +++ b/dist/claude-code-prefixed/.claude/skills/frontend-design/SKILL.md @@ -6,27 +6,6 @@ license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md f 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. -## MANDATORY: Context Gathering (Do This First) - -Before ANY design work, complete these steps in order: - -### Step 1: Scan the codebase for context -Search for and read: README, brand guidelines, design tokens, existing components, style files, color variables. - -### Step 2: Answer these questions (from codebase OR by asking user) -- Who is the target audience? -- What is the brand personality or tone? -- Are there existing design tokens, colors, or fonts to use? - -### Step 3: If ANY question is unclear, STOP and ask -If you cannot confidently answer ALL three questions from the codebase, STOP and call the AskUserQuestionTool to clarify. Do NOT proceed to design work until all three are answered. Guessing leads to generic AI slop. - ---- - -**Only after completing the above, proceed to design work below.** - ---- - ## Design Direction Commit to a BOLD aesthetic direction: diff --git a/dist/claude-code/.claude/skills/frontend-design/SKILL.md b/dist/claude-code/.claude/skills/frontend-design/SKILL.md index 8f564d157..c78cca7e0 100644 --- a/dist/claude-code/.claude/skills/frontend-design/SKILL.md +++ b/dist/claude-code/.claude/skills/frontend-design/SKILL.md @@ -6,27 +6,6 @@ license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md f 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. -## MANDATORY: Context Gathering (Do This First) - -Before ANY design work, complete these steps in order: - -### Step 1: Scan the codebase for context -Search for and read: README, brand guidelines, design tokens, existing components, style files, color variables. - -### Step 2: Answer these questions (from codebase OR by asking user) -- Who is the target audience? -- What is the brand personality or tone? -- Are there existing design tokens, colors, or fonts to use? - -### Step 3: If ANY question is unclear, STOP and ask -If you cannot confidently answer ALL three questions from the codebase, STOP and call the AskUserQuestionTool to clarify. Do NOT proceed to design work until all three are answered. Guessing leads to generic AI slop. - ---- - -**Only after completing the above, proceed to design work below.** - ---- - ## Design Direction Commit to a BOLD aesthetic direction: diff --git a/dist/codex-prefixed/.codex/skills/frontend-design/SKILL.md b/dist/codex-prefixed/.codex/skills/frontend-design/SKILL.md index 9ccafd702..497311f38 100644 --- a/dist/codex-prefixed/.codex/skills/frontend-design/SKILL.md +++ b/dist/codex-prefixed/.codex/skills/frontend-design/SKILL.md @@ -6,27 +6,6 @@ license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md f 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. -## MANDATORY: Context Gathering (Do This First) - -Before ANY design work, complete these steps in order: - -### Step 1: Scan the codebase for context -Search for and read: README, brand guidelines, design tokens, existing components, style files, color variables. - -### Step 2: Answer these questions (from codebase OR by asking user) -- Who is the target audience? -- What is the brand personality or tone? -- Are there existing design tokens, colors, or fonts to use? - -### Step 3: If ANY question is unclear, STOP and ask -If you cannot confidently answer ALL three questions from the codebase, ask the user directly to clarify what you cannot infer. Do NOT proceed to design work until all three are answered. Guessing leads to generic AI slop. - ---- - -**Only after completing the above, proceed to design work below.** - ---- - ## Design Direction Commit to a BOLD aesthetic direction: diff --git a/dist/codex/.codex/skills/frontend-design/SKILL.md b/dist/codex/.codex/skills/frontend-design/SKILL.md index 9ccafd702..497311f38 100644 --- a/dist/codex/.codex/skills/frontend-design/SKILL.md +++ b/dist/codex/.codex/skills/frontend-design/SKILL.md @@ -6,27 +6,6 @@ license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md f 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. -## MANDATORY: Context Gathering (Do This First) - -Before ANY design work, complete these steps in order: - -### Step 1: Scan the codebase for context -Search for and read: README, brand guidelines, design tokens, existing components, style files, color variables. - -### Step 2: Answer these questions (from codebase OR by asking user) -- Who is the target audience? -- What is the brand personality or tone? -- Are there existing design tokens, colors, or fonts to use? - -### Step 3: If ANY question is unclear, STOP and ask -If you cannot confidently answer ALL three questions from the codebase, ask the user directly to clarify what you cannot infer. Do NOT proceed to design work until all three are answered. Guessing leads to generic AI slop. - ---- - -**Only after completing the above, proceed to design work below.** - ---- - ## Design Direction Commit to a BOLD aesthetic direction: diff --git a/dist/cursor-prefixed/.cursor/skills/frontend-design/SKILL.md b/dist/cursor-prefixed/.cursor/skills/frontend-design/SKILL.md index 23fd2d561..d49fe3c77 100644 --- a/dist/cursor-prefixed/.cursor/skills/frontend-design/SKILL.md +++ b/dist/cursor-prefixed/.cursor/skills/frontend-design/SKILL.md @@ -6,27 +6,6 @@ license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md f 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. -## MANDATORY: Context Gathering (Do This First) - -Before ANY design work, complete these steps in order: - -### Step 1: Scan the codebase for context -Search for and read: README, brand guidelines, design tokens, existing components, style files, color variables. - -### Step 2: Answer these questions (from codebase OR by asking user) -- Who is the target audience? -- What is the brand personality or tone? -- Are there existing design tokens, colors, or fonts to use? - -### Step 3: If ANY question is unclear, STOP and ask -If you cannot confidently answer ALL three questions from the codebase, ask the user directly to clarify what you cannot infer. Do NOT proceed to design work until all three are answered. Guessing leads to generic AI slop. - ---- - -**Only after completing the above, proceed to design work below.** - ---- - ## Design Direction Commit to a BOLD aesthetic direction: diff --git a/dist/cursor/.cursor/skills/frontend-design/SKILL.md b/dist/cursor/.cursor/skills/frontend-design/SKILL.md index 23fd2d561..d49fe3c77 100644 --- a/dist/cursor/.cursor/skills/frontend-design/SKILL.md +++ b/dist/cursor/.cursor/skills/frontend-design/SKILL.md @@ -6,27 +6,6 @@ license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md f 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. -## MANDATORY: Context Gathering (Do This First) - -Before ANY design work, complete these steps in order: - -### Step 1: Scan the codebase for context -Search for and read: README, brand guidelines, design tokens, existing components, style files, color variables. - -### Step 2: Answer these questions (from codebase OR by asking user) -- Who is the target audience? -- What is the brand personality or tone? -- Are there existing design tokens, colors, or fonts to use? - -### Step 3: If ANY question is unclear, STOP and ask -If you cannot confidently answer ALL three questions from the codebase, ask the user directly to clarify what you cannot infer. Do NOT proceed to design work until all three are answered. Guessing leads to generic AI slop. - ---- - -**Only after completing the above, proceed to design work below.** - ---- - ## Design Direction Commit to a BOLD aesthetic direction: diff --git a/dist/gemini-prefixed/.gemini/skills/frontend-design/SKILL.md b/dist/gemini-prefixed/.gemini/skills/frontend-design/SKILL.md index 84fdd14df..8df063fbb 100644 --- a/dist/gemini-prefixed/.gemini/skills/frontend-design/SKILL.md +++ b/dist/gemini-prefixed/.gemini/skills/frontend-design/SKILL.md @@ -5,27 +5,6 @@ description: Create distinctive, production-grade frontend interfaces with high 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. -## MANDATORY: Context Gathering (Do This First) - -Before ANY design work, complete these steps in order: - -### Step 1: Scan the codebase for context -Search for and read: README, brand guidelines, design tokens, existing components, style files, color variables. - -### Step 2: Answer these questions (from codebase OR by asking user) -- Who is the target audience? -- What is the brand personality or tone? -- Are there existing design tokens, colors, or fonts to use? - -### Step 3: If ANY question is unclear, STOP and ask -If you cannot confidently answer ALL three questions from the codebase, ask the user directly to clarify what you cannot infer. Do NOT proceed to design work until all three are answered. Guessing leads to generic AI slop. - ---- - -**Only after completing the above, proceed to design work below.** - ---- - ## Design Direction Commit to a BOLD aesthetic direction: diff --git a/dist/gemini/.gemini/skills/frontend-design/SKILL.md b/dist/gemini/.gemini/skills/frontend-design/SKILL.md index 84fdd14df..8df063fbb 100644 --- a/dist/gemini/.gemini/skills/frontend-design/SKILL.md +++ b/dist/gemini/.gemini/skills/frontend-design/SKILL.md @@ -5,27 +5,6 @@ description: Create distinctive, production-grade frontend interfaces with high 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. -## MANDATORY: Context Gathering (Do This First) - -Before ANY design work, complete these steps in order: - -### Step 1: Scan the codebase for context -Search for and read: README, brand guidelines, design tokens, existing components, style files, color variables. - -### Step 2: Answer these questions (from codebase OR by asking user) -- Who is the target audience? -- What is the brand personality or tone? -- Are there existing design tokens, colors, or fonts to use? - -### Step 3: If ANY question is unclear, STOP and ask -If you cannot confidently answer ALL three questions from the codebase, ask the user directly to clarify what you cannot infer. Do NOT proceed to design work until all three are answered. Guessing leads to generic AI slop. - ---- - -**Only after completing the above, proceed to design work below.** - ---- - ## Design Direction Commit to a BOLD aesthetic direction: diff --git a/source/skills/frontend-design/SKILL.md b/source/skills/frontend-design/SKILL.md index 056594fd2..d0c1173ca 100644 --- a/source/skills/frontend-design/SKILL.md +++ b/source/skills/frontend-design/SKILL.md @@ -6,27 +6,6 @@ license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md f 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. -## MANDATORY: Context Gathering (Do This First) - -Before ANY design work, complete these steps in order: - -### Step 1: Scan the codebase for context -Search for and read: README, brand guidelines, design tokens, existing components, style files, color variables. - -### Step 2: Answer these questions (from codebase OR by asking user) -- Who is the target audience? -- What is the brand personality or tone? -- Are there existing design tokens, colors, or fonts to use? - -### Step 3: If ANY question is unclear, STOP and ask -If you cannot confidently answer ALL three questions from the codebase, {{ask_instruction}} Do NOT proceed to design work until all three are answered. Guessing leads to generic AI slop. - ---- - -**Only after completing the above, proceed to design work below.** - ---- - ## Design Direction Commit to a BOLD aesthetic direction: