Design Quality
Use this skill when interface work needs a shared product context, deterministic design checks, browser evidence, critique persistence, or a final quality gate.
This skill adapts selected ideas from pbakaus/impeccable at commit 8259c28209b92792005cec14dad573df39f68eaf. Impeccable is Apache-2.0 licensed. Its detector, hooks, browser server, and live-mode source rewriting remain external runtime capabilities.
Load
- Read
references/project-context.md.
- Read one representative UI source file and the existing tokens, theme, or component system.
- Read
references/quality-gates.md.
- Read
references/impeccable-runtime.md when deterministic scanning or live variants would help.
- Read
references/critique-contract.md for a critique or audit.
Workflow
- Resolve the target to a stable file, route, component, or URL.
- Identify the product goal, user, design register, platform, and established system.
- Choose the smallest applicable action:
- direction through
design-consultation
- variants through
design-shotgun
- implementation through
design-html
- critique or polish through
design-review
- Use the external Impeccable runtime when it is already installed and materially improves evidence or iteration.
- Apply the local quality gates and preserve explicit evidence limits.
- Route material accessibility, human-impact, or organizational questions to
accessibility-review, responsible-design-review, or design-leadership-review.
Outputs
Always include:
- target and design context used
- evidence path
- highest-priority findings or changes
- external runtime status
- verification completed
- remaining uncertainty
Guardrails
- Preserve established product and brand systems unless the user authorizes a redesign.
- Treat anti-pattern rules as evidence-informed defaults. Product context and accessibility can justify a documented exception.
- Never install or update Impeccable implicitly.
- Never claim detector, hook, browser, or live-mode coverage unless that path actually ran.
- Keep private Marlowe context outside public design artifacts and GStack commits.
1---2name: design-quality3description: Project-aware design execution and quality gates for Codex, with optional Impeccable detector or live-mode integration and explicit local fallbacks.4---56# Design Quality78Use this skill when interface work needs a shared product context, deterministic design checks, browser evidence, critique persistence, or a final quality gate.910This skill adapts selected ideas from `pbakaus/impeccable` at commit `8259c28209b92792005cec14dad573df39f68eaf`. Impeccable is Apache-2.0 licensed. Its detector, hooks, browser server, and live-mode source rewriting remain external runtime capabilities.1112## Load13141. Read `references/project-context.md`.152. Read one representative UI source file and the existing tokens, theme, or component system.163. Read `references/quality-gates.md`.174. Read `references/impeccable-runtime.md` when deterministic scanning or live variants would help.185. Read `references/critique-contract.md` for a critique or audit.1920## Workflow21221. Resolve the target to a stable file, route, component, or URL.232. Identify the product goal, user, design register, platform, and established system.243. Choose the smallest applicable action:25 - direction through `design-consultation`26 - variants through `design-shotgun`27 - implementation through `design-html`28 - critique or polish through `design-review`294. Use the external Impeccable runtime when it is already installed and materially improves evidence or iteration.305. Apply the local quality gates and preserve explicit evidence limits.316. Route material accessibility, human-impact, or organizational questions to `accessibility-review`, `responsible-design-review`, or `design-leadership-review`.3233## Outputs3435Always include:3637- target and design context used38- evidence path39- highest-priority findings or changes40- external runtime status41- verification completed42- remaining uncertainty4344## Guardrails4546- Preserve established product and brand systems unless the user authorizes a redesign.47- Treat anti-pattern rules as evidence-informed defaults. Product context and accessibility can justify a documented exception.48- Never install or update Impeccable implicitly.49- Never claim detector, hook, browser, or live-mode coverage unless that path actually ran.50- Keep private Marlowe context outside public design artifacts and GStack commits.
mphaxise