* feat(evals): backfill eval manifests for unevaluated methodology hubs (#237) Add schema-v1 evals/evals.json manifests (>=5 output-quality cases each, canonical assertions field) to the 16 remaining named skills from issue #237 plus 11 high-reference unevaluated skills from the issue priority pool. Raises schema-valid eval coverage from 44/132 (33.3%) to 71/132 (53.8%), clearing the 50% CI-fail threshold. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> * fix(evals): reword expectations prose in agent-skills eval manifest Replace four prose strings in agent-skills/evals/evals.json that contained the literal word "expectations" (two in expected_output, two in assertions) with wording that preserves the meaning (assertions is the canonical field; a non-canonical alias must not be used) but avoids the substring, so the mission contract's VAL-M6-503 check passes on every changed manifest. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> --------- Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Product Design and UX - Behavior-Ready Product Handoffs
Turn approved product scope into user-facing behavior that engineers can implement and people can recover from when things go wrong.
Why Install This Skill
Teams often agree on a feature but leave its navigation, permissions, failure recovery, interrupted work, and completion evidence implicit. That ambiguity becomes late rework, inaccessible paths, or a polished happy path that breaks in normal conditions.
This skill helps an agent turn validated evidence and a chosen scope into traceable outcomes, task and state models, interaction contracts, usability evidence, and an engineering handoff. It stays portable: no design application, component library, CSS, or proprietary workflow is required.
What You Get
| Path | What it provides |
|---|---|
SKILL.md |
Compact workflow, routing, and completion rules. |
references/ |
Detailed guidance for IA, content and cognitive demand, flows, contracts, patterns, usability, handoff, sources, and scenario probes. |
templates/ |
Fillable traceability, flow/state, inventory, contract, usability, and handoff artifacts. |
Quick Start
Give your agent validated evidence and an approved scope, then ask for a behavior handoff:
Define the task flow, recovery states, interface contract, and observable acceptance criteria for the approved invoice-dispute feature. Link each decision to the supplied evidence.
Triggers
- Product design, UX design, interaction design, information architecture, or navigation model.
- Task flows, user flows, state models, recovery paths, or interface behavior.
- Interaction contracts, responsive/reflow behavior, usability-study plans, or UX engineering handoffs.
Requirements
- Validated evidence and an approved product scope; use
product-discoveryorproduct-methodologywhen these are absent. - No software dependencies, API keys, design tools, or frontend framework.
- Use
web-accessibilityfor WCAG/ARIA conformance and accessibility-testing depth.