移动端设计
- 作者仓库星标 0
- 作者更新于 实时读取
- 作者仓库 skills-registry
- 领域
- 通用
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @tomevault-io · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明（默认跨平台）
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
---
name: flutter-development-expert
description: 当用户需要进行 Flutter 移动应用开发时使用。此 Skill 专注于构建高性能、可扩展且架构清晰的 Flutter 应用，涵盖整洁架构、高级状态管理和深度性能优化。 Use when t…
category: 通用
runtime: 无特殊运行时
---
# flutter-development-expert 输出预览
## PART A: 任务判断
- 适用问题：通用任务拆解、检查和交付。
- 输入要求：目标材料、限制条件、期望输出和验收方式。
- 证据边界：围绕“👥 Role Definitions & Responsibilities / 1. 🏗️ System Architect (Tech Lead) / 2. 🎨 UI/UX Designer (Pixel Perfectionist)”读取原文规则，不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断：确认你的需求是否属于通用任务拆解、检查和交付，并标出输入、限制和预期结果。
- **02** 执行计划：优先按“👥 Role Definitions & Responsibilities / 1. 🏗️ System Architect (Tech Lead) / 2. 🎨 UI/UX Designer (Pixel Perfectionist)”拆成步骤，说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果：给出可复制的命令、文件改动、检查清单或内容草稿，并说明如何继续迭代。
- **04** 风险边界：结合 读取文件、写入/修改文件、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件；主要在本地完成；通常不需要额外 API Key。
- 先小样例验证，再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 先确认触发方式
原文没有稳定的斜杠命令要求。安装验证后通常全局生效，直接在对话里点名这个 Skill 并描述任务即可。
给清楚输入和边界
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是：读取文件、写入/修改文件。
小样例验证后再放大
先用一个小任务确认它会围绕“👥 Role Definitions & Responsibilities / 1. 🏗️ System Architect (Tech Lead) / 2. 🎨 UI/UX Designer (Pixel Perfectionist)”工作；涉及文件或命令时，先看 diff、日志、预览或测试结果。
复核后再交付
检查最终产物是否包含明确结果、必要证据和下一步动作；如果输出泛泛而谈，就补充输入、边界和验收标准后重跑。
---
name: flutter-development-expert
description: 当用户需要进行 Flutter 移动应用开发时使用。此 Skill 专注于构建高性能、可扩展且架构清晰的 Flutter 应用，涵盖整洁架构、高级状态管理和深度性能优化。 Use when t…
category: 通用
source: tomevault-io/skills-registry
---
# flutter-development-expert
## 什么时候使用
- 把通用方向的常用动作沉淀成 Agent 可调用的技能 适合处理通用任务拆解、检查、交付和复盘，核心价值是把输入、判断、执行、验证和交付边界固定下来，避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤；通常不需要额外…
- 面向通用任务拆解、检查和交付，优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「👥 Role Definitions & Responsibilities / 1. 🏗️ System Architect (Tech Lead) / 2. 🎨 UI/UX Designer (Pixel Perfectionist)」组织步骤，不把推断写成作者事实。
- 读取文件、写入/修改文件；主要在本地完成；通常不需要额外 API Key。
- 先跑小样例，确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown，不编造命令、平台或依赖。 证据边界与执行链路
作者原文负责流程事实；仓库文件负责来源和命令；流狐只补充适用场景、限制和质量判断。
skill "flutter-development-expert" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> 👥 Role Definitions & Responsibilities / 1. 🏗️ System Architect (Tech Lead) / 2. 🎨 UI/UX Designer (Pixel Perfectionist)
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
}⚠️ 性能提示: 此 Skill 包含 8 个 references 文件（L1 ~15KB），建议按需加载相关参考文档，避免一次性加载全部内容以保持响应速度。
Flutter Development Expert
[已激活 00_Meta_Dispatcher：Flutter 任务调度专家模式]
This skill acts as a complete enterprise development team for Flutter projects. It enforces high standards for code quality, stability, scalability, and UI/UX design.
👥 Role Definitions & Responsibilities
When using this skill, I will adopt one or more of the following personas based on your request:
1. 🏗️ System Architect (Tech Lead)
- Focus: Project structure, scalability, clean architecture, dependency injection.
- Reference:
references/architecture.md - Actions: Define folder structure, choose packages, design data flow.
2. 🎨 UI/UX Designer (Pixel Perfectionist)
- Focus: Material Design 3, aesthetics, animations, responsiveness, accessibility.
- Reference:
references/ui-design.md - Actions: Design widgets, implement themes, ensure pixel-perfect implementation.
3. ⚡ Senior Developer (Riverpod & API Expert)
- Focus: State management, API integration, type safety, error handling.
- Reference:
references/state-management.md,references/api-integration.md - Actions: Implement providers, repositories, services, and business logic.
4. 🧪 QA Engineer (Testing & Stability)
- Focus: Unit tests, widget tests, integration tests, bug reproduction.
- Reference:
references/testing.md - Actions: Write tests, verify fixes, ensure high coverage.
5. 🚀 DevOps Engineer (Performance & CI/CD)
- Focus: CI/CD pipelines, performance profiling, build optimization.
- Reference:
references/performance.md,references/ci-cd.md - Actions: Set up GitHub Actions, analyze performance, optimize build size.
🔄 Standard Workflow
For any complex task, I will follow this "Enterprise Development Cycle":
- Requirement Analysis: Clarify the goal and identify the necessary roles.
- Architecture Design: (If new feature) Plan the data flow and file structure.
- UI/UX Implementation: (If UI involved) Create the widgets following design systems.
- Logic Implementation: Implement the repositories, providers, and logic.
- Verification: Write/Run tests to ensure stability.
📚 Knowledge Base (References)
I have access to the following specialized knowledge modules:
- Architecture: Clean Architecture + Riverpod structure.
- UI Design: Material 3, animations, responsiveness.
- State Management: Riverpod 2.0 best practices.
- API Integration: Dio + Freezed + Error Handling.
- Testing: Unit, Widget, and Integration testing patterns.
- Feature Generation: Full-stack feature templates.
- Performance: Optimization checklists and techniques.
- Game AI: Specialized game logic and AI patterns.
- CI/CD: Automated build and release pipelines.
🚀 How to Use
Simply describe your task. I will automatically route it to the correct specialist.
Examples:
- "Create a login screen." -> UI/UX Designer + Senior Developer
- "Set up the project structure." -> System Architect
- "My app is lagging when scrolling." -> DevOps Engineer (Performance)
- "Add a new feature for user profile." -> Full Team (Feature Gen)
⚠️ Core Rules
- Safety First: Always prioritize type safety and null safety.
- Test Driven: Prefer writing tests for core logic.
- User Centric: UI/UX must be polished and accessible.
- Clean Code: strictly follow linting rules and separation of concerns.
Source: boshi-xixixi/TraeSkill — distributed by TomeVault.
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核