tomada1114

Create ASCII wireframes, user flow diagrams, and cross-cutting specifications for UI/UX visualization. Use PROACTIVELY when user mentions wireframe, UI design, UX flow, screen layout, screen design, user flow, or asks to visualize screens. Examples: <example>Context: User needs screen design user: 'Create wireframes for this feature' assistant: 'I will use designing-wireframes skill' <commentary>Triggered by wireframe request</commentary></example> <example>Context: After requirements are detailed user: 'Let me design the screens' assistant: 'I will use designing-wireframes skill' <commentary>Triggered by screen design request</commentary></example>

Plan and create GitHub Issues with agile/scrum methodology. Analyze requirements, identify parallel work, manage dependencies, and suggest git worktree strategies. Use PROACTIVELY when creating tickets, planning sprints, breaking down features, organizing issues, identifying parallel tasks, managing dependencies, or working with GitHub Issues, scrum, agile planning, ticket breakdown, worktree planning. Examples: <example>Context: User wants to plan implementation user: 'チケットを作っていこう' assistant: 'I will use agile-ticket-planner skill' <commentary>Triggered by ticket creation request</commentary></example> <example>Context: User has requirements user: 'この要件をIssueに分割して' assistant: 'I will use agile-ticket-planner skill' <commentary>Triggered by issue breakdown request</commentary></example>

Clarify ambiguous requirements through structured questioning and produce detailed, implementation-ready specifications. Acts as PdM to identify unclear points and resolve them via AskUserQuestion. Use PROACTIVELY when user mentions requirements, specs, PRD, refine, detail, clarify requirements, or asks to detail/refine app ideas. Also trigger when the user is about to jump into implementation with a vague or incomplete spec — even if they haven't explicitly asked to "refine" anything. Examples: <example>Context: User has rough idea user: 'Help me refine this app spec' assistant: 'I will use refining-requirements skill' <commentary>Triggered by spec refinement request</commentary></example> <example>Context: User jumps to implementation with vague spec user: 'Let me start building this feature' assistant: 'I will use refining-requirements skill first to clarify the requirements' <commentary>Proactively triggered before ambiguous implementation</commentary></example> <example>Context: Planning phase user: 'Let

Design UI/UX concepts for apps and web services through systematic research and questioning. Use PROACTIVELY when designing app interfaces, determining visual direction, creating design systems, choosing color schemes, or establishing UX patterns. Examples: <example>Context: User wants to design an app user: 'UI/UXのデザインコンセプトを決めたい' assistant: 'I will use ui-ux-designing skill' <commentary>Triggered by design concept request</commentary></example> <example>Context: User building new feature user: 'この機能の見た目どうしよう' assistant: 'I will use ui-ux-designing skill' <commentary>Triggered by visual design question</commentary></example>

Author a concise, self-contained prompt to hand to Claude Code's /goal command in a separate, unattended session. Researches the target project (CLAUDE.md, dev rules, baseline build/test state, existing patterns) and drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules. Outputs to chat by default; externalizes bulky context to ~/.claude/goal-prompts/<slug>/ only when inlining would bloat it. Decides autonomously, asking only when a goal-defining axis is genuinely ambiguous. Use PROACTIVELY when the user mentions /goal, goal prompt, ゴールプロンプト, /goal に渡す, 自走/無人実行させたい, unattended run, 完了条件を決めて goal を回す, or setting up a long-running autonomous Claude session. Examples: <example>Context: User wants an unattended run user: '/goal に渡すプロンプトを作って' assistant: 'I will use authoring-goal-prompts skill' <commentary>goal-prompt authoring request</commentary></example>

Claude Code ベストプラクティスの対話形式セットアップウィザード。Use PROACTIVELY when setting up new projects, configuring Claude Code, adding agents/rules/hooks, or when user mentions "bootstrap", "setup claude", "configure claude code", "add agents", "add rules", "セットアップ", "初期設定", "ブートストラップ". Examples: <example>Context: User wants to set up Claude Code user: 'Claude Codeをセットアップしたい' assistant: 'I will use bootstrapping-claudecode skill' <commentary>Triggered by setup request</commentary></example>

Capture Claude Code terminal output and interactive UI screens via tmux. Launch a single Claude Code pane, send commands or keystrokes, capture screen output, and save to markdown files. Use PROACTIVELY when capturing Claude Code output, recording terminal sessions, screen capture, UI navigation capture, tmux capture, recording Claude responses, キャプチャ, 画面記録, 出力記録. Examples: <example>Context: User wants to capture Claude output user: 'Helloの出力を記録して' assistant: 'I will use capturing-claudecode skill' <commentary>Triggered by capture request</commentary></example>

Create, audit, refactor, or troubleshoot Claude Code skills via explicit command. Modes: new (scaffold a fresh skill), audit (run validate + audit scripts and write a report), convert (turn an existing doc into a skill), troubleshoot (diagnose activation, frontmatter, or link issues), add-subagents (introduce multi-phase orchestration). Accepts a skill name or path as the second argument.

Create or update pull requests following project conventions. Runs pre-checks (`just verify`), generates a Conventional Commits title, fills the PR template with summary/test plan/checklist, and verifies all checklist items pass before creating via gh CLI. Use PROACTIVELY when: PR creation, pull request, create PR, open PR, submit PR, PR update, review request.

Triage, verify, and land open Dependabot/Renovate dependency PRs. Surveys all bot PRs, classifies bump risk, checks CI and security signals, then either merges eligible PRs individually or builds one combined integration PR (regenerating uv.lock) and closes the superseded originals once CI is green. Use PROACTIVELY when: dependabot, dependency PRs, bump PRs, dependency update, merge dependabot, batch dependency PRs, 依存関係の更新, 依存PRのマージ.

Analyze working tree changes, group them into logical atomic commits with Conventional Commits messages, and push. Handles staging, sensitive file exclusion, and uv.lock bundling automatically. Use PROACTIVELY when: commit, git commit, save changes, commit and push, stage changes, push my changes, commit this work, ship it.

Create or update pull requests following project conventions. Runs pre-checks (just check), generates Conventional Commits title, fills PR template with summary/test plan/checklist, and verifies all checklist items pass before creating via gh CLI. Use PROACTIVELY when: PR creation, pull request, create PR, open PR, submit PR, PR update, review request.

Analyze working tree changes, group them into logical atomic commits with Conventional Commits messages, and push. Handles staging, sensitive file exclusion, and Package.resolved bundling automatically. Use PROACTIVELY when: commit, git commit, save changes, commit and push, stage changes, push my changes, commit this work, ship it.

Red-green-refactor workflow for this repository: write a failing Swift Testing test in SpyglassCoreTests first, prove it fails, implement the minimum in SpyglassCore to pass, then refactor and re-verify the coverage floor. Use PROACTIVELY when: implementing a feature, changing behavior, fixing a bug, adding logic, new function, new type, TDD, test-first.

Create or update pull requests following project conventions. Runs pre-checks (just check), generates Conventional Commits title, fills PR template with summary/test plan/checklist, and verifies all checklist items pass before creating via gh CLI. Use PROACTIVELY when: PR creation, pull request, create PR, open PR, submit PR, PR update, review request.

Analyze working tree changes, group them into logical atomic commits with Conventional Commits messages, and push. Handles staging, sensitive file exclusion, and Package.resolved bundling automatically. Use PROACTIVELY when: commit, git commit, save changes, commit and push, stage changes, push my changes, commit this work, ship it.

Red-green-refactor workflow for this repository: write a failing Swift Testing test in MyAppCoreTests first, prove it fails, implement the minimum in MyAppCore to pass, then refactor and re-verify the coverage floor. Use PROACTIVELY when: implementing a feature, changing behavior, fixing a bug, adding logic, new function, new type, TDD, test-first.

Design system based on Apple Human Interface Guidelines. Instantly implement iOS System Colors, Semantic Colors, and Dark Mode support in Expo/React Native apps. Use PROACTIVELY when implementing theme system, setting up colors, configuring Dark Mode, building UI components, or following iOS design patterns. Examples: <example>Context: User asks about UI implementation user: 'Add a card component with proper colors' assistant: 'I will use expo-design-system skill' <commentary>Triggered by UI component and color implementation request</commentary></example>

Mobile UX design principles for intuitive, user-centered app experiences. Use PROACTIVELY when designing user flows, navigation patterns, interaction design, onboarding, form design, error handling, loading states, or optimizing for one-handed use. Examples: <example>Context: User asks about user flow user: 'How should I structure the checkout flow?' assistant: 'I will use mobile-ux-design skill' <commentary>Triggered by user flow design request</commentary></example>

Implement subscription monetization in Expo apps using RevenueCat with Clean Architecture patterns. Use PROACTIVELY when building subscription features, setting up RevenueCat, implementing feature gates, adding tiered pricing, or working with in-app purchases. Examples: <example>Context: User asks about monetization user: 'Add subscription to my app' assistant: 'I will use expo-subscription-monetization skill' <commentary>Triggered by subscription/monetization request</commentary></example>

ドキュメントの品質チェックを行う。マークダウン文書、README、技術文書を作成・編集する時に使用。

Create UI components following Google Material Design 3 guidelines using Tailwind CSS. Use when building Material Design compliant interfaces, generating color themes, creating MD3 components (buttons, cards, dialogs, chips), or implementing responsive layouts. Triggers: "Material Design", "MD3", "Material UI with Tailwind", "Google design system", "create Material button/card/dialog", "Material color palette", "Material theme".

Resident designer for PeerPort — the cyber port town life-sim. Owns art direction, screen/UI design, worldview & character consistency, UI copy voice, and pixel-asset specs. Use PROACTIVELY when designing or reviewing anything the Keeper sees (map, Bridge panel, tabs, onboarding, popups), choosing visual direction (pixel scale, palette, neon, typography), writing UI copy, or when user mentions デザイン, 画面設計, 見た目, UI, UX, ワイヤーフレーム, 世界観, キャラクター, ドット絵, アートディレクション, design, wireframe, art direction, sprite, mockup.

Create or update pull requests following project conventions. Runs pre-checks (just check), generates Conventional Commits title, fills PR template with summary/test plan/checklist, and verifies all checklist items pass before creating via gh CLI. Use PROACTIVELY when: PR creation, pull request, create PR, open PR, submit PR, PR update, review request.

Create or update pull requests following project conventions. Runs pre-checks (just check), generates Conventional Commits title, fills PR template with summary/test plan/checklist, and verifies all checklist items pass before creating via gh CLI. Use PROACTIVELY when: PR creation, pull request, create PR, open PR, submit PR, PR update, review request.

Analyze working tree changes, group them into logical atomic commits with Conventional Commits messages, and push. Handles staging, sensitive file exclusion, and uv.lock bundling automatically. Use PROACTIVELY when: commit, git commit, save changes, commit and push, stage changes, push my changes, commit this work, ship it.

Triage, verify, and land open Dependabot/Renovate dependency PRs. Surveys all bot PRs, classifies bump risk, checks CI and security signals, then either merges eligible PRs individually or builds one combined integration PR (regenerating uv.lock) and closes the superseded originals once CI is green. Use PROACTIVELY when: dependabot, dependency PRs, bump PRs, dependency update, merge dependabot, batch dependency PRs, 依存関係の更新, 依存PRのマージ.

Transcribe an audio file to text using the whisper-srt CLI. The output .txt file is saved in the same directory as the input audio. Use PROACTIVELY when the user provides an absolute path to an audio file (mp3, webm, wav, m4a, ogg, flac, mp4, mpeg, mpga, oga) and asks to transcribe it, convert it to text, or perform 文字起こし. Also use when user says "文字起こしして", "テキスト化して", "書き起こして". Argument: absolute path to the audio file.