lsh1215

Scaffold a new domain feature with TDD order (entity -> test -> service -> test -> controller -> test)

새 Spring Boot 멀티모듈 프로젝트의 기초 세팅(common shared kernel + Gradle/Docker/CI 골격)을 깔아주는 스킬. 시스템 설계 문서 기반 구현 시작 시 가장 먼저 발동. 핵심 골격만 포함 — `BusinessException`/`ErrorCodeBase`/`ApiResponse`/`GlobalExceptionHandler`/`BaseEntity` + JPA/CORS/OpenAPI configs. Kafka/Outbox/QueryDSL 같은 도메인 특화 패턴은 별도 llm-wiki에서 끌어다 쓴다.

Design partner mode for system design practice. Activated when the user wants to design a new system (chat, notification, news feed, URL shortener, etc.). Sets up topic directory, copies the mock-interview template, loads the matching problem from sysdesign-question-bank, marks the topic as active in .omx/state/, and conducts a back-and-forth Clarifying → High Level → Drill Down conversation, updating <topic>/System-Design-Document/mock-interview.md immediately as each decision lands. Uses Alex Xu Vol.1's canned numbers as the starting point (book-first), user adjusts. NOT an interview — the user drives, this skill is a design collaborator with a calculator (back-of- envelope, latency estimation via auto-injected sysdesign-frameworks) and a reference book (sysdesign-question-bank).

Scaffold a minimum-viable implementation of a designed system. Activated when the user is ready to write code. Reads sdd.md (or falls back to mock-interview.md), determines the smallest component subset that lets the design's NFRs be testable (NOT a full production build — single-region, in-memory or single-container infra, no CDN, no multi-region), asks the user for the language/framework stack (default Spring Boot + PostgreSQL + Kafka per project's existing skill set), then scaffolds <topic>/source/ with per-service directories, a docker-compose.yml that brings everything up locally, and test-results/ scaffolding for functional / load / failure tests. The point is verification of design assumptions, not production.

Promote a filled mock-interview.md into a formal Software Design Document (sdd.md) following the IEEE 1016 / Atlassian / Google design-doc style. Activated when the user says they are ready to write the SDD. Reads the topic's mock-interview.md AND the topic's conversation log files (which capture the back-and-forth detail not preserved in the structured mock-interview), then asks the user the SDD-specific questions that mock-interview doesn't cover (Constraints, ADRs, Risk Register, Rollout, Testing strategy). Writes sdd.md incrementally as decisions land.

TDD workflow, per-layer test types, naming conventions, and test fixture patterns for Spring Boot. Use when writing or reviewing tests.

Applies Eric Evans' Domain-Driven Design patterns to design and review domain model classes. Covers tactical patterns (Entity, Value Object, Aggregate, Service, Repository, Factory, Domain Event) and strategic patterns (Bounded Context, Context Map, Anti-Corruption Layer, Core Domain, Distillation). Use when designing JPA entities, defining aggregate boundaries, identifying value objects, mapping bounded contexts, creating domain events, or reviewing domain model code. Also use when asked about ubiquitous language, context maps, or anti-corruption layers.

E2E/QA testing with agent-browser CLI for token-efficient browser automation

Generate an Architecture Decision Record for a technical decision

Adversarial critic workflow for the limited-stock booking system. Use when the user asks AI to attack a design or implementation for Redis outage, oversell, undersell, duplicate booking/payment, retry storm, fallback collapse, correctness gaps, or operational blind spots.

Skeptical first-principles design review skill. Use when the user asks whether a design, architecture, product plan, API, data model, workflow, or system design truly satisfies the real requirements. Reviews from fundamentals: decompose claims into requirements, assumptions, constraints, evidence, invariants, trade-offs, failure modes, and simpler alternatives. Inspired by first-principles reasoning and Cartesian doubt, but does not impersonate any real person.

Validate current project phase deliverables against PRD checklist

Resilience4j circuit breaker, retry, rate limiter, and bulkhead patterns with testing strategies. Use when implementing fault tolerance between services.

Design partner mode for system design practice. Activated when the user wants to design a new system (chat, notification, news feed, URL shortener, etc.). Sets up topic directory, uses the project mock-interview document, loads the matching problem from sysdesign-question-bank, marks the topic as active in .omx/state/, and conducts a back-and-forth Clarifying → High Level → Drill Down conversation, updating <topic>/System-Design-Document/mock-interview.md immediately as each decision lands. Uses Alex Xu Vol.1's canned numbers as the starting point (book-first), user adjusts. NOT an interview — the user drives, this skill is a design collaborator with a calculator (back-of- envelope, latency estimation via auto-injected sysdesign-frameworks) and a reference book (sysdesign-question-bank).

Promote a filled mock-interview.md into a formal Software Design Document (sdd.md) following the IEEE 1016 / Atlassian / Google design-doc style. Activated when the user says they are ready to write the SDD. Reads the topic's mock-interview.md AND the topic's conversation log files (which capture the back-and-forth detail not preserved in the structured mock-interview), then asks the user the SDD-specific questions that mock-interview doesn't cover (Constraints, ADRs, Risk Register, Rollout, Testing strategy). Writes sdd.md incrementally as decisions land.

Test-first prompting workflow for this booking system. Use when the user asks AI to first derive failure, race, duplicate, overload, Redis outage, payment failure, or retry-storm scenarios before implementation, and to pin those scenarios as tests before writing production code.

Korean writing pipeline orchestrator. Numeric picker that routes to one of 4 direct format slash commands (blog / cover-letter / paper / letter). Zero AI dispatch - the user picks by number. Use when the user invokes /aiwriting without specifying a format, or asks "글 쓰는 도구 뭐 있어?" / "aiwriting 메뉴" / "어떤 글을 쓸 수 있어?".

Korean cover-letter writing pipeline. Drafts an applicant cover letter (자기소개서) in STAR (Situation/Task/Action/Result) form, then runs deterministic AI-tell scrubbing. Use when the user asks for a cover letter, 자기소개서, or career transition statement. Argument "review" runs only the AI-tell scrubber on an existing file.

Korean personal letter writing pipeline (감사/축하/위로/추천 등). Drafts a personal letter focused on warmth and specificity over structure, then runs deterministic AI-tell scrubbing. Use when the user asks for a personal letter, 감사 편지, 위로 편지, 축하 메시지, 또는 추천서. Argument "review" runs only the AI-tell scrubber on an existing file.

Korean academic paper / technical report writing pipeline. Drafts a structured paper (Abstract / Introduction / Method / Results / Discussion / Limitations / Conclusion) with Toulmin argumentation, then runs deterministic AI-tell scrubbing and structure-critic review. Use when the user asks for a paper, technical report, 논문 초안, or empirical study writeup. Argument "review" runs only the AI-tell scrubber on an existing file.

Korean technical blog writing pipeline. Orchestrates a 5-stage agent pipeline (writer -> scrubber -> copy-killer -> structure-critic -> fact-checker) to produce externally publishable Korean technical blog posts with deterministic anti-AI-detection cleanup. Use when the user mentions writing a blog post, technical article, or asks to "write a blog about X". Argument "review" runs only the AI-tell scrubber on an existing file.

Dashboard Screenshot Capture

Generate professional system architecture diagrams using Excalidraw. Expert-level system design visuals.

Generate infrastructure diagrams using Python Diagrams library (mingrammer/diagrams).

E2E/QA testing with agent-browser CLI for token-efficient browser automation