2,709 件 ・ 関連度順
概要と使いどころ
Meta-validator for HARD-GATEs. Use when auditing whether a skill's mandatory constraints were actually followed during a workflow (not just claimed). Called by cook, team, and audit for discipline compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Returns the universal governance spec for swarm team runs — hard rules, briefing templates, gate presentation contract, launch mechanics, and pulse setup. The canonical source: invoked by launch.md at Step 1 and by user-authored shortcut commands that cannot read launch.md directly. Per-gate constants live in swarm:gate-presentation.
日本語の概要は準備中です。原文の説明を表示しています。
Structural pattern analysis for writing-mode review. Performs paragraph-level decomposition and pattern aggregation. Invoked by the team lead during editorial review.
日本語の概要は準備中です。原文の説明を表示しています。
Builds measurable validation criteria when no existing standards apply. Invoked by team agents during review.
日本語の概要は準備中です。原文の説明を表示しています。
Independent review loop run before delivery in code work. An independent reviewer (Codex, or fresh Codex-style subagents) reads the whole PR against the approved outcome; the lead fixes in-scope functional findings and re-reviews until none remain. Its differentiator is independence and exhaustiveness — a reviewer that fails differently from the authors, run to clean — distinct from the recursive-refinement ladder. Invoked by the team lead from the unified pre-ship gate (code-mode and /swarm:refine) after the ship steps.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates ambient context artifacts (CLAUDE.md, memory, local skills, settings hooks) for compatibility with swarm governance. Returns a classified report so users can address interference before launching a team.
日本語の概要は準備中です。原文の説明を表示しています。
Returns the frozen gate constants — question, header, option labels and descriptions, digest field-list, and preview content — for every catalog gate. Invoked by the team lead fresh on arrival at each gate and on pulse re-emissions, in the same turn as the render. The transport contract, three renders, partition rule, and authoring rubric live in swarm:workflow-rules.
日本語の概要は準備中です。原文の説明を表示しています。
Beginner-friendly App Store Optimization guide covering keyword research, screenshot design, rating management, and A/B testing for iOS and Android. By @WeiYipei — practical ASO for indie developers and small teams.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to build or think through a strategy via guided conversation — for a company, product, team, career, or initiative. Triggers on "help me figure out our direction", "what should we focus on", strategic planning, competitive positioning, go-to-market strategy. Also catches indirect requests like prioritization struggles or "we have too many priorities". Does NOT review existing strategy documents (use strategy-review) or brainstorm project features (use brainstorm-beagle).
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing, critiquing, or stress-testing an existing strategy document. Evaluates seven dimensions — diagnosis quality, guiding policy strength, action coherence, assumption exposure, falsifiability — with optional 7S, Five Forces, Balanced Scorecard, and Hoshin Kanri lenses. Triggers on: review my strategy, poke holes in this plan, what's weak here, strategy audit, red team this. Does NOT build strategy (use strategy-interview) or brainstorm project ideas (use brainstorm-beagle).
日本語の概要は準備中です。原文の説明を表示しています。
A C-level strategy advisory board, run as a team of named specialist agents, that takes an executive from a raw strategic question to a defended, board-ready recommendation. Use this skill whenever the user faces a significant business decision or wants strategic analysis — market entry, build-vs-buy, M&A, digital transformation, annual planning, portfolio prioritization, pricing, a big investment, a competitive threat, a turnaround. Trigger on requests like "should we invest in / build / buy / enter…", "develop a strategy for…", "evaluate this opportunity", "make the business case", "stress-test this plan", "run a pre-mortem", or "prepare a board presentation" — in any language, even when the user doesn't say the word "strategy". Also trigger when the user names a board member (Drucker, Porter, Christensen, Graham, Grove, Wack, Taleb, Minto) or asks to convene the board / open a boardroom session.
日本語の概要は準備中です。原文の説明を表示しています。
A complete fiction-writing studio, run as a team of named specialist agents, that guides an author from a bare idea to a polished prose manuscript. Use this skill whenever the user wants to write, plan, or revise fiction — a novel, novella, short story, or series. Trigger on requests like "help me write a novel", "I have an idea for a story", "develop my characters", "build a world for my fantasy", "outline my plot", "fix this scene", "my dialogue feels flat", "give me beta-reader feedback", or any time the user is doing creative storytelling and would benefit from structured, craft-aware guidance. Also trigger when the user names a studio member (Homer, Aristotle, Fyodor, Tolkien, Scheherazade, Oscar, Max, Virginia, Borges, Bloom) or asks to switch creative roles / bring in a specialist.
日本語の概要は準備中です。原文の説明を表示しています。
Vietnam-specific HR guidance covering the Labor Code, Social Insurance Law, personal income tax registration, work permits for foreign workers, trade union obligations, and cultural norms for managing teams in Vietnam. Use when you need to navigate Vietnam employment law, onboard foreign staff, handle disciplinary procedures under Vietnamese law, or adapt global HR practices for the Vietnam market.
日本語の概要は準備中です。原文の説明を表示しています。
Use when installing or operating the independent Univer Workspace CLI application (`univer-workspace-cli`) for remote Workspace files, Personal or Team Spaces, task Worktrees, Sheet/Doc/Slide/Base/Board Units, Facade authoring, inspection, verification, import/export, screenshots, or review handoff. Do not use for local targets handled by `univer`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a product brief is finalized and ready to hand off to the engineering team, or when asked to send a brief to Apex, kick off engineering work, or start development on a product spec. Examples: "hand this off to engineering", "send brief to Apex", "start building this", "kick off dev on this spec".
日本語の概要は準備中です。原文の説明を表示しています。
Operational efficiency audit — identify waste, redundancy, and friction across processes, tools, and team workflows. Use when asked to "audit our operations for waste", "where are we inefficient", "what tools are we paying for but not using", or "reduce operational overhead".
日本語の概要は準備中です。原文の説明を表示しています。
Audit guardrail coverage — bypass vectors, false positive rates, policy gap analysis, red-team scenarios. Use when asked to "audit our AI guardrails", "can our filters be bypassed", or "check guardrail false positives".
日本語の概要は準備中です。原文の説明を表示しています。
Head of product — orchestrate the product team, write briefs, plan initiatives, hand off to Apex. Use when asked to "write a product brief", "plan the roadmap", "decide what to build", or hand off requirements to engineering.
日本語の概要は準備中です。原文の説明を表示しています。
System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".
日本語の概要は準備中です。原文の説明を表示しています。
Map AI cost topology — billing attribution, team-level spend, forecast vs actuals, alert gaps. Use when asked to "map our AI spend", "who is spending on LLMs", or "set up AI cost attribution".
日本語の概要は準備中です。原文の説明を表示しています。
AI-driven dynamic security fuzzing, exploit generation (XSS, SQLi, SSRF, Prompt Injection), and automated patch remediation / Fuzzing keamanan dinamis berbasis AI, eksploitasi, dan remediasi otomatis.
日本語の概要は準備中です。原文の説明を表示しています。
Spark Studio's team-culture Relic — a 5-person AI product startup that existed 2022–2025: roast first then work, hotpot on Fridays, used Feishu while cursing Feishu daily, requirements always changing but versions always shipping. 星火工作室（Spark Studio）的团队文化 Relic。一个 2022-2025 年间存在过的 5 人 AI 产品创业团队： 先吐槽再开工，周五点海底捞，用飞书但天天骂飞书，需求总在变但总能把版本扛上线。
日本語の概要は準備中です。原文の説明を表示しています。
The fifteen fundamental cooking techniques that together cover most home kitchen work. Organized by the transformation they perform (heat transfer, water management, emulsion, ferment, cut) rather than by cuisine. Covers knife work, sauté, sear, braise, roast, poach, boil, steam, grill, bake, stew, reduce, deglaze, emulsify, and pickle/ferment, each with the physics, the signal, the common failure, and a diagnostic question. Use when teaching a cook, substituting a technique, or diagnosing why a dish failed.
日本語の概要は準備中です。原文の説明を表示しています。
Go-based security techniques from "Black Hat Go" extended with macOS, Cloud, Mobile, IoT, Supply Chain, API, Web3, AI/ML, Red Team, ATT&CK, and LLM chapters. 186 techniques, 36 tools, 33 defenses across 37 chapters. Includes adversarial bisimulation games with Ungar (order-dependent) and join-semilattice structures. AAIF-compatible multiplayer agent games for human-agent security exercises.
日本語の概要は準備中です。原文の説明を表示しています。