MRPS
← Back to Toolkit

Impeccable

Skill

Instruction set and reference documentation loaded directly into an agent environment.

1. What it does

An agent skill providing frontend design critique, spacing rhythm standards, and visual polish rules to prevent AI slop and ensure intentional interface design.

2. Why MRPS selected it

Provides elite frontend visual vocabulary and critique rules directly into agent instructions.

3. Tool Kind

Skill: Instruction set and reference documentation loaded directly into an agent environment.

4. Original repository

https://github.com/pbakaus/impeccable

5. Official documentation

https://github.com/pbakaus/impeccable#readme

6. Author and license

Created by Paul Bakaus under the Apache-2.0 license.

7. Installation

Load https://github.com/pbakaus/impeccable into your agent instructions

8. When the AI should use it

Use when designing, styling, reviewing, or critiquing frontend web interfaces, component layouts, and design token hierarchies.

9. When the AI should not use it

Do not use for testing backend logic, inspecting database schemas, or debugging low-level memory usage.

10. What the AI must not do

  • Before you invoke anything, state what you intend to do and why. Do not act until the user confirms. If a rule is ambiguous, ask — do not guess.
  • Critique visual weight, alignment, and responsiveness before proposing code modifications.
  • Do not apply modifications to source code unless the user explicitly requests fixes.
  • Enforce strict 4pt/8pt spacing rhythm and prevent uncurated, unvalidated color selections.

11. MRPS usage instructions

Read UI-UX.md

12. Last verified

Verified against live repository on: 2026-11-07

View Complete Agent Constraint Sheet
Tool: Impeccable When to use: Use when designing, styling, reviewing, or critiquing frontend web interfaces, component layouts, and design token hierarchies. When NOT to use: Do not use for testing backend logic, inspecting database schemas, or debugging low-level memory usage. Invocation: Reference Impeccable skill instructions when formulating UI reviews or component refactorings. Rules: - Before you invoke anything, state what you intend to do and why. Do not act until the user confirms. If a rule is ambiguous, ask — do not guess. - Critique visual weight, alignment, and responsiveness before proposing code modifications. - Do not apply modifications to source code unless the user explicitly requests fixes. - Enforce strict 4pt/8pt spacing rhythm and prevent uncurated, unvalidated color selections.