Explore skills

Trigger on "what bit me on X", "have I been burned by X", "gotchas with X", "what went wrong last time with X", "warn me about X", "any retros on X", "past incidents with X". Use when the user wants to sanity-check an approach against their own failure history. NOT for general pitfalls (ask Claude directly) or past decisions (use timeln-decided).

Trigger on "frame the engagement", "consult frame", "problem frame", "scope card", "definition of good", "what decision does this support", "in scope out of scope", "client brief → frame", "one-pager frame". Turns a brief or transcript into a structured engagement frame. NOT the solution arc (use consult-arc), NOT phasing gates (use consult-gates), NOT memory recall (use timeln-find / timeln-decid

🤖 My Claude Code config!

Trigger on "acceptance criteria", "consult acceptance", "success criteria", "signoff matrix", "deliverables per phase", "primary path fallback", "definition of done". Per-phase deliverables, measurable criteria (tech + business/ops), owner, primary path + fallback. NOT commercial terms (use consult-commercial), NOT gate questions (use consult-gates).

Install and configure browsers for Windows plus WSL2. Use when a user wants native Linux Chrome inside WSL to work for normal browsing or sign-in flows, or when a tool in WSL needs a Windows host Chrome or Edge instance exposed over CDP. Prefer this skill before any tool-specific browser automation setup.

Troubleshoot Arthur's Dell P2725DE/P2225D monitor setup, especially DisplayPort daisy chaining, "No DP signal from your device" on the P2225D, Windows Fast Startup or shutdown-related display breakage, and reset/reinstall steps for a Lenovo laptop or Dell desktop tower using original Dell cables.

Set or change the per-iTerm2-session label — both the window/tab title AND the badge (watermark) for THIS iTerm2 pane only. Use when the user wants a custom name for this specific tab ("call this tab 'deploy debugging'", "label this session 'prod work'", "set the badge to 'frontend'"). Title and badge always share the same string in this skill (the banner and watermark always match). Edits ~/.clau

Classify a proposed code change as Leaf Node or Core Code to decide how much AI usage and review rigor is appropriate. Use this skill whenever the user asks "is this leaf or core", "what kind of change is this", "should I vibe code this", "can AI write this", "how rigorous should the review be", or before starting any non-trivial change. Also useful as a sub-step inside other workflows (planning,

Review a Pull Request or code change with rigor calibrated to whether it's leaf-node or core code. Use this skill whenever the user asks to review, audit, or evaluate code — phrases like "review this PR", "audit this code", "is this PR ready", "look at this branch", "review my changes", "what do you think of this", "code review please". Also trigger when reviewing AI-authored code specifically. Th

Financial projections and viability analysis for bootstrapped founders. Assesses revenue model clarity, unit economics, cash-flow profile, break-even path, revenue stairs, AI-native cost structure, pricing power, stress resilience, and founder sustainability. Use when user runs `/financial-projections`, asks about "unit economics", "break-even", "cash flow", "revenue projections", "pricing power",

30/60/90-day execution roadmap for bootstrapped founders. Synthesizes all prior analysis into a chronological plan with weekly action items, deliverables, decision gates, kill criteria, tools/budget, and phase exit criteria. Best after running dimension skills. Use when user runs `/launch-plan`, asks about "launch plan", "execution roadmap", "what do I do first", "90-day plan", "action plan", "nex

Risk matrix and pre-mortem analysis for bootstrapped founders. Produces a pre-mortem exercise, ranked risk matrix (10-15 risks), blind spot detection, and 7-dimension risk assessment with 5 validation gates. Surfaces the risks founders aren't thinking about. Use when user runs `/risk-assessment`, asks about "risks", "what could go wrong", "blind spots", "pre-mortem", "risk analysis", "failure mode