newkayak12/claude-skills

harness

Use when a substantial request needs verified, non-repetitive output. Triggers on: "이거 제대로 해줘", "검증까지 해서", "하네스 돌려줘", "run the harness", "do this properly with verification", "6단계로 처리해줘", "메타스크립트로". Not for trivial edits or Q&A.

knowledge-base-builder

Use when turning code, docs, notes, or mixed sources into a small-to-moderate, query-efficient Markdown knowledge base with predictable folders, an AI lookup catalog, source-grounded summaries, and RAG-ready metadata.

knowledge-graph-builder

Use when building knowledge graphs by extracting source-grounded entities, relationships, properties, evidence, schema, and graph-ready data from code, documents, notes, tickets, or mixed corpora.

knowledge-query

Use when answering questions over an existing linked Markdown vault, local SQLite index, ontology, knowledge graph, RAG corpus, or mixed knowledge assets while preserving citations, uncertainty, and retrieval traceability.

knowledge-workflow

Use when turning a body of source material into a queryable knowledge system through iterative graph-like exploration: intake, source frontier, linked Markdown vault, ontology, graph records, RAG corpus, and query surfaces.

ontology-builder

Use when designing or refining an ontology for a knowledge system: domain concepts, classes, relationship semantics, constraints, controlled vocabularies, reasoning rules, and mappings to graph/RAG/vault artifacts.

rag-corpus-builder

Use when preparing a retrieval-augmented generation corpus from code, documents, notes, tickets, or mixed sources by chunking, adding metadata, preserving citations, and designing retrieval/evaluation checks.

codex-control

Use when a harness stage must delegate Implement or Test work to local Codex CLI from plugin, repo-local, or embedded installs.

install

Use when installing the harness into a project. Triggers on: "하네스 설치해줘", "이 프로젝트에 하네스 적용해줘", "harness install", "set up the harness here", "게이트 켜줘", "convention 스캐폴딩해줘". Not for running the engine (use the harness skill).

subagent-driven-development

Use when executing an implementation plan with independent tasks using fresh subagents per task. Triggers on: "계획 실행해줘", "서브에이전트로 구현해줘", "subagent-driven", "plan 실행", 태스크별로 에이전트 배포해줘", "두 단계 리뷰로 구현", "현재 세션에서 계획 실행".

writing-plans

Use when a task is large enough that diving in without a plan leads to rework. Triggers: "구현 계획 써줘", "implementation plan", "코딩 전에 계획 잡아줘", "migration plan", "plan before coding", "스텝별로 정리해줘", "리팩토링 계획".

writing-skills

Use when creating a new skill, editing an existing SKILL.md, or fixing one that misfires. Triggers: "스킬 만들어줘", "새 skill 작성", "SKILL.md 써줘", "skill 개선해줘", "create a skill", "skill documentation", "스킬 문서 작성", "workflow skill로 만들어줘".

test-driven-development

Use when someone wants tests that prove a fix or feature actually works, not just tests that happen to pass — TDD, red-green-refactor, falsifiable tests. Triggers: "TDD", "테스트 먼저 작성", "test-first", "red-green-refactor".

executing-plans

Use when a written implementation plan is about to be run — critically review it, set each step's pass bar, then route to the right executor. Triggers: "계획 실행해줘", "plan 실행", "이 계획 검토하고 진행", "execute this plan", "plan 리뷰하고 가자", "실행 전에 기준 잡아줘".

dispatching-parallel-agents

Use when facing 2+ independent jobs that can run concurrently — fan out in parallel, each on its best-fit persona. Triggers: "병렬로 처리해줘", "동시에 여러 작업", "parallel agents", "독립적인 작업들 한번에", "각자 전문가한테 맡겨줘", "multiple independent failures".

verification-before-completion

Use before claiming work is done, tests pass, a build is green, or a bug is fixed without fresh isolated evidence. Triggers on: "완료했어", "테스트 통과", "빌드 성공", "버그 고쳤어", "커밋할게", "PR 올릴게", "done", "should pass", "bug is fixed".

portfolio-feedback

Use when someone shares a developer portfolio and wants honest, interviewer-perspective feedback. Triggers on: "포트폴리오 피드백 해줘", "내 포트폴리오 어때?", "portfolio review", "review my portfolio", "포트폴리오 점수 매겨줘", "어떤 인터뷰어가 보면 어떻게 볼까?", "portfolio critique".

skill-quality-assurance

Use when reviewing or quality-checking a skill before shipping. Runs 6 checks: usefulness, authoring, structure, MCP, weight, output quality. Triggers on: 스킬 검토, skill review, validate skill, 배포 전 검토.

clarity-toolkit

Use when someone is overwhelmed by information, stuck in vague thinking, or spinning in analysis without moving forward. Three modes: cut signal from noise, eliminate vague language, and break overthinking loops. Triggers on: "overwhelmed", "too

critical-thinking-workflow

Use when stress-testing a high-stakes decision, strategic plan, or argument end-to-end. Triggers on: "critical thinking full process", "decision stress-test", "전략 검토 전체", 논리 전체 점검", "high-stakes decision review", "결정 제대로 검토해줘".

tradeoff-articulator

Use when someone is weighing options or making a decision where something is being given up. Makes the cost structure of each option explicit — including hidden axes — without picking a winner. Triggers on: "tradeoff", "트레이드오프", "장단점", "pros and

cli-developer

Use when someone needs to build a command-line tool — defining subcommands, flags, and argument parsing; adding interactive prompts, progress bars, or shell completions; or distributing a cross-platform terminal application. Triggers on: "build a

examined-life

Use when someone wants to look at their life from a distance — not a specific decision, but the whole shape of it. Especially suited to life transitions, major milestones, or the feeling of running on autopilot. Triggers on: "삶을 돌아보고 싶어", "내 인생을

talk

Use when someone wants to talk, vent, or process emotions — not solve a task. Counseling persona. Triggers: "얘기 좀 하자", "상담해줘", "오늘 좀 힘들어", "talk to me", "I need to vent", "머리가 복잡해", "그냥 들어줘", "기분이 이상해".

Source text: Korean

values-explorer

Use when someone is unclear about what actually matters to them, feeling torn between competing priorities, or agonizing over a choice where something important has to be sacrificed. Two moves: extract genuinely held values from behavioral...

skill-trigger-validator

Use when a skill isn't triggering reliably on natural language or Korean input. Triggers on: "스킬이 트리거 안 돼", "skill not firing", "description 개선해줘", "한국어 트리거 추가해줘", trigger coverage audit", "skill 발동 조건 점검", "description이 너무 keyword만 있어".

adr-writer

Use when capturing an architectural decision as an ADR — after a Design Review or from raw context. Triggers: "ADR 써줘", "이 결정 ADR로", "write an ADR", "document this decision". Fixed template; Decision must be declarative ("~를 채택한다").

brainstorming

Use when something needs to be designed or built and the solution shape is unclear. Triggers on: "어떻게 만들지?", "기능 설계해줘", "아키텍처 잡아줘", "design this feature", "how should we build X?", "옵션 더 뽑아줘", "발산해줘". Always invoke before writing code.

Source text: Korean

deep-thinking-workflow

Use when you need to think through a complex problem systematically — generating ideas, stress-testing them, and converging on a decision. Triggers on: "think workflow", "깊이 있게 생각해보자", "아이디어를 체계적으로 검토", structured thinking", "체계적 사고 프로세스", "idea to

Source text: Mixed languages

devils-advocate

Use when someone wants their idea, plan, or decision stress-tested with the strongest possible objections. Triggers on: "반론 던져줘", "약점 찾아줘", "이 계획 문제점이 뭐야?", "devil's advocate", "결함 찾아줘", "비판해줘", "치명적 약점", "steel-man", "punch holes in".

Source text: Mixed languages

first-principles

Use when the current approach feels fundamentally wrong, inherited constraints need questioning, or someone wants to reason from the ground up. Triggers on: "왜 이렇게 해야 해?", "기본부터 다시 생각해", "first principles", "가정을 의심해봐", 이 방식 자체가 맞는 건지", "처음부터 다시

negotiation

Use when someone needs to negotiate, persuade, or navigate a hard conversation. Triggers on: "연봉 협상", "salary negotiation", "계약 협상", "거절당했어", "설득해야 해", 협상 준비", "ask for a raise", "contract terms", "클라이언트 설득", "상사한테 어떻게 말해".

problem-reframer

Use when solutions keep feeling wrong or shallow — when the problem itself may be mis-defined. Triggers on: "뭔가 잘못된 것 같아", "계속 이 문제가 반복돼", "다른 각도로 봐야 할 것 같아", "wrong problem", "solutions feel off", "이 문제 자체가 맞는 건지", "증상만 자꾸 잡는 느낌".

Source text: Korean

thought-organizer

Use when raw, scattered ideas or notes need structure before writing, presenting, or deciding. Triggers on: "생각 정리해줘", "노트 정리", "머릿속이 복잡해", "아이디어 구조화", "outline 만들어줘", mind map", "이거 어떻게 엮어야 해?", "글 쓰기 전에 구조 잡아줘", "산만한 생각 정리".

design-review-writer

Use when drafting a Design Review for a new feature or system. Triggers: "design review 써줘", "디자인 리뷰 문서", "RFC 초안", "write a design review", "이 기능 설계 같이 잡자". Fixed 8-section template.

architecture-designer

Use when someone needs to make or document architectural decisions from scratch — choosing between system topologies (monolith vs. microservices), writing ADRs, evaluating scalability trade-offs, or selecting database and infrastructure patterns.

architecture-workflow

Use when designing a system from scratch, evaluating a monolith-to-MSA migration, or needing a structured end-to-end architecture process from domain discovery to documentation. Triggers on: "system architecture from scratch", "architecture

code-documenter

Use when code, an API, or a project lacks documentation and needs it created or improved — adding docstrings or JSDoc to functions and classes, generating OpenAPI/ Swagger specs from an existing API, building a documentation site, or writing...

documentation-strategy

Plans and maintains a documentation system across architecture docs, API references, runbooks, and onboarding guides — producing a doc coverage map and writing or improving the highest-leverage missing content. Use when a codebase, API, or team...

event-storming

Use when someone is starting a new product, untangling a legacy system, mapping how a business process actually works, or asking where to begin domain modeling — even if they do not name Event Storming explicitly. Triggers on: "domain modeling",