Find deepening opportunities in a codebase, informed by the project's own domain language and prior design decisions. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Resolve a verified cluster of Rembric issues from causal root to evidence-gated closure. Use after systemic triage identifies a shared root, or when the user asks to attack issues at the root, create a mechanism map, plan a deletion-first fix, or close a fixed/stale issue cluster. Use `diagnose` for a single defect whose reproduction is not yet established.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the `cacheComponents` flag, work through a flood of blocking-prerender / instant validation errors, run the `cache-components-instant-false` codemod, or decide between opting routes out with `export const instant = false` and fixing them in place.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks. Combines /_next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running `next dev`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply npm/pnpm supply-chain hardening when adding a dependency, editing package.json/.npmrc/pnpm-workspace.yaml, reviewing a lockfile change, or configuring CI install steps. Covers the 17 practices from lirantal/npm-security-best-practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-to-end smoke against the local rembric dev server (`pnpm run dev`, host Next.js dev on :3000). Apply when the user says "smoke", "probar contra docker", "dev:up", or after applying an OpenSpec change that touches HTTP (`apps/web/src/app/api/`), MCP tools (`packages/mcp/src/`), or DB migrations (`packages/db/src/migrations/`). Encodes bring-up, readiness verification, probe pattern and teardown — not the probes themselves.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runnable end-to-end validation playbook for the Rembric TUI installer — catch breakage before merging/deploying, AND a sandboxed manual walkthrough to evaluate/iterate its UI/UX without polluting your real env. Apply before shipping any change touching `apps/plugin/install.sh`, the repo-root `install.sh` shim, any per-client `install.sh`/`uninstall.sh`, or distribution docs, or when you want to preview/try/demo the installer and polish how it looks and feels. Layered: CI-safe headless (vitest + `sh -n`), local install round-trips, operator interactive pty smoke, an optional full Docker `up` smoke, plus a sandboxed manual UX walkthrough. For the installer contract/what-not-to-break, see `rembric-tui-installer`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement tasks from an OpenSpec change (Experimental)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Archive a completed change in the experimental workflow
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Propose a new change - create it and generate all artifacts in one step
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in SQLite embedded database development for Tauri/desktop applications with focus on SQL injection prevention, migrations, FTS search, and secure data handling
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Call this skill when faced with "wicked problems", complex challenges, or when a user asks for strategic innovation, root-cause analysis, or long-term problem solving. Do not use for simple, linear tasks. This skill forces the agent to bypass superficial symptoms, map the entire ecosystem, and anticipate second-order consequences before proposing an intervention.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pragmatic testing guidance focused on confidence, behavior over implementation details, and integration-first coverage. Use when designing a test strategy, writing or reviewing tests, reducing brittle mocks, or deciding what is worth testing in an application or library.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rework a change as if the intended UX and architecture had existed from day one — deleting compatibility cruft, dead branches, and accidental complexity instead of patching around them. Use when refactoring, cleaning up after a feature lands, removing flags, collapsing legacy paths, or when the user says the code "should look like X from scratch".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enter explore mode - think through ideas, investigate problems, clarify requirements
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.