Design, audit, and refine interfaces using the complete Impeccable workflow, command references, and pinned local runtime.
Design, audit, and refine interfaces using the complete Impeccable workflow, command references, and pinned local runtime.
# Impeccable ## Scope and complete package Use Impeccable for frontend design, critique, accessibility, responsive behavior, UX copy, production states, and focused refinements. Favorite and synchronize this Skill to install its complete reviewed upstream package. This hosted guide does not install its command references, launchers, browser scripts, or engine. ## Start and choose the right job Read existing product truth, incumbent design, code, and current screenshots. In a synchronized local package, follow its entrypoint and run its context launcher once in the website project. The launcher can download the exact engine version listed in its VERSION file; this dependency and network access remain prerequisites, not files bundled in the catalog. Choose the surface’s visitor mode: Persuade for marketing, Operate for task completion, Read for comprehension, or Experience for a portfolio/gallery. Refinement preserves the existing identity and behavior. Redesign can replace the visual world while retaining factual content and working functionality. The user’s explicit brief wins over generic taste defaults. ## Workflow 1. Record only missing context that affects the task. Preserve real brand, content, constraints, and evidence. Do not invent product context or repair unrelated project drift. 2. Select the exact reference for the requested action: shape/new-work for planning, critique for hierarchy and clarity, audit for accessibility/performance/responsiveness, polish for final cleanup, adapt for device behavior, harden for states and edge cases, or animate for purposeful motion. Read the bundled craft floor before UI edits. 3. Build the entire requested surface or make the narrow requested refinement. Reuse one design system and align type, spacing, color, media, copy, states, and controls with its visitor mode. 4. Inspect desktop and mobile together. Batch the fixes shown by the first inspection, confirm the result in a bounded follow-up, and stop rather than running an open-ended polish loop. Preserve focus, reduced motion, touch behavior, contrast, and real CTA outcomes. 5. Deliver the runnable or editable result, the checks actually performed, unresolved dependencies, and remaining user-owned assets. Do not mistake source inspection or generated screenshots for live behavior verification. ## Operating boundaries Use the complete local instructions when the runtime is installed. If the launcher cannot run, report that context loading did not run, read existing PRODUCT.md and DESIGN.md directly, and continue only supported work. Live browser variant mode requires its own setup; do not claim this guide creates Figma files or deploys a website. Do not auto-install hooks or alter project settings as a side effect of an unrelated refinement. ## Source and rights Read [the pinned upstream and license](UPSTREAM.md).
