개발 스킬

Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Code review guidelines covering code quality, security, and best practices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability patterns (microservices, caching, sharding), DevOps practices (Docker, Kubernetes, CI/CD), and monitoring. Use when designing APIs, implementing authentication, optimizing database queries, setting up CI/CD pipelines, handling security vulnerabilities, building microservices, or developing production-ready backend systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when integrating or optimizing Model Context Protocol (MCP) servers and clients. Keywords: MCP, Model Context Protocol, tool discovery, lazy loading, sampling, resource subscription, MCP server.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Next.js App Router principles. Server Components, data fetching, routing patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when building autonomous code editing, bug fixing, or software engineering agents. Keywords: SWE-agent, code agent, bug localization, patch generation, AST, diff, TDD loop, repository indexing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn a feature request into a minimal, file-level implementation plan before any code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prismatic API access patterns and GraphQL reference. Covers the two-tier access hierarchy (MCP tools → Prism CLI), CLI usage rules, GraphQL query patterns, pagination, authentication, and managing platform resources programmatically.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Core knowledge for migrating integrations from other platforms (Boomi, Cyclr) to Prismatic Code Native Integrations. Provides the standard integration schema, schema-to-spec mapping, confidence scoring, and migration-aware code generation patterns. Use when the user says "migrate", "convert from Boomi/Cyclr", "parse this export".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Alias for the project cr skill. Use unity-cr to perform the same Unity branch or commit-set code review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Investigate stuck runs and execution failures by tracing Symphony agent-provider logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch). Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Investigate stuck runs and execution failures by tracing Symphony and Codex logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Performs critical code reviews using REVIEW.md guidelines. Evaluates code quality, architecture, testing, and domain-specific concerns (legal faithfulness, cross-law references, engine safety). Use after completing significant code changes or before merging.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Writing rules for the regelrecht docs site (docs/). Use when writing or editing prose under docs/ — RFCs, guides, component docs, concept pages, and the NL/EN landing copy. Keeps docs prose free of AI-generated tells and consistent with the site's government-technical register. Not for code, commit messages, or PR descriptions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.