Tools for the design team
Review errors −30%, research coverage 98%, knowledge-sharing ×3.
Today I'd do it this way
Today, rolling out tools to a design team isn't three months of gathering requirements, defending and purchasing. It's one skill that assembles the discovery process into three layers and hands the designer a tailored reference pack in minutes, not days.
design-discovery
ShippedA three-layer discovery helper — final moodboard from your picks, not auto-curation.
$ npx skills add mmkeewa/design-discovery- Layer 1 — Patterns. Mobbin, PageFlows, Liba, Benchmarkee. 5–7 relevant examples, you pick by number
- Layer 2 — Visual. Awwwards, Godly, Screen Gallery, FPS60. Visual language and motion in one doc
- Layer 3 — Mood. Pinterest, Behance, Dribbble, UI8. Optional, around your already-locked direction
How it was done then
Summary
Full version available in Russian. Read in Russian →
Designers were spending disproportionate time on discovery — pattern recall, gallery browsing, moodboarding — before they could even start designing. With deadlines burning, research and testing got squeezed out. Everyone improvised, no shared tooling, no compounding knowledge.
I mapped where time actually leaked across the brief→ship path. Then ran sessions to pick a focused toolset (Mobbin for UX patterns, AI tools for product/graphic work, dedicated inspiration galleries), defended the budget, set up onboarding and guides for PMs and designers.
After three months of rollout: review errors −30%, research coverage 98%, knowledge-sharing initiatives ×3. The team shifted from "ship fast" to "ship well".
What I'd do differently today
I wouldn't spend three months gathering requirements and defending purchases. I'd build one skill that does what we did with a SaaS stack — but faster, and tuned to each designer. SaaS gives an averaged tool and a dozen tabs to switch between. A skill is a lever the team configures around its own flows in one evening: one query, three reference layers on the table.