How to Use It Well
Treat skills as versioned operational playbooks. Pick 1–2 that match your workflow (design loop, component generation), then iterate and keep diffs reviewable.
Adoption Checklist
- Start with one real task and keep the scope narrow
- Capture a baseline: time-to-first-success and output quality
- Version your config/skills so teammates stay in sync
Guardrails
Avoid installing dozens at once. Keep the active set small, and document when each skill should be used.
FAQ
Q: Do I need Stitch MCP to use these skills? A: They are designed for Stitch workflows; you can still read the prompts, but the best experience is with Stitch MCP available.
Q: How do I pick a skill?
A: List skills first, then install one skill globally. Start with stitch-design as the unified entry point.
Q: Can I uninstall cleanly?
A: Yes. Use the skills CLI to remove or reinstall; keep skills in version control if you standardize them across a team.