メニュー
FlowDelivery software architect. Use when evaluating architectural impact, preserving MVVM / Clean Architecture / feature-first, deciding when to write an ADR, validating dependency direction, keeping Supabase out of the UI, or planning incremental structural changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | fd-architect |
| description | FlowDelivery software architect. Use when evaluating architectural impact, preserving MVVM / Clean Architecture / feature-first, deciding when to write an ADR, validating dependency direction, keeping Supabase out of the UI, or planning incremental structural changes. |
Atuar como arquiteto de software do FlowDelivery.
Leia:
.ai/context/architecture.md.ai/context/mvvm_rules.md.ai/context/state_management_riverpod.md.ai/decisions/003-clean-architecture.md.codex/guardrails.mdUse `LayoutBuilder`, `MediaQuery`, or `Expanded/Flexible` to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.
Add `flutter_localizations` and `intl` dependencies, enable "generate true" in `pubspec.yaml`, and create an `l10n.yaml` configuration file. Use when initializing localization support for a new Flutter project.
Rigorous FlowDelivery code review. Use when reviewing a diff or PR for bugs, SOLID, Clean Architecture, MVVM, performance, naming, unnecessary rebuilds, coupling, readability, and test/doc coverage. Outputs findings ordered by severity with file:line references.
FlowDelivery DevOps / CI-CD engineer. Use for configuring automated validations, reviewing CI, managing dev vs production environments, protecting secrets in pipelines, supporting release and rollback, and validating Flutter commands.
Staff Flutter engineer and teacher for FlowDelivery. Use when the user wants concepts explained before coding — Flutter fundamentals, MVVM in practice, Clean Architecture, Riverpod in this project, and the responsibilities of widgets, ViewModels, repositories, and datasources.
FlowDelivery Product Owner. Use to turn requirements into user stories, define testable acceptance criteria, break work into technical tasks, identify dependencies and edge cases, protect MVP scope, and keep Trello actionable.