taewanu
UserPersonal Claude Code skills for freelance and product engineering work
Categories
Indexed Skills (20)
break-the-frame
Generate unexpected, frame-breaking angles on a strategy, product, business model, or career situation by force-applying a library of inversion operators to the user's CONCRETE assets, not by free-associating. Sibling of step-back-as-user and step-back-as-maintainer, but the lens is strategy / identity / business-model, not UX or code. Each angle names a real stake (who has what on the line) and why it was invisible. Use when the user asks for a fresh or unexpected perspective, a different angle, a breakthrough, a way out of a rut, says 'be creative', 'think outside the box', 'what am I not seeing', '색다른 관점', '생각 못한 각도', '돌파구', '프레임 깨줘', or when a discussion has converged too early and needs shaking.
edge-case-challenger
Challenge a working assumption or a settled decision that nobody re-questions, by running a fixed set of probes against the ONE decision, not by free-associating about what could break. Use when something has worked long enough to feel settled and the user wants it pressure-tested: '여태 이렇게 해왔는데', '이 가정 맞나', '전제를 다시 보자', '엣지 케이스', '스케일업하면?', '이거 언젠가 터지지 않나', 'pressure-test this assumption', 'what breaks at scale', 'challenge this decision', 'is this premise still true', 'stress this at 10x', or when a decision passed review on one axis and no one checked the others.
create-obsidian-note
Capture notes into the user's personal Obsidian vault the way its conventions require, and work with its Bases and Categories. Use this WHENEVER the user wants to save, capture, or jot down a note, insight, concept, or learning into their Obsidian vault, or create or edit a Base or Category there, even if they never say "Obsidian", as long as the intent is clearly to persist something into their personal notes. Use it too when they ask where a note should go or how the vault is organized.
time-tracking
Track per-session work time on freelance/personal projects with automatic timestamps, timezone, and category breakdowns. Supports multiple open sessions via switch / pause+resume / concurrent. Use whenever the user wants to start, end, pause, resume, switch, analyze, or invoice a work session, including phrases like "시작", "끝", "일시정지", "재개", "전환", "갈아타", "타임 트래킹 시작", "세션 종료", "이번 주 분석", "분석해줘", "<client> 청구서", "start tracking", "end session", "pause session", "resume", "switch to <project>", "analyze hours", "invoice for X", or simply invoking the skill via /time-tracking. Triggers on any work-session timing intent, even if the user doesn't say "track" or "skill" explicitly.
improve-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
setup-matt-pocock-skills
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
to-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
triage
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
wayfinder
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
handoff
Compact the current conversation into a handoff document for another agent to pick up.
code-review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
codebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
domain-modeling
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
git-guardrails-claude-code
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
prototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
implement
Implement a piece of work based on a spec or set of tickets.
grilling
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.