「what」の検索結果

Compose and Compose Multiplatform expert for UI development across Android, Desktop, iOS, and Web. Use whenever the user mentions Compose APIs (@Composable, remember, LaunchedEffect, NavHost, MaterialTheme, LazyColumn, Modifier, recomposition), Compose Multiplatform (commonMain, expect/actual, Res.*, ComposeUIViewController, UIKitView, ComposeViewport), Android TV (tv-material, D-pad, focus, Carousel), Material 3 motion, atomic design systems, design-to-code workflows, Paging 3, or navigation. Activates Review Mode on GitHub PR URLs and review phrases ("review this PR", "what's wrong with this"). Auto-detects Compose projects on session_start. Backed by actual androidx/androidx and JetBrains/compose-multiplatform-core source receipts. See "## When this skill applies" in SKILL.md for the full trigger surface.

日本語の概要は準備中です。原文の説明を表示しています。

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

日本語の概要は準備中です。原文の説明を表示しています。

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

日本語の概要は準備中です。原文の説明を表示しています。

Clarify domain concepts, language, boundaries, and durable architectural decisions. Use when terminology is ambiguous, the user is shaping a domain model, or a design depends on resolving what concepts mean.

日本語の概要は準備中です。原文の説明を表示しています。

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

日本語の概要は準備中です。原文の説明を表示しています。

Discover help documentation work from operately git history. Use when the user asks to audit what needs documenting since a release, tag, or SHA, or to identify documentation gaps from code changes. Requires a baseline SHA or tag as input.

日本語の概要は準備中です。原文の説明を表示しています。

Captures, masks, compares, and updates screenshot baselines for web and mobile suites, with per-region thresholds and a reviewed-diff rule for every baseline change. Use when a screenshot assertion fails, a baseline needs updating, or visual checks are being added; not for deciding what to verify.

日本語の概要は準備中です。原文の説明を表示しています。

Define a repository review policy fixing what each review pass checks, how severities rank, which paths are skipped, the nit cap, and who approves. Use when review findings feel inconsistent or noisy, or when tuning an automated reviewer.

日本語の概要は準備中です。原文の説明を表示しています。

Generate user-facing release notes for the App Store and Google Play from git history (App Store <=4000 chars, Google Play <=500). Use when generating release notes, app store changelog, play store release, or "what's new" text for a mobile app.

日本語の概要は準備中です。原文の説明を表示しています。

Creates a Check for Understanding (CFU) for a math topic or standard: 1–3 targeted formative items whose distractors come from documented student misconceptions, plus a teacher guide routing each likely response to a specific next instructional step. Load BEFORE asking any clarifying question about grade, standard, or topic. This skill is for math; for other subjects, help as you normally would and don't mention the skill to the user. Triggers on asks to create, write, generate, or design a check for understanding, formative check, quick check, or exit ticket for a math concept or standard, and on implicit signals like "I need to see who got it before I move on." Not a quiz, test, or practice set — a CFU is read for what it reveals, not scored, so a numbered quiz or a bare answer key is a different job. Does not create a lesson (k12-lesson-plan-creation, which brings its own exit ticket), tier one (k12-lesson-differentiation), or prepare a teacher to teach one (k12-lesson-prep).

日本語の概要は準備中です。原文の説明を表示しています。

Helps a teacher prepare to teach an existing K-12 lesson (math / ELA / science / social studies) — a prep partner that thinks through the lesson's key student task with the teacher and leaves a short teacher-only prep note. Triggers on asks to internalize, prepare for, get ready to teach, or understand a lesson, including implicit ones ("help me get ready for tomorrow's lesson"), and right after another skill built a lesson, which it can follow. Not for building or adapting a lesson, grading, rubrics, assessment feedback, or generating quizzes or student-facing material, and not for single-fact lookups a sentence would answer ("what standard is this?", "how long is this lesson?").

日本語の概要は準備中です。原文の説明を表示しています。

Walk through the Elixir/Phoenix plugin commands, workflow; Use when a new user wants to learn what the plugin offers…

日本語の概要は準備中です。原文の説明を表示しています。

Analyze Elixir/Phoenix technical debt — duplicates, refactoring; Use when asked about code quality, cleanup, or what…

日本語の概要は準備中です。原文の説明を表示しています。

Recall prior work from past sessions — how a bug was fixed, what was; Use when asked 'have we done this before'…

日本語の概要は準備中です。原文の説明を表示しています。

Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.

日本語の概要は準備中です。原文の説明を表示しています。

Walk through the Elixir/Phoenix plugin commands, workflow, and features in 6 interactive sections. Use when a new user wants to learn what the plugin offers or needs a refresher on available commands.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.

日本語の概要は準備中です。原文の説明を表示しています。

Recall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked 'have we done this before' or 'how did I fix X' in Elixir/Phoenix work. ccrider MCP when available, else git + solution docs.

日本語の概要は準備中です。原文の説明を表示しています。

Recall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked 'have we done this before' or 'how did I fix X' in Elixir/Phoenix work. ccrider MCP when available, else git + solution docs.

日本語の概要は準備中です。原文の説明を表示しています。

Walk through the Elixir/Phoenix plugin commands, workflow, and features in 6 interactive sections. Use when a new user wants to learn what the plugin offers or needs a refresher on available commands.

日本語の概要は準備中です。原文の説明を表示しています。

Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.

日本語の概要は準備中です。原文の説明を表示しています。

Intent-driven knowhow precipitation — describe what you want to capture (记一个关于X的决策 / 保存这段代码模板 / 写个部署配方 / 存个调试技巧) and the workflow infers the type and records it into .workflow/knowhow/. Pure capture surface; knowhow 的管理/审计走 /maestro-knowledge；项目约束规则走 /maestro-spec add。Triggers on "knowhow capture", "知识沉淀", "沉淀经验", "记录模板", "记录决策", "adr", "存个技巧".

日本語の概要は準備中です。原文の説明を表示しています。

Intent-driven issue lifecycle management — describe what you want in natural language (报告一个 bug / 列出开放 issue / 关掉 ISS-xxx / 关联到 task / 扫描发现问题) and the workflow routes to the right operation. Operates on .workflow/issues/. 知识管理走 /maestro-knowledge；knowhow 沉淀走 /maestro-knowhow；约束规则走 /maestro-spec。Triggers on "issue 管理", "报 bug", "记录问题", "issue list", "关闭 issue", "issue discover", "发现问题".

日本語の概要は準備中です。原文の説明を表示しています。

Shows available skills, common workflows, and quick reference for the plugin. Use when the user asks for help, what skills are available, or how to do something.

日本語の概要は準備中です。原文の説明を表示しています。