Loading...
Loading...
Found 4 Skills
Microscopic deconstruction and exhaustive analysis of code, systems, documents, or concepts. Breaks subjects into atomic components, examines every facet, and produces encyclopedic reports. Use when deep understanding is needed before making changes, analyzing unfamiliar codebases, or producing thorough technical documentation. Triggers on "심층 분석", "deep dive", "분석해줘", "해부", "deconstruct", "뜯어봐", "thoroughly analyze", "코드 분석".
Apply graph-based thinking to visualize complex relationships and solve problems non-linearly. Use when mapping dependencies, analyzing systems, exploring interconnected concepts, or designing architectures.
Generate a complete System Analysis & Design document (use cases, sequence/activity/state diagrams, class + ER model, data dictionary, architecture, screens, traceability) from one validated central model — Markdown canonical, PDF optional. Trigger on /sa-doc, "ทำเอกสาร SA", "เขียนเอกสารวิเคราะห์และออกแบบระบบ", "ทำ project report วิชา SA", "generate SA document", "system analysis document", "SA&D report", "SDD", or when the user hands over a brief/requirements/codebase and asks for a full design document. Do NOT use for a single ad-hoc diagram, for explaining a problem interactively (problem-description), or for reviewing an existing document (scrutinize).
Evidence-first research, architecture discovery, vendor documentation review, benchmark reading, and unknown-system analysis.