rule-flutter-flutter-screen-workflow-glob

Name: rule-flutter-flutter-screen-workflow-glob
Availability: InStock
Author: belluga

Enforce Flutter screen workflow governance on screen modifications.

Updated Nov 7, 2025

Search Tags:#architecture #governance #flutter #screen-workflow #subscope

Ready to run

npx skills add https://github.com/belluga/delphi-ai --skill rule-flutter-flutter-screen-workflow-glob

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rule-flutter-flutter-screen-workflow-glob
Source: https://github.com/belluga/delphi-ai/tree/main/skills/rule-flutter-flutter-screen-workflow-glob
Command: npx skills add https://github.com/belluga/delphi-ai --skill rule-flutter-flutter-screen-workflow-glob

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flutter screens in Flutter apps are governed by a Screen Workflow to maintain architecture, ownership, and consistency across the codebase.

Core Features & Use Cases

Enforces Screen Workflow checks on edits to flutter-app/lib/presentation//screens/.
Requires canonical scope/subscope attribution and updates to ModuleScope/GetIt registrations.
Ensures screen documentation updates (screens/*.md) accompany changes.

Quick Start

Review delphi-ai/workflows/flutter/create-screen-method.md and apply the Screen Workflow before editing any Flutter screens.

Frequently Asked Questions about rule-flutter-flutter-screen-workflow-glob

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

FAQPage Schema

How do I enforce the Flutter screen workflow when modifying presentation files?▼

To enforce the Flutter screen workflow, apply governance checks to edits under flutter-app/lib/presentation/**/screens/**, ensuring canonical scope and subscope attribution before changes are accepted.

What is scope and subscope governance in Flutter screen architecture?▼

Scope and subscope governance in Flutter screens requires aligning screen modifications with foundation_documentation/policies/scope_subscope_governance.md to maintain architectural ownership and consistency across the codebase.

Do I need to update GetIt registrations when changing Flutter screens?▼

Yes, changing Flutter screens requires updating ModuleScope and GetIt registrations to ensure dependency injection governance remains consistent with the modified screen architecture.

How do I document Flutter screen changes in my project?▼

Document Flutter screen changes by updating the corresponding screens/*.md file, ensuring screen documentation updates accompany all code modifications to maintain architectural consistency.

What happens if I edit Flutter screens without following the screen workflow?▼

Editing Flutter screens without following the screen workflow bypasses governance checks, risking inconsistent architecture, missing scope attribution, and outdated GetIt registrations and screen documentation.

Can I use the Flutter screen workflow for files outside the presentation directory?▼

No, the Flutter screen workflow specifically targets modifications under flutter-app/lib/presentation/**/screens/**, and does not apply governance checks to files outside this path.