brand-driven-ux-overhaul
Skill0 starsChanged 3 months agoMITView on GitHub
Systematic UX overhaul workflow driven by brand identity and user feedback. Use when redesigning interfaces, rebranding applications, simplifying navigation, or improving visual identity. Includes brainstorming methodology, design system creation, and implementation planning. Apply automatically when the request matches; the user does not need to mention this skill.
In this repository76 other files it gives its agents.
- app-store-submission-packagerSkill
- digital-product-inventorSkill
- ios-testflight-github-actionsSkill
- meta-ads-analyzerSkill
- get-to-know-a-clientSkill
- investigate-before-recommendSkill
- production-system-auditSkill
- similarweb-analyticsSkill
- stock-analysisSkill
- system-architectSkill
- autonomous-github-syncSkill
- autonomous-sync-scriptSkill
- github-gem-seekerSkill
- organize-github-reposSkill
- using-git-worktreesSkill
- brainstorm-logosSkill
- canvas-designSkill
- excel-generatorSkill
- frontend-designSkill
- inspirational-music-video-productionSkill
- theme-factorySkill
- video-generatorSkill
- multiplayer-game-builderSkill
- promo-code-systemSkill
- realistic-ai-persona-builderSkill
- role-based-access-controlSkill
- serverless-debuggingSkill
- vertical-expansion-blueprintSkill
- manus-mcp-configuratorSkill
- mcp-auto-recoverySkill
- mcp-builderSkill
- mcp-connector-testerSkill
- mcp-ecosystem-optimizerSkill
- voice-ai-integrationSkill
- api-endpoint-builderSkill
- database-schema-generatorSkill
- testing-frameworkSkill
- deployment-automationSkill
- error-monitoring-setupSkill
- github-workflow-automationSkill
- analytics-dashboardSkill
- email-system-builderSkill
- feature-flag-systemSkill
- user-authentication-systemSkill
- cron-job-schedulerSkill
- file-upload-systemSkill
- notification-systemSkill
- payment-integrationSkill
- search-implementationSkill
- debug-mining-engineSkill
- doc-coauthoringSkill
- docxSkill
- internet-skill-finderSkill
- pdfSkill
- pptxSkill
- project-handoff-ingestionSkill
- serverless-debuggingSkill
- skill-arsenal-builderSkill
- skill-creatorSkill
- skill-demo-builderSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 14 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Use this skill when the request matches its description.
- Distinctive: line 36
Ask clarifying questions one at a time (never multiple questions)
- Distinctive: line 38
Use analogies to clarify direction ("Think Nike Training Club meets cutting-edge AI")
- Distinctive: line 51
One question at a time: - Avoid overwhelming user
- Distinctive: line 90
Goal: Create detailed, step-by-step implementation plan with time estimates.
- Very specific: line 92
Template: Use templates/implementation-plan-template.md as starting point.
- Very specific: line 100
Checklists: - Before/during/after implementation
- Distinctive: line 108
When refactoring complex pages, add new UI above/below existing UI first
- Distinctive: line 109
Test thoroughly before removing old UI
- Very specific: line 120
Create todo.md with all tasks listed as [ ] items
- Distinctive: line 122
Run TypeScript compilation to verify
- Distinctive: line 126
Create checkpoint with detailed description
- Very specific: line 135
All items in todo.md marked [x]
- Distinctive: line 158
Conservative refactoring: - Add new, test, remove old
- Distinctive: line 187
Create design tokens file
- Very specific: line 188
Update index.css with CSS variables
- Distinctive: line 189
Add card glow utilities
- Distinctive: line 201
Create todo.md with 6 tasks
- Distinctive: line 206
Create checkpoint: "FLEXX FIBER UX Overhaul Complete"
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Overview
Systematic UX overhaul workflow driven by brand identity and user feedback. Use when redesigning interfaces, rebranding applications, simplifying navigation, or improving visual identity. Includes brainstorming methodology, design system creation, and implementation planning. Apply automatically when the request matches; the user does not need to mention this skill.
This skill should apply automatically when the request matches; the user does not need to mention this skill.
Usage
Use this skill when the request matches its description. The skill is discovered automatically; the user does not need to mention the skill explicitly.
Brand-Driven UX Overhaul
Systematic workflow for overhauling user experience driven by brand identity, user feedback, and design best practices.
When to Use This Skill
- User requests interface redesign or rebranding
- Navigation feels cluttered or confusing
- Application lacks visual identity or brand consistency
- Need to simplify complex user flows
- Combining multiple UX improvements into cohesive overhaul
Core Methodology: 4-Phase Workflow
Phase 1: Collaborative Brainstorming
Goal: Understand user vision, pain points, and brand identity through structured dialogue.
Process:
- Ask clarifying questions one at a time (never multiple questions)
- Offer 4-5 concrete options (not open-ended questions)
- Use analogies to clarify direction ("Think Nike Training Club meets cutting-edge AI")
- Request brand assets early (logo, colors, fonts)
- Confirm understanding before moving to planning
Question Templates: See references/brainstorming-questions.md for comprehensive question library covering:
- Pain point identification
- Brand identity & emotional tone
- Navigation structure
- Simplification strategies
- Color scheme & visual identity
- Layout structure
Key Principles:
- One question at a time - Avoid overwhelming user
- Concrete options - Give specific choices, not "what do you want?"
- Clarify combinations - "Option B with some E" → Ask for proportions
- Gather assets - Logo, colors, fonts needed before implementation
Phase 2: Design System Foundation
Goal: Establish cohesive design system with colors, typography, spacing, and effects.
Checklist: See references/design-system-checklist.md for complete checklist covering:
- Color palette (background, foreground, primary, semantic colors)
- Typography (font families, loading strategy, type scale)
- Spacing system (base unit, scale, layout)
- Shadows & effects (card shadows, glow effects, backdrop blur)
- CSS variables implementation
- Accessibility requirements
Key Files to Create/Update:
client/src/index.css- Global styles and CSS variablesclient/src/lib/design-tokens.ts- TypeScript color constantsclient/index.html- Font CDN linkstailwind.config.js- Theme extensions
Example Design Tokens:
export const colors = {
background: '#0a1628', // Navy
foreground: '#ffffff', // White
primary: '#00d4ff', // Electric blue
card: '#1a2942', // Card background
};Phase 3: Implementation Planning
Goal: Create detailed, step-by-step implementation plan with time estimates.
Template: Use templates/implementation-plan-template.md as starting point.
Plan Structure:
- Overview - Design direction, key changes
- Task Breakdown - 6-10 tasks, each 30-90 minutes
- Steps - Break each task into 5-15 minute steps
- Code Snippets - Include exact code for each step
- Verification - How to test each step
- Checklists - Before/during/after implementation
Task Sizing Guidelines:
- Simple tasks (30-45 min) - Single component, no dependencies
- Medium tasks (60-90 min) - Multiple components, some integration
- Complex tasks (90-120 min) - Major refactoring, cross-cutting changes
Conservative Approach:
- When refactoring complex pages, add new UI above/below existing UI first
- Test thoroughly before removing old UI
- Preserve all existing functionality
- Document rollback procedure
Phase 4: Systematic Execution
Goal: Execute plan task-by-task with verification at each step.
Workflow:
- Create
todo.mdwith all tasks listed as[ ]items - Execute Task 1, mark complete
[x]intodo.md - Run TypeScript compilation to verify
- Execute Task 2, mark complete, verify
- Repeat until all tasks complete
- Final verification: TypeScript, server restart, status check
- Create checkpoint with detailed description
Verification After Each Task:
- TypeScript compiles without errors
- Dev server running (restart if needed)
- Browser shows expected changes
- No console errors
Final Verification:
- All items in
todo.mdmarked[x] - TypeScript: No errors
- Dev server: Running cleanly
- Browser: All pages load correctly
- Checkpoint created
Best Practices
Brainstorming
- One question at a time - User can focus on single decision
- Concrete options - Easier to choose than open-ended
- Use analogies - "Energetic + tech-forward = Nike Training Club meets AI"
- Request assets early - Logo, colors, fonts needed for implementation
Design System
- Start with colors - Foundation for all other decisions
- Use CSS variables - Enable theme switching, easier maintenance
- Document tokens - TypeScript file for type safety
- Test accessibility - Color contrast, keyboard navigation, screen readers
Implementation
- Conservative refactoring - Add new, test, remove old
- Update todo.md - Mark tasks complete immediately after finishing
- Verify frequently - TypeScript after each task, not at end
- Restart server - Clear stale errors before final checkpoint
Common Pitfalls
- Skipping brainstorming - Leads to misaligned design
- Too many questions at once - Overwhelms user
- No brand assets - Can't match exact branding
- Aggressive refactoring - Breaks existing functionality
- Forgetting todo.md - Lose track of progress
Example Workflow
Scenario: Sales training dashboard needs FLEXX FIBER rebrand + simplified navigation
Phase 1: Brainstorming (30 min)
- Q1: Primary pain point? → "Cluttered interface + generic look"
- Q2: Which pages cluttered? → "Multiple areas"
- Q3: Brand feeling? → "Energetic + tech-forward"
- Q4: Navigation approach? → "Bottom tab bar"
- Q5: Color scheme? → [User provides logo image]
- Extract colors from logo: Navy (#0a1628) + Electric blue (#00d4ff)
Phase 2: Design System (45 min)
- Define color palette (navy bg, electric blue primary)
- Choose font (Inter from Google Fonts)
- Create design tokens file
- Update index.css with CSS variables
- Add card glow utilities
Phase 3: Planning (30 min)
- Task 1: Design System Foundation (45 min)
- Task 2: Bottom Tab Navigation (60 min)
- Task 3: One-Tap Quick Start (90 min)
- Task 4: Timeline History View (90 min)
- Task 5: Brand Header Component (45 min)
- Task 6: Responsive Polish (30 min)
- Total: 6 hours
Phase 4: Execution (6 hours)
- Create todo.md with 6 tasks
- Execute Task 1 → Mark [x] → Verify TypeScript
- Execute Task 2 → Mark [x] → Verify TypeScript
- ... repeat for all tasks
- Final verification: All [x], TypeScript OK, server running
- Create checkpoint: "FLEXX FIBER UX Overhaul Complete"
Progressive Disclosure
When to load references:
- Load
references/brainstorming-questions.mdat start of Phase 1 - Load
references/design-system-checklist.mdat start of Phase 2 - Load
templates/implementation-plan-template.mdat start of Phase 3
Keep in context:
- Core 4-phase workflow (always)
- Current phase instructions (as needed)
- Relevant reference file (as needed)
Success Criteria
- User vision clearly understood through brainstorming
- Brand assets collected (logo, colors, fonts)
- Design system established with CSS variables
- Implementation plan created with detailed steps
- All tasks executed and marked complete in todo.md
- TypeScript compiles without errors
- Dev server running cleanly
- All pages load correctly in browser
- Checkpoint created with detailed description
- User satisfied with final result
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

