arndvs/ux-test-driven-design
skills/ux-test-driven-design/SKILL.md
Phase 7 of Sketch the Solution. Plan user testing sessions and validate designs. Use when asked to 'test design', 'user testing', 'validate UI', 'test driven design', or 'get feedback on design'.
testing
Updated Apr 30, 2026
$ install --global
skillsauthnpx skillsauth add arndvs/ctrlshft ux-test-driven-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 2:37 AM13.9s1 file scanned
SKILL.md
- name:
- ux-test-driven-design
- description:
- Phase 7 of Sketch the Solution. Plan user testing sessions and validate designs. Use when asked to 'test design', 'user testing', 'validate UI', 'test driven design', or 'get feedback on design'.
UX Phase 7 — Test Driven Design
Output "Read UX Test Driven Design skill." to chat to acknowledge you read this file.
Pipeline position: /ux-user-stories → /ux-system-map → /ux-flow-diagram → /ux-model-attributes → /ux-screen-requirements → /ux-interface-design → /ux-test-driven-design
Decide what you want to test first. Testing is its own process.
Design is "done" when customer feedback becomes predictable — when you can correctly predict what users will do and say at each step. Until then, iterate.
Prerequisites
interface-design.mdfrom Phase 6- Prospect list from idea extraction
- All prior artifacts for reference
Steps
Step 1 — User Testing
Invoke /ux-user-testing
Create a structured test plan with per-screen questions. Design the feedback session script.
Step 2 — Six Mistakes Review
Invoke /ux-six-mistakes
Apply Amir Khella's "Six Mistakes of User Testing" as a validation checklist against your test plan.
Output
Generate test-plan.md containing:
- Test session script (intro, expectations, walkthrough structure)
- Per-screen question list (benefit probing, value assessment)
- Price anchoring capture template
- Hidden benefits tracking table
- Iteration log (version → feedback → changes)
- Six Mistakes checklist (pass/fail per anti-pattern)
Rules
- NEVER email prototypes for feedback — always walk through live on screen share
- Always record feedback sessions
- Set expectations: "This is rough. Tell me what sucks. Nothing is final."
- Ask benefit questions at every screen: "How would this help you?"
- Track price anchors: "How much time/money would this save?"
- Plan for 3+ iterations before asking for the sale
- Design is done when feedback becomes predictable
Handoff
After completion, offer:
/architect— create implementation plan from validated UX artifacts/do-work— begin building the product/write-a-prd— formalize into a PRD/sketch-the-solution— return to orchestrator
If context is high, follow the standard handoff protocol (@~/dotfiles/instructions/handoff.instructions.md).
Related Skills
arndvs/visual-feedback
development
VerifiedTrustedCommunity
Use when implementing UI, checking dark/light mode, or validating animations — adds a visual feedback loop via browser screenshots so frontend changes are verified, not assumed.
SKILL.mdUpdated May 21, 2026
arndvs/press1-check
development
VerifiedTrustedCommunity
Use when Claude Code sessions had many manual approval ("press 1") prompts or when auditing hook permissions; identifies which Bash commands required approval.
SKILL.mdUpdated May 21, 2026
arndvs/plan-archive
tools
VerifiedTrustedCommunity
Use after merging a PR or during periodic cleanup to archive plan-mode files by linking them to merged PRs.
SKILL.mdUpdated May 21, 2026
arndvs/grill-with-docs
testing
VerifiedTrustedCommunity
Use when stress-testing a plan against the project's domain model — grills the design, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
SKILL.mdUpdated May 21, 2026