signalcompose

Web search using Google Antigravity CLI (agy, formerly Gemini CLI). Use for: latest information, documentation lookup, current events, or when up-to-date web data is needed.

Team-based PR review with specialized parallel agents, CI integration, and iterative fix loop. Use when: "review this PR", "PR review", "PRレビュー", "PRをレビューして", "チームでPRレビュー".

Surface things worth considering before merging a PR: simplify run, pr-review-team iterate, security scan (trufflehog), .gitignore patterns, tests, docs, and any project-specific items from CLAUDE.md. This is a reminder, not a verifier. Use when: "merge 前チェック", "チェックリスト", "何か漏れてない?", "pre-merge", "checkup", "マージ前確認".

Research topics or review code using OpenAI Codex CLI. Use for: technical research, documentation lookup, code analysis, or when external AI perspective is needed.

Research AWS topics using Kiro CLI as an AWS expert (readonly mode). Use for: AWS documentation, error investigation, CloudFormation/CDK questions, AWS best practices. Note: Uses Kiro's training knowledge only (no web search).

Team-based code refactoring with analysis and user-approved changes. Use when: "refactor this code", "リファクタリング", "コード整理", "refactor team", "リファクタチーム".

X (Twitter) Articles のエディタ仕様・記事構造・ベストプラクティス。 Use when: "X Articlesの記事を書く", "Twitter Article", "X Articlesのエディタ", "DraftJSの制約", "ヘッダー画像を作る", "記事を公開する", "X Articlesに投稿", "ヘッダー画像を生成する", "publish to X Articles".

This skill displays recently active projects updated within the configured threshold. Use when the user asks "show active projects", "what am I working on", "recent projects", "current projects", "アクティブなプロジェクト", "最近のプロジェクト", or "今やってるプロジェクト".

Organize and tidy up Max/MSP patch layout. Use this skill when: - User asks to organize, tidy, or clean up a patch layout - After completing a series of patch edits (add/remove/connect objects) - Automatically triggered for partial layout adjustment after individual operations - Optimizing patchcord routing and object positioning

Guidelines for creating Max/MSP patches with MaxMCP. Use this skill when: - Creating new Max patches via MaxMCP - Adding Max objects with add_max_object - Connecting objects with connect_max_objects or managing patchcords - Planning patch layout and organization - Building audio/MIDI processing patches - Designing presentation mode UI (panels, colors, object visibility) - Setting varnames or naming conventions for Max objects - Asking about MaxMCP patch creation best practices

Max for Live development techniques and best practices. Use this skill when: - Accessing Ableton Live parameters from Max for Live (Live Object Model) - Using live.path, live.object, live.observer - Building dynamic LOM paths or monitoring Live set properties - Managing M4L device namespaces (

Access Max/MSP built-in resources. Use when: - User asks about Max objects ("How do I use cycle~?") - User wants to find examples or snippets - User needs object reference information (inlets, outlets, methods)

Max/MSP implementation techniques and best practices. Use this skill when: - Working with poly~ for polyphonic or parallel processing - Using bpatcher for modular patch design - Managing parameters with pattr/pattrstorage - Building audio signal chains or MIDI processing logic - Handling sampling rate dependent behavior - Multi-stage initialization patterns (loadbang, delay chains)

Build a multi-page, research-grade VitePress learning site from scratch for a topic the user wants to deeply understand. Drives an interview-first workflow — grills the user one decision at a time on scope, audience, language, depth, and boundaries; gathers primary sources before any writing begins; scaffolds a VitePress project with Mermaid (and optionally KaTeX); dispatches parallel writing sub-agents under strict fact-first discipline (mandatory source citations per file, explicit uncertainty markers, zero speculation); runs an independent external audit pass (e.g., via a second LLM/agent such as Codex) for fact-check and structural critique; verifies rendering in a real browser with dev tools (build success alone is insufficient — math layout, Mermaid SVGs, console errors all get checked). Use this skill whenever the user asks to "build a learning site", "make a study reference", "produce a structured explainer for X", wants a VitePress-based "I want to deeply understand X" outcome, or says things like "ド