lif

Four-phase debugging framework for any technical issue. Use when encountering bugs, errors, or unexpected behavior. Prevents random fix attempts.

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

Art-direct complete illustrated websites and write project-specific image-generation prompts. Use when the user requests Illustrated Gallery, a gallery-inspired visual style, or $illustrated-gallery. Covers visual direction, original artwork, and page-wide composition; not a fixed website clone, standalone image task, or generic dashboard skill.

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

Provides React patterns for hooks, effects, refs, and component design. Covers escape hatches, anti-patterns, and correct effect usage. Use when reading or writing React components with hooks or effects.

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

Use when creating elaborate, multi-component claude.ai HTML artifacts with React, Tailwind CSS, shadcn/ui, state management, routing, or complex frontend structure; not for simple single-file HTML/JSX artifacts.

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

Use when a skill is brittle, drifting, repeatedly failing, or needs a Reliable Skill Contract. Trigger for phrases like skill lifeguard, reliable skill, self-maintaining skill, negative examples, verification checkpoints, drift signals, replay hooks, or failure log to skill patch. Audits or patches skills so high-value workflows include explicit forbidden behaviors, checkpoints, machine-checkable done conditions, replay or smoke hooks, and drift detection.

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

Audit and safely repair cross-runtime Skill governance: canonical-source ownership, divergent or duplicate projections, exposure scopes and budgets, lifecycle drift, quarantine, and retirement. Use when the user explicitly requests cross-runtime or cross-scope Skill governance; ignore project-local Skill inventory, product/runtime loading or enablement checks, usage statistics, and mentions/traces.

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

React and Next.js performance playbook distilled from Vercel Engineering guidance. Use when building, reviewing, or refactoring React/Next.js code for waterfalls, bundle size, rendering cost, and client/server data flow.

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

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

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

想法群聊室主持人 — 把一句话想法丢给多角色 AI 团队（调研员/反方/类比者）做查漏补缺。每个角色有自己的 voice，他们互相 @ 接话；你随时插话。**这是创意扩展工具，不打分、不否决、不堵路**。Use when 用户说"组个团队聊一下"、"开会讨论这个想法"、"找几个角度看看"、"群聊一下 X"、"team review X"，或调用插件命令 `/idea-coach:idea-team`。Do NOT use when 用户已决定做这个想法只要 PRD（用 `idea-to-product`）、或用户要单独某个角色 skill、或用户只想自由 brainstorm（不需要 team 结构）。

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

查看远程服务器 GPU 使用情况。SSH 连接服务器，展示每张卡的显存占用、运行进程、所属容器。当用户说查看 GPU、显卡占用、显存使用时使用

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

Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing

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

Create distinctive, production-grade web frontend interfaces with high design quality. Use when the user explicitly asks to build or substantially redesign a web component, page, or application. Only applies when repository inspection confirms that the visual surface is a browser-rendered web UI. Do not use for native or GPU-rendered graphics, shaders, games, terminal UIs, or other non-web visual systems. Ignore incidental mentions and traces.

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

Modern Go Web application architecture guide. Use when creating new Go web projects, APIs, or microservices. Covers project structure, tech stack selection, and best practices based on Go standards.

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

Use when designing PostgreSQL + Redis data models, indexes, caching strategies, JSONB usage, tiered storage, or cache consistency contracts.

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

Design architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service boundaries, compare mature project architecture, prevent stacked one-off PRs, audit migration debt in existing repos, or produce a spec before coding.

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

Clash Verge 与 mihomo 诊断和 profile 管理。当用户遇到代理失败、需要配置 AI 工具路由、本地 Hub 拓扑、多机对齐、TUN 绕过、克隆或切换订阅，或同步后 配置未生效时使用。进程线路使用 clash-routes，出口 IP 质量使用 ip-check。 普通网络测速不使用。

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

端到端产品教练 — 把一句话想法走到 PRD + 可点击 HTML 原型。会顶嘴、强制砍功能、用 Nielsen + Norman 做友好性硬检。Use when user 说"我有一个想法"、"想做一个产品"、"做 MVP"、"写 PRD"、"做用户友好的产品"，或调用插件命令 `/idea-coach:idea`。Do NOT use when 用户已有完整 PRD 在跑、明确说"只 brainstorm 不决策"、只想要 UI 设计（用 design-shotgun）、或只想起项目骨架（用 /init）。

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

Use when you want a second-opinion review via Codex CLI, cross-verification after another agent implements changes, debugging help, or alternative implementation proposals. Requires Codex CLI to be installed and authenticated.

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

Audit and organize AI coding-agent instructions, including AGENTS.md, CLAUDE.md, skills, and agent definitions. Use when the user asks to diagnose conflicting instructions, excessive approval pauses, broad skill triggers, duplicate guidance, or broken instruction references, or to clean up that instruction set. Ordinary code review, Markdown editing, or application debugging alone does not trigger this workflow. Inspection stays read-only; apply changes when authorized.

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

Route full software-development architecture work from product intent through design, implementation, testing, release, and operations. Use when the user asks for a complete development architecture, wants to know which Spellbook skills to combine, needs an execution path across PRD/spec/API/data/security/performance/release/SRE, or asks to turn an idea or repo into a production-ready engineering plan.

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

想法群聊室 — 反方角色。被 idea-team 主编排器调用，或用户单独说"反方意见"、"挑这个想法的刺"、"为什么会失败"、"找漏洞 / 反例"、"devil's advocate"时触发。**专门挑漏洞、找隐藏假设、给反例——不安慰、不"也许可以这样"、不全盘否定**。Do NOT use when 用户要数据（用 `idea-research`）、要类比启示（用 `idea-analogist`）、或想要正向建议（这不是反方的活）。

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

Use when Codex feels slow, bloated, or heavy after heavy use. Provides safe session hygiene, archive strategy, and handoff discipline to keep daily Codex usage responsive and low-friction. Always pairs with comprehensive handoffs before archiving active work.

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

Design and verify data contracts, schema changes, migrations, rollbacks, backfills, compatibility windows, tenant isolation, and API-to-database field mapping. Use when changing database schema, event payloads, persisted documents, analytics tables, multi-tenant data boundaries, or any user-visible data contract where silent fallback or undeclared fields would be dangerous.

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

想法群聊室 — 调研员角色。被 idea-team 主编排器调用，或用户单独说"调研一下 X"、"X 的现状/竞品/数据"、"找 2026 数据"、"事实底"时触发。**用 WebSearch 拉真实 2026 数据、列竞品、引来源——只给事实，不评判，不建议**。Do NOT use when 用户要评价想法好坏（那是反方）、或要跨界启示（那是类比者）、或已有 PRD 在跑（不需要这种调研）。插件内 skill 会由 `idea-coach` namespace 路由；catalog 用户直接按 skill 名调用。

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