Investigate UI-UX-PRO-MAX skill for installation flow

[nille]

Overview

Investigate whether UI-UX-PRO-MAX skill should be included in shipkit installation flow.

Description from site: "Searchable database of UI styles, color palettes, font pairings, chart types, and UX guidelines for Claude Code skill."

Questions to Answer

1. What does it do?

   • Review the skill definition and capabilities
   • What UI/UX tasks does it automate?
   • How does it differ from existing skills?
   • Is it just a reference database or interactive tooling?

2. Quality assessment:

   • Is it well-maintained?
   • Does it follow Agent Skills standard?
   • Is it battle-tested or experimental?
   • Who built it (credibility)?

3. Where does it belong in shipkit?

   • Core (everyone needs it)?
   • Experimental (new, unproven)?
   • Advanced (specialized for UI/UX devs)?
   • Marketplace (opt-in plugin)?

4. Installation strategy:

   • Include in default /install flow?
   • Add to Advanced layer for frontend devs?
   • Offer during layer selection?
   • Keep as marketplace plugin only?

5. Dependencies:

   • Does it require specific MCP servers?
   • Does it need particular tools installed?
   • Any API keys or configuration?
   • Database or web service?

Recommendation Format

After investigation, provide recommendation:

Recommendation: [Core / Experimental / Advanced / Marketplace]

Rationale:
- [Why it belongs there]
- [Who benefits]
- [Setup complexity]

Implementation:
- [What files to modify]
- [How to integrate with install flow]

Related Decisions

Similar to how we handle:

• Browser automation (Advanced layer, opt-in)
• MCP servers (offered during install, user chooses)
• Experimental skills (user opts in with --with-experimental)

Should UI-UX skill follow similar pattern, or is it universally valuable enough for Core?

Next Steps

1. Review the skill thoroughly
2. Test it in a real project
3. Assess quality and maintenance
4. Decide on layer placement
5. Integrate if valuable