panda850819

Comprehensive health check of Claude Code skill ecosystem — cross-check registry.yaml, disk, symlinks, INDEX.md, and frontmatter validation. Use after skill restructuring or periodically.

Audit Claude Code settings.json for security vulnerabilities — detect allow-bypasses-deny, missing sensitive file denies, and overly broad permissions. Use after any settings.json change.

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.

Toggle peon-ping sound notifications on/off. Use when user wants to mute, unmute, pause, or resume peon sounds during a Claude Code session.

Use when installing packages, adding dependencies, or running package manager commands. Triggers on npm install, npm add, package installation, dependency management.

Expert quantitative analyst for financial modeling, algorithmic trading, and risk analytics. Use when developing trading strategies, backtesting, risk analysis, or quantitative research. Triggers on "strategy", "backtest", "Sharpe", "VaR", "quant", "alpha", "pandas", "numpy", "quantlib", "zipline", "backtrader", "ta-lib", "yfinance", "ccxt".

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Pull a decorrelated second opinion from a DIFFERENT model on a LOAD-BEARING judgment: a design fork, a pre-commit plan, an irreversible or outward-facing call. Reversible calls just decide. `--panel` = blind critics on a prepared plan. NOT code-diff review (review), NOT mechanical work for Codex (handover), NOT sharpening a fuzzy idea (grill).

Build or fix UI surfaces with a committed point of view: pages, components, layout, typography, motion feel, design review. Triggers: 設計, 做頁面, 做組件, 不好看, 很醜, 突兀, 不協調, 字體, 排版, 樣式, 前端, UI, 截圖, 很死, 死板, 生硬, 沒動效, 沒回饋感, 切換好硬, design, build a page/component, make it look good, typography, feels dead, stiff, lifeless, janky transition, this looks wrong. NOT for backend logic, browser-test verification (use `qa`), root-cause debugging of a broken render (use `debug`), or throwaway variant exploration before a direction is chosen (use `prototype`).

Bounded fresh-context handover for unfinished mechanical build units from an existing plan. A Claude Code or Codex orchestrator may start a fresh Claude or Codex worker and keeps ownership. - /handover [--agent claude|codex] [slug]: sync handoff through `scripts/verbs fresh-run`. - /handover --async [slug]: write a self-contained payload to docs/handoffs/ only; does not spawn Codex or touch git. Use when a locked, file-scoped task benefits from fresh conversation context. NOT for plan writing, closing finished work, PR/ship flow, or exploratory judgment-heavy work (pull a cross-model take with advisor instead).

Review a code diff before PR or on request. Uses a bounded low-risk fast path, scoped evidence, risk-triggered lenses, and cold-context escalation. NOT browser QA, prepared-plan critique, or external artifact trust checks.

Focused execution from a concrete outcome to SHIPPED, PAUSED, FAILED, or ABORTED_BY_USER. Adds acceptance-driven loops, bounded review, and delivery evidence beyond native coding behavior. Routes unclear requirements to grill, bugs to debug, UI work to ui, and completed delivery to ship. NOT for hypothetical or planning-only responses.

Audit and reduce a live multi-runtime agent harness after adoption. Use for installed skill/plugin parity, cold-start context, routing overlap, telemetry, or human-attention load. Produces a reversible proposal; it does not mutate the harness.

Adversarial requirement discovery. Ask ONE question at a time, hunting for hidden requirements / unknown unknowns. Drills one angle at a time, then by default runs a structured close that writes a brief (+ executable plan) to docs/. Say "quick" or "don't write files" to stop at a chat-only log instead. Use when the user says "grill me on X", "interrogate this idea", "stress test this scope", "what am I missing", "draft a brief", "structured intake". Skip for tasks where scope is already concrete.

Chart or work a decision map across sessions until the route to its destination is clear. With a large, fuzzy topic and no map, delegate charting to grill and stop after the map is created. With an existing map, take ONE unblocked entry, resolve it by type (research / grilling / prototype / task), write the decision back, and graduate the fog. Use when starting or resuming a multi-session effort. NOT executing a locked plan (sprint).

協助撰寫 PRD、分析功能需求、規劃路線圖。Use when writing PRD, analyzing feature requests, planning roadmap, or need structured product thinking. Triggers on "PRD", "產品規格", "feature request", "roadmap", "功能分析".