What problem does it solve? Deciding which API fields deserve primary placement on a screen is often ad-hoc and inconsistent. This Skill turns a scenario plus an API field set into a principled information-architecture analysis, producing a validated handoff document that downstream design work can consume directly. ## Core Features & Use Cases - JTBD and Principle-Anchored Analysis: Elicits functional, emotional, and social jobs, then anchors every field-priority decision to one of five principles (JTBD, CognitiveLoadTheory, HicksLaw, MillersLaw, ProgressiveDisclosure). - PII-Safe Pipeline: Redacts sensitive values before any LLM phase, then validates the final report with fingerprint and regex leak checks, retrying once on critical violations. - Anti-Pattern and Gap Detection: Flags whitelisted UI anti-patterns (e.g., too_many_primary, hidden_critical_info) and produces a bidirectional UI↔API gap report. - Use Case: Given a crypto transaction-confirmation scenario and a sample JSON payload, produce a handoff report with a field decision table, anti-pattern findings, and an information hierarchy that a frontend-design step can implement directly. ## Quick Start Run /ui-first-principles "transaction confirmation" --api fixtures/tx-confirm.json --domain crypto to generate a validated UI analysis handoff report.
