Loading...
Loading...
Found 2 Skills
Create a comprehensive inventory of a codebase. Map structure, entry points, services, infrastructure, domain models, and data flows. Pure documentation—no opinions or recommendations. Use when onboarding to an unfamiliar codebase, documenting existing architecture before changes, preparing for architecture reviews or migration planning, or creating a reference for the team. Triggers on requests like "map this codebase", "document the architecture", "create an inventory", or "what does this codebase contain".
Socratic questioning discipline - the user is asked, not told, until they can state the rule themselves. Use when the user says "ช่วยถามคำถามหน่อย", "ถามให้คิด", "ask me questions", "grill me", "quiz me", "make me think"; when they own an artifact they do not understand - "ยังไม่ค่อยเข้าใจสิ่งนี้ที่ให้ AI ทำ", "I don't understand what was built for me", a plan/map/pipeline/codebase handed to them; before a sign-off, handover, or onboarding onto a system they now own. Not for explaining on request (feynman-explain) and not for challenging a plan before building it (grill-then-plan).