Shape vague feature ideas into decided product directions before designing screens
Shape/Review/Handoff modes, evidence ledger separating known from assumed, AI necessity gate, risk rating, smallest coherent end-to-end feature, and concrete interaction contracts with real labels and error copy
- What
- Shape/Review/Handoff modes, evidence ledger separating known from assumed, AI necessity gate, risk rating, smallest coherent end-to-end feature, and concrete interaction contracts with real labels and error copy
- Cost
- Free
- Needs
- a feature idea, concept, or product area to decide on (and optionally a .uxproof/ contract from om-ux-setup) — the skill decides direction, it does not implement
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @open-mercato's om-ux-shape skill: turn ambiguity into a decided direction before anyone draws screens. Three modes (Shape for vague opportunities, Review for existing concepts/flows, Handoff for implementation-ready behavior), an operating discipline of ten principles (start from the consequential problem, treat requirements as claims, label facts/inferences/assumptions/unknowns, recommend a direction rather than hiding behind menus, treat AI as a design material with uncertainty/latency/cost), an evidence ledger separating known from assumed, an AI necessity gate with a rules-based-alternative check, human-value metrics, four product-risk ratings plus AI-specific risks, generation of 2-3 meaningfully different mechanisms with an explicit trade-off call, the smallest coherent end-to-end feature (now/later/not-doing), and concrete interaction contracts — named screens, named components, real labels, empty/loading/error/permission states, undo/retry/fallback paths — with a quality rubric gate before delivery. Honest caveats: process-heavy by design — overkill for trivial tweaks (scale depth to decision risk); required references (decision-framework, ai-interaction, report-templates) live in the skill's `references/` and must be loaded when triggered; the `.uxproof/` design contract (from om-ux-setup) constrains the output when one exists. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a feature idea, concept, or product area to decide on (and optionally a .uxproof/ contract from om-ux-setup) — the skill decides direction, it does not implement Install "Shape vague feature ideas into decided product directions before designing screens" for me. It gives my agent @open-mercato's om-ux-shape workflow: choose the mode (Shape/Review/Handoff), write for the least-context reader, load the required references when triggered (decision-framework, ai-interaction, report-templates), build the evidence ledger, run the AI necessity gate, rate the four product risks, choose a direction from 2-3 mechanisms with an explicit trade-off, shape the smallest coherent end-to-end feature, and deliver a concrete interaction contract (real labels, states, recovery paths) checked against the quality rubric. MIT licensed. Repository: https://github.com/open-mercato/skills/blob/main/skills/om-ux-shape/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "om-ux-shape". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. tell the agent the feature idea or concept to shape and who the least-context reader is (builder/drawer); pair it with om-ux-setup's .uxproof/ contract when one exists — install om-ux-setup separately; keep the process depth proportional to the decision risk). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.