newkayak12/claude-skills - Page 2

microservices-architect

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: "microservices

service-boundary-validator

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.

bias-auditor

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", "확신이 과한 것 같아".

Source text: Korean

ppt-keycolor-changer

Use when the user wants to change, swap, or replace colors in a PPTX/PPT file. Also triggers on: PPT 키컬러 변경, 슬라이드 색상 교체, 브랜드 컬러로 교체, 색상 일괄 변경, ppt keycolor, 키컬러 교체, 브랜드 적용, 색상 전체 바꿔줘, 색상 스캔해줘, 팔레트 교체.

Source text: Mixed languages

portfolio-jd

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랑 비교해줘", "이 포지션 지원해도 돼?", "match my

portfolio-pattern

Use when someone wants to understand the writing patterns in their portfolio — not what it says but how it reads: passive voice ratio, subject audit, number density, and decision visibility. Triggers on: "패턴 분석해줘", "오너십이 잘 드러나나", "피동형 많이 썼나", "주어

incident-response-playbook

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...

1-on-1-ic

Use when an individual contributor wants to get more value from 1-on-1s with their manager — preparing agendas, driving career conversations, surfacing blockers, and giving upward feedback. Triggers on: "1-on-1 prep", "how to use my 1-on-1 better",

1-on-1-manager

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", "how to have

leveling-ic

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",

leveling-manager

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",

roadmap-planning

Use when product goals or competing initiatives need to become a sequenced, stakeholder-ready roadmap. Triggers on: "로드맵 만들어줘", "분기 계획", "roadmap planning", "이니셔티브 우선순위 정해줘", feature list를 outcome 기반으로 바꿔줘", "Q2 로드맵", "분기별 계획 세워줘", "이해관계자 정렬".

competitive-analysis

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", how

contagious

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", "바이럴", "입소문", "공유되게 하고 싶어", "제품이 퍼지게".

go-to-market-planning

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", "출시 전략", 론칭 계획", "how

post-launch-retrospective

Use after a feature or product launch to formally close the cycle: validate the original hypothesis, analyze which metrics moved, document learnings, and decide what to do next. Triggers on: "출시 후 회고", "런칭 결과 분석", "피처 성과 리뷰", post-launch review",

prd-development

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", "I

pricing-monetization-strategy

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", usage-based

shape-up

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...

technical-feasibility-assessment

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: "technical

user-story-mapping-workshop

Use when someone wants to be guided interactively through building a story map — step by step through scope, personas, backbone activities, tasks, and release slices via adaptive questions. Triggers on: "walk me through story mapping", "help me

microinteractions

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", "이 버튼 어떻게

doc-coauthoring

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 써줘".

feature-prioritization

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", 피처 순위 매겨줘".

hypothesis-driven-dev

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",

inspired-pm

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", "outcome not

okr-planning

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", 목표 정렬",

roadmap-communication

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,...

user-story-mapping

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", "backbone

user-story

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", "acceptance

user-story-splitting

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",

interview-prep

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", "how to

portfolio-company

Use when someone wants to know which companies or company types their portfolio would appeal to — without a specific JD in hand. Triggers on: "which companies fit my portfolio", "where should I apply", "어느 회사에 잘 맞아?", "네이버 지원하려는데 어때?", "어디 써볼 만해?",

resume-tailorer

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: "이력서 맞춰줘", "공고에 맞게 고쳐줘", "이력서 최적화", "tailor my resume to

agent-task-decomposer

Use when a task is too large or ambiguous to hand to a single agent without first defining clear subtask boundaries. Triggers on: "큰 작업 분해해줘", "에이전트 분리해줘", "subtask로 나눠줘", "task decomposition", 이 작업 어떻게 나눠야 해?", "agent에게 어떻게 전달해?", "병렬 작업 계획 잡아줘".

assumption-extractor

Use when someone presents a plan, argument, or belief with confidence and its hidden dependencies have not been examined — surfacing factual, causal, value, and definitional assumptions, then ranking which ones would collapse everything if wrong.

epistemic-reasoner

Use when someone states something with more certainty than the evidence supports, or when an analogy is doing the main argumentative work. Two instruments: calibrate what confidence level the evidence actually warrants, and stress-test whether...

fallacy-detector

Use when someone presents a chain of reasoning or a story explaining why something happened, and the logic may have a structural flaw or the narrative may be too tidy. Covers logical fallacies (false dichotomy, post hoc, straw man) and narrative...

mental-model-toolkit

Use when someone is stuck on a problem and needs a different frame entirely, suspects they have blind spots, or has exhausted obvious solutions. Three instruments: choose the right mental model, systematically surface unknown unknowns, and break...

question-upgrader

Use when someone is asking a question that is too narrow, too closed, or based on a hidden assumption that may be wrong. Upgrades weak questions and generates meta-questions to check whether the right question is even being asked. Triggers on: