Curated prompts and workflows to level up your design process.
Gives you the honest, structured design critique you'd get from a senior designer — covering usability, hierarchy, consistency, and user goals. Works on screenshots, wireframes, or written descriptions.
Activate this skill whenever the conversation involves writing user stories, breaking down a validated direction into design-ready scenarios, or defining what a feature should do at the story level. Trigger on phrases like "write a user story", "turn this into stories", "break this down", "what should this feature do", or when transitioning from the idea-validator with a validated direction. This skill always checks for a session-brief.md and validation file first — it never re-asks questions already answered upstream. Stories are written in plain human language using named personas, readable by anyone regardless of technical background. tags: [product, user-stories, handoff, requirements]
Activate this skill when a designer is starting to think about a new feature, working through an ambiguous problem space, or needs PM-level thinking they're not getting from their team. Trigger on phrases like "I'm working on", "I have an idea for", "help me think through", "what should I build", "where do I start", or any time a designer is in early-stage discovery. This skill acts as a dedicated PM thought partner — it doesn't critique designs, it doesn't write stories. It asks the questions a good PM would ask, brings market and business perspective, runs a competitive search, and produces a structured session brief the designer can carry forward. Always manages toward output, not endless conversation.
Activate this skill when a designer or PM has a validated set of user stories and wants to convert them into a human-readable Product Requirements Document. Trigger on phrases like "turn this into a PRD", "generate a PRD from these stories", "I want to hand this to an engineer or stakeholder", "make this shareable", or "write up the requirements". Always checks for stories-*.md, validation-*.md, and session-brief.md first — does not re-ask what's already been established. Produces a clean, structured PRD a coding agent can also consume directly.
Activate this skill when a designer has a rough direction, idea, or concept and needs to pressure-test it before committing to design. Trigger on phrases like "validate my idea", "does this direction make sense", "I'm thinking of building X", "pressure-test this", or when transitioning from the pm-thinking-coach with a direction in hand. This skill is NOT post-design critique — it operates before any design work begins. It stress-tests whether the user, JTBD, and proposed direction actually hold together. Always checks for a session-brief.md first before asking questions already answered.