my-claude-skills

Structured problem-framing discipline before solving non-trivial problems. Activate ONLY when the user explicitly requests it — phrases like "frame this", "think through this first", "elegance-first", "analyze before solving", "structure this problem", or "step back and think". Do NOT auto-trigger on general coding or implementation requests.

Audit whether user intent has been preserved in code artifacts. Use this skill when the user asks to check, audit, or verify that their reasoning and decisions were captured in commits, comments, or documentation. Also trigger when the user says "check intent", "did you capture why", "audit the session", "review what was lost", "verify commits match discussion", or references preserving decision context. Trigger at the end of a coding session if the user asks for a final review before finishing.

Guide for working with Jujutsu (jj) version control system. Use when the user is working in a jj repository, asks about jj commands, or needs help with version control operations in a jj-based project. Covers commands, revsets, filesets, templates, conflicts, and AI-safe workflows.

---

Extract a minimal, revision-ready specification from an existing codebase. Use this skill whenever the user wants to understand what their project does without reading all the code, needs a spec document generated from existing implementation, asks to "reverse-engineer a spec," wants a project overview or summary for handoff, or says things like "what do we have," "summarize the project," "generate a spec from code," "I need to review the architecture," or "document what exists." Also trigger when the user mentions extracting contracts, interfaces, or feature maps from code. Works best on projects up to ~5K LOC but handles larger ones by focusing on public interfaces.