Build something new | Impeccable

Make something new, with a direction you can shape.
Describe the page you want to make. Impeccable helps you choose a direction, builds it, and reviews the result. No special command or visual concept required.
Image generation opens up bolder compositions. Expect a few rounds to carry that ambition into code; the first build will lose some of the mockup’s detail.
Say who it serves, what it should do, and what must stay.
Compare options and steer the design. Small additions can follow your existing style.
Try the interface and refine it. Impeccable records the decisions for future work.
Only need a plan? Start with shape.
You can choose how a new design becomes a working interface. A comp is a visual composition: a detailed mockup of the page.
Comp-led is not a one-shot workflow. An image model can propose a composition the coding model cannot reproduce faithfully on its first pass. Typography, spacing, imagery, and proportions will drift in translation. Impeccable gives the build a visual target and helps check fidelity, but you should expect to prompt a few rounds until you are satisfied. Use a capable coding model for that work.
Choose mockup first for a higher visual ceiling you are willing to work toward. Choose build directly for a stronger first implementation within the model’s natural range. Without image generation, Impeccable uses the code-led path.
Use the workflow switch in the design picker for a session-specific choice:
With image generation available and no saved preference, Impeccable defaults to mockup first. Without image generation, it builds directly in code and does not show the switch.
The picker’s switch applies to the current session. To change the project’s default, ask in plain language:
The setting is buildPath in .impeccable/config.json: comp or code. A value in .impeccable/config.local.json overrides the shared setting for that developer. See Configuration & ignores for the file format.
On a project without a saved preference, changing the switch can prompt a one-time question about keeping the new choice. Init can also establish the preference during setup.
These paths apply to new design work and redesigns. A focused polish pass keeps the current design. Either path can use generated images as finished assets; code-led skips the mockup approval stage.
Tell Impeccable what it can change. A new section should fit the surrounding page; a new page should fit the product. For a redesign, name what to keep.
Redesign this within our current system. Keep the product names and signup flow.
Impeccable reads the actual interface, tokens, components, and assets alongside DESIGN.md. Missing documentation does not erase an established design. It can record that system before extending it.
If the boundary is unclear, Impeccable should ask. “Replace the current look” gives different permission from “Redesign within our current system.”
Compare the options in the picker, then choose one or tell Impeccable what to change. Here, the same release catalog takes three different forms:
You can reject the whole set. After two consecutive new sets, Impeccable asks what quality is missing so the next attempt has a clearer basis. If the browser decision page cannot run, the choice moves into the conversation.
For a new page inside an existing product, the choice is about structure. These three layouts explore Relay’s integrations page while keeping its visual identity:
Your references and constraints guide the design:
Impeccable develops the choices your brief leaves open. A chosen aesthetic is a starting point for a complete design, including navigation, controls, and interaction.
Compare the lettering, artwork, and section proportions: the overall direction carries through, but the translation changes details. Closing the gaps takes review and iteration. The implementation also needs readable text, working controls, accessible behavior, and responsive layouts.
Try the main task, check a narrow screen, and tell Impeccable what to keep or adjust. The chosen direction guides the review; the finished interface still needs to work for real users.
The design plan belongs in the development record. It is not placed in the page’s HTML comments, hidden content, or other output sent to visitors.
Creative prompts can still produce familiar answers. In Impeccable’s published July 2026 experiments, 30 of 35 answers under different creative framings returned the same concept. Read the research for the experiment and its limits.
Impeccable introduces variation into the selection process. It develops directions from your product and audience, uses a seeded selection to avoid always choosing the model’s first preference, and considers alternatives from a curated catalog when the visual identity is open.
Those references have to become a design for your product: its content, tasks, controls, and constraints. A catalog image shows inspiration and a level of finish, rather than a ready-made page to copy.
A direction has to fit the product before it reaches you:
For a new page inside an established system, the alternatives explore structure within that system. For a new or replacement identity, they can explore a different visual language.
The surface brief holds a short direction contract: the central idea, visual language, visitor’s path, first-screen composition, chosen form and seed, and what must be checked before the work is complete.
The finishing review uses those commitments to assess the result. For mockup-led work, it also compares the implementation with the approved image.
Keep the seed if you want to replay the selection, including its re-roll rounds. Replaying a selection does not guarantee identical generated images or code.
When you are reviewing the choices, Impeccable asks you to select a direction and approve the mockup where that workflow applies. You can also delegate a choice.
In an unattended run, it proceeds with the assigned direction and states its assumptions. If the decisi