Loading...
Loading...
Found 13,238 Skills
Review source files changed during a phase for bugs, security issues, and code quality problems
Execute all plans in a phase with wave-based parallelization
career/ 에 기록된 경험 하나를 면접관 시점으로 검증하고, 파고들 자리를 되캐서 채운다. 기록이 실제로 면접에서 방어 가능한지 확인할 때 쓴다.
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
Set up your project's global rules, a lean and well-structured root CLAUDE.md (plus a starter .claude/), following the course methodology. Greenfield: pass your PRD and/or architecture-spec path and it derives rules from your engineering decisions (a PRD alone is product context). Brownfield: leave it blank to derive from your primed codebase (run /prime-codebase first), or pass a codebase-analysis doc for a large repo. Use when initializing or re-deriving the AI Layer's rules, onboarding a codebase, or replacing a generic /init output. The customizable replacement for /init.
Self-evolving skills. Record user feedback, update methodologies and rules. Trigger words: update rules, record feedback, improve skill
Apply the skills collection's UPGRADE_NOTES.md after an upgrade. Re-syncs installed tracker and browser-provider descriptors while preserving local edits, reports custom-provider gaps, checks pipeline config and installed artifacts, and summarizes exactly what changed.
Canonical workflow for a task. Read and follow strictly end to end while working on the task.
In chat-only mode, reply like a chat assistant without changing the current code base.
Applies this repository's skill-authoring standard as a procedure. Use for any change to, or judgment about, a file under skills/** — a SKILL.md, a reference, a persona prompt, a bundled script's instructions: creating a skill, editing one, reviewing a skill change, or acting on review feedback (human or bot) about one. Not for src/, tests/, or scripts/ code.
Know a company completely. Opens by asking your goal and where your context lives (CRM? call recorder? team chat? email?), then routes to 4 modes - account deep-dive & plan (external + your internal history with them), org chart (who runs it), tech stack & wedge, competitive battlecard. Use for "tell me about <company>", "account plan for <company>", "org chart for <company>", "what's their tech stack", "battlecard for <competitor>", "how do we beat <X>", "research this account".
[user] 명시적인 작업 원천을 저장소 근거와 자연스러운 대화로 구체화해, 새 세션이나 더 낮은 수준 실행자가 원 대화 없이 사용할 수 있는 `.tigerkit/seed.md`를 준비합니다.