shape

Plans UX and UI direction for a feature through structured discovery interviews and design briefs.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ShyamRavidath/oscc-detection-v2 --skill shape-shyamravidath
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/ShyamRavidath/oscc-detection-v2/tree/main/.agents/skills/shape
Command: npx skills add https://github.com/ShyamRavidath/oscc-detection-v2 --skill shape-shyamravidath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into coding UI features without clarifying user needs, content ranges, edge cases, or design direction, resulting in interfaces that miss the mark. This Skill runs a structured discovery process before any code is written, producing a design brief that guides implementation. ## Core Features & Use Cases - Discovery Interview: Conducts a guided dialogue covering purpose, audience, content and data ranges, edge cases, design goals, constraints, and anti-goals. - Design Brief Generation: Synthesizes interview answers into a nine-section brief covering feature summary, primary user action, design direction, layout strategy, key states, interaction model, content requirements, recommended references, and open questions. - Handoff to Implementation: Produces an artifact that can be passed to implementation skills such as /impeccable craft or used to guide any build approach. - Use Case: Before building a new dashboard settings page, run this Skill to clarify who uses it, what states it needs (empty, loading, error), and how it should feel, then hand the confirmed brief to your implementation workflow. ## Quick Start Ask the AI to shape the UX and UI for your feature, for example: "Shape the onboarding flow for new team members before we write any code."

Frequently Asked Questions about shape

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan UI design before writing code?

Run a structured discovery interview covering purpose, users, content ranges, edge cases, design goals, and constraints, then synthesize the answers into a design brief. This Skill automates that process and requires explicit confirmation of the brief before finishing.

What is a design brief for a software feature?

A design brief is a structured artifact describing what a feature is, its primary user action, design direction, layout strategy, key states, interaction model, and content requirements. It guides implementation so developers build from decisions rather than guesswork.

Does this Skill write any UI code?

No, this Skill explicitly does not write code. Its scope is design planning only: it runs the discovery interview and produces a design brief that you hand off to an implementation skill such as /impeccable craft.

When should I use design planning versus jumping straight to implementation?

Use design planning when the feature's users, states, or direction are unclear, or when skipping thinking has previously produced generic interfaces. If you want discovery and build in one step, use /impeccable craft, which runs this Skill internally.

What questions does the discovery interview ask?

The interview covers purpose and context, content and data with realistic ranges and edge cases, design goals and feel, technical and accessibility constraints, and anti-goals. Questions are asked conversationally rather than dumped all at once.