liquid-cat-physics

Liquid Cat Physics

Autonomous deep-work engine. One command to start, then walk away.

How it works

Type /liquid-cat-physics and the skill runs a pre-flight readiness check (once), sets up a recurring cron loop, and keeps going autonomously every 10 minutes.

Each iteration cycle:

ORIENT  → Read state, know where you are           (fast read)
THINK   → Expert assessment, decide next action     (subagent)
GATE    → GREEN/YELLOW/RED confidence check         (decide)
ACT     → Execute ONE unit of work                  (main context)
PERSIST → Update PROJECT_STATE.md + selective notes  (always)

State lives on disk, not in conversation. Context compaction can't erase it.

Reference files (read on demand, NOT every iteration):

• references/confidence-gate.md — re-read when GATE decision is uncertain
• references/anti-thrashing.md — re-read when a failure occurs or failure_log is non-empty
• references/elevate-lens.md — re-read in THINK phase (what to work on)
• references/prodev-standard.md — re-read in THINK + ACT phases (how to execute)
• references/browser-verification.md — re-read when doing visual/UI work

---

When NOT to use this skill

• No project structure (no git repo, no CLAUDE.md, no clear goals) — set those up first
• One-off task or quick fix — just do it directly
• Project requires continuous human design decisions — use /architect instead

---

Invocation

Input	Action
/liquid-cat-physics	Start the loop (default 10m interval) + run first iteration
/liquid-cat-physics 5m	Start with custom interval
/liquid-cat-physics status	Show current state: iteration, cron ID, blocked items, recent actions
/liquid-cat-physics stop	Cancel the cron loop + set status to paused
/liquid-cat-physics reset	Reset iteration count, clear failure log, keep notebook history

---

Startup Decision Tree

Every invocation enters here. One path, no ambiguity.

Read PROJECT_STATE.md → look for ## Loop State
│
├── No Loop State found → FIRST RUN
│   1. Run Phase 0: Pre-Flight (interactive)
│   2. Initialize Loop State + _notebook/
│   3. Create cron at requested interval
│   4. Proceed to ORIENT
│
├── Loop State exists, status: paused
│   1. Create new cron at stored interval
│   2. Set status: active
│   3. Proceed to ORIENT
│
├── Loop State exists, status: active
│   1. Check cron_id via CronList
│   ├── Cron alive → Proceed to ORIENT
│   └── Cron dead (session restart, expired)
│       1. Recreate cron at stored interval
│       2. Update cron_id
│       3. Proceed to ORIENT
│
├── Loop State exists, status: checkpoint
│   1. Human resumed after checkpoint — create new cron
│   2. Set status: active
│   3. Proceed to ORIENT
│
├── Loop State exists, status: complete → Exit. "Project complete."
│
└── Loop State exists, status: blocked-stopped
    1. Check if blocked items are now unblocked
    ├── Still blocked → Exit. Show blocked items.
    └── Something unblocked → Create cron, set active, ORIENT