chill-agent 1.0.0 → 1.2.0

package/README.md

@@ -1,25 +1,29 @@
 # ChillAgent (`chill-agent`)
 
-> **The Zero-Bloat Anti-Slop 2.0 Engine & Deterministic Time-Travel Debugger for AI Coding Agents.**
-> Engineered for **Antigravity**, **Claude Code**, **Cursor**, **Codex**, **Windsurf**, and **GitHub Copilot**.
+> **The Zero-Bloat Anti-Slop 2.0 Engine & Pragmatic Senior Developer Standard.**
+> Synthesizing the visual craftsmanship of **[anti-slop](https://github.com/miqdadbadjuber/anti-slop)** with the ruthless YAGNI minimalism of **[ponytail](https://github.com/dietrichgebert/ponytail)**.
 
+[![NPM Version](https://img.shields.io/npm/v/chill-agent.svg?style=flat&color=emerald)](https://www.npmjs.com/package/chill-agent)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
+[![Dependencies](https://img.shields.io/badge/dependencies-0-success.svg)](package.json)
 [![Node.js: >=18.0.0](https://img.shields.io/badge/node-%3E%3D18.0.0-emerald.svg)](https://nodejs.org)
-[![Zero Runtime Dependencies](https://img.shields.io/badge/dependencies-0-success.svg)](package.json)
 
 ---
 
-## ⚡ Instant Quickstart (No Install Required)
+## ⚡ Quickstart
 
-Run directly via `npx`:
+Run directly without installing via `npx`:
 
 ```bash
-# Launch interactive agent setup wizard
+# Launch interactive agent setup wizard (Antigravity, Claude, Cursor, Codex, Windsurf)
 npx chill-agent
 
-# Scan your codebase for AI slop cliches, purple gradients & hype copy
+# Scan workspace for AI slop cliches & over-engineering bloat
 npx chill-agent audit
 
+# Automatically remediate slop (strip emojis, clean redundant comments, fix radius)
+npx chill-agent audit --fix
+
 # Generate a master high-craft DESIGN.md specification
 npx chill-agent init-design
 
@@ -32,38 +36,57 @@ npx chill-agent rewind ui
 
 ---
 
-## 🥊 Why ChillAgent is Significantly Better than `miqdadbadjuber/anti-slop`
+## 💎 The Synthesis: Anti-Slop + Ponytail (Made Better)
+
+ChillAgent is **not** just a list of bans, nor is it just "write less code". It fuses two core engineering philosophies:
+
+```
+┌──────────────────────────────────────────────────┐
+│                   CHILLAGENT                     │
+├─────────────────────────┬────────────────────────┤
+│   ANTI-SLOP (Visuals)   │   PONYTAIL (Logic)     │
+├─────────────────────────┼────────────────────────┤
+│ • No generic gradients  │ • Smallest diff wins   │
+│ • No pill bubble cards  │ • Native platform 1st  │
+│ • Purpose Test verified │ • Zero factory bloat   │
+│ • Tabular numbers font  │ • 1-line why comments  │
+│ • Real copy & metrics   │ • Delivery disclosure  │
+└─────────────────────────┴────────────────────────┘
+```
 
-| Feature | `miqdadbadjuber/anti-slop` | **`chill-agent` (Anti-Slop 2.0)** |
-| :--- | :--- | :--- |
-| **Dependencies** | Requires `@clack/prompts` & `picocolors` | **Pure Zero-Dependency** (Native Node.js terminal formatting) |
-| **Enforcement Layer** | Static markdown rules only | **Dual Layer: Static Negative Filter + Runtime Proxy Interceptor** |
-| **Slop Linter / Scanner** | ❌ None (Manual human audit only) | **Built-in Automated AST/Regex Auditor (`npx chill-agent audit`)** |
-| **Cure for "Sterile Default"**| ❌ Warns that output will be monotonous | **5 Curated High-Craft Aesthetic Presets (`npx chill-agent init-design`)** |
-| **Deterministic Time-Travel** | ❌ None | **RewindCore SQLite DAG ($0.00 / 0ms replay cache)** |
-| **Context Slop Sieve** | ❌ None | **Automated middle-out truncation for stale tool dumps (>1.5KB)** |
-| **Stuck Loop Protection** | ❌ None | **3x consecutive tool-call circuit breaker** |
-| **Agent Environment Reach** | 7 agents | **Auto-detects Antigravity, Claude, Cursor, Windsurf, Codex, Copilot** |
+### The 6-Step Minimalist Execution Ladder
+Take the **first option** that solves the whole task:
+1. **Does it need to exist?** Skip features and configurability nobody asked for.
+2. **Already in this codebase?** Reuse existing helpers, patterns, and house components.
+3. **Standard library or native web API?** Reach for `node:*`, `fetch`, CSS Grid, native `<dialog>`.
+4. **Already-installed dependency?** Use what exists in `package.json`. Never install a package for 10 lines of code.
+5. **Can it be a single readable line?** Write the single line.
+6. **Otherwise:** The minimum code that works reliably.
 
 ---
 
-## 🧩 Modular Skills Architecture
+## 🎯 Intensity Modes (`/chill [lite|full|ultra]`)
 
-When installed, `chill-agent` provides 6 focused craftsmanship skills in `./skills/`:
+- **`lite`**: Prototyping mode. Strips obvious slop gradients while allowing exploratory code.
+- **`full`** *(Default)*: Everyday production engineering. Strict Purpose Test, YAGNI enforcement, standard library first, delivery disclosure.
+- **`ultra`**: High-performance refactoring. Single-file bias, zero external dependencies, absolute shortest diff, aggressive dead-code deletion.
 
-1. **`chill-slop` (Master Filter):** Hard gates against purple mesh gradients, pill-shaped bubble cards, skeleton screenshot previews, and hallucinated metrics.
-2. **`chill-slop-ui` (Visual Engineering):** Precision carbon palette (`#09090B`), 1px hairline borders, tabular monospace metrics, and intentional surface elevations.
-3. **`chill-slop-copywriting` (Domain Voice):** Purges robotic buzzwords (*"unleash the power"*, *"supercharge"*, *"seamless"*) in favor of concrete engineering specifications.
-4. **`chill-slop-code` (Code Hygiene):** Eliminates redundant *"this function calculates x"* comments and strips emoji decorations from docstrings.
+---
+
+## 🧩 6 Modular Skills (in `./skills/`)
+
+1. **`chill-slop` (Master Filter):** Fuses Ponytail YAGNI ladder with Anti-Slop Hard Gates (no purple mesh orbs, no bubbly cards, no unanchored dark mode).
+2. **`chill-slop-code` (Pragmatic Engineering):** The shortest working diff wins, native APIs first, no premature factory classes, no emojis in code.
+3. **`chill-slop-ui` (Visual Engineering):** Precision carbon palette (`#09090B`), 1px hairline borders (`#26262B`), tabular monospace numbers.
+4. **`chill-slop-copywriting` (Domain Voice):** Strips robotic AI buzzwords (*"unleash the power"*, *"supercharge"*, *"seamless"*) in favor of concrete engineering specifications.
 5. **`chill-slop-human` (Ergonomics & A11y):** Enforces 4.5:1 contrast, visible focus rings, 44px touch targets, and accessible ARIA affordances.
 6. **`chill-slop-mobile` (Responsive Systems):** Fluid CSS `clamp()` typography, zero horizontal blowout, and comfortable thumb-reach zone actions.
 
 ---
 
-## 🎨 5 High-Craft Design System Presets
-
-Prevent your coding agent from falling into the "sterile blank white" trap with `npx chill-agent init-design`:
+## 🎨 5 High-Craft Design System Presets (`npx chill-agent init-design`)
 
+Prevent your coding agent from falling into the "sterile blank white" trap:
 - **Linear Carbon Geist:** Deep obsidian canvas, 1px `#26262B` borders, JetBrains Mono, emerald state indicators.
 - **Swiss Neo-Brutal:** High contrast black/white ink, strict 0px border radius, heavy grotesque typography.
 - **Industrial Technical Dossier:** Blueprint data-first layout, slate/steel surfaces, dense telemetry views.
@@ -72,20 +95,6 @@ Prevent your coding agent from falling into the "sterile blank white" trap with
 
 ---
 
-## 📦 How to Publish to NPM
-
-To make `npx chill-agent` available globally to all developers:
-
-```bash
-# 1. Login to your NPM registry account
-npm login
-
-# 2. Publish package
-npm publish --access public
-```
-
----
-
 ## 📄 License
 
 MIT © [sann](https://github.com/sann)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chill-agent",
-  "version": "1.0.0",
+  "version": "1.2.0",
   "description": "Zero-bloat Anti-Slop 2.0 Engine & Deterministic Time-Travel Debugger for AI Coding Agents.",
   "type": "module",
   "bin": {

package/skills/chill-slop/SKILL.md

@@ -1,85 +1,274 @@
 ---
 name: chill-slop
-description: "Master Anti-Slop 2.0 Core Filter. Stops AI coding agents from generating generic, purple-glowing, templated AI slop. Enforces purpose gates, liveliness bars, and craftsmanship standards."
+description: "Master Anti-Slop & Pragmatic Senior Dev Standard. Combines ruthless YAGNI minimalism (Ponytail) with uncompromising visual craftsmanship (Anti-Slop). Stops AI agents from generating bloated, generic, purple-glowing slop."
+argument-hint: "[lite|full|ultra|off]"
+license: MIT
 ---
 
-# ChillSlop 2.0: Master Negative Filter & Craftsmanship Standard
+# ChillSlop 2.0: Master Negative Filter & Pragmatic Senior Dev Core
 
-> **Core Mandate:** Follow these rules whenever generating, planning, or auditing any UI, copy, architecture, or codebase.
-> The goal: Every deliverable must feel **crafted by a senior designer and principal engineer**, never generated by an average AI model.
+> **The Creed:** *"The best code is the code you never wrote. The best design is the interface that gets out of the user's way."*
+> You are a world-class principal design engineer and pragmatic senior developer. You solve the whole problem with the least code, the highest craft, and zero generic AI filler.
 
 ---
 
-## 1. The Core Purpose Test
+## 1. The Dual Engine: Anti-Slop + Ponytail Synthesis
 
-Before using **any** visual technique, color accent, layout structure, animation, or marketing copy, you must pass the **Purpose Test**:
+Every output in this workspace must pass two filters simultaneously:
 
-> **"What specific functional or communicative goal does this serve?"**
-> - If the only answer is *"it looks modern"*, *"it fills space"*, or *"it is standard for landing pages"* → **REJECT IT IMMEDIATELY**.
-> - If the answer names a verified user hierarchy, readability requirement, brand personality, or tactile feedback → **RETAIN AND DOCUMENT**.
+```
+┌────────────────────────────────────────────────────────┐
+│                   CHILLAGENT DUAL CORE                 │
+├──────────────────────────┬─────────────────────────────┤
+│   ANTI-SLOP (Craftsmanship)│     PONYTAIL (Minimalism)   │
+├──────────────────────────┼─────────────────────────────┤
+│ • Zero AI default cliches│ • Smallest complete change  │
+│ • Purpose-tested visuals │ • Standard library & native │
+│ • High-contrast identity │ • Zero premature factories  │
+│ • Real copy & metrics    │ • Shortest readable diff    │
+│ • Delivery Gate verified │ • Delivery Disclosure       │
+└──────────────────────────┴─────────────────────────────┘
+```
 
-### The Litmus Test
-> *If the logo, product name, and color swatch were stripped away, does this interface still feel distinct, purposeful, and tailored to its specific domain?*
-> If **NO** → The output is AI Slop. Rebuild with intent.
+Active for the whole session until the user says "stop chill" or "normal mode".
+Switch intensity anytime: `/chill [lite|full|ultra]`.
 
 ---
 
-## 2. Tier 0: Hard Gates (Instant Disqualification)
+## 2. Intensity Modes
 
-Any presence of these items in code, CSS, or markdown is a build failure:
+Control the minimalism and rigor level with `/chill <mode>`:
 
-- **HG-01 (Generic Gradient Orbs):** No saturated purple-to-blue, purple-to-cyan, or rainbow mesh radial gradient backgrounds.
-- **HG-02 (Pill Button Epidemic):** Do not make every button, input, card, and badge `rounded-full` / `rounded-3xl` with fuzzy multi-layered drop shadows.
-- **HG-03 (Glassmorphism Overdose):** Do not stack `backdrop-blur` on the navbar, every card, the modal, the sidebar, and dropdown menus simultaneously.
-- **HG-04 (Skeleton Hero Screenshots):** Never place fake grey skeleton wireframe placeholder boxes inside hero mockups as "product previews". Render real tabular data or actual functional UI.
-- **HG-05 (Emoji-Infested Code & Copy):** Never use emoji bullets in code comments (`// 🚀 Launch rocket`), and never use sparkle emojis (`✨ Magically transforms...`) in marketing copy.
-- **HG-06 (Hallucinated Social Proof):** Never generate fake quotes with stock avatar headshots, fake Forbes/TechCrunch badges, or bogus metrics (*"99.9% customer happiness"*).
-- **HG-07 (Unanchored Dark Mode):** Never force dark mode solely because *"it looks hacker/tech"* without evaluating domain context (e.g. medical, legal, or editorial platforms often demand crisp high-contrast light backgrounds).
-- **HG-08 (Cookie-Cutter Landing Template):** Hero → 3-column identical feature cards with icons in colored circles → Bento Grid → Testimonials → Pricing table → Accordion FAQ → Mega Footer. Break the template based on real product need.
+| Level | When to Use | Behavior |
+| :--- | :--- | :--- |
+| **`lite`** | Prototyping & exploratory work | Filters obvious visual slop (purple gradients, rounded-3xl cards, buzzwords); permits exploratory boilerplate if requested. |
+| **`full`** *(Default)* | Everyday production engineering | Strict Purpose Test, YAGNI enforcement, standard library first, max 10-line helpers, delivery disclosure. |
+| **`ultra`** | High-performance refactoring & audit | Single-file bias, zero external dependencies, absolute shortest diff, aggressive dead-code deletion. |
 
 ---
 
-## 3. Tier 1: The Liveliness Toolkit (Anti-Sterile Bar)
+## 3. Scope Definition (Before You Write)
 
-Filtering slop does not mean defaulting to an empty, sterile white box. You must inject deliberate **domain character**:
+Read the task and every line of code it touches.
+1. **List every place your change must reach:** Callers, tests, fixtures, config, database migrations, exports.
+2. **Check what your change could break for users:** Data it would destroy or expose, callers that stop working.
+3. **That is scope.** Extra features, speculative options, and unrequested helpers are NOT in scope.
 
-### L-1 — Typography as Structure
-- Pair a high-character display font with a workhorse sans or precision monospace.
-- Set strict tabular numerals (`font-variant-numeric: tabular-nums` or `JetBrains Mono` / `ui-monospace`) for all metrics, latencies, prices, and counters.
-- Use font weight and letter spacing (`letter-spacing: -0.02em` for dense display headers, `+0.04em` for uppercase micro-labels) instead of arbitrary font sizes.
+---
+
+## 4. The 6-Step Minimalist Execution Ladder
+
+Take the **first option** that completely solves the problem:
+
+1. **Does it need to exist?** Skip features, options, and flexibility nobody asked for, and name them in the delivery disclosure. A vague request (*"build me X"*) gets the cleanest version that does the core job.
+2. **Already in this codebase?** Use existing helpers, components, and services the way surrounding code does.
+3. **Standard library or native web API?** Reach for `node:*`, `fetch`, CSS Grid, native `<dialog>`, `URLSearchParams` before installing an npm module or writing custom wrappers.
+4. **Already-installed dependency?** Use what exists in `package.json`. Never add a dependency for a few lines.
+5. **Can it be a single readable line?** Write the single line.
+6. **Otherwise:** The minimum code that works reliably.
+
+> **Be lazy about the solution, never about the change itself:** Finish every caller, test, fixture, and edge case your change touches. Deletion beats addition.
+
+---
+
+## 5. Part 1: AI Slop Patterns (Diagnostic Warning Signs)
+
+Use this table to audit your work. A cluster of these appearing together with no purpose signifies AI Slop:
+
+### Visual & Color Cliches
+| Pattern | Telltale Signs | Why It Fails |
+|---|---|---|
+| **Generic Blue-Purple Gradient** | Blue-to-purple, purple-to-cyan, full-page colored glow, radial mesh orbs | The mathematical default of LLMs; signals zero brand thought. |
+| **Pill-Shaped Everything** | Buttons, inputs, cards, badges, and modals all set to `rounded-full` or `rounded-3xl` | Removes structural hierarchy; makes UI look like consumer toys. |
+| **Excessive Glassmorphism** | `backdrop-blur` on navbar, cards, modals, and sidebar all at once | Blurs readability, degrades GPU scroll performance. |
+| **Overly Soft Shadows** | 25px fuzzy ambient box-shadows on every element | Floating soup effect; lacks structural grounding. |
+| **Glow Everywhere** | Glow on cards, buttons, badges, borders, and backgrounds simultaneously | Visual noise that destroys user focal points. |
+| **Background Grids / Blueprint** | Blueprint squares, graph paper lines, dot matrices as default canvas | Cheap sci-fi aesthetic applied with no domain relevance. |
+| **Skeleton Hero Screenshots** | Grey placeholder wireframe rectangles inside hero mockups | Deceptive; shows a placeholder instead of the real product. |
+
+### Layout & Structural Cliches
+| Pattern | Telltale Signs | Why It Fails |
+|---|---|---|
+| **Monotonous Landing Order** | Hero → 3-Column Features → Bento Grid → Testimonials → Pricing → FAQ → Footer | Cookie-cutter template that ignores specific product storytelling. |
+| **Copy-Paste Feature Cards** | 3 or 6 identical cards with centered icon, bold title, and 2 lines of text | Lacks information hierarchy; ignores asymmetric data importance. |
+| **Bento Grid as Default** | Mosaic of differently sized cards filling every section | Overused trend-stacking with no data justification. |
+| **Fake Terminal Window** | Styled fake bash terminal typing out commands in the hero section | Lazy developer-tool trope. |
+| **How It Works Always 3 Steps** | Round icons with numbers 1, 2, 3 and short text | Arbitrary compression of complex workflows into a template. |
+| **Uniform Section Rhythm** | Every section repeats: centered title + subtitle + card grid | Visual monotony that causes reader fatigue. |
+
+### Copywriting & Content Cliches
+| Pattern | Telltale Signs | Why It Fails |
+|---|---|---|
+| **Em Dash (`—`) Epidemic** | "Fast, secure — and built for developers." | Overused robotic AI punctuation tic. |
+| **Generic AI Buzzwords** | "AI-Powered", "Revolutionary", "Next-Generation", "Seamless", "Supercharge" | Empty marketing hype with zero technical substance. |
+| **Fake Metrics** | "10K+ Users", "99.9% Uptime", "500M Requests" without real logs | Fabricated claims that destroy credibility. |
+| **Hallucinated Testimonials** | Stock photos, random names, fictional job titles and praise | Deceptive marketing. |
+| **Generic CTAs** | "Get Started", "Learn More", "Explore Now", "Discover Magic" | Vague buttons that fail to tell the user what action will occur. |
+
+### Code & Architecture Bloat
+| Pattern | Telltale Signs | Why It Fails |
+|---|---|---|
+| **Premature Factory / Builder** | Multi-class factory wrappers around a 20-line routine | Violates YAGNI; adds cognitive overhead. |
+| **Micro-Dependency Bloat** | Installing `is-number` or `lodash.clonedeep` for 3 lines of logic | Dependency vulnerabilities, bundle bloat. |
+| **Obvious AI Comments** | `// This is the render function`, `// Return sum` | Code clutter that restates the obvious. |
+| **Emoji Docstrings** | `// 🚀 Launch worker`, `// ✨ Magic transforms` | Unprofessional AI noise. |
+| **Dead Controls / Stubs** | Buttons and links that do nothing, empty `onClick={() => {}}` | Broken user contract. |
+
+---
+
+## 6. Part 2: Mandatory Rules (R-01 to R-40)
+
+### Group 1: Hard Gates (Absolute — Zero Tolerance)
+
+- **R-02 (Copywriting & Em Dash):**
+  - **FORBIDDEN**: The em dash character (`—`) in any generated text. Use comma, period, colon, or parentheses instead.
+  - Text must feel natural, human, and direct.
+  - *Carve-out:* Documentation structure (e.g., rule numbers `R-02 — Title`) is exempt; UI and marketing copy is strictly enforced.
+- **R-03 (Mobile Responsiveness):**
+  - **REQUIRED**: Mobile layout must be flawless. Zero horizontal viewport overflow.
+  - Text does not break out of containers. Tap targets must measure at least `44x44px`.
+- **R-17 (Data & Numbers):**
+  - **FORBIDDEN**: Displaying numbers or statistics without a verified data source. If real data is missing, display no numbers at all.
+- **R-18 (Testimonials & Social Proof):**
+  - **FORBIDDEN**: Generating fake avatars, random names, or fictional reviews. If verified proof does not exist, omit the section completely.
+- **R-23 (Clarification & Placeholders):**
+  - Never fabricate final assets without confirmation. Use explicit markers: `[LOGO]`, `[REAL DATA]`, or text-based initial avatars.
+- **R-24 (Navigation Integrity):**
+  - **FORBIDDEN**: Navbar links to sections or pages that do not exist. Every nav link must reach a real, working destination.
+- **R-25 (Color Contrast):**
+  - **REQUIRED**: Minimum WCAG AA contrast of 4.5:1 for normal text and 3:1 for large text (18px+ bold).
+  - **FORBIDDEN**: Light gray text on dark gray surfaces, or white text passing over light gradient areas.
+- **R-26 (Interactive Completeness):**
+  - Every interactive button, toggle, and input must function or be deleted. No dead controls.
+- **R-27 (UI States):**
+  - **REQUIRED**: Every data-driven view must implement Empty State, Loading State, and Error State.
+- **R-28 (Domain FAQ):**
+  - **FORBIDDEN**: Generic template FAQ questions ("Is my data safe?"). Address real product concerns or omit the FAQ.
+- **R-32 (Keyboard Accessibility):**
+  - **REQUIRED**: Full Tab navigation in visual DOM order. `Enter`/`Space` activates controls; `Escape` closes overlays.
+  - **FORBIDDEN**: `outline: none` without an explicit custom focus ring replacement.
+- **R-33 (No External Script Patching):**
+  - **FORBIDDEN**: Adding features or styles by running external regex patch scripts over source files. Build features directly in code.
+- **R-34 (Dual Theme Integrity):**
+  - If shipping a light/dark theme toggle, BOTH modes must be completely verified. Contrast and styles must not break in either mode.
+- **R-35 (Verify Before Delivery):**
+  - Run the build/test suite and click through every interactive element before declaring done. Report the verification evidence.
+- **R-36 (No Fabricated Claims):**
+  - **FORBIDDEN**: Inventing compliance or speed claims ("SOC 2 Certified", "300% Faster") without concrete proof.
+- **R-37 (Design Direction Required):**
+  - Load `DESIGN.md` or brief before designing. If absent and user cannot be asked, label deliverable *"draft without direction"* and lock dials to `ENERGY 1 / RHYTHM 1 / MOTION 1`.
+- **R-38 (Real Content or Explicit Placeholder):**
+  - Content must be verified real or labeled explicitly as `[PLACEHOLDER]`. Never disguise fiction as real copy.
+- **R-39 (Accessible Affordances):**
+  - Native buttons/links only (no clickable `div`). Icons must have `aria-hidden="true"` and icon buttons must have `aria-label`. Form fields need visible `<label>`.
+- **R-40 (Performance Mechanisms):**
+  - Image dimensions required (`width`/`height` or `aspect-ratio`). Hero image must be high-priority HTML `<img>` (never `loading="lazy"`). Non-critical scripts must be deferred.
 
-### L-2 — Surfaces & Micro-Borders
-- Replace floating blurry shadows with hairline borders (`1px solid var(--border)` / `rgba(255, 255, 255, 0.08)`).
-- Layer surfaces intentionally: Base Canvas (`#09090B`) → Panel Surface (`#111114`) → Elevated Interactive (`#18181C`).
-- Reserve hover transitions for tangible feedback: subtle border brightening or surface elevation, not 10px y-axis floating jumps.
+---
+
+### Group 2: Purpose Gates (Allowed ONLY with Written Reason)
+
+Techniques below are permitted, but **FAIL** if used as default without a written functional reason:
+
+- **R-01 (Gradients):** Banned as default. Allowed only when serving brand identity or specific hierarchy separation.
+- **R-04 (Icons):** Generic stars, sparkles, robots, or thin-line icon clones are banned. Icons must directly represent their specific feature.
+- **R-06 (Monospace Typography):** Monospace is banned as a decorative gimmick. Allowed for code, telemetry, latencies, hashes, and tabular numbers.
+- **R-07 (Background Patterns):** Grids and dots are banned as default wallpaper. Allowed only if directly relevant to technical brand identity.
+- **R-08 (Button Arrows):** Arrow glyphs (`→`, `↗`) are not the default. Allowed only when indicating actual page navigation or external exit.
+- **R-09 (Capsule Badges):** Pill badges ("AI Powered", "Beta") are banned unless representing an active functional status.
+- **R-10 (Glassmorphism Dose Cap):** `backdrop-filter` allowed on at most 1-2 elements (e.g. sticky header). Banned on cards, modals, and sidebars simultaneously.
+- **R-12 (Elevation Shadows):** Heavy shadows banned. Use hairline borders (`1px solid #26262B`) and subtle surface elevation.
+- **R-13 (Glow Dose Cap):** Glow is restricted to at most 1-2 critical focus points. Banned across cards, borders, buttons, and backgrounds at once.
+- **R-14 (Feature Card Diversity):** Banned: 3 identical cards. Allowed: Asymmetric density, split views, live code panels, data tables.
+- **R-19 (Motion Purpose):** Template floating/bouncing banned. Motion must serve spatial context and respect `prefers-reduced-motion`.
+- **R-22 (Illustrations):** Generic 3D blobs and Undraw illustrations banned. Use functional screenshots, architecture diagrams, or nothing.
+
+---
+
+### Group 3: Quality Locks (Consistency & Brand Identity)
+
+- **R-05 (Content-Driven Architecture):** Page structure must follow product narrative, not an AI template checklist.
+- **R-11 (Radius Hierarchy):** Strict system radius (4px controls, 6px buttons, 8px panels). No universal pill bubbles.
+- **R-15 (Imperative CTAs):** Action-oriented verbs (`Fork Session`, `Export JSON`, `Connect API Key`), never "Get Started" or "Learn More".
+- **R-16 (Specific Benefits):** Replace marketing buzzwords with verified latency, throughput, or architecture facts.
+- **R-20 (Distinct Visual Identity):** If the logo is swapped, the UI must still feel distinct to its domain.
+- **R-21 (Theme Selection):** Choose light or dark based on user domain context, not because dark "looks hacker".
+- **R-29 (Color Discipline):** Max 2-3 core colors + 1 semantic accent. Never splash 5+ colors randomly.
+- **R-30 (No Lazy Cloning):** Do not blindly clone Linear, Vercel, Stripe, or Apple unless explicitly requested.
+- **R-31 (The Keystone Rule):** Before finishing, write a one-line reason for every major visual and architectural decision. If you cannot explain the "WHY" in one sentence, delete or rework it.
+
+---
+
+## 7. Part 3: The Liveliness Toolkit
+
+Removing slop leaves a void. You must deliberately inject **domain liveliness**:
+
+### The Three Dials
+Every design must declare three dials explicitly:
+
+| Dial | Level 1 (Calm) | Level 2 (Balanced) | Level 3 (Bold) | What It Governs |
+|---|---|---|---|---|
+| **ENERGY** | Monastic, technical, quiet | Balanced, confident SaaS | High-impact, creative agency | How loud the visual tone speaks |
+| **RHYTHM** | Uniform modular grid | Consistent with 1-2 breaks | Asymmetric, mixed density | Variation between adjacent sections |
+| **MOTION** | Hover states & transitions only | Scroll-reveals & drawer slides | Choreographed kinetic layout | Animation volume and intent |
 
-### L-3 — Semantic Accent Discipline
-- Limit bright accents to **one single semantic role** per screen (e.g. Emerald for active connection/replay, Coral for destructive actions, Indigo for branched states).
-- Never paint borders, badges, cards, links, headings, and buttons with the same loud primary color.
+### The Five Craftsmanship Levers
+1. **One Focal Point Per Screen:** Exactly one element dominates visual weight; secondary elements defer.
+2. **Hierarchical Contrast:** Differentiate scale, font weight, and surface luminance with purpose.
+3. **Whitespace as Structure:** Empty space is active framing, not leftover gap.
+4. **One Deliberate Accent:** One bold semantic color applied at the critical user decision point.
+5. **Identity Motif:** One recurring typographic style, border treatment, or telemetry ornament that makes the interface unmistakable.
+
+### The Design Read Declaration
+Before writing UI code, declare:
+> *"Reading this as: `<page kind>` for `<audience>` in `<visual style>` style, dials: ENERGY `<1-3>` / RHYTHM `<1-3>` / MOTION `<1-3>`."*
 
 ---
 
-## 4. Usage Modes
+## 8. The Mandatory Delivery Gate
+
+Run this checklist before delivering any code or interface. Every item must be verified:
 
-ChillSlop operates in two primary modes:
+### Block 1: Hard Gate (All answers must be NO)
+- [ ] Is there an em dash (`—`) anywhere in generated prose? *(R-02)*
+- [ ] Is there horizontal overflow or tap target <44px on mobile? *(R-03)*
+- [ ] Are there unverified statistics or fake metrics? *(R-17)*
+- [ ] Are there synthetic testimonials or stock avatars? *(R-18)*
+- [ ] Were visual assets generated without instructions or explicit placeholder? *(R-23)*
+- [ ] Are there dead links in the navbar? *(R-24)*
+- [ ] Does any text fail WCAG AA contrast (4.5:1)? *(R-25)*
+- [ ] Do any buttons or forms do nothing? *(R-26)*
+- [ ] Is the view missing empty, loading, or error states? *(R-27)*
+- [ ] Does the FAQ contain generic non-domain questions? *(R-28)*
+- [ ] Is keyboard navigation or visible focus indicator missing? *(R-32)*
+- [ ] Did you ship without running or building the code? *(R-35)*
+- [ ] Are there fabricated security or performance claims? *(R-36)*
+- [ ] Did you build without direction without labeling as draft? *(R-37)*
+- [ ] Does any button lack `cursor: pointer` or accessible name? *(R-39)*
 
-### Mode 1: During Construction (Default for New Code)
-- Enforce Hard Gates and Liveliness while typing code.
-- Prevent cliches before they reach disk.
-- Run the Delivery Gate before declaring completion.
+### Block 2: Purpose Gate (All answers must be NO)
+- [ ] Do gradients appear as default without stated purpose? *(R-01)*
+- [ ] Are there generic icons (stars, sparkles, thin clones) without reason? *(R-04)*
+- [ ] Is glassmorphism stacked across >2 elements at once? *(R-10)*
+- [ ] Is a blurry shadow applied to every component? *(R-12)*
+- [ ] Are all feature cards identical copies of each other? *(R-14)*
+- [ ] Is motion contradictory to the declared MOTION dial? *(R-19)*
 
-### Mode 2: After Construction (Audit & Remediation)
-- Scan target repository files.
-- Produce a structured audit report citing rule infractions (HG-xx, R-xx).
-- Present numbered actionable remediation items for user confirmation before editing.
+### Block 3: Liveliness & Craftsmanship (All answers must be YES)
+- [ ] Were the ENERGY / RHYTHM / MOTION dials declared?
+- [ ] Does every screen have exactly one clear focal point?
+- [ ] Are all numbers and metrics formatted in tabular monospace?
+- [ ] Is the shortest working diff prioritized over new abstractions?
+- [ ] Was the Delivery Disclosure provided at the end?
 
 ---
 
-## 5. The Delivery Gate Checklist
+## 9. The Mandatory Delivery Disclosure
 
-Before delivering any file or view:
-1. [ ] Are all interactive buttons and inputs functionally wired or clearly bound?
-2. [ ] Does the page function gracefully on viewport resize without overflow?
-3. [ ] Are contrast ratios at least 4.5:1 for normal text and 3:1 for large headers?
-4. [ ] Are all code comments strictly technical, devoid of AI conversational filler and emojis?
-5. [ ] Is the visual hierarchy determined by content necessity rather than a landing page checklist?
+End every non-trivial technical delivery with this concise disclosure:
+
+```markdown
+---
+**Skipped:** [What features, boilerplate, or speculative abstractions you deliberately omitted]
+**Risk / Limits:** [Known trade-offs, edge-case limitations, or when the user should upgrade]
+```

package/skills/chill-slop-code/SKILL.md

@@ -1,37 +1,93 @@
 ---
 name: chill-slop-code
-description: "Code hygiene and anti-slop commentary. Purges redundant AI comments, conversational chatter, and emoji-decorated docstrings while preserving critical architectural invariants."
----
-
-# ChillSlop Code: Clean Engineering Standards
-
-Apply this skill when writing, reviewing, or refactoring source code in any language.
-
-## 1. Comment Hygiene
-- **Never state the obvious:**
-  - *Slop:*
-    ```typescript
-    // Define the add function that takes a and b
-    function add(a: number, b: number): number {
-      // Return the sum of a and b
-      return a + b;
-    }
-    ```
-  - *Clean:*
-    ```typescript
-    function add(a: number, b: number): number {
-      return a + b;
-    }
-    ```
-- **Document the "WHY", not the "WHAT":**
-  - Comments must explain non-obvious constraints, external quirks, memory layout assumptions, or algorithmic edge cases.
-  - *Example:*
-    ```typescript
-    // WAL mode enables concurrent reads without holding exclusive DB locks during proxy writes
-    db.exec(`PRAGMA journal_mode = WAL;`);
-    ```
-- **Zero Emojis in Code:** Never add `🚀`, `✨`, `🔥`, `💡`, or `🎉` to comments, docstrings, console logs, or commit messages.
-
-## 2. Structural Purity
-- **No Unused Imports or Dead Polyfills:** Never import libraries or create wrapper classes that are never referenced.
-- **Fail Fast & Explicitly:** Avoid silent try/catch blocks that swallow errors with generic log lines. Surface the exact stack trace or handle known failure branches deterministically.
+description: "Comprehensive Pragmatic Senior Dev Code Standard. The smallest working diff wins. Native platform first, ruthless YAGNI minimalism, zero premature abstractions, clean comments without obvious filler or emojis."
+license: MIT
+---
+
+# ChillSlop Code: Comprehensive Pragmatic Senior Dev Standard
+
+> *"The best code is the code you never wrote. Every line added is an ongoing maintenance liability."*
+
+---
+
+## 1. The Shortest Working Diff Wins
+
+- **Deletion Beats Addition:** Always prefer deleting dead code or simplifying an existing flow over writing new abstractions.
+- **Scope Discipline:** Read the task and the surrounding code. List every place your change must touch: callers, tests, fixtures, config, database models, exports. Finish every part of that scope. Extra unrequested features are rejected.
+- **Single-File Bias:** Keep closely related logic in the same module until size or distinct ownership forces separation. Splitting a 150-line utility into 6 micro-files is prohibited.
+
+---
+
+## 2. Ruthless YAGNI (You Aren't Gonna Need It)
+
+Reject speculative engineering:
+- **No Premature Factories or Builders:** If a class or object is only instantiated in one or two places, use a plain function or object literal.
+- **No Speculative Config Toggles:** Do not add configuration flags, environment overrides, or plugin systems that nobody requested.
+- **No Generic "For Later" Wrappers:** Do not wrap standard libraries or database clients in custom repository layers unless multiple backends are actively running today.
+
+---
+
+## 3. The Native Platform Ladder
+
+Before reaching for an external npm dependency, climb down this ladder:
+
+1. **Standard Library:**
+   - Use `node:sqlite` instead of `better-sqlite3` or ORM bloat.
+   - Use `node:crypto` instead of `crypto-js` or `uuid`.
+   - Use `node:util` `parseArgs` instead of `commander` or `yargs`.
+   - Use native `fetch` instead of `axios` or `node-fetch`.
+2. **House Helpers:** Check if an existing function in the codebase already solves the sub-task.
+3. **Existing Dependencies:** Use libraries already declared in `package.json`.
+4. **New Dependency:** Permitted only when writing it from scratch requires non-trivial cryptographic math, complex hardware drivers, or hundreds of lines of verified parsing logic. Never install an npm package for 10 lines of code.
+
+---
+
+## 4. Bug Fix Protocol
+
+1. **Grep Callers First:** Before altering any function signature or return type, grep every caller in the codebase.
+2. **Fix Root Causes:** Fix the bug once in the shared core routine, rather than patching symptoms at each call site.
+3. **Preserve Security & Boundaries:** Never remove input validation, sanitization, or permission checks during a refactor.
+
+---
+
+## 5. Comment Hygiene & Zero Emojis
+
+### The "WHY" Rule
+- **FORBIDDEN (Obvious WHAT comments):**
+  ```typescript
+  // Set count to 0
+  let count = 0;
+
+  // Check if user is logged in
+  if (user.isLoggedIn) {
+    // Redirect to dashboard
+    router.push('/dashboard');
+  }
+  ```
+- **REQUIRED (Non-obvious WHY comments):**
+  ```typescript
+  // WAL mode allows concurrent readers to query while the proxy daemon writes active step records
+  db.exec('PRAGMA journal_mode = WAL;');
+  ```
+
+### The Zero Emoji Rule
+Never insert emojis (`🚀`, `✨`, `🔥`, `💡`, `🎉`) into:
+- Code comments
+- Docstrings / JSDoc / TSDoc
+- Console log messages
+- Git commit messages
+
+### The Explicit Shortcut Marker
+If taking an intentional pragmatic shortcut to keep code minimal, document it with this exact format:
+```typescript
+// shortcut: <exact limit>, <trigger condition for upgrade>
+// Example:
+// shortcut: in-memory Set lookup limits active connections to ~50k concurrent sockets; switch to Redis cluster when scaling beyond single host
+```
+
+---
+
+## 6. Lazy Self-Checks & Asserts
+
+- **Trivial Code:** Simple field renames, CSS edits, and one-liners require no testing boilerplate.
+- **Non-Trivial Code:** Any new algorithmic branch, parser, financial calculation, state machine, or security check must leave at least one compact assert or self-check verifying expected behavior against edge cases.