product-builders-pack

Plugin product-builders-pack from marketplace 90n-skills in polar-bear-org/claude-skills. Commands read from the repo's manifest — 17 days ago.

Skills (32)

• build-access-check

  Record who can open a prototype link today and narrow it before testers arrive, producing the current sharing setting read off the screen, a list of what travels with the link, and an end date with the role who removes access. Use for "run build-access-check", "who can open my prototype link", "I pa

• build-ai-prototype-check

  Checks where the inputs of an AI feature inside a prototype came from and writes an AI Prototype Input Check with every hand-picked input listed, a masked share of real cases drawn at random, runs per input, picked and random results reported apart and what one good run cannot show. Use for "run bui

• build-claude-code-setup

  Sets up a safe room for a prototype in Claude Code and writes a Claude Code Setup Record with a separate folder outside company code, the permission mode that asks first, a short CLAUDE.md of rules, an approve and decline list and the request for an engineer's written yes. Use for "run build-claude-

• build-clickable-prototype

  Builds a clickable prototype in Claude Design screen by screen from your spec, with two or three structurally different layouts, every screen in its empty, error and loading state, sample content, a visible prototype label and a build record. Use for "run build-clickable-prototype", "build a clickab

• build-connector-plan

  Decides whether a prototype needs live tool data at all and writes a Connector Plan with each connector page checked, reads allowed and writes kept off, personal data flagged, who turns each connector on and one first-run question you can check by hand. Use for "run build-connector-plan", "should my

• build-decision-memo

  Writes a one-page decision memo after a prototype test, producing the decision asked in the first lines, three options (build, change and test again, stop) with their cost as engineering states it, and the roles who decide, contribute and are informed. Use for "run build-decision-memo", "write the d

• build-demo-script

  Writes a Prototype Demo Script with the one moment to show first, the limits said out loud straight after it, a timed path through the prototype, what users did in the sessions as counts, the decision asked and prepared answers for the date question. Use for "run build-demo-script", "write my demo s

• build-design-system-brief

  Writes a brief for bringing your design system into Claude Design, covering what to import and from where, the components and tokens the prototype must use, a three-screen spot check and the gaps for the system owner. Use for "run build-design-system-brief", "make the prototype look like our product

• build-engineering-handover

  Writes an Engineering Handover Note covering how to open and run the prototype, a map of screens to requirements, the decisions made and why, everything faked or hardcoded, known problems, and what you recommend keeping, rebuilding or throwing away. Use for "run build-engineering-handover", "hand my

• build-error-fix-log

  Keeps an Error Fix Log for one error in a prototype, with the error in plain words, what you did just before it, the fewest steps that bring it back, one change per attempt with its result, when to rewind to a save point and the line where you stop and ask an engineer. Use for "run build-error-fix-l

• build-experiment-design

  Plans a controlled experiment for the version engineers build and run on real traffic, producing a hypothesis, one primary metric with guardrails, a sample and duration check from your own numbers and a decision rule written before launch. Use for "run build-experiment-design", "plan the A/B test fo

• build-first-working-version

  Plans the first working version of a prototype as a First Working Version Build Plan with the one flow that must really work end to end, the parts that stay faked and labelled, small build steps each with a check you can see on screen, a save point after every working step and a stop rule. Use for "

• build-heuristic-review

  Walks your prototype against the 10 usability heuristics and writes up each problem with its screen and a proposed severity, an over-design check, a short accessibility pass and a ranked fix list. Use for "run build-heuristic-review", "review my prototype", "heuristic evaluation of these screens", "

• build-idea-one-pager

  Writes an Idea One-Pager with the ask in the first lines (a time box to prototype and access to five real target users), the problem with its evidence source, who it is for and why now, the bet in one paragraph, one success measure, what you will not build and open questions with owners. Use for "ru

• build-iteration-plan

  Writes a Prototype Iteration Plan that sorts the problems from your sessions into fix now, fix after the round and leave, sets one change per problem with the reason, logs which version each participant saw, says what the following round must show and what cannot be compared, and fixes a stop rule.

• build-learning-card

  Writes the one fixed account of a prototype test, producing the belief copied from the test card, what was observed as counts against the pass line, what was learned and what is still unknown. Use for "run build-learning-card", "write the learning card", "what did the prototype test show", "did we m

• build-personal-data-check

  Walk a prototype for real personal data before a link goes out, producing a list of every place data is shown, stored or sent, each item marked invented, masked or real, and a remove-or-approve record signed by role. Use for "run build-personal-data-check", "is there real customer data in my prototy

• build-problem-frame

  Writes a Problem Frame that turns an idea you are already attached to into one testable question with no feature inside it, the decision it feeds and its owner by role, scope in three lists, a "how might we" line and one alternative framing. Use for "run build-problem-frame", "frame the problem", "w

• build-product-context-file

  Writes one short file that tells Claude what your product is and how it speaks, with users by need, a glossary, what exists today, hard constraints, tone, a never list and a review date. Use for "run build-product-context-file", "write a CLAUDE.md for my product", "stop re-explaining my product to C

• build-production-gap-note

  Writes a Prototype vs Production Note that reads the test result against the dated pass line, lists what the prototype does not prove and what is faked, and sets out the gap to production as work items with an owning role and no dates. Use for "run build-production-gap-note", "people are calling my

• build-prototype-brief

  Writes a one-page prototype brief that sets how real the prototype must be on three separate dimensions, what is real and what a person fakes by hand, which Claude surface fits, the visual direction, the out list and a time box. Use for "run build-prototype-brief", "how real does this prototype need

• build-prototype-spec

  Writes the spec for one prototype, answer first, with problem and evidence, non-goals, numbered requirements that each carry one behaviour and a Given-When-Then check, open questions with an owner and a date, and a dated export kept as the record. Use for "run build-prototype-spec", "write the spec

• build-prototype-test-card

  Writes a Prototype Test Card that sorts the beliefs behind your idea by how much rides on each and how little evidence it has, then puts one belief on a card with the task, who sees it, one observable measure and a pass line you set and date before anything is built. Use for "run build-prototype-tes

• build-review-request

  Writes an Engineering Review Request with the one question you need an engineer to answer, a plain list of what you are not asking, a thirty-minute walk-through plan, the three places you most suspect a problem and what you will do with each answer. Use for "run build-review-request", "ask an engine

• build-routine-skill

  Turns the steps you repeat for every new idea into your own custom Claude skill, producing a skill draft with the phrases you really type, a quality bar that carries the pre-share checks, a test on three past cases and a change log. Use for "run build-routine-skill", "turn my prototyping routine int

• build-sample-data-plan

  Plans the invented data a prototype runs on as a Sample Data Plan with every field it needs, an invented value for each one, the cases to cover (empty, long, odd characters, large volume), the places real data is tempting and why it stays out, and who approves any exception. Use for "run build-sampl

• build-secrets-check

  Find every key, password and token in a prototype before anyone else opens it, producing a credential inventory, a search record of the files and the history, and a revoke-and-replace list with questions for an engineer. Use for "run build-secrets-check", "where is my API key", "is the key in the pa

• build-share-sign-off

  Gather the three pre-share checks onto one page for a go or no-go, producing a record of what is shared and with whom, each check with its result as run, and the named person's yes or no with the date access ends. Use for "run build-share-sign-off", "can I send the prototype now", "who signs off the

• build-test-recruitment-note

  Writes a Tester Recruitment and Consent Note that says who counts as a real target user for the belief you are testing and who does not, where to find five of them, the invitation message and a plain consent note covering recording, how notes are kept and the right to stop. Use for "run build-test-r

• build-usability-findings

  Turns your session notes into Usability Test Findings with completed, completed with help and not completed per task against the criteria set before testing, what people did beside what they said, a sheet with one observation per row, problems with a proposed severity and the moments to show. Use fo

• build-usability-test-plan

  Writes a Five-User Usability Test Plan with test goals tied to the belief on your test card, task scenarios that do not give the path away, success criteria set before any session, a word-for-word moderator script with the think-aloud ask and neutral prompts, an observer note grid and a pilot. Use f

• build-user-flow

  Maps one journey from entry to done as a screen-by-screen flow, with each screen's purpose, the control that leaves it and where that leads, the dead ends, the empty, error and loading state per screen and one large-data case. Use for "run build-user-flow", "list every screen before I build", "what

Similar plugins