Claude Skills by utk2103

Prompt-Studio memory compressor. Shrinks CLAUDE.md, todo lists, and preference files into Prompt-Studio's lean format to cut input tokens on every load. Preserves all technical substance, code, URLs, and structure. Compressed output overwrites the original; human-readable backup stored out-of-tree as FILE.original.md so Prompt-Studio's skill auto-loader won't re-ingest it. Trigger: /prompt-studio:compress FILEPATH or "compress memory file".

Whole-repo audit for over-engineering. Like lean-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "lean-audit", or "/lean-audit". One-shot report, does not apply fixes.

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /prompt-studio:lean-commit. Offer it when the user stages changes.

Harvest every `lean:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals Lean leaves behind get tracked instead of rotting into "later means never". Use when the user says "lean debt", "/lean-debt", "what did lean defer", "list the shortcuts", "lean ledger", or "what did we mark to do later". One-shot report, changes nothing.

Show Lean's measured impact as a compact scoreboard: less code, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /lean-gain, "lean gain", "what does lean save", "show lean impact", "lean scoreboard".

Quick-reference card for all Lean modes, skills, and commands. One-shot display, not a persistent mode: shows the card and exits without switching levels, writing flag files, or persisting anything. Trigger: /lean-help, "lean help", "what lean commands", "how do I use lean", "lean cheatsheet", "lean reference".

Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /lean-review. Complements correctness-focused review, this one only hunts complexity.

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Al...