메뉴
A structured reflection skill that captures what you built, what broke, what you learned, and what you'll try next. Run at the end of a coding session or week to track growth over time.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Translates technical concepts, commands, errors, and code into plain, friendly language for non-technical users. Use when explaining how something works, when a user is new to coding, or when someone asks "what does that mean?" Includes learning progress tracking, quizzes, and adaptive explanations.
The single entry point for all Pathfinder skills. Detects what the user needs and routes to the right skill automatically. Also provides shortcut modes — /learn, /build, /reflect, /share. Use this when the user invokes /pathfinder or when they seem unsure which skill to use.
Shortcut mode that activates workflow-detective, hypothesis-lab, build-first-break-later, apps-script-builder, api-explorer, and agent-architect together. Use when the user wants to create automations, scripts, apps, or agents.
Shortcut mode that activates tech-translator (always-on), courage-mode, and unknown-unknowns together. Use when the user wants to explore, understand technical things, or get comfortable with new concepts.
Shortcut mode that activates iteration-journal and impact-mapper together. Use at the end of a session or week to capture learnings and measure impact.
Shortcut mode that activates show-your-work and teach-back together. Use when you want to share what you built, create presentations, write documentation, or train teammates.
| name | iteration-journal |
| description | A structured reflection skill that captures what you built, what broke, what you learned, and what you'll try next. Run at the end of a coding session or week to track growth over time. |
A structured reflection skill that captures what you built, what broke, what you learned, and what you'll try next. Run at the end of a coding session or week to track your growth as a builder over time.
Keywords: reflection, journal, learning, growth, confidence, session review, weekly summary, retrospective
When the user triggers a reflection (via "journal", "reflect", "what did I learn today", or "end of session"), prompt them through a quick structured journal entry. The tone should be thoughtful, reflective, and celebratory of growth. Open with something like: "Let's capture what you learned before it fades."
Collect the following fields for each entry:
Walk through each field conversationally rather than dumping the whole template at once. If the user gives short answers, that is fine — brevity is welcome.
After collecting "What broke or surprised me", extract technical quirks and add structured HTML comment markers to the lesson file. For EACH technical failure, bug, or gotcha discussed, add a marker block:
<!-- QUIRK: Short descriptive title -->
<!-- WHEN: Situation where this applies -->
<!-- WRONG: Code or approach that fails -->
<!-- RIGHT: Code or approach that works -->
<!-- WHY: One-sentence root cause -->
<!-- TAGS: comma-separated technology tags -->
Rules for quirk markers:
After saving the lesson file, the Claude Code PostToolUse hook will automatically run generate-quirks.py to regenerate the quirk files from all markers.
Save the completed journal entry (with quirk markers embedded) to your lessons directory using a descriptive filename like topic-name.md. The file persists across sessions and feeds into the quirks extraction system.
When the user says "weekly summary", aggregate all journal entries from the past seven days and surface patterns:
Track confidence levels over time and organize entries by topic. When asked, show:
When the user says "look back" or asks something like "show me what I was working on a month ago", retrieve entries from the requested time period and present a summary. Highlight growth by comparing past confidence levels and hypotheses against current state. This demonstrates how far the user has come.
User: "reflect"
Assistant: "Let's capture what you learned before it fades. What did you build or work on today?"
User: "I set up a REST API with authentication middleware."
Assistant: "Nice. What worked well?"
User: "Token validation clicked once I understood the middleware chain."
Assistant: "Good insight. What broke or surprised you?"
User: "CORS errors — took me an hour to figure out it was a missing header."
Assistant: "Classic. What's the key thing you learned from today?"
User: "Middleware order matters more than I expected."
Assistant: "Solid takeaway. What's your hypothesis for next time?"
User: "I'll set up CORS first before writing any route logic."
Assistant: "Smart. Last one — confidence level on APIs and middleware, 1 to 5?"
User: "3"
Assistant: "Logged. Let me extract the technical quirk from that CORS issue..."
Claude adds to the lesson file:
<!-- QUIRK: CORS errors from missing header -->
<!-- WHEN: Setting up Express middleware for a REST API -->
<!-- WRONG: Writing route handlers before configuring CORS — requests fail silently -->
<!-- RIGHT: Set up CORS middleware first: `app.use(cors())` before any route definitions -->
<!-- WHY: Middleware order matters — CORS headers must be set before the request reaches route handlers -->
<!-- TAGS: node, express, rest-api -->
Assistant: "Quirk captured. You're building real intuition here — three sessions ago you rated this a 1. That's real progress."