platty-mcp

Plugin platty-mcp from marketplace platty in paradigmshift-labs/platty. Commands read from the repo's manifest — 1 month ago.

Skills (24)

• heroines-low-fi-wireframes

  Use when turning a Heroines FSD or confirmed screen behavior into a low fidelity wireframe, reviewing its visual hierarchy, or adding interactions to that wireframe.

• ba-interview

  Orchestrate a BA interview through JTBD, PRD, user experience, storyboard and Notion delivery, screen behavior, and verified wireframes. Use to start or resume an interview; it routes to exactly one current stage.

• design-pack-edit

  Change what the Heroines design knowledge pack contains — tokens, components, screen roles, recipe rules, principles, usability checks, reference screens — through the upstream seeds that produce it, then build and verify a new pack version. Use when a designer wants to fix, add, or remove something

• design-pack-review

  Render the Heroines design knowledge pack — tokens, components, screen roles, recipe rules, principles, reference screens — as one HTML page a designer can open and judge. Use when someone asks to see, review, or check what the design system currently contains.

• wireframe

  Author and verify Heroines design-system wireframes from confirmed screen behavior using the design pipeline harness, then export the completed wireframe to a new Figma file. Use only while the session stage is design_system_wireframe.

• jtbd

  Interview the planner for the customer's job-to-be-done and the experiences that job requires, before any PRD exists. Use only while the session stage is jtbd.

• notion-publish

  Publish a confirmed BA case (JTBD, PRD, user experience) to Notion through the Notion REST API — find the right place, create one bundle page, and put the documents under it as native Notion pages. Use when the planner asks to upload, post, or share BA documents in Notion.

• planning-context

  Establish a BA planning context for Heroines: problem, goal, users, solution intent, scope, rules, and success criteria. Use only while the interview session stage is planning_context.

• ba-retrieval

  Retrieve bounded Heroines evidence from Platty for a BA stage without returning raw MCP output to the interview orchestrator. Use when a stage needs current service facts or source confirmation.

• prd

  Turn a confirmed job-to-be-done into a PRD by copying the planner's judgments and asking only about the solution, under a two-question discovery budget. Use only while the session stage is prd.

• screen-behavior

  Derive Heroines screens, elements, interaction states, focus, loading, errors, and recovery from confirmed user experience and the design knowledge pack, without interviewing the planner. Use only while the session stage is screen_behavior.

• storyboard

  Draw an Airbnb "Snow White" style journey storyboard — stages left to right, layers (사람·기분·제품·정책·서비스·측정) top to bottom — from a confirmed JTBD, PRD, and user experience, so designers and developers understand why the work exists and what the user should feel. Use after the user_experience stage is c

• user-experience

  Derive role-based Heroines journeys, states, branches, exceptions, and recovery from a confirmed PRD without interviewing the planner. Use only while the session stage is user_experience.

• platty-mcp-client-setup

  Use when registering, validating, or troubleshooting a Platty MCP endpoint from an MCP-capable runtime such as Codex or Claude Code.

• platty-mcp-figma-design-sync

  Use when a Figma URL, Figma page, Figma section, or Figma frame must become reusable, revisioned design evidence before Platty MCP product specification or technical design.

• platty-mcp-impact-analysis

  Use when a Platty MCP question asks what changes, what breaks, blast radius, affected screens/APIs/services, implementation locations, cross-EPIC effects, or technical-design impact.

• platty-mcp-memory

  Use when a user explicitly asks to read, record, correct, update, or delete Platty memories or glossary aliases through configured Platty MCP tools.

• platty-mcp-retrieval

  Use when answering Platty project questions through configured read-only MCP tools, including domain terms, epics, business documents, specs, exact code locations, or source confirmation, or when another Platty MCP skill needs an Impact Seed Packet.

• platty-mcp-sdd-design-with-figma

  Use when a user separately requests technical or system design from approved product documents with a Figma URL, current-session Figma evidence, or a validated figma_handoff.json discovered beside the product pair.

• platty-mcp-sdd-design

  Use when creating locally saved MCP-grounded SDD technical design and executable implementation plans from existing prd.md and user_stories.md.

• platty-mcp-sdd-spec-from-figma

  Use when a Figma URL accompanies a request to organize, draft, create, or improve a product plan, planning document, feature brief, requirements, PRD, user stories, 기획서, 요구사항, or 기능 기획, with or without existing product documents.

• platty-mcp-sdd-spec

  Use when creating locally saved MCP-grounded SDD PRD and user-story drafts from a product idea, feature request, PRD need, policy change, or requirements discussion.

• using-platty-mcp

  Use when a task should use configured Platty MCP tools for remote project context, tool capability checks, Figma-backed product-plan or 기획서 authoring, Figma evidence routing, client setup routing, Platty MCP retrieval, memory or glossary-alias lifecycle routing, or MCP-grounded SDD file creation.

• writing-fsd

  Use when an approved PRD or JTBD needs a screen and user-experience FSD, when design decisions must be interviewed before that FSD, or when an existing FSD needs a human-readability and implementation-handoff review.

Similar plugins