learn-codebaselisted

# learn-codebase — Intent-Anchored Reading ## Overview To understand code another agent wrote, anchor every read on the intent that justifies it. Read intent and code as **paired columns**, never in sequence. Code without intent = ritual mimicry (you copy the shape but can't extend it). Intent without code = aspiration (theory you can't ship). Side-by-side = bidirectional traceability you can act on. ## Response Language Rule — applies to ALL outputs Match the user's language. If the user writes in Korean or the repo/team context is Korean, produce the learn-codebase response in Korean by default while preserving code identifiers, file paths, API names, SQL, and exact error text. Use natural Korean product/engineering terms instead of untranslated workflow labels: - `happy path` → `정상 흐름` or `기본 성공 흐름` - `If you only read one thing` → `하나만 읽는다면` - `next options` / `menu` → `다음 선택지` - `TL;DR` → `핵심 요약` - `Level` / `Stage` output labels → `단계` / `기본 응답` - `Map` / `Walk` / `Probe` / `Master` output labels → `지도` / `흐름 추적` / `판단 근거 점검` / `규칙 지도` - `trace` → `흐름 추적` - `entry` → `진입점` - `exit` → `종료 지점` - `error path` → `오류 흐름` Do not output English section labels such as `Level 1 Map` or `Happy Path` for Korean users unless the user explicitly asks for English. ## Plain-Speech Rule (Feynman Mode) — applies to ALL outputs If a non-technical teammate cannot follow your output, the skill failed. Every artifact this skill produces (Map, Walk, Probe, Master) MUST pass `templa