Loading...
Loading...
Found 6 Skills
Generate a SYSTEM_OVERVIEW.md that orients a senior engineer new to an unfamiliar codebase, with a Mermaid architecture diagram, a sequence diagram for data flow, and a legacy-pattern assessment. Use when user says 'give me a system overview', 'onboard me on this repo', 'walk me into this legacy codebase', 'document the high-level architecture', or 'create a SYSTEM_OVERVIEW.md'. Do NOT use for code walkthroughs (use explain), persistent architecture chapters (use arc42), or ADRs (use document-decision).
Show users how Continuous Claude works - the opinionated setup with hooks, memory, and coordination
Giải thích phương pháp C4 Model (Context, Container, Component, Code — c4model.com) và dẫn dắt tạo docs/system-overview/c4-context.md + c4-container.md + c4-component-*.md đúng tầng, đúng audience, cùng container-interface.md (mỗi luồng giao tiếp giữa container gán 1 mã CIC, khi cần) và entity-interface.md (entity + quan hệ dữ liệu, khi nhiều CIC/container dùng chung entity, khi cần) đúng phạm vi (schema, không phải API/Code). Dùng khi user hỏi "C4 model là gì", "vẽ context/container/component diagram", "system overview", "kiến trúc hệ thống", "interface contract giữa các container", "entity/ data model", hoặc khi BR/UR/FR đã approved và cần sinh system overview.
Organize reusable programming patterns / library usages / technical skills that answer "To do this kind of thing, the correct approach is this" into a prescriptive reference library, which can be retrieved and reused as needed during feature-design and issue-analyze phases. Three types: pattern (design patterns, programming idioms), library (usage and pitfalls of a certain library/framework), technique (specific operation skills / command recipes). Trigger scenarios: When the user says "record a trick", "this usage is worth recording", "tricks", "record library usage", or when a skill worth archiving is discovered during feature-design / issue-analyze phases and actively pushed. Refer to `codestable/reference/system-overview.md` for how to distinguish it from learning / decisions / explore.
Conduct a targeted code exploration of the repository, and document the process of "Ask Questions → Read Code → Draw Conclusions" as searchable evidence for direct reuse when similar questions arise next time. There are three types: question (investigate code around a specific question and provide conclusions), module-overview (sort out the structure, boundaries, entry points, and dependencies of a module), and spike (conduct lightweight technical exploration of multiple possible directions without making final decisions). Trigger scenarios: Users say "Let's explore first", "How is X implemented in this repository", "Quickly get familiar with this module", "Archive the exploration results". Refer to `codestable/reference/system-overview.md` for how to distinguish it from learning / tricks / decisions.
Dẫn dắt team phân rã BR/UR/FR đã approved thành Epic → Feature → User Story. Dùng skill này khi user nói "tạo backlog", "phân rã epic/feature/user story", "backlog hoạt động thế nào", hoặc sau khi BR/UR/FR đã `status: approved` và `docs/system-overview/ c4-container.md` đã có mà chưa có Epic nào trong docs/backlog.