코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.6만건)
Diagnose Kolu client-side performance issues (memory leaks, high GPU, slow interactions) using chrome-devtools MCP + the Debug → Diagnostic info dialog + heap-snapshot analyzers. Triggers on "memory leak", "GPU memory", "tab bloat", "why is kolu slow", "debug performance", "zombie canvas", "WebGL leak", or any
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
How a downstream app consumes the shared @kolu/surface stack (@kolu/surface · surface-app · surface-remote · surface-mcp) — declaring a typed reactive surface, serving it, consuming it (SolidJS hooks or a CLI), and mirroring a remote surface over ssh. Grounded in the real consumers: kolu, drishti, odu, and the TUIs. Load when wiring a surface server/client/mirror, or reaching for makeSession / a link / the `.use()` hooks. CHANGING the framework is gated separately — see "Changing the framework" below (a paired, CI-green drishti PR pinned to final kolu HEAD).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cut a kolu release — tag master, promote the Unreleased changelog entry, publish a GitHub release. ONLY invoke when the user explicitly types `/release` or `$release`; never auto-select from a natural-language request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Launch the kolu dev server on two RANDOM free ports so it never collides with the running production `kolu.service`, remember the ports for the rest of the session, and tear down only the dev instance. Load before running the app locally — for evidence capture, driving a live kolu with the chrome-devtools MCP, or any `just dev` you'd otherwise run by hand. Triggers on "run kolu locally", "launch the dev server", "boot kolu", "drive a live kolu", "start the app to screenshot it", or before pointing chrome-devtools at a local kolu.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a feature request into a minimal, file-level implementation plan before any code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintain the slopus/happy open source project. Triage issues, manage the GitHub project board, draft closing comments, find duplicates, check if bugs are fixed on main, and engage with community contributors. NEVER posts comments or closes issues without showing exact text and getting approval first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Playbook for capturing SOCKS5/VPN-tunnel traffic on Android devices and emulators with mitmproxy, tcpdump, or PCAPdroid. Use when debugging on-device network traffic or correlating Kotlin/Rust logs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
RIPDPI's own Compose conventions: ViewModel pattern, Route/Screen split, DataStore->StateFlow, RipDpiThemeTokens. Use for how this app does Compose, not generic Compose API questions (see compose).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reference for Android VPN/proxy service lifecycle: runtime coordinators, status/telemetry flow, where to make changes. Use when touching service start/stop, handover, or coordinator code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MTProto-over-WebSocket tunnel for Telegram: DC classification, obfuscated2 detection, TLS backend choice, and the relay loop. Use when touching Telegram DC routing, MTProto classification, or ripdpi-ws-tunnel.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ADB-based RIPDPI device/emulator debugging: build/install/launch, logcat filtering, fixture port-forwarding, instrumented tests, crash/ANR triage. Use when debugging on a real device or emulator.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Author or modify a build-logic convention plugin. Use when changing plugin internals, the diagnostics catalog, or Rust-native wiring. Not for adding a dependency/module (gradle-build-system) or version bumps (dependency-update).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bump a Gradle or Rust dependency version. Use when editing libs.versions.toml, native/rust/Cargo.toml, or reviewing a Renovate PR. Not for adding a module or plugin (gradle-build-system, convention-plugin-development).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Make AI coding-agent messages to humans clear and easy to follow. Use for every user-facing update, explanation, review, question, and handoff in this repository, or when the user asks to simplify or rewrite an agent message.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Make AI coding-agent messages to humans clear and easy to follow. Use for every user-facing message in this repository, or when the user asks to simplify or rewrite an agent message.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discoverability shim for the Retail-Agentic-Commerce pre-commit analysis Codex skill. Use before commits, after significant changes, or for implementation-quality validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discoverability shim for the Retail-Agentic-Commerce setup Codex skill. Use when the user asks to setup, install, start, launch, or run the project stack.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discoverability shim for the Retail-Agentic-Commerce CVE remediation Codex skill. Use for CVE, BDSA, GHSA, OSV, Dependabot, Black Duck, Snyk, npm, PyPI, or package advisory remediation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
A perfectly innocent-looking skill whose manifest hides nothing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when starting a new Spring Boot 4 project. That covers scaffolding a service, REST API, or modular backend; picking an architecture (layered, package-by-module, modular-monolith, tomato, DDD-hexagonal); selecting Spring Boot 4 features; generating the base project with progen or Spring Initializr; or applying the bundled templates and references in this skill. Not for migrating existing projects or for isolated JPA/repository work without broader project-creation context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reviewing Spring Boot 4 / Java 17+ code with concrete files or diffs (pull requests, modules, or pasted Java and Spring sources) for migration risks, architecture boundary leaks, JSpecify null-safety gaps, security flaws, performance regressions, Spring Data pitfalls, or tests that pass without catching bugs. A test review reports which bugs the suite would let through and which tests fail on correct code, and proves each finding by running it. Not for Kotlin-only code, non-Spring frameworks, or generic review advice without code context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query Codex banked reset credits from the local Codex Desktop login state and report available reset count plus expiration times. Use when the user asks to check Codex reset credits, reset opportunities, reset chances, reset count, rate-limit reset credits, or expiration times; also use when the user provides a codex-reset-credits-skill or codex-reset-credits runbook link and asks Codex to query the result directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up concise, guidance-first Claude/Codex/Grok project context after inspecting the repository. Use on first setup, after cloning, or when the user runs /project-init.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.