REST and GraphQL API design patterns, OpenAPI/Swagger specifications, versioning strategies, and authentication patterns. Use when designing APIs, reviewing API contracts, evaluating API technologies, or implementing API endpoints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria. Use when designing system architectures, evaluating patterns, or planning scalability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unified domain and data modeling for business entities, invariants, schema design, aggregate boundaries, and evolution strategy. Use when designing business models, schema changes, bounded contexts, or consistency rules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Context enrichment for frontend UI development using shadcn/ui and Tailwind CSS. Use when building component libraries, implementing UI designs, theming, or working with accessible React components.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create architectural decision records (ADRs), system documentation, API documentation, and operational runbooks. Use when capturing design decisions, documenting system architecture, creating API references, or writing operational procedures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writing effective tests and running them successfully. Covers layer-specific mocking rules, test design principles, debugging failures, and flaky test management. Use when writing tests, reviewing test quality, or debugging test failures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unified platform operations guidance for CI/CD pipeline design, deployment strategies, observability, SLI/SLOs, and incident-ready rollouts. Use when building release workflows, production monitoring, or reliability controls.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Measurement approaches, profiling patterns, bottleneck identification, and optimization guidance. Use when diagnosing performance issues, establishing baselines, identifying bottlenecks, or planning for scale. Always measure before optimizing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Vulnerability review, threat modeling, OWASP patterns, and secure coding assessment. Use when reviewing code security, designing secure systems, performing threat analysis, or validating security implementations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.