메뉴
이 저장소의 skills
SkillsMP는 joenandez/caspar에서 59개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
joenandez/caspar수집된 skill 59개 중 19개를 표시합니다.
Lightweight scope→research→plan workflow for small/medium tasks (bug fixes, small features). Confirms functional scope with the user, runs parallel read-only research, then writes a quick_task_plan.md with phased parent/sub-task structure. Trigger when the…
원문 언어: 영어
👻 | Safe guided git rebase — backup ref, auto-resolve conflicts, verify tests, smoketest guide. Use to rebase the current branch onto a target (e.g. origin/main), especially when conflicts or post-rebase verification are expected. Do NOT use for merges,…
원문 언어: 영어
Use when the user wants to search the project's captured knowledge, recall a specific past learning, or discover what learnings already exist (e.g. "/caspar:recall", "what do we know about X", "is there a learning for Y"). Do NOT trigger to capture or write…
원문 언어: 영어
Research a codebase to answer a question — fan out read-only agents (finder/analyst/patterns, web-research for 3rd-party), then synthesize evidence-backed findings into a saved research doc with file:line citations. Use when the user asks "how does X work",…
원문 언어: 영어
Interactively scope a feature or improvement into explicit IN / OUT / ANTI-SCOPE boundaries before any planning or code — grounds a hypothesis in repo reality, asks blocking + optional questions, and writes a scope.md. Trigger at the start of a new feature,…
원문 언어: 영어
Execute implementation via strict red/green/refactor — derive test opportunities, write happy + failure tests, confirm RED failures before any production code, ship minimal GREEN code, then report test evidence. Trigger when a task or prompt requires TDD,…
원문 언어: 영어
Define exactly how a feature behaves — user flows, screens, components, states, copy, and accessibility — producing a definitive ux.md spec for implementation. Two stages: align on user flows, then write the detailed spec. Trigger after scope/PRD when a…
원문 언어: 영어
Turn a PRD/scope into a technical implementation plan (`plan.md`) — codebase research, clarifications, then a verification-spine plan ready for task breakdown. Use when planning HOW to build an already-scoped feature, or when `plan` routes here with a depth…
원문 언어: 영어
Generate a right-sized manual test guide for completed work — feature-based checklists scaled to change size, focused on risk. Use after execute/validate when you need a human-runnable QA pass before clean/test. Do NOT use to write automated tests (that's the…
원문 언어: 영어
Investigate a reported bug, pin the root cause, and implement a verified fix. Use when given an error, stack trace, failing behavior, or repro steps and asked to diagnose and fix it — the diagnose-then-fix loop. Do NOT use for greenfield feature work (use…
원문 언어: 영어
Project kickoff — deep codebase + external research producing an evidence-backed kickoff doc, gap analysis, and MVP path before scoping. Use to start a fresh feature/project from an unclear problem, when the user wants research/options/an MVP recommendation…
원문 언어: 영어
Use when the user invokes /learn or asks to remember, save, or capture a pattern, decision, gotcha, procedure, or feature dossier from this session for later re-use ("please remember", "what did we learn?"). Captures durable project knowledge as an on-demand…
원문 언어: 영어
Generate a single self-contained, clickable HTML prototype to make a feature visible before planning — resolving ambiguity pre-scope, validating flows pre-plan, or rendering an approved UX spec for stakeholder review. Triggers on "prototype this", "mock up…
원문 언어: 영어
Lightweight scope→research→plan workflow for small/medium tasks (bug fixes, small features). Confirms functional scope with the user, runs parallel read-only research, then writes a quick_task_plan.md with phased parent/sub-task structure. Trigger when the…
원문 언어: 영어
Use when the user wants to search the project's captured knowledge, recall a specific past learning, or discover what learnings already exist (e.g. "/caspar:recall", "what do we know about X", "is there a learning for Y"). Do NOT trigger to capture or write…
원문 언어: 영어
Research a codebase to answer a question — fan out read-only agents (finder/analyst/patterns, web-research for 3rd-party), then synthesize evidence-backed findings into a saved research doc with file:line citations. Use when the user asks "how does X work",…
원문 언어: 영어
Interactively scope a feature or improvement into explicit IN / OUT / ANTI-SCOPE boundaries before any planning or code — grounds a hypothesis in repo reality, asks blocking + optional questions, and writes a scope.md. Trigger at the start of a new feature,…
원문 언어: 영어
Execute implementation via strict red/green/refactor — derive test opportunities, write happy + failure tests, confirm RED failures before any production code, ship minimal GREEN code, then report test evidence. Trigger when a task or prompt requires TDD,…
원문 언어: 영어
Define exactly how a feature behaves — user flows, screens, components, states, copy, and accessibility — producing a definitive ux.md spec for implementation. Two stages: align on user flows, then write the detailed spec. Trigger after scope/PRD when a…
원문 언어: 영어