Run any Skill in Manus with one click

Get Started

vibe-check

Stars0

Forks0

UpdatedJune 24, 2026 at 06:04

Audit UI/UX against the Anti-Vibe Coding Checklist to ensure modern aesthetics and best practices.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

peaceyyy

peaceyyy/Alexandria---DCISM-Thesis-Repository

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Web and Digital Interface DesignersComputer and Mathematical Occupations·SOC 15-1255

File Explorer

2 files

SKILL.md

readonly

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"}

Vibe Check

Review UI/UX code against the Anti-Vibe Coding Checklist to ensure modern aesthetics and best practices.

How It Works

Read Context: Analyze the provided files (or the entire active UI context if none provided).
Load Rules: Read anti-vibe-coding-checklist.md located in this skill directory.
Audit: Compare the implementation against the "Anti-Patterns" and "Fixes" in the checklist.
- Technical: Libraries vs. Custom, Clean Patterns.
- Design: Consistency, Hierarchy, Spacing, Tokens.
- UX: Feedback, Onboarding, Accessibility, Mobile.
- Slop Signals: Phantom deps, clone clusters, over-abstraction, AI tells.
Report: Generate a "Vibe Report".

Slop Signals posture: Flag and explain. Never silently change. Human decides.

Usage

Arguments: files (optional) - The specific files or directories to audit. If empty, the agent should ask or infer based on open files.

Vibe Report Format

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. ...

Resources

Anti-Vibe Coding Checklist

More from this repository

same repository

git-detailed

peaceyyy/Alexandria---DCISM-Thesis-Repository

Enforces semantic commit messages driven by diff-level semantic analysis. Use when making highly detailed commits that require context, conventional formatting, and diff review.

2026-07-070

excalidraw-diagram

peaceyyy/Alexandria---DCISM-Thesis-Repository

Create Excalidraw diagram JSON files that make visual arguments. Use when the user wants to visualize workflows, architectures, or concepts.

2026-06-240

plan-writing

peaceyyy/Alexandria---DCISM-Thesis-Repository

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

2026-06-240

planning-project

peaceyyy/Alexandria---DCISM-Thesis-Repository

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.

2026-06-240

Vibe Check

Review UI/UX code against the Anti-Vibe Coding Checklist to ensure modern aesthetics and best practices.

How It Works

Read Context: Analyze the provided files (or the entire active UI context if none provided).

Load Rules: Read anti-vibe-coding-checklist.md located in this skill directory.

Audit: Compare the implementation against the "Anti-Patterns" and "Fixes" in the checklist.

Technical: Libraries vs. Custom, Clean Patterns.
Design: Consistency, Hierarchy, Spacing, Tokens.
UX: Feedback, Onboarding, Accessibility, Mobile.
Slop Signals: Phantom deps, clone clusters, over-abstraction, AI tells.

Report: Generate a "Vibe Report".

Slop Signals posture: Flag and explain. Never silently change. Human decides.

Usage

Arguments: files (optional) - The specific files or directories to audit. If empty, the agent should ask or infer based on open files.

Vibe Report Format

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. ...

Resources