Convert vague UI intent into a structured brief.md specification.
npx skills add https://github.com/ThorStarlord/interface-skills --skill ui-brief
Please help me install this Agent Skill. Skill: ui-brief Source: https://github.com/ThorStarlord/interface-skills/tree/main/scratch/claude-install-test/ui-brief Command: npx skills add https://github.com/ThorStarlord/interface-skills --skill ui-brief
ui-brief helps teams stop mismatched expectations by converting vague UI intent into a precise, constraint-based product and design brief that downstream work can trace back to.
Use ui-brief to create a structured brief by telling the AI: "I want to build a settings page for our team chat app where admins manage members; web only; users are IT admins at mid-sized companies—draft the UI brief and ask any open questions."
High-intent search queries and answers about installing and using this skill.
To turn vague UI ideas into a structured product brief, you provide initial design intent and target users. The system then asks clarifying questions to fill gaps and outputs a brief.md with measurable success criteria, constraints, and non-goals.
Spec recovery for an existing UI involves separating what the current interface does (Observed) from what it should do (Target). This process reconstructs missing design intent and highlights explicit gaps without inventing new decisions.
Documenting interaction design assumptions requires a validation-oriented template that records open questions and assumptions explicitly. This prevents mismatched expectations by ensuring downstream work traces back to recorded constraints rather than invented defaults.
Yes, generating a UI specification from a basic description triggers pre-flight requirement gathering. The system collects missing information about primary actions, success criteria, and constraints by asking questions instead of assuming default behaviors.
The product brief output template strictly enforces measurable success criteria and explicit non-goals. It follows a validation-oriented structure to ensure all constraint-based specifications are testable and traceable for downstream interface work.
saranskumarPlan screens and page responsibilities from existing user journeys.
chughtapanConvert user intent into a formal spec document with goals and acceptance criteria.
aziglerConvert scoped briefs and baselines into structured specification beads with test cases.
lionbenjaminDraft product specifications with problem, goals, user stories, and acceptance criteria.
