flutter-add-widget-preview
Use when configuring widget previews in Flutter development, testing visual component variations, or isolating widget UI states.
38,472 Skills
Search uses this published catalog; rankings and counts are snapshots.
Use when configuring widget previews in Flutter development, testing visual component variations, or isolating widget UI states.
Use when writing widget tests, finding UI elements with finders, simulating user gestures, or testing widget state updates.
Use when structuring Flutter application layers across data, domain, and presentation using Clean Architecture and BLoC.
Use when managing complex form state, synchronous and asynchronous input validation, or form submission transitions in BLoC.
Semantic code search and navigation using the cix index. Reach for cix when you don't already know where to look. Covers search, definitions, references, symbols, files, and indexing.
Master orchestrator for 18+ Firebase agent skills from official Google repositories. Use when working with Firebase, Firestore, Firebase Auth, Firebase Hosting,
Master orchestrator for 35+ mobile development agent skills from official Google repositories. Use when working with Android, Flutter, Dart, Jetpack Compose, Na
Model a requirement/system: extract goals, scope, roles, rules, exceptions, dependencies from PRD, docs, bugs, code; outputs a structured model with clarifications. Not for: writing cases, strategy decisions, the pipeline. 建模需求/系统:从 PRD、文档、Bug、代码提炼目标/范围/角色/规则/异常/依赖。不用于:直接写用例、策略、流
Review existing test cases (legacy, others', AI) for coverage and executability: build a testable-points baseline, assess independently, revise in place with records. Not for: writing cases from scratch (test-case-writing), pipeline. 审查已有用例(存量/他人/AI 产出)的覆盖与可执行性:先建基准再独立评估,修订留审查记录。
Write manual test cases (markmap) from docs, bugs or code — code-first: review code for bugs first; extracts machine-readable schema. Not for: requirement-analysis / test-strategy / test-case-review / automation. 从 PRD/API 文档、Bug 或代码写手动用例(markmap)——代码优先:先查代码找 bug 再写,抽 Schema。不用于:
\"How should this be tested?\" Evidence-backed risk map → scope and depth across functional domains and 10 testing-type axes; includes carry signals, excludes reasons. Not for: writing cases, requirement-analysis, pipeline (qa). 回答“这个功能应该怎么测”:风险挂证据(Risk Map),译为功能域+类型域十轴的范围与深度。不用于
MANDATORY handler for incoming ACCORD protocol messages. Activate immediately, before anything else, whenever your task begins with CONVENE_REQUEST, FRAME_REQUEST, GROUND_REQUEST, CLARIFY_REQUEST, VERIFY_REQUEST, or EXECUTION_REQUEST — every time, including when the request alrea
当用户希望启动另一个独立的 Claude Code 实例来分析、审查、讨论或提供第二意见时,使用此 skill。典型表达:'再开一个 claude 看看''用另一个 claude 审查一下''让 claude 给个第二意见''起一个新 claude 分析这个问题'。此 skill 通过 `claude -p` 启动一个独立的 Claude Code 子进程,在隔离的上下文中完成任务并返回结果。若用户只是询问 Claude Code CLI 本身的安装、配置或故障排查,则不触发。
当用户在自然语言中提到 codex,并希望它分析、讨论、复核或给方案时,立即使用此 skill。典型表达包括:'和 codex 讨论一下''让 codex 看看''问问 codex''用 codex 给个第二意见''多和 codex 讨论几轮'。此 skill 负责调用 Codex CLI 获取另一模型的独立意见。若用户只是询问 codex CLI 本身的安装、配置、命令或故障排查,则不触发。
与 Codex 进行多轮对抗式计划讨论。当用户希望 Codex 对计划、方案或架构设计进行深度审查,期望自动化多轮质疑-修改循环而非单次反馈时触发。典型表达:'和 codex 讨论计划''让 codex 审查方案''codex 对抗式讨论''多轮讨论方案''把计划给 codex 过一遍'。若用户只是让 codex 看一眼或给个简单意见,应使用 codex skill。
Use when users ask to update, refresh, or upgrade the local TapTap Maker MCP package.
Catalog captured:2026-11-21