all publishers

newkayak12

@newkayak12 source repo

197 published skills · page 2 of 2

  1. ▌
    Microservices Architect · newkayak12 bundle
    Use when someone needs to design or evaluate a distributed system — decomposing a monolith, defining service boundaries with DDD, choosing between sync and async communication, or planning resilience and observability. Triggers on:.
    3 repo stars
  2. ▌
    Test Driven Development · newkayak12 bundle
    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".
    3 repo stars
  3. ▌
    Knowledge Base Builder · newkayak12 bundle
    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.
    3 repo stars
  4. ▌
    Pricing Monetization Strategy · newkayak12
    Use when deciding how to charge for a product, evaluating a shift from one pricing model to another, or when a GTM plan needs pricing addressed before launch. Triggers on: "가격 전략", "요금제 설계", "pricing model", "freemium vs free trial".
    3 repo stars
  5. ▌
    Thinking Style Profiler · newkayak12
    Use when someone wants to understand their characteristic thinking style or why they think the way they do — mapping tendencies to actionable learning and working strategies. Triggers on: "thinking style", "내 사고 방식이 어떤지", "사고 패턴 파악".
    3 repo stars
  6. ▌
    Leveling Ic · newkayak12
    Use when an IC wants to understand their current level, close gaps to the next level, and build a promotion-ready evidence portfolio. Triggers on: "what does senior mean in practice", "how do I get to staff", "promotion conversation with manager".
    3 repo stars
  7. ▌
    Identity Explorer · newkayak12
    Use when someone is questioning who they are, feeling unlike themselves, "or going through a period of identity confusion or crisis. Also triggers when someone resists change with that's not like me" — which often signals identity-protective...
    3 repo stars
  8. ▌
    Knowledge Graph Builder · newkayak12
    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.
    3 repo stars
  9. ▌
    Dispatching Parallel Agents · newkayak12
    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".
    3 repo stars
  10. ▌
    Subagent Driven Development · newkayak12 bundle
    Use when executing an implementation plan with independent tasks using fresh subagents per task. Triggers on: "계획 실행해줘", "서브에이전트로 구현해줘", "subagent-driven", "plan 실행", "태스크별로 에이전트 배포해줘", "두 단계 리뷰로 구현", "현재 세션에서 계획 실행".
    3 repo stars
  11. ▌
    Incident Response Playbook · newkayak12
    Guides the developer-side incident lifecycle from triage through mitigation to blameless RCA — with severity classification, Slack update templates, escalation paths, and a structured post-mortem format. Use when a production issue is active or...
    3 repo stars
  12. ▌
    Service Boundary Validator · newkayak12
    Use when someone is deciding whether to split a service, suspects their services are too tightly coupled to deploy independently, wants to validate a proposed service boundary, or is decomposing a monolith and needs to know where to cut.
    3 repo stars
  13. ▌
    Job Application Workflow · newkayak12
    Use when preparing for a job application or career transition end-to-end — from analyzing a JD through to interview preparation. Triggers on: "job application workflow", "이직 준비 전체", "취업 프로세스 시작", "career transition", "job search process".
    3 repo stars
  14. ▌
    Motivation Explorer · newkayak12
    Use when someone has lost motivation, is doing something but doesn't know why, or suspects their stated reason isn't the real one. Also triggers when someone knows what they want but can't seem to pursue it — ambivalence almost always has a...
    3 repo stars
  15. ▌
    Technical Feasibility Assessment · newkayak12
    Use when a PM or product team needs a rapid feasibility signal on a feature idea before committing engineering time — assessing implementation risk, complexity, and make-vs-buy tradeoffs without full engineering involvement. Triggers on:.
    3 repo stars
  16. ▌
    Critical Thinking Workflow · newkayak12
    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", "결정 제대로 검토해줘".
    3 repo stars
  17. ▌
    1 On 1 Manager · newkayak12
    Use when a manager wants to run better 1-on-1s — moving from status-update check-ins to growth and feedback conversations that build real trust with direct reports. Triggers on: "improve my 1-on-1s", "1-on-1 feels like a status update".
    3 repo stars
  18. ▌
    Ego State Identifier · newkayak12
    Use when someone is confused about why they reacted the way they did — especially when it felt automatic, disproportionate, childlike, or like they heard a parental voice in their head. Triggers on: "왜 이렇게 반응했지", "자동으로 나왔어", "어린애처럼 굴었어".
    3 repo stars
  19. ▌
    Design Review Writer · newkayak12 bundle
    Use when drafting a Design Review for a new feature or system. Triggers: "design review 써줘", "디자인 리뷰 문서", "RFC 초안", "write a design review", "이 기능 설계 같이 잡자". Fixed 8-section template.
    3 repo stars
  20. ▌
    Codex Control 2 · newkayak12
    Use when a harness stage must delegate Implement or Test work to local Codex CLI from plugin, repo-local, or embedded installs.
    3 repo stars
  21. ▌
    Transaction Boundary Reviewer · newkayak12 bundle
    Use when data appears inconsistent after failures, when two writes need to succeed or fail together, or when transactions are causing lock contention or timeout errors under load. Reviews isolation levels, atomicity gaps, overly wide...
    3 repo stars
  22. ▌
    Leveling Manager · newkayak12
    Use when an engineering manager needs to evaluate an engineer's level fairly, build a promotion case with evidence, or align with peers in a calibration conversation. Triggers on: "write a promotion case", "calibration prep", "level rubric design".
    3 repo stars
  23. ▌
    Strength Growth Mapper · newkayak12
    Use when someone wants to understand what they are genuinely good at, is processing feedback, or deciding where to invest development effort. Maps the underlying strength pattern, the shadow it casts when overused, whether a weakness is a...
    3 repo stars
  24. ▌
    Attachment Style Mirror · newkayak12
    Use when someone is confused about a recurring relationship pattern, struggling with closeness or distance, or asking why certain dynamics keep repeating across relationships. Triggers on: "애착 유형", "attachment style", "불안 애착", "회피 애착", "관계 패턴".
    3 repo stars
  25. ▌
    Self Discovery Workflow · newkayak12
    Use when someone wants to understand themselves more deeply — not just answer a single question, but explore the full landscape of who they are. Especially suited to life transitions, career crossroads, burnout recovery, and wanting to know...
    3 repo stars
  26. ▌
    Verification Before Completion · newkayak12 bundle
    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".
    3 repo stars
  27. ▌
    Leadership Workflow · newkayak12
    Use when someone wants to run the full IC growth cycle or the full manager development cycle — from understanding level expectations through to high-quality growth conversations. Triggers on: "IC growth cycle", "manager development cycle".
    3 repo stars
  28. ▌
    Performance Profiling Optimization · newkayak12
    Guides systematic performance investigation from symptom to fix — establishing a baseline, profiling the bottleneck, identifying root cause, applying a targeted change, and verifying the improvement with data. Use when someone has a concrete...
    3 repo stars
  29. ▌
    QA · newkayak12
    Use when the user has said this is a QA pass — cases written and executed against existing work — to run through the teams harness — "QA 그래프로 돌려줘", "테스트 케이스 작성하고 실행해줘", "run the qa flow". Pins flow: qa.
    3 repo stars
  30. ▌
    Plan · newkayak12
    Use when the user has said the deliverable is a PRD to run through the teams harness — "기획서 그래프로", "PRD 작성해서 그래프로 돌려줘", "run the planning flow", "write a PRD through the graph". Pins flow: plan.
    3 repo stars
  31. ▌
    Shape Up · newkayak12
    Use when a team is stuck in an infinite backlog, cannot ship complete features, or needs a planning process with real tradeoffs and hard commitments. Also use when setting up 6-week cycles, writing pitches, running a betting table, or replacing...
    3 repo stars
  32. ▌
    Board · newkayak12
    Use when the user wants a status board of teams runs via tm_board — every EPIC, or one EPIC's STORY kanban. Triggers: "보드 보여줘", "티켓 현황", "show me the board", "what EPICs are running". Read-only, prints a table, never raw JSON or a doc's contents.
    3 repo stars
  33. ▌
    Patch · newkayak12 bundle
    Use when preparing a patch release of the teams plugin source: bumps x.y.Z in plugin.json and marketplace.json and prepends the same entry to README Status and KOR.md 상태. Not for project installs.
    3 repo stars
  34. ▌
    Remove · newkayak12 bundle
    Use when removing teams from a project: team.json, the dispatch gate, the CLAUDE.md block and gitignore lines. Keeps conventions, run and task history unless asked by name. Refuses to purge a task whose driver is alive.
    3 repo stars
  35. ▌
    Ticket · newkayak12
    Use when the user wants one ticket's detail via tm_ticket — an EPIC (E-xxxxxxxx) or a STORY (E-xxxxxxxx/Pn). Triggers: "이 티켓 상세", "P2 상태가 뭐야", "show me ticket E-xxx/P2", "last verdict on this story". Read-only, prints a card, never the raw JSON.
    3 repo stars
  36. ▌
    Mentor · newkayak12 bundle
    Use when someone brings a question about how to decide, judge, or live and wants it examined rather than answered. Philosophical mentor — takes a position, tests theirs. Triggers: "멘토가 필요해", "조언이 필요해", "이렇게 사는 게 맞나", "어떻게 판단해야 할지", "mentor me".
    3 repo stars
  37. ▌
    Install · newkayak12
    Use when installing, connecting, or verifying the graph-engineering MCP for a Claude Code project. Not for running a graph; use graph:orchestrate.
    3 repo stars
  38. ▌
    Patch 2 · newkayak12 bundle
    Use when preparing a patch release of the harness plugin source. Triggers on: "harness patch", "하네스 패치", "하네스 버전업", "bump harness patch version". Not for refreshing project copies.
    3 repo stars
  39. ▌
    Contagious · newkayak12 bundle
    Use when someone wants to make a product, feature, campaign, or idea spread through word-of-mouth or organic sharing. Triggers on: "word of mouth", "virality", "how to make this spread", "shareability", "바이럴", "입소문", "공유되게 하고 싶어", "제품이 퍼지게".
    3 repo stars
  40. ▌
    User Story · newkayak12 bundle
    Use when someone needs to write a single user story or a small set of stories — translating a known user need into a structured, development-ready format with acceptance criteria. Triggers on: "write a user story", "user story format".
    3 repo stars
  41. ▌
    Develop · newkayak12
    Use when the user says this is code work for the teams harness — "구현해줘 그래프로", "이 기능 코드로 돌려", "run the dev flow on this", "implement this through the graph". Pins flow: develop; else use orchestrate. Not for installation.
    3 repo stars
  42. ▌
    Install 2 · newkayak12 bundle
    Use when installing teams into a project: team.json defaults, the dispatch gate, and conventions. Not for running a task; use teams:orchestrate.
    3 repo stars
  43. ▌
    Remove 2 · newkayak12 bundle
    Use when removing harness governance from a project. Triggers on: "harness remove", "하네스 삭제", "하네스 제거", "uninstall harness". Preserves project conventions by default.
    3 repo stars
  44. ▌
    Inspired Pm · newkayak12
    Use when applying Marty Cagan's empowered product team model — continuous discovery, outcome ownership, four-risk validation before delivery. Triggers on: "Marty Cagan", "empowered team", "continuous discovery", "discovery vs delivery".
    3 repo stars
  45. ▌
    Document · newkayak12
    Use when the user says the deliverable is a written artifact for the teams harness — "문서 작성 그래프로", "설계 문서 돌려줘", "write the design doc through the graph", "run the document flow". Pins flow: document; else use orchestrate. Not for installation.
    3 repo stars
  46. ▌
    SQL Pro · newkayak12 bundle
    Use when someone needs help writing or rewriting SQL — authoring complex joins, CTEs, window functions, or recursive queries — or designing a schema from scratch, normalizing an existing one, or migrating queries between database dialects.
    3 repo stars
  47. ▌
    Harness · newkayak12
    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.
    3 repo stars
  48. ▌
    Install 3 · newkayak12 bundle
    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).
    3 repo stars
  49. ▌
    Okr Planning · newkayak12
    Use when defining team or company goals for a quarter, aligning cross-team efforts, or when goals exist but progress is unclear and teams are pulling in different directions. Triggers on: "OKR 설정", "분기 목표", "quarterly goals", "key results", "목표 정렬".
    3 repo stars
  50. ▌
    Sbi Writer · newkayak12
    Use when giving feedback to a colleague and the wording feels judgmental, vague, or accusatory. Triggers on: "피드백 어떻게 말해?", "feedback 써줘", "SBI", "동료한테 어떻게 말해야 해?", "칭찬 어떻게 해?", "건설적 피드백", "peer review 써야 해", "이 말이 너무 공격적인 것 같아".
    3 repo stars
  51. ▌
    Orchestrate · newkayak12 bundle
    Use when running a whole request through the graph-engineering MCP and driving its harness nodes without holding the payload yourself. Triggers on: "그래프 돌려줘", "노드 단위로 돌려줘", "run it through the MCP", "orchestrate this run". Not for installation.
    3 repo stars
  52. ▌
    Orchestrate 2 · newkayak12 bundle
    Use when running a whole request through the teams-engineering MCP and driving its harness nodes without holding the payload yourself. Triggers on: "그래프 돌려줘", "노드 단위로 돌려줘", "run it through the MCP", "orchestrate this run". Not for installation.
    3 repo stars
  53. ▌
    Negotiation · newkayak12 bundle
    Use when someone needs to negotiate, persuade, or navigate a hard conversation. Triggers on: "연봉 협상", "salary negotiation", "계약 협상", "거절당했어", "설득해야 해", "협상 준비", "ask for a raise", "contract terms", "클라이언트 설득", "상사한테 어떻게 말해".
    3 repo stars
  54. ▌
    Clean Code · newkayak12 bundle
    Use when reviewing, refactoring, or writing code that others need to read and maintain — any code that is hard to understand, has grown too long, or whose intent is not immediately clear. Triggers on: "리팩토링", "코드 가독성", "clean code", "code review".
    3 repo stars
  55. ▌
    Prd Development · newkayak12 bundle
    Use when turning scattered discovery notes, Slack threads, or stakeholder requests into a structured PRD that engineers can act on. Triggers on: "PRD 작성", "기획서", "제품 요구사항 문서", "write a PRD", "product requirements document", "engineering handoff".
    3 repo stars
  56. ▌
    Test Master · newkayak12 bundle
    Use when someone needs to write, improve, or audit tests — generating unit, integration, E2E, performance, or security tests, analyzing coverage gaps, or producing a test plan or defect report. Triggers on: "테스트 작성", "단위 테스트", "커버리지 분석".
    3 repo stars
  57. ▌
    Brainstorming · newkayak12 bundle
    Use when something needs to be designed or built and the shape of the solution is still open — before any code. Triggers on: "어떻게 만들지?", "기능 설계해줘", "아키텍처 잡아줘", "옵션 더 뽑아줘", "발산해줘", "design this feature", "how should we build X?".
    3 repo stars
  58. ▌
    Writing Plans · newkayak12 bundle
    Use when a task is large enough that diving in without a plan leads to rework. Triggers: "구현 계획 써줘", "implementation plan", "코딩 전에 계획 잡아줘", "migration plan", "plan before coding", "스텝별로 정리해줘", "리팩토링 계획".
    3 repo stars
  59. ▌
    Talk · newkayak12 bundle
    Use when someone wants to talk, vent, or process emotions — not solve a task. Counseling persona. Triggers: "얘기 좀 하자", "상담해줘", "오늘 좀 힘들어", "talk to me", "I need to vent", "머리가 복잡해", "그냥 들어줘", "기분이 이상해".
    3 repo stars
  60. ▌
    Sre Engineer · newkayak12 bundle
    Use when someone needs to establish or improve production reliability practices: defining SLOs and error budgets, setting up golden-signal alerting and dashboards, building incident response runbooks, reducing operational toil through automation,...
    3 repo stars
  61. ▌
    Product Discovery · newkayak12
    Use when uncertain which discovery approach fits the situation, or when evaluating whether continuous discovery vs. fixed-cycle planning better suits the team. Triggers on: "discovery process", "product discovery", "우리 팀에 맞는 프로세스가 뭘까".
    3 repo stars
  62. ▌
    Writing Skills · newkayak12 bundle
    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로 만들어줘".
    3 repo stars
  63. ▌
    CLI Developer · newkayak12 bundle
    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:.
    3 repo stars
  64. ▌
    Codex Control · newkayak12
    Use when a harness stage must delegate Implement or Test work to local Codex CLI from plugin, repo-local, or embedded installs.
    3 repo stars
  65. ▌
    User Story Mapping · newkayak12 bundle
    Use when someone wants to generate a structured user story map directly from existing context — outputting a two-dimensional artifact with backbone activities, steps, tasks, and release slices. Triggers on: "user story map", "story map".
    3 repo stars
  66. ▌
    Devils Advocate · newkayak12 bundle
    Use when someone wants their idea, plan, or decision attacked with the strongest objections before acting on it. Triggers on: "반론 던져줘", "약점 찾아줘", "이 계획 문제점이 뭐야?", "비판해줘", "치명적 약점", "devil's advocate", "steel-man this", "punch holes in".
    3 repo stars
  67. ▌
    Doc Coauthoring · newkayak12 bundle
    Use when starting a substantial written artifact that will be read by others. Triggers on: "문서 같이 써줘", "PRD 작성", "design doc", "RFC 초안", "제안서 써야 해", "technical spec", "decision doc", "write a doc", "문서 작성 도와줘", "spec 써줘".
    3 repo stars
  68. ▌
    Bias Auditor · newkayak12
    Use when evaluating a person or making a decision with high confidence — audits judgment / attribution / metacognition layers and prescribes per-bias remedies. Triggers on: "편향 점검", "내 판단 비뚤어진 것 같아", "audit my reasoning", "bias check", "확신이 과한 것 같아".
    3 repo stars
  69. ▌
    Chaos Engineer · newkayak12 bundle
    Use when someone wants to proactively test whether a distributed system will survive real failures — by designing controlled chaos experiments, injecting faults (network latency, pod deletion, zone outages), planning a game day exercise, or...
    3 repo stars
  70. ▌
    Event Storming · newkayak12
    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".
    3 repo stars
  71. ▌
    Scenario Actor · newkayak12 bundle
    Use when one API scenario spec must be run by hand against a live server — curl per step, captured values chained, evidence logged, verdict returned. Triggers: "이 시나리오 하나만 돌려줘", "이 spec 실행해줘", "run this scenario", "spec=… BASE_URL=…".
    3 repo stars
  72. ▌
    Portfolio Jd · newkayak12
    Use when someone provides both a portfolio and a specific job description and wants to know how well they match — gap analysis, fit score, and positioning advice for that exact role. Triggers on: "이 공고에 맞아?", "JD랑 비교해줘", "이 포지션 지원해도 돼?".
    3 repo stars
  73. ▌
    First Principles · newkayak12
    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", "가정을 의심해봐", "이 방식 자체가 맞는 건지".
    3 repo stars
  74. ▌
    Problem Reframer · newkayak12 bundle
    Use when solutions keep feeling wrong or shallow — when the problem itself may be mis-defined. Triggers on: "뭔가 잘못된 것 같아", "계속 이 문제가 반복돼", "다른 각도로 봐야 할 것 같아", "wrong problem", "solutions feel off", "이 문제 자체가 맞는 건지", "증상만 자꾸 잡는 느낌".
    3 repo stars
  75. ▌
    Code Documenter · newkayak12 bundle
    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...
    3 repo stars
  76. ▌
    Competitive Analysis · newkayak12 bundle
    Use when making a product or business decision where knowing the competitive context changes the answer — before a launch, when writing strategy, or when articulating differentiation. Triggers on: "competitor analysis", "competitive landscape".
    3 repo stars
  77. ▌
    Pm Strategy Workflow · newkayak12
    Use when you need to run the full PM strategy process end-to-end — from market analysis through to stakeholder communication and roadmap delivery. Triggers on: "PM workflow", "제품 전략 전체", "처음부터 GTM까지", "pm process start to finish".
    3 repo stars
  78. ▌
    User Story Splitting · newkayak12 bundle
    Use when a user story, epic, or feature is too large to estimate, sequence, or release independently — breaking it into smaller, independently deliverable stories using proven split patterns. Triggers on: "split this story", "story is too big".
    3 repo stars
  79. ▌
    Microinteractions · newkayak12 bundle
    Use when a UI element feels off, robotic, or incomplete — or when adding polish and delight to moment-to-moment interactions. Triggers on: "버튼 느낌이 어색해", "로딩 애니메이션", "toggle 디자인", "UI 디테일", "인터랙션 개선", "loading state", "feedback animation".
    3 repo stars
  80. ▌
    Thought Organizer · newkayak12 bundle
    Use when raw, scattered ideas or notes need structure before writing, presenting, or deciding. Triggers on: "생각 정리해줘", "노트 정리", "머릿속이 복잡해", "아이디어 구조화", "outline 만들어줘", "mind map", "이거 어떻게 엮어야 해?", "글 쓰기 전에 구조 잡아줘", "산만한 생각 정리".
    3 repo stars
  81. ▌
    Testing Workflow · newkayak12
    Use when someone wants to build a complete, stable test suite from scratch — starting with TDD discipline, moving into coverage strategy, and ending with flaky test elimination. Triggers on: "testing workflow", "테스트 전체 프로세스", "TDD부터 커버리지까지".
    3 repo stars
  82. ▌
    Executing Plans · newkayak12
    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 리뷰하고 가자", "실행 전에 기준 잡아줘".
    3 repo stars
  83. ▌
    Go To Market Planning · newkayak12
    Use when a product or feature is near-complete and the team needs to answer: who do we target first, what do we say, where do we reach them, and how do we know the launch succeeded? Triggers on: "GTM plan", "launch strategy", "출시 전략", "론칭 계획".
    3 repo stars
  84. ▌
    Hypothesis Driven Dev · newkayak12
    Use when testing a product idea before committing to building it, or when a team needs to validate a key assumption with the smallest possible experiment. Triggers on: "hypothesis", "experiment design", "가설 검증", "실험 설계", "최소 테스트", "fake door test".
    3 repo stars
  85. ▌
    Roadmap Communication · newkayak12
    Focuses on ARTIFACTS and MESSAGES: turning a prioritized plan into clear, audience-specific communication that lands with engineering, executives, customers, or sales. Use when the challenge is WHAT TO SAY — how to explain ordering decisions,...
    3 repo stars
  86. ▌
    Interview Prep · newkayak12 bundle
    Use when someone needs a structured interview preparation plan before their interview process begins — a study schedule, gap analysis by topic area, and STAR story bank. This is planning, not practice. Triggers on: "interview prep plan".
    3 repo stars
  87. ▌
    Clarity Toolkit · newkayak12
    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".
    3 repo stars
  88. ▌
    Database Workflow · newkayak12
    Use when investigating database performance degradation end-to-end — from query quality through server tuning, connection layer, and transaction safety. Triggers on: "database workflow", "DB 성능 전체", "database performance investigation", "DB 전체 점검".
    3 repo stars
  89. ▌
    Kotlin Specialist · newkayak12 bundle
    Use when someone is writing Kotlin code and needs idiomatic guidance — coroutine and Flow patterns, Kotlin Multiplatform (KMP) structure, Android with Jetpack Compose, Ktor server setup, or type-safe DSL authoring. Triggers on: "Kotlin coroutines".
    3 repo stars
  90. ▌
    Scenario Director · newkayak12 bundle
    Use when a backend's API scenario tests must be collected or read from md, written as specs, then run against a live server by one actor AI per flow. Triggers: "API 시나리오 테스트", "시나리오 md 읽고 서버에 돌려줘", "flow test", "시나리오 CI 붙여줘".
    3 repo stars
  91. ▌
    Knowledge Query · newkayak12 bundle
    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.
    3 repo stars
  92. ▌
    Roadmap Planning · newkayak12 bundle
    Use when product goals or competing initiatives need to become a sequenced, stakeholder-ready roadmap. Triggers on: "로드맵 만들어줘", "분기 계획", "roadmap planning", "이니셔티브 우선순위 정해줘", "feature list를 outcome 기반으로 바꿔줘", "Q2 로드맵", "분기별 계획 세워줘", "이해관계자 정렬".
    3 repo stars
  93. ▌
    Feature Prioritization · newkayak12
    Use when there are more things to build than capacity allows and the team needs a defensible, data-backed order. Triggers on: "backlog 정리", "우선순위 정해줘", "P1이 너무 많아", "what to build next", "how do we decide", "backlog grooming", "피처 순위 매겨줘".
    3 repo stars
  94. ▌
    Metrics Interpretation · newkayak12
    Use when a number moved unexpectedly and you need to understand why before deciding what to do. Triggers on: "지표가 떨어졌어", "retention 하락", "conversion drop", "A/B test 결과 해석", "KPI 이상", "metrics dropped", "why did this metric change", "dashboard 분석해줘".
    3 repo stars
  95. ▌
    Stakeholder Management · newkayak12
    Focuses on PEOPLE and RELATIONSHIPS: mapping influence, building trust, and overcoming interpersonal resistance to get decisions approved and initiatives unblocked. Use when the challenge is WHO — a specific person blocking progress, an exec who...
    3 repo stars
  96. ▌
    Resume Tailorer · newkayak12
    Use when someone has a resume and a specific job description and wants the resume rewritten to match that JD — keyword alignment, achievement reframing, and skills reordering. Triggers on: "이력서 맞춰줘", "공고에 맞게 고쳐줘", "이력서 최적화".
    3 repo stars
  97. ▌
    Writer Verification · newkayak12 bundle
    Use when writing must read as if a person wrote it — reviewing text, or drafting a PR description or post and revising until the machine tells are gone. Triggers on: "글 검토해줘", "맞춤법 확인", "proofread", "글 다듬어줘", "PR 설명 써줘", "AI 티 나", "사람이 쓴 것처럼".
    3 repo stars