rule-flutter-flutter-contract-alignment-always-on

Name: rule-flutter-flutter-contract-alignment-always-on
Availability: InStock
Author: belluga

Align Flutter DTOs with domain entities and update documentation.

Updated Nov 7, 2025

Search Tags:#architecture #documentation #alignment #flutter #contracts #domain-entities

Ready to run

npx skills add https://github.com/belluga/delphi-ai --skill rule-flutter-flutter-contract-alignment-always-on

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rule-flutter-flutter-contract-alignment-always-on
Source: https://github.com/belluga/delphi-ai/tree/main/.cline/skills/rule-flutter-flutter-contract-alignment-always-on
Command: npx skills add https://github.com/belluga/delphi-ai --skill rule-flutter-flutter-contract-alignment-always-on

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Rule MUST keep Flutter contracts in sync with domain entities and downstream teams to prevent drift between models, DTOs, and canonical docs.

Core Features & Use Cases

Ensure bidirectional alignment between Flutter DTOs/models and domain entities in foundation documentation.
Preserve repository/DAO transport boundaries in docs and implementation, and propagate changes via system roadmaps.
Log and synchronize changes in foundation_documentation and module docs when Flutter schemas or endpoints are modified, so backend teams can plan API updates.

Quick Start

Ensure Flutter DTO updates trigger corresponding domain-entity mappings and documentation changes.

Frequently Asked Questions about rule-flutter-flutter-contract-alignment-always-on

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I align Flutter DTOs with domain entities to prevent model drift?▼

Align Flutter DTOs with domain entities by updating foundation_documentation/domain_entities.md and module docs to maintain consistent DTO-to-entity mappings. This prevents drift between models and canonical docs when repository schemas change.

What happens to documentation when Flutter endpoint changes affect domain contracts?▼

When Flutter endpoint changes affect domain contracts, update system_roadmap.md and module docs to log modifications. This synchronizes foundation documentation so backend teams can plan necessary API updates.

How do I keep Flutter contract mappings synced with foundation documentation?▼

Keep Flutter contract mappings synced by ensuring DTO updates trigger corresponding domain-entity mappings within foundation_documentation. This bidirectional alignment preserves repository transport boundaries across docs and implementation.

When should I update domain entities for Flutter pagination updates?▼

Update domain entities for Flutter pagination updates whenever repositories introduce DTO changes or new endpoints. Modify foundation_documentation/domain_entities.md to reflect these changes and maintain consistent downstream mappings.

Does aligning Flutter contracts require updating the system roadmap?▼

Aligning Flutter contracts requires updating system_roadmap.md to propagate changes. This ensures backend teams can plan API updates when Flutter schemas or endpoints are modified.

What is the best way to prevent drift between Flutter DTOs and downstream teams?▼

Prevent drift between Flutter DTOs and downstream teams by maintaining bidirectional alignment with domain entities in foundation documentation. Log and synchronize schema changes via system roadmaps to keep backend teams informed.