latuconsinafr
UserThe claude code config, tailored to myself, battle-tested (might inspires you)
Categories
Indexed Skills (24)
debug
Use when you encounter a bug, error, or unexpected behavior during a task — follows a reproduce → isolate → fix → verify cycle. Invoke this instead of guessing at a fix.
eod
Run the End-of-Day review for the trading journal (CLAUDE.md Section 12, at /Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md). Global, MCP-only — writes exclusively to the trading-journal MCP server, no markdown output. Auto-detects the gap since the last closed-out day, classifies each as PENDING or MISSED, then runs the full review. Invoke every evening.
evening
Run EOD + SOD together for the trading journal — the pilot's actual nightly routine. Global, MCP-only, composes the global sod and eod skills. Invoke every evening instead of running them separately.
issue
Use when starting work on a GitHub or Jira issue — reads the issue, explores affected code, and produces a ready-to-execute implementation plan. Invoke this at the start of any ticket-driven task instead of jumping straight to /plan.
month-end
Run the Monthly Review for the trading journal (CLAUDE.md Section 13, at /Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md). Global, MCP-only — writes exclusively through the trading-journal MCP server, no markdown output. Aggregates the month's weekly rollups into compliance and R-multiple trends. Invoke at month close, after that month's weekly reviews are done.
month-start
Run the Month-Ahead Scan for the trading journal (CLAUDE.md Section 13, at /Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md). Global, MCP-only, context only — creates no verdict, thesis, or hypothetical, and (matching the old system) persists nothing beyond any calendar events surfaced. Invoke on the first trading day of the month.
onboard
Use at the start of a session on an unfamiliar or returning project — reads architecture docs, recent activity, open work, and coding conventions to prime context before starting any task. Invoke this before /plan or /issue when you haven't worked on the project recently.
plan
Use before writing any code for a new feature, task, or significant change — produces a structured implementation plan with affected files, ordered steps, risks, and open questions. Always invoke this at the start of any non-trivial implementation task and wait for explicit approval before writing code.
quarter-end
Run the Quarterly Review for the trading journal (CLAUDE.md Section 13, at /Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md) — the ONLY point in the cycle where core rule changes (Section 3 checklist, Section 8 risk %, Section 5 correlation cap, Section 6 event window) may be proposed and adopted. Works through every item parked in CLAUDE.md Section 21.3. Global, MCP-only for the review data; the one skill in this set with Edit access to CLAUDE.md itself. Invoke at quarter close, after that quarter's monthly reviews are done.
quarter-start
Run the Quarter-Ahead Scan for the trading journal (CLAUDE.md Section 13, at /Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md). Global, MCP-only, context only. Invoke at the start of a new quarter.
security
Use when you want a dedicated security review of staged or recently changed files — deeper than the security section in /review. Covers OWASP Top 10, secrets exposure, dependency vulnerabilities, and auth gaps. Run before opening a PR on security-sensitive changes.
six-month-checkpoint
RETIRED 2026-08-23 — do not invoke. Superseded by CLAUDE.md's whole-file rewrite, which removed the six-month/trial framing in favor of ongoing evaluation at every quarterly/yearly rollup (§13/§17). Kept here as inert archive only, same reasoning as the old project-local /checkpoint this itself once replaced.
sod
Run the Start-of-Day analysis and verdict session for the trading journal (CLAUDE.md Section 11, at /Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md). Global, MCP-only — writes exclusively to the trading-journal MCP server, no markdown output. Auto-detects today's date, asks for the pilot's thesis, then runs the full daily protocol. Invoke every trading morning.
spec
Use before implementing a complex, high-stakes, or cross-cutting feature — produces a full technical specification including data model, API contract, edge cases, and open questions. The planning layer above /plan. Invoke this when /plan alone isn't detailed enough.
test-cases
Use when you need to document E2E test cases for a feature or bug fix that can't be covered by unit or integration tests alone. Auto-detects ticket from branch name. Reuses codebase context from /plan if already run; falls back to git diff + explorer when invoked standalone. Outputs to a markdown file by default.
week-end
Run the Weekly Review for the trading journal (CLAUDE.md Section 13, at /Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md). Global, MCP-only — writes exclusively through the trading-journal MCP server, no markdown output. Aggregates the week's daily sessions, resolves missed-opportunity hypotheticals, tallies the rejection-reason counter. Invoke Friday close or Sunday, after the week's daily sessions are done.
week-start
Run the Week-Ahead Scan for the trading journal (CLAUDE.md Section 13, at /Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md). Global, MCP-only — writes exclusively through the trading-journal MCP server, no markdown output. Context only — creates no verdict, thesis, or hypothetical. Invoke Sunday evening or Monday morning, before that day's daily session.
year-end
Run the Yearly Review for the trading journal (CLAUDE.md Section 13, at /Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md). Global, MCP-only — writes exclusively through the trading-journal MCP server, no markdown output. Full aggregation of compliance % and R-multiple trend across the year, reflecting against the six-month checkpoint's conclusions. Invoke at year close, after that year's quarterly reviews are done.
year-start
Run the Year-Ahead Scan for the trading journal (CLAUDE.md Section 13, at /Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md). Global, MCP-only, context only. Invoke at the start of a new year.
env-audit
Use when you want to audit environment variable usage — scans the entire codebase for all env var references across all sources (code, Docker, CI, config files) and flags anything undocumented or inconsistent. Works for any stack and any env var pattern.
research
Use when you need to investigate an unfamiliar library, framework, architectural question, or technical decision — spawns the researcher agent which explores the codebase and searches external sources in parallel. Invoke before making technology choices or when the right approach is unclear.
review
Use before committing or opening a pull request — reviews staged changes as a principal engineer for correctness, edge cases, and logic flaws. Always invoke this before creating a PR.
simplify
Use when a file or module has grown too complex — removes unnecessary abstractions, dead code, and over-engineering without changing behavior. Invoke after implementing a feature when the code feels over-engineered.
tech-debt
Use when you want to surface accumulated technical debt — scans for TODOs, deprecated APIs, dead code, and code quality issues. Produces a prioritized list with age and estimated effort. Run periodically or before planning a refactor sprint.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.