菜单
Set up and manage a UI redesign experiment with three git worktree branches for modern minimal, bold creative, and classic refined design directions. Use when asked to run a UI redesign experiment, compare design approaches, or prototype multiple visual directions in parallel branches.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | ui-redesign |
| description | Set up and manage a UI redesign experiment with three git worktree branches for modern minimal, bold creative, and classic refined design directions. Use when asked to run a UI redesign experiment, compare design approaches, or prototype multiple visual directions in parallel branches. |
First, create 3 git worktree branches from the current main branch:
ui-redesign-modern-minimalui-redesign-bold-creativeui-redesign-classic-refinedSet up the worktree structure:
git worktree add ../project-modern-minimal ui-redesign-modern-minimal
git worktree add ../project-bold-creative ui-redesign-bold-creative
git worktree add ../project-classic-refined ui-redesign-classic-refined
Design Directions for Each Branch Branch 1: Modern Minimal (ui-redesign-modern-minimal) Work in ../project-modern-minimal
Design Philosophy: Clean, minimalist, lots of whitespace Color Palette: Monochromatic with one accent color Typography: Sans-serif, limited font weights Components: Flat design, subtle shadows, micro-interactions Focus: Maximum usability and clarity
Branch 2: Bold Creative (ui-redesign-bold-creative) Work in ../project-bold-creative
Design Philosophy: Vibrant, experimental, attention-grabbing Color Palette: Bold gradients, contrasting colors Typography: Mix of fonts, creative text treatments Components: 3D elements, animations, glassmorphism Focus: Memorable user experience and visual impact
Branch 3: Classic Refined (ui-redesign-classic-refined) Work in ../project-classic-refined
Design Philosophy: Timeless, professional, trustworthy Color Palette: Traditional color schemes, navy/gold/cream Typography: Serif fonts for headers, clean sans for body Components: Card-based layouts, subtle borders, traditional patterns Focus: Professional appearance and accessibility
Implementation Tasks for Each Branch For each design direction, implement these changes:
Update the main color scheme and CSS variables Redesign the homepage/landing page Update the navigation menu style Redesign at least 2 key components (buttons, cards, forms, etc.) Create a style guide document showing the design system Update any relevant documentation
Working Process
Start with branch 1, make all changes, commit with clear messages Move to branch 2, repeat the process Move to branch 3, complete the redesign After all three are complete, create a comparison document
Final Deliverable Create a COMPARISON.md file in the main branch that includes:
Screenshots of each design approach Pros and cons of each approach Performance metrics if applicable Recommendation for which design to move forward with
Please proceed with this setup and implementation. Start by creating the worktree branches and confirming they're set up correctly, then begin with the Modern Minimal design.
XP-style plan review that identifies gaps, hidden assumptions, and critical misses. Triggers on 'review the plan', 'check the plan', 'audit the plan'. Reviews plans for YAGNI violations, missing feedback loops, and over-engineering.
Comprehensive code review for quality, security, performance. Triggers on 'review code', 'code review', 'check this PR', 'audit code'.
TDD Production Code Refactoring Process. Triggers on 'tidy up', 'tidy this', 'clean up code'. Use for refactoring production code with test coverage.
Systematically explore an unfamiliar codebase and build a reusable architecture summary. Use for repo onboarding, understanding legacy or inherited code, mapping architecture before a migration or refactor, tracing a bug or feature path, or answering "what does this project do?". Documentation-first, then data flow — ends in a concise technical architecture summary with file:line evidence, not a raw file dump.
Compile deep repository evidence into artifact-bound correctness doctrine — authority/law/proof maps, owned invariants, failure archaeology, and the strongest durable destination for each piece of knowledge, plus an optional minimal repository-specific skill portfolio. Use when the user wants both deep codebase understanding AND durable doctrine, knowledge routing, or repo-specific skill recommendations. Research discoverable facts before asking. Read-only. Not for quick onboarding, one isolated invariant, ordinary implementation, generic review, or direct skill creation.
Run a targeted fresh-eyes blunder pass over code, specs, plans, reviews, closure gates, or skill edits. Use when asked to reread with fresh eyes, find obvious bugs, catch mistakes/oversights/omissions, check for embarrassing misses, or do a second independent pass before closure. Use it as the final falsification/check pass for another workflow, not as a substitute for implementation or verification.