nwiizo

技術カンファレンスのCFP（Call for Papers）を新規作成・改善・段階レビューする。イベントとの整合、冒頭2〜3行、聴講者価値、実践的根拠、新規性、読みやすさ、提出制約を検証し、採択確率を上げる応募文と具体的な修正案が必要なときに使用する。

Rust/Axum などで SPA 向け OAuth 2.0 / OpenID Connect BFF を実装・レビュー・検証する。ブラウザにアクセストークンやリフレッシュトークンを出さない設計、HttpOnly Cookie セッション、CSRF/CORS/Origin 検証、Hydra などの認可サーバー連携、Playwright でのログイン往復検証を扱うときに使用。

Marpプレゼンテーションの技術的制約とベストプラクティス。marp:trueのMarkdown編集時やスライド作成リクエスト時に自動使用。

公式翻訳との比較から導出した技術書翻訳の品質基準。翻訳作業時に自動参照。

Build→Test→Feedback→Refineの反復改善ワークフロー。ツール開発時のフィードバックループとOSS検証を支援。

複雑タスクを逐次ステップに分割し、各ステップ内で並列サブタスクを実行する。大きなタスクを依頼されたとき、または「分割して」「段階的に」と指示されたときに使用。

Claude Code TaskList と vibe-ticket の同期。タスク管理の状態を双方向で同期する。

ツールを実際のOSSプロジェクト(bat, fd, ripgrep, eza, tokei)で検証する。ツールの品質・パフォーマンス検証時に使用。

Add config to this macOS dotfiles repo. Use for env vars, fish abbreviations/functions/plugins, direct symlinked config files, tool integrations, shared agent config, and app config such as Neovim, Ghostty, Warp, Git, Bat, Atuin, tealdeer, and gh.

Add a package to this macOS dotfiles repo. Use when the user asks to install, add, or migrate a CLI package or GUI app, for example "add jq", "ripgrep を入れて", "lazygit 入れたい", "brew install foo を repo 管理に", "kubectl 追加して". Homebrew owns binaries here; update…

実装前の計画・設計・意思決定を、1問ずつの徹底インタビューで叩いて固める。共有理解に達するまで実装しない。Invoke manually before non-trivial implementation when a plan or design already exists and needs stress-testing.

Use before non-trivial creative work when a material product or design choice is still unresolved. Clarifies purpose, constraints, success criteria, and tradeoffs before implementation. Skip when the request is trivial or already well specified.

高頻度・高リスクのagent向け指示、または期待どおり動かないskillやプロンプトを、独立した実行者と固定シナリオで比較評価する。小さな文言修正には使わず、指示側の曖昧さや過剰制約を実測したいときに使用する。

Build→Test→Feedback→Refineの反復改善ワークフロー。ツール開発時のフィードバックループとOSS検証を支援。

Spawn a parallel coding-agent session in its own jj workspace. Uses `jj_agent` if the nwiizo/jujutsu.fish plugin is installed, otherwise falls back to raw `jj workspace add`. Use when starting a second (or Nth) agent on a different task without disturbing the…

In any jj (Jujutsu) repository, complete the "commit" pattern — describe the current working copy with a message, then open a fresh change for the next unit of work. Use when a coherent edit is finished and should be preserved before moving on. Teach the user…

Duplicate code detection using similarity-rs. Identifies refactoring candidates based on semantic similarity.

Duplicate code detection using similarity-rs. Identifies refactoring candidates based on semantic similarity.

Run performance benchmarks with criterion. Compare against baselines and profile hotspots.

Implementation verification - runs format, lint, test, and build checks on the workspace.

Production readiness audit - checks unwrap elimination, error handling, clippy, docs, channel usage, and test count.

Release deployment process for ccswarm. Version update, quality gates, build, tag, publish.

Parallel development workflow using git worktrees. Each agent gets an isolated worktree for safe concurrent work.

Human-in-the-loop approval workflow for high-risk agent operations (file deletions, deployments, config changes).

Khononov's Balanced Coupling model reference. Auto-loaded when analyzing coupling patterns, reviewing architecture, or interpreting analysis results.

Run coupling analysis and interpret results. Use when analyzing Rust project coupling patterns and generating improvement proposals.

Quick health check for coupling balance score. Use for daily score verification and CI quality gates.

Modularity review using Balanced Coupling model. Combines automated analysis with semantic code review to find implicit coupling and design issues.

Start interactive web UI for coupling analysis visualization. Graph exploration with filters, hotspots, and export.

Run mutation testing with cargo-mutants to evaluate test quality. Identifies untested code paths.

Explain coupling issue types in detail with detection conditions, code examples, and solution approaches.

Identify high-priority refactoring targets using hotspot scoring. Ranks modules by issue severity and coupling count.

Run full quality gate before release — fmt, clippy, test, mutants, similarity, coupling.

Run cargo-coupling and similarity-rs to identify refactoring targets, then create a prioritized plan.

Systematic bug investigation and fix workflow. Use when fixing bugs, investigating issues, or debugging test failures.

Pre-release verification workflow - version, security audit, performance, cross-platform builds, documentation.

Development environment setup - Rust toolchain, cross-compilation targets, dependencies, git hooks, IDE config.

Split complex tasks into sequential steps with parallel subtasks. Use for multi-step workflows needing dependency ordering and adaptive planning.

Comprehensive quality assurance - tests, linting, formatting, code analysis, and release build verification.

Systematic code refactoring - analysis, pattern detection, incremental changes with verification. Use for code improvement and tech debt reduction.

Test and deepen the load-bearing claims in a Marp presentation. Use when punchlines feel generic, causal claims are unsupported, conclusions overreach their evidence, trade-offs or boundary conditions are missing, or the audience cannot tell how an insight…

Validate and prepare Marp slides for public release. Use before publishing or pushing changes that affect slide Markdown, themes, images, PDFs, README links, brand packs, or build configuration, especially when clean-clone reproducibility and…

Review a Marp presentation’s logical flow from the audience’s point of view. Use when checking section order, slide-to-slide reasoning, unanswered questions, hidden prerequisites, promise fulfillment, transitions, or whether a proposed reordering will make a…

Review the narrative and audience-empathy design of a Marp presentation. Use when a technically correct talk feels flat, the opening lacks stakes, examples do not connect to the audience, tension or agency disappears, the ending lacks payoff, or proposed…

Coordinate and synthesize multiple specialist reviews of a Marp presentation into one coherent edit strategy. Use when a deck needs flow, claim depth, narrative, redundancy, and wit reviews together, or when specialist recommendations conflict over adding,…

Review humor, satire, irony, metaphor, and rhetorical wit in a Marp presentation for purpose, precision, speaker voice, audience fit, and context-collapse safety. Use when a talk contains jokes or playful phrasing, needs sharper memorable language, risks…

Find and safely remove redundancy in a Marp presentation while preserving comprehension, emphasis, pacing, and accessibility. Use when a deck is too long, repeats claims or examples, contains thin or overloaded slides, needs a target duration, or requires…

スライドビルド - Marpスライドを `--no-stdin` 付きで HTML/PDF 出力する

スライドレビュー - Marpプレゼンテーションを聴衆起点・構成・容量・配色・視覚装飾・ファクト・表現の7観点で総合評価

構成チェック - プレゼンテーションの骨格（全体構成・目次整合・Why→What→How順序・繋ぎスライド）を評価する

ファクトチェック - スライド内の数値・引用・技術仕様・人名・年号の事実関係をWebSearch/WebFetchで検証

Spawn a parallel coding-agent session in its own jj workspace using `jj_agent`. Use when starting a second (or Nth) agent on a different task without disturbing the current working copy. Invoke manually; creates a workspace directory on disk.

In a jj repository, complete the "commit" pattern — describe the current working copy with a message, then open a fresh change for the next unit of work. Use when a coherent edit is finished and should be preserved before moving on. Invoke manually; mutates…

Add a new jj abbreviation across the 4 required sites (register, erase, README, test) with verification. Invoke manually; has side effects.

Scaffold a new jj_fzf_* picker following the shared contract — dependency guards, cancel code 130, tab-delimited templates, binding wiring, README entry. Invoke manually; has side effects.

Generate Japanese daily reports, reflection prompts, guides, reviews, and trend reports from Claude Code or Codex work logs. Use when the user asks for nippo, 日報, daily, reflection, guide, report, review, insight, trend, plan, ledger, or wants to summarize…

ユーザーが日報・振り返り・作業まとめ・週報・自己評価を求めたときに、 Claude Code / Codex のセッションログから日報・リフレクション・インサイトを生成する。 /nippo と /nippo daily で日報、/nippo reflection で内省の問い、/nippo guide で学習支援、 /nippo report で進捗報告、/nippo review で自己評価、/nippo insight で深い振り返り、 /nippo trend で長期変化分析、/nippo plan…

Maintain cargo.nvim's Rust native module, Lua/Neovim runtime, build configuration, tests, CI, dependencies, documentation, release tooling, and version metadata. Use when changing Cargo.toml, Cargo.lock, .cargo/config.toml, src/, lua/, plugin/, tests/,…

Bridge Claude Code to cargo.nvim's canonical maintenance instructions. Use when changing or reviewing the Rust native module, Lua/Neovim runtime, build configuration, tests, CI, dependencies, documentation, release tooling, or version metadata.

Prepare, verify, publish, or troubleshoot a tfmcp release to crates.io and GitHub. Use for version changes, release readiness checks, changelog preparation, tagging, or publication.

日本語文書のAI由来の均一さ、翻訳調、不自然さ、論旨、読解負荷を、決定的なRust CLIと目視で診断し、依頼に応じて書く・直す。Use when the user explicitly mentions suiko, asks whether Japanese text looks AI-generated, requests a naturalness score or final readability pass, wants a Japanese meeting note, report, guide,…