用于从 1flowbase 当前源码构建、修复和审计 MCP 配置：只读投影 GUI 用户任务与后端契约，配置 Tool、input/output mapping、参数说明、Group、Binding 与 discovery policy，并通过 mcp_list、mcp_get、mcp_call 验证。只修改 MCP 配置数据；不修改 GUI、业务接口、产品源码或产品语义。
Evidence-driven QA evaluation for 1flowbase dev acceptance, PR merge gates, project health gates, regression, stale or incompatible test expectation triage, delivery, full-project and AI code audits, quality gate routing, i18n/multilingual key-value hygiene,…
Use for 1flowbase frontend implementation in web/: building, fixing, refactoring, or code-reviewing UI pages, app shell, routes, workspace flows, node UI, schema UI, i18n resources, responsive layout, visual structure, ECharts/reporting UI, low-code JS Block…
Use for 1flowbase backend implementation in api/: building, fixing, refactoring, or code-reviewing Rust/Axum APIs, routes, services, repositories, storage adapters, migrations, domain models, state transitions, write paths, module boundaries, permissions,…
Use when implementing 1flowbase features, bug fixes, refactors, backend APIs, state transitions, permissions, contract changes, or behavior changes that can be covered by automated tests. For a Single Issue, run the minimum failing test before implementation.…
1flowbase 需求对齐、会导向产品决策的现状诊断与动工前决策 Skill。用于功能、缺陷、交互、重构、规则、文档、架构、数学或算法表达、状态、权限、数据、API contract 或跨前后端需求；也用于诊断为什么两个流程不一致、能力为何缺失或不可编辑、职责应放在哪个入口、当前设计是否应改变。从证据中收敛现状、需求分析、保守 / 平衡 / 激进三个方向与唯一建议，再选择 Single Issue 或两层 Issue Tree。确认前不实现；只有不影响产品 /…
Use when a concrete engineering problem, bug, integration failure, dependency issue, unclear API usage, implementation blocker, or tool/capability need may already have a proven solution in GitHub open-source projects, issues, pull requests, discussions,…