Playful Design Router

One skill that knows the others. Read the request, decide which design skills apply, and use them in a sensible order. Curated by Playful Design (playfuldesign.app/skills).

1. See what is installed

Before routing, check which of these skills are present. Look in .claude/skills/, .agents/skills/ and .cursor/skills/ in the project, and the same folders under ~/. Only route to skills that exist. If a skill would clearly help but is missing, say so once and give its install command from the table at the end. Do not install anything without asking.

2. Always on (standards)

Apply these to every interface change. They do not need to be named:

• scope: change exactly what was asked, keep what worked, finish every item.
• restraint: ship the smallest thing that does the job; delete what nobody asked for.
• reuse: the project's own components first, then a maintained library, then a native feature.
• copy: short, plain interface labels.
• defaults: house defaults for focus, forms, loading, dialogs, scroll edges and type.
• color: contrast held to exact ratios, colour through role tokens, a real dark palette.
• motion or emil-design-eng: what animates, easing, durations, springs and reduced motion. If both are installed, use emil-design-eng for animation decisions and motion for house numbers.