Menú
Audit UI/UX against the Anti-Vibe Coding Checklist to ensure modern aesthetics and best practices.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | vibe-check |
| description | Audit UI/UX against the Anti-Vibe Coding Checklist to ensure modern aesthetics and best practices. |
| metadata | {"author":"user","version":"1.0.0","argument-hint":"file-or-pattern"} |
Review UI/UX code against the Anti-Vibe Coding Checklist to ensure modern aesthetics and best practices.
anti-vibe-coding-checklist.md located in this skill directory.Slop Signals posture: Flag and explain. Never silently change. Human decides.
Arguments: files (optional) - The specific files or directories to audit. If empty, the agent should ask or infer based on open files.
Generate the output in the following format:
# 🌊 Vibe Check Report
**Vibe Score**: [1-100] / 100
**Verdict**: [Passed / Needs Polish / Critical Fail]
## 🚫 Major Vibe Killers
(List top 3 critical issues that ruin the feel)
- [ ] **Issue**: [Description]
- **Fix**: [Specific recommendation]
## 🎨 Design & Aesthetics
- **Color/Theme**: [Comments on consistency, tokens]
- **Typography**: [Comments on hierarchy, readability]
- **Spacing/Layout**: [Comments on breathing room, grid]
## 🧠 UX & Polish
- **Feedback**: [Interactive states, loading, errors]
- **Mobile**: [Responsiveness check]
## 🤖 AI Slop Signals
(Structural patterns that signal uncurated AI generation — your call on each)
- **Phantom Deps**: [Any imports not in the manifest, or "None found"]
- **Clone Clusters**: [Repeated logic blocks, or "None found"]
- **Over-Abstraction**: [Single-use utils/wrappers, or "None found"]
- **AI Tell**: [Robotic naming or structural predictability, or "None found"]
## ✨ Quick Wins
(Low effort, high impact changes)
1. ...
2. ...
Enforces semantic commit messages driven by diff-level semantic analysis. Use when making highly detailed commits that require context, conventional formatting, and diff review.
Create Excalidraw diagram JSON files that make visual arguments. Use when the user wants to visualize workflows, architectures, or concepts.
Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
Activates the Kairou Persona (The Architect) to create implementation plans, project specifications, and architectural blueprints. Use when the user asks to "plan", "roadmap", or "architect" a solution.