980 件 ・ 関連度順
概要と使いどころ
When scoring a roadmap, PR review, ADR, or ticket for completeness — risk, tests, migration, maintainability. Dispatched by /refine-ticket, /adr-create, /review-changes; never auto-gates.
日本語の概要は準備中です。原文の説明を表示しています。
Use when choosing between alternatives with trade-offs — X-or-Y decisions or a weighted decision matrix / gewichtete Entscheidungsmatrix ('score my options'); ADR via `adr-create`.
日本語の概要は準備中です。原文の説明を表示しています。
Especialista em event sourcing, CQRS e padrões de arquitetura orientada por eventos. Domina design de event store, construção de projeções, orquestração de sagas e padrões de consistência eventual. Use PROATIVAMENTE para sistemas baseados em event sourcing, requisitos de trilha de auditoria ou modelagem de domínio complexa com consultas temporais.
日本語の概要は準備中です。原文の説明を表示しています。
Padrões de codificação universais, melhores práticas e padrões para desenvolvimento em TypeScript, JavaScript, React e Node.js.
日本語の概要は準備中です。原文の説明を表示しています。
Padrões especialistas para desenvolvimento com Azure Functions, incluindo modelo isolated worker, orquestração de Durable Functions, otimização de cold start e padrões de produção. Cobre modelos de programação .NET, Python e Node.js. Use quando: azure function, azure functions, durable functions, azure serverless, function app.
日本語の概要は準備中です。原文の説明を表示しています。
Padrões abrangentes para criar, manter e gerenciar Registros de Decisões de Arquitetura (ADRs) que capturam o contexto e a lógica por trás de decisões técnicas significativas.
日本語の概要は準備中です。原文の説明を表示しています。
Aplica as cores oficiais da marca Anthropic e tipografia a qualquer tipo de artefato que possa se beneficiar da identidade visual da Anthropic. Use quando diretrizes de cores da marca ou padrões de design, formatação visual ou padrões de design corporativo se aplicarem.
日本語の概要は準備中です。原文の説明を表示しています。
Aplica as cores de marca oficiais e tipografia da Anthropic a qualquer tipo de artefato que possa se beneficiar de um visual e sentimento do padrão Anthropic. Use quando diretrizes de cores de marca, guias de estilo, normas de design visual ou padrões de design corporativo se aplicarem.
日本語の概要は準備中です。原文の説明を表示しています。
Expert em LangGraph - o framework de nível produção para construir aplicações de IA com múltiplos atores e estado. Aborda construção de grafos, gerenciamento de estado, ciclos e ramificações, persistência com checkpointers, padrões human-in-the-loop e o padrão ReAct. Usado em produção no LinkedIn, Uber e 400+ empresas. Esta é a abordagem recomendada pelo LangChain para construir agentes. Use quando: langgraph, langchain agent, stateful agent, agent graph, react agent.
日本語の概要は準備中です。原文の説明を表示しています。
Single owner of everything under docs/architecture/ — ADRs, architecture and design documents, and architecture diagrams. Routes each deliverable to the right engine: /mermaid-architecture for Markdown-native diagrams, /drawio-architecture for editable .drawio diagrams, and the optional archify skill for interactive standalone HTML diagrams (used only when already installed in the environment; never installed at runtime). Use whenever architecture documentation, ADRs, or architecture diagrams must be created or updated.
日本語の概要は準備中です。原文の説明を表示しています。
アーキテクチャ設計（境界/依存/データフロー/非機能/運用）を、制約とトレードオフで言語化し、ADR-liteで合意形成しながら段階的に形にする。doc/input/rdd.md にアーキテクチャ/非機能/運用の要求がある、または設計判断（分割/責務/インタフェース/データ整合/観測性/スケール）相談で使う。
Audit code, docs, tests, and registries against the Constitution, ADRs, and decision map without making broad repairs. Use when checking whether the repository is drifting away from accepted architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts an architecture or design decision record (ADR) from the discussion notes, design review minutes, chat threads and diagram descriptions the user provides: context, decision drivers, options considered with arguments as stated, the decision as the group worded it, consequences and a review date, with every factual claim tagged evidenced, asserted or UNKNOWN so unsupported claims are marked for the author to substantiate. Use when the user asks to "write an ADR", "document the architecture decision", "record why we chose this design", "turn these design review notes into a decision record" or "draft the design decision log entry". Do not use for a business or governance decision with no technical design, use decision-memo-builder instead; for the change ticket that implements the decision, use change-request-pack. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Adrapid tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Public relations, corporate communications, and analyst relations for B2B SaaS. Use this skill for earned media and press strategy, announcements and press releases, executive and crisis communications, media relationships and briefings, and the Gartner/Forrester/IDC analyst program including Magic Quadrant and Wave evaluation submissions. Also triggers on: PR, public relations, press release, earned media, media relations, journalist, embargo, announcement, crisis comms, corporate communications, analyst relations, AR, Gartner, Forrester, IDC, Magic Quadrant, Forrester Wave, analyst briefing, inquiry.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure design changes stay consistent across ADRs, diagrams, and specs; decisions are traceable; and drift is explicitly managed.
日本語の概要は準備中です。原文の説明を表示しています。
リファクタリングを「更新されたチームの理解と、コードが表現する過去の理解の差分同期」と捉え、今回得た新知識（要求・ドメイン知識・制約）が naming と responsibility へ反映されているか、boundary が現在の understanding を表現しているか、diff の削除行やコメントに現れる過去の design history と constraint を失っていないかを diff-time で確認する。Knowledge Delta の signal は diff（追加/削除された hunk・コメント・ADR 参照）を一次情報とし、PR 本文が供給されるときは補助に用い、不確実なら question に留める。ドメイン用語の一貫性は ubiquitous-language-naming、集約/コンテキスト境界の設計判断は bounded-context-language、投機的抽象化・caller special-case は altitude-generalization、スコープ逸脱/前提破壊は fix-scope-integrity、振る舞い変更と構造変更の分離は behavior-structure-separation、完了主張の反証は refactor-claim-audit へ委譲する
Use when managing Volcengine A-Drive resources with ve-adrive-cli, including AK/SK, OAuth, or Unified authentication, login and status, owner-aware Space creation and listing, and file or folder operations.
日本語の概要は準備中です。原文の説明を表示しています。
Subquadratic Attention Harvard NVIDIA Arya Tschand Yaosheng Fu Vijay Janapa Reddi Splitting quadrati
日本語の概要は準備中です。原文の説明を表示しています。
Imports a custom RoadRunner map (FBX geometry + XODR OpenDRIVE) into a CARLA source build as a drivable map — reads the map from the directory the user names, runs CARLA's Import.py to cook the level, Traffic Manager graph and (standard maps only) pedestrian navmesh, and verifies it loads on a server. Handles both standard maps and large tiled maps; large maps get no navmesh, matching upstream CARLA. Use when the user asks to "import a map into CARLA", "add a custom/RoadRunner map", "ingest an FBX+XODR map", "make import", bring in a "large/tiled map", or fix missing walkers / a missing pedestrian navmesh.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-agent debate orchestration for Architecture Decision Records. Automatically triggers on ADR create/edit/delete. Coordinates architect, critic, independent-thinker, security, analyst, and high-level-advisor agents in structured debate rounds until consensus.
日本語の概要は準備中です。原文の説明を表示しています。
モデル世代交代の手順（model-roster.md 更新 → ADR-0001 確認 → drift 検査 → agents 更新 → 再測定 → カタログ追記）
既存の計画・設計・アイデアを尋問形式でストレステストし、前提と未決定事項を洗い出す対話スキル。「グリルして」「grillして」「この計画を詰めて」「計画の穴を突いて」「ストレステストして」等の依頼時、実装着手前に計画の前提を検証したい時に使用。要件書等は生成せず、確定した重要決定だけを ADR に記録する。境界: ゼロからの要件定義は design-feature。
Mantém a documentação técnica viva no Notion e no repositório — arquitetura, runbooks, inventário, ADRs e procedimentos operacionais, gerados a partir da infraestrutura real. Use quando o usuário disser "documentar", "runbook", "ADR", "wiki", "Notion", "atualizar a documentação", "inventário", "ninguém sabe como isso funciona".
日本語の概要は準備中です。原文の説明を表示しています。