Automated summary
A workflow guide for systematically improving the design of a personal website (Tailwind, Framer Motion, Vercel deploy) against a predefined color palette and typographic hierarchy.
Strengths
- Clear six-step workflow from analysis to commit, with reusable checklists
- CARIO format (context, problems, options, recommendation, impact) forces tiered effort estimates before any edit
- Concrete before/after JSX and Tailwind snippets that can be copied directly
- Palette, typography and responsive breakpoints are explicitly defined, limiting visual drift
Limitations
- Tightly coupled to one project: slate/coral/cream palette, Tailwind, Framer Motion and automatic Vercel deploys
- No accessibility checks (contrast, text sizing) and no automated visual regression testing
- The file is truncated (card-grid example cuts off) and only covers four page types
Use it when a page of a Tailwind/Framer Motion personal site looks off and you want a structured design pass that stays consistent with the existing brand.
Avoid it on projects using a different CSS stack or brand, or when the task is a full visual identity redesign rather than polishing what exists.
Security analysis
SafeThe skill is a design/CSS guidance document for a Next.js + Tailwind + Framer Motion personal site. Its executable surface is limited to standard npm and git commands, it explicitly requires user confirmation before making changes, and it contains no network exfiltration, destructive filesystem operations, or obfuscation. Bash usage is powerful but scoped to legitimate build/version-control tasks, so the risk is low.
- •Includes `git add . && git commit && git push` steps that auto-deploy to Vercel; scope of `git add .` could sweep unrelated files into a commit, but this is a normal dev workflow rather than a malicious action
- •Bash is used for `npm run dev`, `npm run build`, and git commands — legitimate, non-destructive purposes
- •No curl|sh, no credential/secret handling, no obfuscated payloads, no rm -rf or safety-disabling instructions
Examples
我的首頁排版很醜,間距不一致,顏色也很亂,幫我按照專案的設計原則改善。The projects page card grid breaks on tablet. Improve the layout mobile-first with Tailwind breakpoints and add subtle Framer Motion animations.Improve the hero section on the About page: better typographic hierarchy, gradient background, and a smooth entrance animation, then verify at 375px, 768px and 1280px.name: design-improvement description: | Systematic design optimization for young-personal-site following established design principles. Ensures consistent color palette, responsive layout, and professional appearance. activation-keywords: [設計, design, UI, UX, 很醜, 不好看, 排版, layout, 顏色, color, 間距, spacing] priority: high allowed-tools: [Read, Edit, Write, Bash, Grep, Glob]
Design Improvement Skill
Purpose
Streamline design optimization with systematic improvements following project design principles.
Prevents: Inconsistent design, broken responsive layouts, brand violations Ensures: Color palette consistency, mobile-first responsive design, professional appearance
Design Principles
Color Palette
Primary: slate-blue (#475569, #64748b)
Accent: coral-orange (#fb923c, #f97316)
Background: warm-cream (#fef3c7, #fef9c3)
Gradients: Smooth transitions for visual interest
Typography
Hierarchy: h1 > h2 > h3 > p (clear distinction)
Body text: 16px+ for readability
Line-height: Consistent spacing
Hero sections: Center-aligned
Layout
Approach: Mobile-first responsive
Spacing: Tailwind utilities (p-4, gap-6, etc.)
Animations: Framer Motion (smooth, not jarring)
Workflow
1. Analyze Current Design
Issues Checklist:
- [ ] Color consistency problems?
- [ ] Layout/alignment issues?
- [ ] Typography hierarchy unclear?
- [ ] Spacing inconsistent?
- [ ] Responsive breakpoints broken?
- [ ] Animations missing/excessive?
2. Propose Improvements (CARIO)
📋 Context:
- Page: [Home/Projects/About/Speaking]
- Current state: [description]
- Issue: [what looks bad]
❓ Problems:
1. [Color inconsistency]
2. [Poor spacing]
3. [Weak hierarchy]
🎯 Options:
A. Minor tweaks (15 min, low impact)
B. Moderate redesign (30-45 min, medium impact)
C. Major overhaul (1-2 hours, high impact)
💡 Recommendation: [Option B]
- Changes: [color X→Y, spacing p-4→p-6, add gradient]
- Reasoning: [balances improvement vs time]
⚡ Impact:
- Files: [list]
- Testing: [responsive + visual]
3. Get User Confirmation
Identified [N] design improvements for [Page] page:
1. [Change 1]
2. [Change 2]
3. [Change 3]
Proceed with these improvements?
4. Implement Changes
Checklist:
- [ ] Update Tailwind classes
- [ ] Ensure responsive (sm:, md:, lg: breakpoints)
- [ ] Add/update Framer Motion animations
- [ ] Maintain color palette
- [ ] Follow typography hierarchy
Example:
// Before
<div className="p-4 bg-white">
<h1 className="text-2xl">Title</h1>
</div>
// After
<div className="p-6 md:p-8 bg-gradient-to-br from-warm-cream to-white">
<h1 className="text-3xl md:text-4xl font-bold text-slate-700 text-center mb-6">
Title
</h1>
</div>
5. Test Responsive Design
npm run dev
# Test at: Mobile (375px), Tablet (768px), Desktop (1280px)
Visual checklist:
- [ ] Mobile (< 640px): Readable, no overflow
- [ ] Tablet (640-1024px): Proper spacing
- [ ] Desktop (> 1024px): Optimal layout
- [ ] Animations: Smooth (60fps)
6. Commit and Deploy
npm run build # Verify
git add .
git commit -m "style: improve [page] design with better spacing and colors"
git push # Auto-deploys to Vercel
Common Improvements
Hero Section Enhancement
// Before: Basic section
<section className="py-12">
<h1 className="text-3xl">Welcome</h1>
</section>
// After: Enhanced with gradient + animation
<section className="py-16 md:py-24 bg-gradient-to-br from-warm-cream via-white to-blue-50">
<motion.div initial={{ opacity: 0, y: 20 }} animate={{ opacity: 1, y: 0 }}>
<h1 className="text-4xl md:text-5xl lg:text-6xl font-bold bg-gradient-to-r from-slate-600 to-slate-800 bg-clip-text text-transparent mb-6">
Welcome
</h1>
</motion.div>
</section>
Card Grid Optimization
// Before: Fixed 3-column grid
<div className="grid grid-cols-3 gap-4">
{projects.map(p => <Card {...p} />)}
</div>
// After: Responsive grid with hover animation
<div className="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-6 md:gap-8">
{projects.map(p => (
<motion.div whileHover={{ scale: 1.03 }}>
<Card {...p} />
</motion.div>
))}
</div>
Typography Hierarchy
// Before: Flat hierarchy
<h1>Title</h1>
<p>Body text</p>
// After: Clear hierarchy
<h1 className="text-4xl md:text-5xl font-bold text-slate-800 mb-4 leading-tight">
Title
</h1>
<p className="text-base md:text-lg text-slate-600 leading-relaxed max-w-prose">
Body text
</p>
Quality Checklist
Before committing:
Visual:
- [ ] Colors match palette (slate-blue, coral-orange, warm-cream)
- [ ] Spacing consistent (4px increments: p-4, p-6, p-8)
- [ ] Typography hierarchy clear
- [ ] Contrast WCAG AA (4.5:1 for text)
Responsive:
- [ ] Mobile (< 640px): Works
- [ ] Tablet (640-1024px): Optimized
- [ ] Desktop (> 1024px): Polished
- [ ] No horizontal scroll
- [ ] Touch targets ≥ 44px (mobile)
Performance:
- [ ] Animations smooth (60fps)
- [ ] No layout shift (CLS < 0.1)
- [ ] Next.js Image component used
Consistency:
- [ ] Matches existing pages' style
- [ ] Follows Tailwind conventions
- [ ] Framer Motion patterns consistent
- [ ] Bilingual support maintained
Anti-Patterns
❌ Breaking Responsive
// Bad: Fixed width
<div className="w-[1200px]">Content</div>
// Good: Responsive width
<div className="w-full max-w-7xl mx-auto px-4">Content</div>
❌ Inconsistent Colors
// Bad: Random colors
<div className="bg-red-500 text-purple-700">Content</div>
// Good: Follow palette
<div className="bg-warm-cream text-slate-700">Content</div>
❌ Poor Typography
// Bad: Unreadable
<p className="text-xs">Important content</p>
// Good: Readable
<p className="text-base md:text-lg">Important content</p>
Quick Reference
Spacing Scale
p-4 = 16px p-8 = 32px
p-6 = 24px p-12 = 48px
Typography Scale
text-base = 16px text-2xl = 24px text-4xl = 36px
text-lg = 18px text-3xl = 30px text-5xl = 48px
Responsive Breakpoints
sm: ≥ 640px (mobile landscape)
md: ≥ 768px (tablet)
lg: ≥ 1024px (desktop)
xl: ≥ 1280px (large desktop)
Integration
- content-update: Content + design updates together
- deploy-check: Pre-deployment design verification
Version: v1.1 | Updated: 2025-12-31 Project: young-personal-site Philosophy: "Design is not just what it looks like. Design is how it works." - Steve Jobs
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/systematic-design-improvement-mmbizjt9/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/systematic-design-improvement-mmbizjt9' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/systematic-design-improvement-mmbizjt9/download' --output '.skill-downloads/systematic-design-improvement-mmbizjt9/SKILL.md.part' && mv '.skill-downloads/systematic-design-improvement-mmbizjt9/SKILL.md.part' '.skill-downloads/systematic-design-improvement-mmbizjt9/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Quick Reference
Spacing Scale
p-4 = 16px p-8 = 32px
p-6 = 24px p-12 = 48px
Typography Scale
text-base = 16px text-2xl = 24px text-4xl = 36px
text-lg = 18px text-3xl = 30px text-5xl = 48px
Responsive Breakpoints
sm: ≥ 640px (mobile landscape)
md: ≥ 768px (tablet)
lg: ≥ 1024px (desktop)
xl: ≥ 1280px (large desktop)
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/systematic-design-improvement-mmbizjt9/SKILL.md' && test -s '.skill-downloads/systematic-design-improvement-mmbizjt9/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/design-improvement' && cp -R '.skill-downloads/systematic-design-improvement-mmbizjt9' '.claude/skills/design-improvement'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/systematic-design-improvement-mmbizjt9'openskills read 'systematic-design-improvement-mmbizjt9'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/systematic-design-improvement-mmbizjt9/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.