Impeccable integration

Impeccable is the execution companion to this transversal UI/UX system. It provides a design vocabulary, focused workflows, production checks, and implementation discipline. It does not replace the house method.

Installed for Codex: ~/.codex/skills/impeccable
Installed version: 4.0.2
Source: pbakaus/impeccable

Authority and precedence

For work in this workspace, apply the sources in this order:

1. The user's brief and the real product or service constraints.
2. The Teletubbies principle: the page speaks to the eye before it is read, creates appetite, and stays easy and pleasant.
3. The Kennedy method: one job, hierarchy by de-emphasis, grayscale first, colour last, generous whitespace, locality, and ABD for interactive screens.
4. documentation-design.md for didactic pages in Read mode.
5. The incumbent project's tokens, components, content, and interaction conventions.
6. Impeccable's command playbook and craft floor.
7. Token and composition auditors as regression nets.

When Impeccable advice conflicts with layers 1 to 5, the earlier authority wins. In particular, "bolder" never means louder without purpose, and "delight" never outranks comprehension or task completion.

Where context belongs

Run Impeccable from the root of the specific project being designed, never from `[local implementation path]

• PRODUCT.md records that project's users, purpose, positioning, voice, and durable constraints.
• DESIGN.md records that project's visual implementation: colours, typography, components, and tokens.
• This folder remains the transversal method shared by all projects.

Do not copy the whole transversal system into every DESIGN.md. Link to this folder and record only the project-specific decisions that apply it.

Working sequence

1. Classify the surface

Choose the visitor-success mode before choosing a command:

2. State the one job

Write one sentence describing what should happen on roughly 95 of 100 visits. Use it to de-emphasize everything that does not directly support the job.

For Read mode, state what the reader should understand or be able to explain after reading.

3. Choose one Impeccable intervention

Use the narrowest command that owns the need:

Use bolder, colorize, delight, animate, or overdrive only after the one job and hierarchy are sound. They are enhancements, not substitutes for structure.

4. Verify in the house order

1. One-job and squint test.
2. Grayscale hierarchy check.
3. Locality and ABD check for interactive surfaces.
4. Impeccable critique or polish, as appropriate.
5. Impeccable audit for production quality.
6. composition-audit.js.
7. python3 token-audit.py <file>.
8. Pleasure gate: every part must remain easy and pleasant to read or use.

Passing Impeccable's detector does not prove that the page is good. Passing the house audits does not prove it either. The final judgment is whether the surface communicates before it is read and helps the visitor succeed without friction.

Invocation examples

Use natural requests; the skill routes them to its internal command playbooks:

Use Impeccable to shape this form. Apply the transversal UI/UX system and state the screen's one job before proposing UI.

Use Impeccable to critique this teaching page in Read mode. Apply documentation-design.md and report hierarchy, orientation, and reading-rhythm issues.

Use Impeccable to polish this dashboard. Preserve the incumbent tokens and run the house verification order before delivery.