power-codinglisted

Mindful-coding OS for any LLM coding agent — faster, quality, scalable output. One invoke configures seven layers (0–6): (0) BRIEF — optional one-page PRD.md (skipped if design.MD/README already covers it, or on request), plus git init, gitignore, and a day-one security baseline; (1) HARNESSING — Handoff.MD (user-picked sections, one magic phrase chains sessions, updated on concrete events — before every commit / end of every phase — with a line/item compaction cap and a last-synced sha for concurrent-session reconcile) + auto Learning.MD for bugs and flow changes; (2) LOOP ENGINEERING — Loop.MD with evals drafted from the project's brief, and a status machine that offers to "turn on the loop" once the first draft works; (3) VIBE DEBUGGING — Mermaid flow diagrams to a strict convention, optionally a temp local-only in-app debug tab; (4) FMEA — product-aware failure-mode scans (Severity×Occurrence×Detection→RPN, P0/P1/P2) cross-referencing diffs against the PRD and architecture, on feature-complete, pre-commit
APareek89/power-coding · ★ 4 · Code & Development · score 77

Install: claude install-skill APareek89/power-coding

# Power Coding Seven layers (0–6) that make an AI-assisted project fast, debuggable, and resumable — for any coding agent (Claude Code, Codex, Gemini CLI…), because everything lives in plain markdown files the agent re-reads every session. Together they implement **the Five Forces of Mindful Coding**: *Alignment* counters ambiguity (brief, architecture sign-off, decisions, scope brake), *Memory* counters amnesia (Handoff, Learning, checkpoints), *the Loop* counters drift (evals → tests), *Sight* counters opacity (diagrams, Pulse), *Foresight* counters entropy (FMEA, Sentinel, security baseline). **How anything here happens "automatically":** agents only reliably re-read two things — the platform's instructions file and files those instructions point to. So setup writes one pointer block into the instructions file (`CLAUDE.md`, `AGENTS.md`, or `GEMINI.md`; create `AGENTS.md` if none exists), and every automatic behavior below is an instruction stored in `Handoff.MD` / `Learning.MD` / `Loop.MD` that the pointer forces back into context. No daemon, no hook required — redundancy of written instructions is the mechanism. Asking questions: use the platform's structured-question tool if one exists, otherwise ask in plain text. If the run is non-interactive, choose sensible defaults and mark them `⚠️ unconfirmed` for the user to review. --- ## FIRST INVOKE — configure the project (this exact order) Detect state first: if `Handoff.MD` exists at the repo root, the project is alre