2,807 件 ・ 関連度順
概要と使いどころ
Multi-path parallel product analysis with cross-model test-time compute scaling. Spawns parallel agents (Claude Code agent teams + Codex CLI) to explore product from multiple perspectives, then synthesizes findings into actionable optimization plans. Can invoke competitors-analysis for competitive benchmarking. Use when "product audit", "self-review", "发布前审查", "产品分析", "analyze our product", "UX audit", or "信息架构审计".
日本語の概要は準備中です。原文の説明を表示しています。
Investigates network, streaming and protocol failures with falsification-first layered experiments, the general fallback for unknown root causes. Use for ECONNRESET / RST_STREAM / SSE stalls, CDN/CGNAT timeouts or certificate errors, throughput collapse where everything returns 200 but transfers crawl, or LAN identity/topology mysteries. Not for known Tailscale/TUN/DNS/proxy-path conflicts (use tunnel-doctor).
日本語の概要は準備中です。原文の説明を表示しています。
MUST be used first for tunnel / proxy-path connectivity failures or slow throughput (网络故障 / 连不上 / 代理或隧道下超时). Diagnoses Tailscale, proxy, TUN, DNS and SSH-tunnel problems on macOS and Windows/WSL, e.g. Tailscale ping works but SSH fails, curl works but browser gets 503, Git/Docker fails behind the proxy, or downloads crawl despite a reachable proxy. Not for application-layer bugs (use debugging-network-issues).
日本語の概要は準備中です。原文の説明を表示しています。
Co-creates a personal investment-research LLM Wiki (Karpathy's pattern) by interviewing the user for THEIR OWN analysis framework, not a template — a living CLAUDE.md of pure markdown + wikilinks, no RAG in place of compilation. Use to build a compounding 投研第二大脑 / 投研知识库 / 个人投研 wiki, ingest research reports / earnings calls into an existing wiki, or run post-earnings prediction→fulfillment reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Audit or defend Octane performance. Use when a change can affect per-render, per-node, scheduling, compiler-output, SSR, hydration, or bundle cost, or when asked whether something is fast enough. Holds the V8-shape, DOM, and scheduling rules hot-path code must follow.
日本語の概要は準備中です。原文の説明を表示しています。
Write a new Octane component in .tsrx, convert JSX to .tsrx, or add scoped <style> blocks and themes. Use when creating a .tsrx file rather than editing one, because the path-scoped tsrx-authoring rule only fires once such a file is open.
日本語の概要は準備中です。原文の説明を表示しています。
Change Octane's runtime, compiler, scheduler, reconciler, SSR, or hydration engine. Use before editing packages/octane/src. Covers the observable contract, hot-path analysis, and the performance evidence required before handoff.
日本語の概要は準備中です。原文の説明を表示しています。
Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 质量追溯体系怎么建, 产品追溯方案, 批次追溯, 一物一码, 客户要求可追溯性, 召回演练, 正向追溯和反向追溯, or plan product and batch traceability in a Chinese factory. Produces a traceability plan in Chinese: the trace unit and coding rule, the data to capture at each process step (material lots, work orders, equipment, people, inspection results), forward and backward trace paths, record retention, a mock recall drill with a target time, gaps against the current system, and a phased rollout, with industry rules (food, medical devices, automotive) marked to confirm.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 怎么给老师发消息, 跟班主任沟通, 孩子在学校被欺负怎么跟老师说, 对老师的做法有意见, 请假怎么写, 家长群里怎么说话, or write a message from a parent to a teacher in China. Produces a ready-to-send WeChat or note message in Chinese, polite and specific, for the situation (asking, leave, a concern, a disagreement, bullying, thanks), a calmer version if the parent is upset, what to say if the teacher calls back, the escalation path if it is not resolved, and 家长群 etiquette.
日本語の概要は準備中です。原文の説明を表示しています。
Write changelogs and release notes readers actually benefit from — changes translated to so-whats, grouped by reader impact (breaking first, gifts second, plumbing last), with the upgrade path stated and the marketing kept honest. Use when asked write the release notes, turn this commit list into a changelog, announce this update to users, or why does nobody read our changelogs. Produces the impact-grouped changelog, the so-what translations, the breaking-changes block with migration steps, and the two-audience split when needed.
日本語の概要は準備中です。原文の説明を表示しています。
Write a sincere, effective apology to a customer, group, or the public. Use when asked to write an apology, say sorry to a customer or community, make amends after a mistake, or respond to a complaint with an apology. Produces a genuine apology — acknowledgement, taking responsibility, empathy for the impact, the concrete fix and prevention, and an offer to make it right — in the right tone, without excuses or non-apologies.
日本語の概要は準備中です。原文の説明を表示しています。
Think clearly about whether bankruptcy is the right move, or whether another path fits better — without shame and without a sales pitch. Use when asked should I file for bankruptcy, is bankruptcy my best option, alternatives to bankruptcy, or what happens if I file. Produces an honest read on whether your situation is the kind bankruptcy actually helps, the main types and what each does (and doesn't) discharge, the real trade-offs (what you keep, the credit impact and its recovery, what's not dischargeable), the alternatives to weigh first (negotiation, debt management, doing nothing on time-barred debt), and a strong push to consult a bankruptcy attorney. Not legal advice.
日本語の概要は準備中です。原文の説明を表示しています。
Get back into a locked or hacked account the right way — the official recovery routes, what proof you'll need, and how to re-secure it so it doesn't happen again. Use when asked I'm locked out of my account, my account got hacked, help me recover my [email/social/bank] account, or I lost access to 2FA. Produces the official recovery path for the account type, the identity proof to prepare, a re-securing checklist for after you're back in, and warnings about fake 'recovery' services and support scams.
日本語の概要は準備中です。原文の説明を表示しています。
Create learning paths for programming tools, and define what information should be researched to create learning guides. Use when user asks to learn, understand, or get started with any programming tool, library, or framework.
日本語の概要は準備中です。原文の説明を表示しています。
Help users navigate the path from junior product manager to executive leadership by focusing on ownership, cross-functional influence, and intentional career design.
日本語の概要は準備中です。原文の説明を表示しています。
Help users identify the most viable path into product management, assess their role fit, and execute a transition strategy through internal mobility, APM programs, or startup roles.
日本語の概要は準備中です。原文の説明を表示しています。
EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair skew, board edge radiation, PDN impedance, return paths, crosstalk, ESD protection, shielding, and magnetic leakage from switching inductors. Produces severity-ranked risk report with pre-compliance test plan. Supports FCC Part 15, CISPR 32, CISPR 25 (automotive), MIL-STD-461G. SPICE-enhanced when available. Use when the user asks about EMC, EMI, radiated/conducted emissions, FCC compliance, CE marking, CISPR, ground plane issues, decoupling strategy, clock routing EMC, switching noise, differential pair skew, or whether their board will pass EMC testing. Also for "will this pass FCC?", "check my EMC", "is my ground plane okay?", "check my decoupling", or "generate an EMC test plan".
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have an approved spec or written requirements for a multi-step task that needs a durable plan document before touching code. Small, single-owner, or fast-path tasks do not need this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
日本語の概要は準備中です。原文の説明を表示しています。
Use when defining ambiguous or high-complexity new features, product behavior, UI/component design, architecture choices, contract changes, or when grilling/pressure-testing a plan or design. Routine small requests stay on the fast path.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked for first-principles or Occam's-razor review, or when high-risk decisions involve competing constraints, fallback growth, duplicate owners, or architecture direction risk. Ordinary bug fixes stay on the fast path.
日本語の概要は準備中です。原文の説明を表示しています。
Install or verify the oma CLI and its runtimes (bun, uv, serena) before any oma-* skill, agent, or workflow runs an `oma` command. Use when `oma` is missing from PATH, when a skill says to run `oma ...` and the shell reports "command not found", or on the first task in a fresh Cursor or Grok Bot workspace.
日本語の概要は準備中です。原文の説明を表示しています。
A minimal, fully spec-conformant fixture skill used to exercise the happy path.
日本語の概要は準備中です。原文の説明を表示しています。