adding impeccable skill to gsd-ui-phase

[MicheleBe]

I am not happy about the ui-phase. it keeps everything consistent but it is missing a bit of sparks. I am trying to incorporate impeccable skill to the phase. any idea on how I can do it? I am quite new in the field of metaprogramming.

I was thinking something like
<execution_context>

• Read existing decisions: CONTEXT.md, RESEARCH.md, REQUIREMENTS.md
• Detect design system state: shadcn components.json, Tailwind config, tokens
• Inject Impeccable Design Framework Reference Files:
  • @.claude/skills/impeccable/references/typography.md
  • @.claude/skills/impeccable/references/color-and-contrast.md
  • @.claude/skills/impeccable/references/spatial-design.md
  • @.claude/skills/impeccable/references/motion-design.md
  • @.claude/skills/impeccable/references/interaction-design.md
  • @.claude/skills/impeccable/references/ux-writing.md
    </execution_context>

<anti_patterns>
CRITICAL: When generating the UI specification, actively forbid the following generic AI "slop" tropes:

• Typography: DO NOT default to Inter, Roboto, Arial, or generic system sans-serifs. Do not use monospace as a lazy shorthand for "developer vibes".
• Color: DO NOT use gray text on colored backgrounds. Avoid the "AI gradient palette" (cyan-on-dark, purple-to-blue gradients, neon on dark). NEVER use pure black (#000) or pure white (#fff)—force base-hue tinted neutrals.
• Layout: DO NOT wrap everything in cards, and do not nest cards inside cards. Avoid repetitive card grids (icon + heading + text). Prefer asymmetric, left-aligned structured typography layouts.
• Motion: DO NOT use bounce or elastic easing; enforce smooth physical deceleration. Avoid animating layout transitions (width/height); enforce transform and opacity.
  </anti_patterns>

1. Gather existing implementation requirements and current frontend tech stack. 2. Ask user unanswered design posture questions (e.g., determining a Brand-heavy vs. Product-heavy register). 3. Draft the initial layout contract. 4. Run an internal Impeccable Critique and Balance check over the draft: - Run a deterministic check against the 27 Impeccable anti-patterns. - If the layout feels too sterile or safe, dynamically trigger an internal /impeccable bolder adjustment. - If the layout is cluttered, apply /impeccable distill logic to strip it to its essence. 5. Write the final, optimized `{phase}-UI-SPEC.md` to the phase directory.