gvastethecreator Improve UI
Improve existing interface. Preserve its path. Trace weakness to its source. Smallest authorized systemic change. Limit claims to evidence.
Contents
Mandatory Entry Frame
- Code, screenshots, and runtime prove different claims; source cannot prove visual quality. Nontrivial implementation: execution-contract.md, product contexts, finish quality.
- Scope: existing web UI. Route blank-canvas, native UI, specialist renderer/game/3D elsewhere. Keep web HUD, overlay, fallback, and integration here.
- Preserve IA, routes, labels, contracts, analytics, SEO, legal copy, and accessibility wins unless scoped. Never claim WCAG certification.
diagnose,verify,audit,review,critique, androaststay read-only. Do not edit source or persistent artifacts. Durable reports only when requested.- Explicit
improve,fix,repair,polish,redesign,implement, orharden: edit only requested path. Mixed requests diagnose briefly, then fix in scope. - Neutral forensic language. Verdict or roast tone only when requested.
Choose A Profile
Profiles set scope and proof — not mutation authority.
micro: One defect. Reproduce it. If implementation is authorized, patch and check same state and viewport.focused(default): One bounded surface or flow. Inspect main path plus one edge or recovery state. Fix only when authorized.deep: Broad audit or redesign, shared primitives, 3+ state families, production readiness, or explicit comprehensive work. Cover relevant dimensions. Uninspected stayunknown.
Do not escalate to deep only because references or scripts exist. State profile in working notes for nontrivial runs.
Process
- Inspect rules, tree, framework, tokens, primitives, route, and run/test commands. Preserve unrelated changes.
- Frame one surface: archetype, user mode, artifact, pressure, input, spatial model, costly states, hierarchy, cause, constraints, proof matrix. Split unrelated archetypes into isolated units.
- Choose one Context Router row. Combine only in-scope domains.
- Builder owns baseline capture -> inspect -> correct -> recapture. If reproduction is missing, change only a clear source-backed cause. Label proof provisional.
focused/deep: inventory applicable dimensions before editing (dimension - damage - planned move - severity). Clean rowspass; uninspectedunknown. Implementation: P0/P1 first, in-scope P2 and taste. Diagnose/audit/verify: report with evidence; do not edit. Close each row or record whyblocked.- Check by profile.
micro: exact defect state and viewport.focused: main path plus one edge or recovery.deep: declared relevant state-family and viewport matrix. - Run
structureandfinish. Persist context, before/after/detail proof, and finish ledger from execution contract. Stop when applicable dimensions pass, or a named blocker limits the claim. - Material reviews or proposals: reporting. Synchronized Markdown and HTML from one manifest.
Implementation: start with interface-surgery.md. Add surgical-patterns.md only when a symptom repeats. Do not preload other core refs.
Context Router
Choose one primary row. Union only domain references and proof obligations the scope needs.
| Task | Read the minimum set | Required proof |
|---|---|---|
| Tiny visual regression | interface-surgery.md | Same state/viewport before/after when available |
| Component or repeated UI defect | interface-surgery.md; if repeated, surgical-patterns.md. Add finish-quality.md for rendered craft | Main state plus one edge |
| Product context: studio/editor, dashboard, command center, transactional/admin, game HUD, prototype, commerce/content | references/product-contexts.md | Context card plus costly states, viewports, interactions, detail evidence |
| Neutral audit or design verdict | forensic-roast.md, finish-quality.md, references/evidence-and-scoring.md. Add reporting for a durable dossier | Source for implementation findings. Rendered viewport and detail evidence for visual verdict. Unknown where absent |
| Explicit roast | forensic-roast.md, finish-quality.md | Same evidence bar as neutral audit |
| Geometry, rhythm, dense layouts, HUD safe areas | references/geometry-and-rhythm.md, finish-quality.md | Alignment map, measured repetition, detail crops |
| Hierarchy, taste, typography, surfaces, generic or cheap-looking UI | references/visual-quality.md, references/authorship-and-specificity.md, finish-quality.md | Before/after or reference/after artifact, product-causality test, finish ledger |
| Product copy, labels, state messages, or report prose | references/copy-and-writing.md plus matching product route | Same-state before/after, preserved facts/tokens, rendered fit, accessible names/status |
| Semantics, keyboard, focus, forms, contrast | references/accessibility.md | Manual interaction plus automated evidence when available |
| Modality, permissions, onboarding, progress, search, undo, large text, inclusion | references/human-interface-craft.md | Pattern's costly state from that file's proof table |
| Responsive, content, i18n, async, real-data states | references/responsive-hardening.md | Run states, assertions, relevant viewports |
| Motion or gesture | references/motion.md. Add motion implementation traps while editing. Add performance only for runtime cost | Repeated or interrupted trigger, reduced motion, visual/runtime evidence |
| Material review or proposal | references/reporting.md plus the diagnosis route | Synchronized reports, local assets, exact annotation mapping, proof limits |
| Frontend performance | references/performance.md, proof-recipes.md | Measured interaction or limited source-only claim |
| Landing or pricing page | references/marketing.md. Add visual quality only for art direction | First viewport, proof/decision section, mobile |
| Canvas/WebGL/3D already present | references/immersive.md, performance | Readability, fallback, offscreen pause, cleanup, runtime |
| Detector or harness operation | detector-rules.md, proof-recipes.md | Exact command, outputs, exit status |
| Broad production-readiness pass | references/foundation.md, accessibility, responsive hardening, evidence/scoring | Relevant dimensions and state manifest. Untested remains unknown |
core-moves.md only as a compact map when route is still unclear. references/sources-and-provenance.md when a standard, browser behavior, or third-party recommendation determines a finding.
Deep Review Harness
- Keep commands and manifest formats in proof-recipes.md. Do not copy stale CLI examples into other refs.
- Strict mode only for final implementation claims with valid target and required evidence.
- Objective detector rules are gateable. Advisory taste heuristics stay opt-in; check visually.
- Named runtime states must run and meet their assertion. A listed state is not coverage. Cross with viewports only where claim or risk requires it. Record tested matrix.
- Structured before/after or equivalent artifacts for change proof. Prose is not proof.
--detail-capturefor strict visual-polish, critique, icon, alignment, dense-layout, or scrollbar claims. - Keep
assessment,evidenceCoverage, and harness expectations separate. Never raise quality because a regression expectation passed. - Uninspected dimension stays
unknown. Do not total-score across unknown dimensions.
Failure Conditions
Incomplete when any condition holds:
- read-only request edited product source without implementation authority
- implementation request stopped at advice despite editable, reachable path
- missing target or zero supported source files reported as clean
- frontend code changed without rendered proof, skipped applicable finish dimension, used unreadable detail evidence, or lacked explicit proof blocker
- named state not run and asserted successfully
focusedordeepstarted editing without an improvement inventory, or ended with in-scope rows neither closed norblockedwith a reason- run completed only cosmetic inventory rows while higher-severity rows stayed open without a named blocker
- prose, a pathless success message, or mismatched artifacts used as change proof
- detector heuristic reported as objective design truth
- repair used a generic cross-context prescription, left primary archetype unknown, or skipped its costly states
- unrelated primary archetypes batched into one implementation work unit, or builder delegated its proof loop to a later coordinator
- unresolved in-scope P0/P1 findings hidden by an aggregate score
- unknown dimensions initialized, scored, or presented as passing
- formal conformance or production-readiness language exceeded inspected scope
Output Contract
- Audits: context card, findings by severity, evidence limits, preserved strengths, next actions.
- Implementations: result first, inventory (row status, files, proof, skipped checks, blockers, remaining risk).
- Separate report usefulness from claim status. Evidence can be partial while completion stays blocked.
- Cite file/line for source findings; viewport, state, and artifact for visual findings. Finish ledger for nontrivial visual work.
- Label rules
standard,practice,heuristic, orpreference. Never block on taste alone. - Match user language and tone. For UI copy or report prose, apply copy and writing quality. Preserve voice and facts. Critique decisions and user effects.
- Material reviews and proposals: one-manifest
report.md+report.html. Ids, annotation geometry, decisions, proof states, and limitations must match. - Use checklist.md before nontrivial final claim.
Reference Files
Secondary refs, templates, examples, tooling: package map after the router selects concern.