- Skills
- 15
- 仓库
- 1
- 职业覆盖
- 4
- 场景覆盖
- 3
- Stars
- ★ 3
Sanghyeon Kim 的 Skills 15
diagram
Use when something must be drawn as a checked figure, not Mermaid: page layout, B-tree, lock timeline, ER, benchmark chart, architecture, sequence. SVG + PNG. Triggers: "도식화해줘", "그림으로 그려줘", "책에 넣을 그림", "시퀀스 다이어그램", "draw this as a figure".
test-master
Use when writing, improving, or auditing tests, or writing case specs with expected results from a spec. Triggers: "테스트 작성", "테스트 케이스 작성", "test case writing", "단위 테스트", "커버리지 분석", "test plan", "defect report".
sre-engineer
Use when setting up production reliability practices. Triggers on: "SLO 정하고 싶어", "에러 버짓", "알람 피로", "반복 작업(toil) 줄이기", "golden signals dashboard", "burn-rate alert". Not for active incidents or chaos tests.
sql-pro
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.
spring-boot-engineer
Use when building or extending a Spring Boot 3.x Java backend — REST, Spring Security, JPA, WebFlux, Actuator. Triggers on: "Spring Boot API", "스프링 시큐리티 설정", "JPA 연동". Not for service decomposition or query tuning.
spec-driven-development
Use when a feature should be specified before it is coded — stories, acceptance criteria, tasks, a per-criterion check. Triggers: "스펙 먼저", "명세부터 쓰고 구현", "수용 기준 먼저", "spec first", "spec-driven development".
like-my-code
Use when a repo's code style must become written policy — harness conventions (coding.md, boundaries.md) backed by repo evidence. Triggers: "내 코드 스타일로 컨벤션 뽑아줘", "이 레포 스타일을 정책으로", "like my code", "extract conventions from this repo".
kotlin-specialist
Use when writing idiomatic Kotlin — coroutines and Flow, KMP, Compose, Ktor, DSLs. Triggers on: "Kotlin coroutines", "코루틴", "코틀린으로 전환", "Flow 취소 처리". Not for Spring Java backends or Android XML layouts.
domain-driven-design
Use when aligning code structure with business concepts, designing service boundaries, or when domain experts and developers cannot agree on what things mean. Triggers on: "도메인 모델링", "바운디드 컨텍스트", "DDD", "domain-driven design", "bounded context".
database-optimizer
Use when DB slowness is server-side, not query text. Triggers on: "락 경합", "VACUUM 밀림", "shared_buffers 튜닝", "파티셔닝 설계", "lock contention", "stale statistics", "InnoDB buffer pool". Not for SQL rewrites or pool sizing.
cli-developer
Use when building a command-line tool — subcommands, flags, prompts, progress bars, shell completions, cross-platform distribution. Triggers on: "CLI 도구 만들어줘", "서브커맨드 설계", "build a CLI". Not for web UIs or REST APIs.
clean-code
Use when a diff, branch or PR needs review or a gate verdict, code needs refactoring, or a requirement needs implementing cleanly. Triggers: "코드 리뷰", "이 브랜치 리뷰해줘", "PR 리뷰", "리팩토링", "어떻게 구현해?", "review this branch", "code review".
clean-architecture
Use when designing layered architectures, separating concerns across boundaries, implementing ports and adapters, or when business logic is leaking into frameworks and the codebase feels tangled. Triggers on: "의존성 규칙", "레이어 아키텍처".
chaos-engineer
Use when you want to test whether a system survives real failures. Triggers on: "장애 주입 테스트", "game day 준비", "pod 죽여보고 싶어", "chaos experiment", "kill a pod in staging", "simulate zone outage". Not for active incidents.
architecture-designer
Use when designing or documenting system architecture — topology, trade-offs, ADRs, database choice ("시스템 아키텍처 설계해줘", "ADR 써줘", "design this system").