메뉴
Use when the user asks "what can I ask you to do?", "what skills do you have?", "show me a usage guide", or types /help. Presents a user-facing cheat sheet of all personal skills grouped by category.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Reviews Python code changes for quality, correctness, and adherence to project conventions before commits or PRs. Checks for SOLID violations, DRY/YAGNI issues, missing tests, type safety, security concerns, and style compliance. Use when reviewing diffs, preparing PRs, after implementing features, or when the user asks to review code. Python-specific — covers ruff, pyright, pytest, and modern Python 3.13+ idioms by default (falls back to the project's pyproject.toml `requires-python` floor if it pins something lower). For deep silent-failure hunting or type-invariant design, use code-review's targeted agents instead.
Turn clear requirements into an ordered, verifiable implementation plan. Use when a spec or well-understood goal needs decomposition before coding — when the task feels too large to start, the order of work isn't obvious, or scope must be communicated. Trigger phrases include: "plan this", "break this down", "make an implementation plan", "how should we implement this", "create a task list", "what order should we build this in". This skill defines HOW to build and in what order — it assumes WHAT to build is already pinned down. If requirements are loose, unverified, or missing, first run the task-scoping skill (task-scope-and-spec: scope a loose engineering task into a tight, testable spec list) or gather inputs per the Input Gate below.
Scope a loose engineering task into a tight, testable spec list. Use when the user gives background for a piece of work and wants the requirements narrowed down before implementation. Trigger phrases include: "scope this", "what are the specs", "what's involved", "what would it take", "what's left for this task", "port this to", "bring this logic to", and "spec this ticket/issue". This skill defines WHAT must be true when the work is done — it does not produce an implementation plan, task ordering, or execution steps. For sequencing the specs into ordered, verifiable tasks, use planning-and-task-decomposition instead.
Bootstrap the .hac/ (Human-Agent Context) directory in any project. Use when the user says "set up hac", "add .hac", "set up working memory", "initialize hac", or when beginning multi-session work on a project that lacks a .hac/ directory. Language-agnostic — works for Python, TypeScript, Go, Rust, or any project type. Also trigger when migrating existing plan files into .hac/ or when resetting a stale .hac/ directory.
Write focused pytest tests covering critical paths, edge cases, and error handling. Avoids redundant tests that bloat codebase. Use for creating minimal but comprehensive test coverage of complex logic, public APIs, and failure scenarios.
Generates a minimal, clear PR description from the current branch's diff and the repo's PR template. Use at the end of any task when the user wants to open a PR or needs a PR description written.
| name | help |
| description | Use when the user asks "what can I ask you to do?", "what skills do you have?", "show me a usage guide", or types /help. Presents a user-facing cheat sheet of all personal skills grouped by category. |
Present this guide to the user exactly as formatted below.
| What you want | What to say |
|---|---|
| Architect or implement a Python feature | "implement X" / "architect Y" / "refactor this module" |
| Scaffold a new Python project from scratch | "new Python project" / "set up a project" / "create a repo" |
| Write pytest tests for a file or module | "write tests for X" / "add test coverage to Y" |
| What you want | What to say |
|---|---|
| Review Python code changes before a commit or PR | "review my code" / "review the diff" / "review before PR" |
| What you want | What to say |
|---|---|
| Diagnose a bug or failing test systematically | "debug this" / "fix this bug" / "why is X failing" |
| What you want | What to say |
|---|---|
| Find where something lives in the codebase | "where is X?" / "find all uses of Y" / "how is this structured?" |
| Understand how code works with a walkthrough | "explain this code" / "how does X work?" / "walk me through Y" |
| What you want | What to say |
|---|---|
| Build RAG, agents, evals, fine-tuning pipelines | "help me build a RAG system" / "design an eval pipeline" / "fine-tune this model" |
| What you want | What to say |
|---|---|
| Automate browser interactions or test a UI | "automate this page" / "test this UI" / "click X on the page" |
| What you want | What to say |
|---|---|
| Draw an Excalidraw diagram of anything | "draw a diagram of X" / "visualize this" / "sketch the architecture" |
| What you want | What to say |
|---|---|
Set up .hac/ working memory on a project | "set up hac" / "add .hac" / "initialize working memory" |
| Create a task in HAC for the current work | "create a hac task for X" / "track this in hac" |
| Update HAC with progress from this session | "update hac" / "log this session in hac" |
| Record an architectural decision | "add a decision to hac" / "record this decision in hac: [choice and why]" |
| Park an idea for later | "park this idea in hac" / "add to parked ideas: X" |
| Mark a task as done | "mark X as done in hac" / "close the hac task for X" |
| Mark a task as blocked | "block the hac task for X" / "X is blocked on Y, update hac" |
| What you want | What to say |
|---|---|
| Hand off work to a new session | "wrap up" / "hand off" / "let's continue in a new chat" |
