개발 스킬

Refactor duplicated code by extracting helpers, shared abstractions, or clearer reusable structure. Use when asked to apply DRY, remove duplication, consolidate repeated logic, or run `/refactor:dry`.

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

Refactor long methods or large code blocks by extracting small, focused helper methods with clear names and narrow responsibilities. Use when asked to extract methods or run `/refactor:methods`.

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

Analyze a class or module for code smells and produce a prioritized refactoring plan. Use when the user asks for code smell analysis, says `/smells`, or runs `/refactor:smells`.

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

Refactor Swift code toward declarative functional programming with immutability, value types, pure functions, transformations, and closure-based APIs. Use when asked for functional refactoring or `/refactor:functional`.

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

Refactor a class toward the Single Responsibility Principle by identifying responsibilities, grouping cohesive behavior, and extracting focused classes. Use when the user says `/srp`, asks for SRP refactoring, or runs `/refactor:srp`.

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

Compile deep repository evidence into artifact-bound correctness doctrine — authority/law/proof maps, owned invariants, failure archaeology, and the strongest durable destination for each piece of knowledge, plus an optional minimal repository-specific skill portfolio. Use when the user wants both deep codebase understanding AND durable doctrine, knowledge routing, or repo-specific skill recommendations. Research discoverable facts before asking. Read-only. Not for quick onboarding, one isolated invariant, ordinary implementation, generic review, or direct skill creation.

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

Mitigate incidental code complexity when control flow is tangled, nesting is deep, names are hard to parse, or reasoning requires cross-file hops. Use when a review stalls on readability, you need an analysis-first refactor plan before edits, or you want essential-vs-incidental verdicts, ranked simplification steps, a small structural sketch, and a TRACE assessment (analysis-only; no edits).

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

Build a rich, self-contained HTML explanation of a code change — diff, branch, commit range, MR/PR — with background, intuition, a code walkthrough, diagrams, and a glossary, then quiz the reader interactively in chat. Use when the user asks to explain a change, understand a PR/MR, walk through a diff, onboard onto a branch, or says "explain this PR", "what does this branch do", "teach me this change", or "/explain-diff".

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

Comprehensive, measurement-driven performance optimization for latency, throughput, memory/GC, and tail behavior. Use when the user asks to optimize/speed up, reduce latency (p95/p99), increase throughput/QPS, lower CPU/memory/allocations/GC pauses, profile hot paths, or run a benchmarked perf pass (including JSONL/query-heavy code). Requires before/after measurement on a runnable workload (or an explicit `UNMEASURED` plan) plus a correctness gate.

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

Use when modifying, removing, or refactoring code that lacks test coverage. Emphasizes the danger of untested changes and the RGR workflow to add characterization tests before modifications.

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

Systematically explore an unfamiliar codebase and build a reusable architecture summary. Use for repo onboarding, understanding legacy or inherited code, mapping architecture before a migration or refactor, tracing a bug or feature path, or answering "what does this project do?". Documentation-first, then data flow — ends in a concise technical architecture summary with file:line evidence, not a raw file dump.

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

Apply Steven's Bash script style rules: strict mode, minimal validation, concise logic, executable scripts, and no unnecessary comments or echoes. Use when creating, reviewing, or refactoring shell scripts.

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

Check any artifact against an explicit specification and report adherence using the add-comments workspace format. Use when validating plans, scripts, docs, or code changes against a source-of-truth spec.

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

Join the Antigravity CLI (agy, Gemini 3.5 Flash) to the Interlateral mesh as a native CLI peer with its own tmux session, identity stamping, and the agy.js send helper. Use this instead of the Antigravity desktop-app CDP path.

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

Coordination guidance for the narrow case of multiple desktop-backed agents active concurrently in the same desktop-backed coordination context. Use ONLY when two or more desktop peers are running at the same time; normal CLI agents and single desktop peers should ignore this skill. Read this BEFORE concurrent desktop-to-desktop handoffs to keep sender labels unique, identity routing cooperative, and material handoffs proven.

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

Join Claude Code and Codex CLI to the Interlateral mesh in Warp panes by attaching Warp to the standard tmux socket; Warp is the visible terminal surface, tmux remains the transport.

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

Join Claude Desktop or Codex Desktop to the Interlateral mesh as a desktop peer with its own tmux inbox session, identity, direct ACK, and ledger mirror. This is separate from the standard CLI init flow.

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

Initialize the standard Interlateral two-agent CLI mesh from a bootstrap agent by running me.sh, launching Claude Opus 5.5 plus Codex 5.5, proving live ACK, and waiting for "Reporting for Duty!". The bootstrap agent is not part of the mesh.

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

Run a two-agent independent review/redteam followed by peer collaboration to produce a consensus superset of findings and enumerated revision requests. Use when Codex 5.5 and Claude Opus 5.5 should first critique a matter independently, then exchange work, synthesize the best combined analysis, and finish with a single agreed revision list.

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

Port one complete feature family with provenance, current-API adaptation, repository ownership, localization, resources, and verification.

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

Use owner APIs and established EntitySystem helpers without copying low-level logic.

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

Reproduce failures, trace authoritative flow, prove the broken assumption, and add targeted regression coverage.

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

Resolve localized text at presentation boundaries using English-source keys and safe typed variables.

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

Change persistent models and SQLite/PostgreSQL migrations without breaking existing servers.

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