코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.8만건)
Lightweight refactor: audit → plan → approve → implement in a single Opus context, no sub-agent fan-out. Behavior preservation is the goal — verifies tests still pass, optionally commits, and offers a separate /code-review pass at the end. Use by default; reach for /refactor only when the cleanup needs parallel fan-out or exceeds one context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refactoring pipeline: analyzes a target file or directory for code quality issues, plans safe incremental improvements, optionally writes tests first as a safety net, implements the changes, and reviews the result. Orchestrates refactor-planner → (test-writer) → parallel-task-orchestrator → code-reviewer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Lightweight refactor: audit → plan → approve → implement in a single Opus context, no sub-agent fan-out. Behavior preservation is the goal — verifies tests still pass, optionally commits, and offers a separate /code-review pass at the end. Use by default; reach for /claude-setup:refactor only when the cleanup needs parallel fan-out or exceeds one context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guidelines for upgrading Expo SDK versions and fixing dependency issues
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up the local iOS dev/build toolchain for NowStack Mobile: Xcode, Simulator, CocoaPods, Watchman, mobile deps, and first `expo run:ios`. Use for `/ns setup-ios`, simulator preview, `expo run:ios` failures, or before local TestFlight builds. macOS only; signing is `/ns ios setup`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up and verify Sign in with Apple for NowStack Mobile web and iOS against the shared Better Auth and Convex backend. Use for Apple Services IDs, return URLs, Sign in with Apple keys, APPLE_CLIENT_ID or APPLE_CLIENT_SECRET, expiring Apple JWTs, or production Apple auth rotation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when optimizing Convex database read bandwidth, documents-read cost, query indexes, full-table scans, function-level usage dashboard findings, or code that uses .filter(), unbounded .collect(), N+1 reads, or expensive reactive Convex queries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates or adds Convex to an app. Use for new Convex projects, npm create convex@latest, frontend setup, env vars, or the first npx convex dev run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up local iOS dev/build tooling for NowStack Mobile: Xcode, Simulator, CocoaPods, Watchman, mobile deps, and first `expo run:ios`. Use for `/ns ios local-setup`, legacy `/ns setup-ios`, simulator preview, or local TestFlight prerequisites. macOS only; signing is `/ns ios setup`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Connect every external account NowStack Mobile needs (Convex, Expo/EAS, Apple Developer, Vercel, Stripe, Google Play) by acquiring PROGRAMMATIC API ACCESS for each, then doing everything automatically through that access. Use for "setup accounts", "connect my accounts", first-run onboarding, or when check-setup reports CLI/auth gaps. The skill obtains a token/key per service, stores it in the right place, and only asks the user for the irreducible manual steps (browser signup, 2FA, one-time key download). Every account is skippable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
First-run setup wizard for a freshly cloned NowStack Mobile. Installs the machine's CLIs, connects every account, wires Convex, creates YOUR own clean Git repo, gathers the product brief, then rebrands the boilerplate into your app. Use for "set up my project", "initial setup", "onboard me", "ns onboard", "I just cloned this", or the very first run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build reusable Convex components with isolated tables and app-facing wrappers. Use for defineComponent, app.use, ComponentApi, or shared backend modules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read and write the user's SaveIt.now bookmarks from the terminal or from JS/TS code, via the official `saveitnow` npm package (CLI + SDK). Handles its own install and API-key setup on first use. Use whenever the user mentions SaveIt, saveit.now, "my bookmarks", "my saved links", "my reading list", asks to save/bookmark a URL, to search what they saved, or to pick something to read.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs viral referral programs with incentive structures, sharing mechanics, and tracking. Covers one-sided, two-sided, tiered, and milestone models with viral coefficient calculations. Use when someone wants word-of-mouth growth, viral loops, invite programs, or says 'referral', 'viral loop', 'word of mouth', 'invite program', 'refer a friend', 'growth loop', 'referral incentive', 'affiliate program', 'ambassador program', 'get users to invite friends', or 'organic growth'. Even casual mentions like 'how do I get my users to spread the word' or 'can users invite others' should trigger this. Includes anti-fraud measures and copy templates for both referrer and referee. Use this whenever user-driven acquisition or viral mechanics are discussed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Trigger when: (1) User mentions "manim" or "Manim Community" or "ManimCE", (2) Code contains `from manim import *`, (3) User runs `manim` CLI commands, (4) Working with Scene, MathTex, Create(), or ManimCE-specific classes. Best practices for Manim Community Edition - the community-maintained Python animation engine. Covers Scene structure, animations, LaTeX/MathTex, 3D with ThreeDScene, camera control, styling, and CLI usage. NOT for ManimGL/3b1b version (which uses `manimlib` imports and `manimgl` CLI).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The Chemical compiler API bindings in lang/libs/compiler/ and the C++ AST node hierarchy — ASTNode, Value, BaseType, ASTAllocator, and their unsafe casting methods.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive guide to the Chemical Compiler Binding Interface (CBI) — how compiler plugins are built, registered, and integrated into the compilation pipeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The compiler-side machinery of the Chemical Compiler Binding Interface (CBI) — the CompilerBinder/CBIData/CBIFunctionIndex model, the full CBIFunctionType hook enum and where each fires, the extern "C" bindings dispatch tables in CBI.cpp, ASTBuilder/ASTCBI/PtrVec/BatchAllocator/SourceProvider/ASTDiagnoser wrappers, the TinyCC JIT bridge and LabBuildCompiler plugin compilation/indexing, the enum-sync rule, and how to add a new CBI binding. Load when modifying the CBI model/bindings layer, adding compiler hooks or bindings, debugging plugin ABI/symbol issues, or trying to understand how the compiler calls into Chemical plugin code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive guide to the C translation backend (2c) — how Chemical AST is translated to C code, key patterns, gotchas, and optimization strategies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive guide to Chemical interpretation and comptime evaluation after the MIR migration — the MIR interpreter engine, the comptime driver, the residual AST expression folder, and how to debug `--interpret` and comptime failures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The Chemical compiler's MIR (mid-level IR) lowering path — architecture, current status (C and LLVM suites green, legacy 2c deleted), the AST→MIR lowering and per-backend emission pipeline, the coroutine/async lowering, type-spelling rules, destructor/move semantics via drop flags, and the hard-won codegen gotchas. Also carries the post-migration evaluation (measured compile-time/memory/generated-code/binary-size regressions) and the consolidation+performance action plan needed for the JVM/JS backends. Load before touching compiler/mir/*, compiler/CodegenMir.cpp, compiler/async/*, ASTProcessor MIR integration, or debugging generated C.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive guide to the Chemical compiler's name mangling subsystem — how declarations get unique runtime symbol names, how scoped prefixes, module/package prefixes, generic instantiation suffixes, `@extern`/`@no_mangle`, interface/impl methods and vtables are mangled, and how the LLVM and C backends consume the result. Load when working on symbol naming, generic instantiation suffixes, C interop, vtable naming, or adding a new declaration kind that has a runtime footprint.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive guide to the Chemical type verification pass — how types are verified after symbol resolution, before codegen.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.