shape

Turn an idea into a design brief you can build from.

On this page 3 sections

Use shape when you know what you want to make but need to work out how it should work. Impeccable helps you define the job, explore the direction, and agree on a brief before writing code.

You do not need a finished specification or design vocabulary. Bring the idea and what you know about the people who will use it.

Try it

/impeccable shape an email preferences page. Subscribers should be able to get fewer emails without having to unsubscribe from everything.

Include the problem, who encounters it, and anything that must stay. Impeccable reuses context already available in the project and conversation.

How it works

  • Clarify the job: ask a few related questions about the audience, situation, and desired outcome. Follow up where an answer leaves an important gap.
  • Set the boundaries: establish the content, relevant states, scope, and constraints. Identify what a builder must not invent or change.
  • Choose a direction: explore the structure and interaction where they are still open. For new surfaces or a change of visual identity, work through the visual direction with you.
  • Confirm the brief: capture the decisions, invite a correction, and stop before implementation.
Starting idea

“Let people get fewer emails.”

Email preferencesExample of a confirmed brief
Job
Help a subscriber reduce email without losing the updates they want.
Direction
A single page showing topics and frequency together, with one Save action.
Keep
An equally clear option to unsubscribe from all emails.
Cover
Current choices, saving, save failure, and confirmation. Preserve choices after an error.
Still needed
The actual topic names and available delivery schedules.
Illustrative brief: the original request becomes a concrete plan, including a direction and the decisions that remain open. The length of a real brief depends on the task.

The brief can be a few bullets for a settled task or a fuller document for a complex flow. It records the choices a builder needs, including interaction and layout intent, without prescribing every CSS value.

What happens next

Read the brief for assumptions about your users, scope, and constraints. Correct anything that would lead the build in the wrong direction.

Shape ends with the confirmed brief. Ask Impeccable to build from it when you are ready, or take it to another implementation workflow. Confirmed answers carry forward, so you should not have to repeat the discovery conversation.

Can I plan and build in one request?

Yes. Describe what you want to make in a normal Impeccable request. Its new-work flow handles discovery and design direction before continuing into implementation. Use shape when you want to stop at the plan.