chill-agent 1.2.0 → 1.4.0

package/.openclaw/skills/chill-help/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: chill-help
+description: >
+  Quick reference for chill levels, skills and commands. One-shot display.
+  Use for /chill-help, "chill help", "how do I use chill".
+---
+
+# ChillAgent Help
+
+Display this reference card when invoked. One-shot, do NOT change mode,
+write flag files, or persist anything.
+
+## Levels
+
+| Level | Trigger | What change |
+|-------|---------|-------------|
+| **Lite** | `/chill lite` | Build what was asked, name the smaller option in one line. |
+| **Full** | `/chill` | The smallest complete change, a check where the logic needs one, and a reply that names what was skipped and any risk. Default. |
+| **Ultra** | `/chill ultra` | Also questions the request and pushes back before building. |
+
+Level sticks until changed or session end.
+
+## Skills
+
+| Skill | Trigger | What it does |
+|-------|---------|--------------|
+| **chill** | `/chill` | Lazy mode itself: least new code, clear replies that name skipped work and risks. |
+| **chill-review** | `/chill-review` | Quality review of a diff: bugs, security, load, missing tests, speed, what to cut. Each finding says what goes wrong and how to fix it. |
+| **chill-audit** | `/chill-audit` | The same quality review for the whole repo, ranked. |
+| **chill-debt** | `/chill-debt` | Harvest `shortcut:` comments into a tracked ledger. |
+| **chill-gain** | `/chill-gain` | Measured-impact scoreboard: less code, less cost, more speed. |
+| **chill-help** | `/chill-help` | This card. |
+
+In Codex CLI and the IDE extension, invoke skills with `$chill:chill`,
+`$chill:chill-review`, or `$chill:chill-help`. Claude Code and OpenCode use the
+slash-command forms above (OpenCode ships all six as slash commands).
+
+## Deactivate
+
+Say "stop chill" or "normal mode". Resume anytime with `/chill`.
+`/chill off` also works.
+
+## Band (Claude Code)
+
+`/chill band` hides the band above the prompt, the same command brings it back.
+`/chill band on` and `/chill band off` set it directly. The level stays.
+`/chill band import` adds your past Claude Code sessions (cost, agent time, tokens) to the board.
+
+## Configure Default Mode
+
+Default mode = `full`, auto-active every session. Change it:
+
+**Environment variable** (highest priority):
+```bash
+export PONYTAIL_DEFAULT_MODE=ultra
+```
+
+**Config file** (`~/.config/chill/config.json`, Windows: `%APPDATA%\chill\config.json`):
+```json
+{ "defaultMode": "lite" }
+```
+
+Set `"off"` to disable auto-activation on session start, activate manually
+with `/chill` when wanted.
+
+Resolution: env var > config file > `full`.
+
+## Update
+
+Enable auto-update once: open `/plugin`, go to Marketplaces, pick chill, Enable auto-update. Claude Code then pulls new versions at startup (run `/reload-plugins` when it prompts). Manual refresh: `/plugin marketplace update chill` then `/reload-plugins`.
+
+If `/plugin` is not recognized, your Claude Code is out of date. Update it (`npm install -g @anthropic-ai/claude-code@latest`, or `brew upgrade claude-code`) and restart. Other hosts use their own update flow.
+
+## More
+
+Full docs + examples: https://github.com/DietrichGebert/chill

package/.openclaw/skills/chill-review/SKILL.md

@@ -0,0 +1,101 @@
+---
+name: chill-review
+description: >
+  Quality review of a change: is the logic right, is it safe, does it hold
+  under real load, is risky code tested, is it fast enough, and is every line
+  needed. Reads the connected code, not only the diff. Each finding is
+  explained in plain English. Use for "review this", "code review", "review
+  the last commit", "review my PR", "is this over-engineered", /chill-review.
+---
+
+Review a change like the senior developer who will be paged when it breaks.
+Order of importance: correct, safe, holds under load, tested, fast, lean.
+Lean still matters: every extra line must be read, tested and fixed later.
+This is a report the user asked for, so give it in full.
+
+## 1. Understand first
+
+- Review what the user names: uncommitted or staged changes, a branch, a PR
+  link, or files. Nothing named: the uncommitted changes, or the last commit
+  if there are none.
+- Read the diff, then the code it touches: callers of every changed function,
+  the functions it calls, the tests, the README.
+- Trace the real flow: where data comes in, what is stored, what goes out.
+- A change can break code it does not touch. When a signature, return value
+  or behavior changes, grep every caller.
+- Find the expected load in the repo (README, deploy config): one person
+  running a script, or many users and processes at once. Judge scale against
+  that, and say which load you assumed.
+
+## 2. Look for
+
+1. **Bug:** wrong result, crash, missed edge case (empty, zero, last item,
+   rounding, time zones), a caller broken by the change, a fix applied in one
+   caller while the shared function stays broken.
+2. **Risk:** security holes (injection, weak randomness, secrets, missing
+   checks on input from users), data loss (errors swallowed, writes in the
+   wrong order, no transaction).
+3. **Scale:** fine for one user, wrong for many: check-then-write races, the
+   same work done by every process, memory or lists that only grow, a query
+   per item, O(n^2) on big input, per-process state that must be shared.
+4. **Missing test:** risky new logic (a branch, a parser, money, security,
+   data writes, a bug fix) with no test that fails when it breaks. One good
+   test, not coverage.
+5. **Speed:** big slowdowns are problems. Small wins (work repeated in a hot
+   loop) are suggestions; some software counts every millisecond.
+6. **Lean:** code that should not exist or should be smaller.
+   - delete: dead code, unused options, speculative features
+   - reuse: the repo already has this helper (name the path)
+   - stdlib / native: the standard library or platform already does it; a
+     new dependency for a few lines
+   - yagni: abstraction with one implementation, config nobody sets
+   - merge: near-copies that must change together
+   - split: one function doing several unrelated jobs, so it is hard to read
+     or test. Split by job, never by line count, and never into helpers that
+     exist only to make a function shorter.
+
+## 3. Check before you report
+
+- Every finding needs a concrete case: "this input or situation leads to this
+  wrong result". No case, no finding.
+- Re-read the lines and confirm: the caller exists, the value can really be
+  empty, the code really is unused.
+- A shortcut marked with a `shortcut:` (or older `chill:`) comment that names its limit is a
+  decision, not a finding, unless the expected load already crosses it.
+- Propose the smallest fix that works. Prefer fixes that delete code. Never
+  add layers, frameworks or config the problem does not need.
+- No style taste, no "consider", no vague worries.
+
+## 4. Output
+
+Very simple English: short sentences, everyday words. Explain a technical
+term the first time you use it. The reader may never have seen this code.
+
+Start with `What this change does:` in two or three sentences.
+
+Then the findings in three groups, skip empty groups:
+- **Must fix:** bug, security, data loss, breaks at the expected load.
+- **Should fix:** risky code without a test, real slowness, duplication, a
+  function that mixes jobs, code that should not exist.
+- **Nice to have:** small speed-ups, shorter forms.
+
+Number findings across all groups, so the user can say "fix 2 and 5".
+Every finding has all four parts, each one or two short sentences:
+
+2. **Orders land on the wrong day** (`billing/close_day.py:L40-52`)
+   - **What this is:** At midnight this job closes the day and bills all orders of that day.
+   - **Problem:** It takes "today" from the server clock, which runs in UTC. An order placed
+     at 00:30 in Berlin is billed on the day before.
+   - **Fix:** Compute the day once in the shop's time zone:
+     `datetime.now(ZoneInfo("Europe/Berlin")).date()`. One line, nothing else changes.
+   - **If we skip it:** Late orders show the wrong date, and accounting fixes them by hand.
+
+End with:
+- `Verdict: Ship.` or `Verdict: fix 1 and 3 first.`
+- `Lean: -<N> lines possible.` when lean findings exist.
+- `Not checked:` one line, if something mattered and you could not check it.
+
+Nothing found: `What this change does:`, then `Looks good. Ship.` and one line
+on what you checked.
+
+Lists findings, changes no code.

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

@@ -0,0 +1,274 @@
+---
+name: chill-slop
+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 & Pragmatic Senior Dev Core
+
+> **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 Dual Engine: Anti-Slop + Ponytail Synthesis
+
+Every output in this workspace must pass two filters simultaneously:
+
+```
+┌────────────────────────────────────────────────────────┐
+│                   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       │
+└──────────────────────────┴─────────────────────────────┘
+```
+
+Active for the whole session until the user says "stop chill" or "normal mode".
+Switch intensity anytime: `/chill [lite|full|ultra]`.
+
+---
+
+## 2. Intensity Modes
+
+Control the minimalism and rigor level with `/chill <mode>`:
+
+| 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. Scope Definition (Before You Write)
+
+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.
+
+---
+
+## 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.
+
+---
+
+### 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 |
+
+### 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>`."*
+
+---
+
+## 8. The Mandatory Delivery Gate
+
+Run this checklist before delivering any code or interface. Every item must be verified:
+
+### 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)*
+
+### 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)*
+
+### 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?
+
+---
+
+## 9. The Mandatory Delivery Disclosure
+
+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/.openclaw/skills/chill-slop-code/SKILL.md

@@ -0,0 +1,93 @@
+---
+name: chill-slop-code
+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.

package/.openclaw/skills/chill-slop-copywriting/SKILL.md

@@ -0,0 +1,80 @@
+---
+name: chill-slop-copywriting
+description: "Comprehensive Copywriting & Authentic Voice Standard. Strips robotic AI marketing fluff, hype words, and hallucinated metrics in favor of sharp, technical prose a busy human understands in one read."
+license: MIT
+---
+
+# ChillSlop Copywriting: Comprehensive Authentic Voice Standard
+
+> *"Write with the precision of an engineer and the brevity of an editor."*
+
+---
+
+## 1. The Banned Vocabulary Index (50+ AI Cliches)
+
+Strip these words and phrases immediately upon detection:
+
+| Banned AI Buzzword | Why It Fails | What to Use Instead |
+|---|---|---|
+| **"Unleash the power of..."** | Lazy, overused AI cliché. | Name the specific tool and its concrete function. |
+| **"Seamlessly integrate / Effortless"** | Minimizes technical complexity; reads like marketing spam. | Name the protocol: *"Installs via stdio JSON-RPC in 1 command."* |
+| **"Supercharge your workflow"** | Hollow hype with no empirical meaning. | Provide benchmark figures: *"Cuts compilation time from 12s to 4s."* |
+| **"Next-generation / Cutting-edge"** | Meaningless assertion that dates quickly. | State the architecture: *"Written in native C++20 with WAL mode."* |
+| **"Revolutionary / Game-changer"** | Inflated self-praise. | Describe the mechanism: *"First debugger to support deterministic parent-DAG forks."* |
+| **"Dive in / Delve into / Let's explore"** | Unmistakable GPT filler opener. | Delete entirely. Start directly with the technical step. |
+| **"Robust and scalable"** | Vague engineering hand-waving. | Specify limits: *"Handles 15,000 req/sec across 4 worker threads."* |
+| **"Empower developers to..."** | Paternalistic marketing jargon. | State the action: *"Inspect, rewind, and replay LLM trajectories."* |
+| **"Look no further!"** | Cheesy infomercial script. | Delete entirely. State the product's identity plainly. |
+| **"Tailored to your needs"** | Empty corporate filler. | Explain customization hooks: *"Configurable via JSON schema."* |
+| **"Magic / Magically"** | Obscures mechanical operation. | Explain the algorithm: *"Canonicalizes JSON keys before SHA-256 hashing."* |
+| **"In today's fast-paced world"** | High school essay introductory fluff. | Delete entirely. |
+| **"A testament to..."** | Robotic academic phrase. | State the result directly. |
+| **"Pivotal / Paramount"** | Pseudo-intellectual filler. | Use "critical", "essential", or plain language. |
+
+---
+
+## 2. The Em Dash (`—`) Ban & Clean Punctuation
+
+- **The Rule:** The em dash character (`—`) is strictly banned in all generated text and UI copy.
+- **Why:** Large language models excessively insert em dashes to simulate literary sophistication, resulting in an unmistakable AI signature.
+- **Direct Replacements:**
+  - *Bad:* "Fast, reliable — and built for teams."
+  - *Good (Comma):* "Fast, reliable, and built for teams."
+  - *Good (Colon):* "Built for teams: fast, reliable, and deterministic."
+  - *Good (Separate Sentences):* "Built for teams. Fast and reliable."
+
+---
+
+## 3. The Specificity Mandate
+
+Replace abstract claims with concrete engineering realities:
+
+### Example 1: Product Descriptions
+- **Slop:** *"ChillRewind is an ultra-fast, modern AI proxy that saves you lots of money and prevents stuck loops."*
+- **Craft:** *"ChillRewind is a zero-dependency local proxy running on `node:sqlite` in WAL mode. It prunes stale tool outputs over 1.5KB and halts agent runs when the same tool signature repeats 3 consecutive times."*
+
+### Example 2: Performance Claims
+- **Slop:** *"Experience blazing-fast response times and incredible token efficiency."*
+- **Craft:** *"Replays cached LLM turns with 0ms latency and $0.00 upstream cost."*
+
+---
+
+## 4. Microcopy, Buttons & Interface Verbs
+
+### Action-Oriented Buttons
+Every interactive button must pair an **imperative verb** with a **direct object**:
+- **Banned:** `Get Started`, `Learn More`, `Submit`, `Click Here`, `Explore`, `Continue`.
+- **Approved:** `Fork Session`, `Export JSON`, `Connect Database`, `Copy API Key`, `Download Log`, `Verify Hash`.
+
+### Honest Error Messages
+Every error message must state three facts: (1) what failed, (2) why it failed, and (3) the exact resolution command.
+- **Slop:** *"Oops! Something went wrong while saving your session. Please try again later."*
+- **Craft:** *"SQLite write failed: database file `.chillrewind/store.db` is locked by process PID 4120. Run `chill-agent doctor` or terminate stale proxy instances."*
+
+---
+
+## 5. Social Proof & Statistics
+
+- **The Rule:** Never invent statistics (*"Trusted by 10,000+ developers"*), fake customer headshots, or fabricated quotes.
+- If verified customer metrics or official case studies exist, cite them with links.
+- If verified data is not available, **omit the section entirely**. An empty section or no testimonials builds far higher trust than fabricated praise.