How do I install the High Fidelity Prototype Planner skill?

Run npx skillmds@latest add 45ck/high-fidelity-prototype-planner in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the High Fidelity Prototype Planner skill do?

high-fidelity-prototype-planner It is listed under Coding & Dev Tools on SkillMD.

Is High Fidelity Prototype Planner safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with High Fidelity Prototype Planner?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is High Fidelity Prototype Planner free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published High Fidelity Prototype Planner?

45ck (@45ck) published this skill. Their other Agent Skills are listed on their SkillMD profile.

High Fidelity Prototype Planner by 45ck

Name: High Fidelity Prototype Planner
Author: 45ck

File contents

high-fidelity-prototype-planner

Purpose

Plan high-fidelity prototypes when interaction detail, visual hierarchy, timing, or handoff fidelity needs to be tested.

Trigger this skill when

You need to understand users, tasks, or interaction problems before building or changing an interface.
A team is making UX claims without enough structure, evidence, or critique.
Prototype, flow, or usability work needs a repeatable checklist rather than ad hoc opinions.

Expected inputs

interface or workflow under review
target users or user assumptions
task context
constraints or evidence already available

Deliverables

structured findings
open questions
recommended artifact or next step
handoff recommendation

Operating procedure

Clarify the user, task, and design question this skill is meant to answer.
Separate observed facts, inferred assumptions, and speculative hypotheses.
Produce concrete findings tied to user goals and task completion.
Surface uncertainty explicitly instead of masking it with confident UX language.
Recommend the next most useful research, design, or evaluation step.

Quality gates

Findings are tied to a user goal or task, not generic taste.
Assumptions are marked as assumptions.
Recommendations are concrete enough to act on.
Accessibility, clarity, and cognitive load are not ignored when relevant.

Handoff targets

wireframe-critic
usability-test-planner
error-and-time-metrics-analyzer

Output style

Be concrete and structured.
Prefer task-based critique over aesthetic vagueness.
Separate evidence, inference, and recommendation.
Use severity or priority when useful.

Failure modes to avoid

Do not confuse stakeholder preference with user evidence.
Do not write generic UX advice detached from the scenario.
Do not assume a persona is real evidence if it is only hypothesized.
Do not recommend high-fidelity work when the underlying problem is still unclear.

Minimum output skeleton

## Summary
## Findings
## Evidence vs assumptions
## Open questions
## Recommended next skill

---name: high-fidelity-prototype-plannerdescription: high-fidelity-prototype-planner---# high-fidelity-prototype-planner## PurposePlan high-fidelity prototypes when interaction detail, visual hierarchy, timing, or handoff fidelity needs to be tested.## Trigger this skill when- You need to understand users, tasks, or interaction problems before building or changing an interface.- A team is making UX claims without enough structure, evidence, or critique.- Prototype, flow, or usability work needs a repeatable checklist rather than ad hoc opinions.## Expected inputs- interface or workflow under review- target users or user assumptions- task context- constraints or evidence already available## Deliverables- structured findings- open questions- recommended artifact or next step- handoff recommendation## Operating procedure1. Clarify the user, task, and design question this skill is meant to answer.2. Separate observed facts, inferred assumptions, and speculative hypotheses.3. Produce concrete findings tied to user goals and task completion.4. Surface uncertainty explicitly instead of masking it with confident UX language.5. Recommend the next most useful research, design, or evaluation step.## Quality gates- Findings are tied to a user goal or task, not generic taste.- Assumptions are marked as assumptions.- Recommendations are concrete enough to act on.- Accessibility, clarity, and cognitive load are not ignored when relevant.## Handoff targets- wireframe-critic- usability-test-planner- error-and-time-metrics-analyzer## Output style- Be concrete and structured.- Prefer task-based critique over aesthetic vagueness.- Separate evidence, inference, and recommendation.- Use severity or priority when useful.## Failure modes to avoid- Do not confuse stakeholder preference with user evidence.- Do not write generic UX advice detached from the scenario.- Do not assume a persona is real evidence if it is only hypothesized.- Do not recommend high-fidelity work when the underlying problem is still unclear.## Minimum output skeleton```md## Summary## Findings## Evidence vs assumptions## Open questions## Recommended next skill```

Frequently asked questions

High Fidelity Prototype Planner