메뉴
Rules, constraints, boundaries, and best practices for the multi-agent Python to Dart porting workflow.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/flutter/demos --skill tdd-dart-workflow명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | tdd-dart-workflow |
| description | Rules, constraints, boundaries, and best practices for the multi-agent Python to Dart porting workflow. |
These rules govern the development, design, and TDD workflow of porting a Python library to Dart. All agents running in this workspace must adhere strictly to these guidelines.
Development proceeds in structured TDD cycles coordinated by the parent agent:
<dart_package_dir>/specs/architecture_blueprint.md.<dart_package_dir>/specs/ (e.g. <dart_package_dir>/specs/<module_name>_spec.md) describing the interfaces, types, behaviors, and expected test cases for a single module.<dart_package_dir>/test/ based on the spec (compilation errors targeting missing classes are expected here).
// TEST UTILITIES - KEEP PERMANENTLY. Label temporary stub classes that will be moved to lib/ as // SKELETON STUBS FOR COMPILATION - DELETE ONCE SKELETON IS IMPLEMENTED.<dart_package_dir>/lib/src/ defining all required classes, constructors, methods, and properties, but returning dummy values or throwing .UnimplementedError()dart test and verifies the test compiles successfully and fails on execution due to UnimplementedError or assertion failure, NOT syntax or import errors.
<dart_package_dir>/lib/ to make all tests pass.dart test and verifies the tests pass successfully.<dart_package_dir>/example/ (Treated as Integration Tests) and create the developer-facing skill documentation in <dart_package_dir>/skills/.To preserve strict roles, agents are restricted to write to specific directories:
| Agent Role | Allowed Read Path | Allowed Write Path | Forbidden Actions |
|---|---|---|---|
| Coordinator (Parent) | Anywhere | Anywhere | Direct code modifications (delegates to Coder/Tester instead) |
| Architect | Anywhere | <dart_package_dir>/specs/, skills/ | Cannot write to <dart_package_dir>/lib/, <dart_package_dir>/test/, or <dart_package_dir>/example/ |
| Tester | Anywhere | <dart_package_dir>/test/, <dart_package_dir>/example/ | Cannot write to <dart_package_dir>/lib/ or <dart_package_dir>/specs/ |
| Coder | Anywhere | <dart_package_dir>/lib/, <dart_package_dir>/example/ | Cannot write to <dart_package_dir>/test/ or <dart_package_dir>/specs/ |
Note: The Coordinator is the only agent allowed to execute Git operations or run arbitrary tests in the shell.
git-commit-workflow rules:
Add AgentConfig properties, write unit tests).dynamic unless required by external JSON parsing). Avoid dynamic collections (use generics or shared interface classes).Future for async values and Stream for streaming data (e.g. async event stream).package:test for writing tests. Place tests in <dart_package_dir>/test/ mirroring the structure of <dart_package_dir>/lib/src/.dart format . and dart analyze inside <dart_package_dir>/ before verifying implementations.package:json_serializable or freezed via build_runner for serialization. Avoid writing custom JSON parser logic unless necessary.package:mocktail or package:mockito instead of patching dynamic properties.hasattr), use Dart abstract interface class definitions, or explicit callback delegates to achieve same results type-safely.Iterable<T> (forwarding its iterator to the underlying list) or expose an explicit collection getter (e.g. .transitions, .items) so that Dart's spread operator (...) can be used cleanly in configurations.