bruno/dss

Files

Digital Production Factory 276ed71f31 Initial commit: Clean DSS implementation

Migrated from design-system-swarm with fresh git history.
Old project history preserved in /home/overbits/apps/design-system-swarm

Core components:
- MCP Server (Python FastAPI with mcp 1.23.1)
- Claude Plugin (agents, commands, skills, strategies, hooks, core)
- DSS Backend (dss-mvp1 - token translation, Figma sync)
- Admin UI (Node.js/React)
- Server (Node.js/Express)
- Storybook integration (dss-mvp1/.storybook)

Self-contained configuration:
- All paths relative or use DSS_BASE_PATH=/home/overbits/dss
- PYTHONPATH configured for dss-mvp1 and dss-claude-plugin
- .env file with all configuration
- Claude plugin uses ${CLAUDE_PLUGIN_ROOT} for portability

Migration completed: $(date)
🤖 Clean migration with full functionality preserved

2025-12-09 18:45:48 -03:00

2.9 KiB

Raw Blame History

name, description, arguments

name

description

arguments

dss-quick-wins

Find quick win opportunities for design system adoption

name	description	required
path	Path to project directory	false

DSS Quick Wins Command

Find low-effort, high-impact opportunities for design system adoption.

Usage

/dss-quick-wins [path]

Examples:

/dss-quick-wins
/dss-quick-wins ./src

What This Does

Analyzes Codebase
- Scans styles and components
- Identifies patterns
- Measures usage frequency
Finds Opportunities
- Color consolidation
- Spacing standardization
- Typography cleanup
- Border radius normalization
- Shadow standardization
Scores by Impact/Effort
- Calculates potential impact
- Estimates implementation effort
- Ranks by ROI
Generates Recommendations
- Prioritized list
- Specific actions
- Expected outcomes

Instructions for Claude

When the user runs this command:

Use dss_find_quick_wins tool with path
Present quick wins in priority order
For each quick win, show:
- Category (colors, spacing, etc.)
- Impact level (high/medium/low)
- Effort level (high/medium/low)
- Specific values to consolidate
- Files affected
Provide total time estimate
Offer to implement top quick wins

Example Output

Quick Win Analysis: /path/to/project

TOP QUICK WINS

1. COLOR CONSOLIDATION
   Impact: HIGH | Effort: LOW

   Found 47 color values reducible to 8 tokens
   Files affected: 23

   Consolidate:
   #0066cc, #0067cd, #0065cb -> primary
   #6c757d, #6b747c, #6d767e -> secondary

   Estimated time: 2 hours

2. SPACING STANDARDIZATION
   Impact: HIGH | Effort: LOW

   Found 34 spacing values reducible to 6 tokens
   Files affected: 31

   Consolidate to 4px grid:
   4px, 8px, 16px, 24px, 32px, 48px

   Estimated time: 3 hours

3. BORDER RADIUS NORMALIZATION
   Impact: MEDIUM | Effort: LOW

   Found 12 radius values reducible to 4 tokens
   Files affected: 15

   Consolidate:
   2px (sm), 4px (md), 8px (lg), 16px (xl)

   Estimated time: 1 hour

4. SHADOW CLEANUP
   Impact: MEDIUM | Effort: LOW

   Found 8 shadow definitions reducible to 3 tokens
   Files affected: 12

   Consolidate:
   sm: 0 1px 2px rgba(0,0,0,0.05)
   md: 0 4px 6px rgba(0,0,0,0.1)
   lg: 0 10px 15px rgba(0,0,0,0.1)

   Estimated time: 1 hour

5. FONT SIZE SCALE
   Impact: HIGH | Effort: MEDIUM

   Found 15 font sizes reducible to 7 tokens
   Files affected: 28

   Consolidate to type scale:
   12px, 14px, 16px, 18px, 24px, 32px, 48px

   Estimated time: 3 hours

SUMMARY

Total quick wins: 5
Total estimated time: 10 hours
Expected impact: 60% reduction in style inconsistency

RECOMMENDED ORDER

1. Colors (biggest impact)
2. Spacing (most widespread)
3. Border radius (quick win)
4. Shadows (contained scope)
5. Font sizes (needs coordination)

Ready to implement? I can create tokens for any of these.

2.9 KiB Raw Blame History