wf-flutter-create-screen-method

Scaffold Flutter feature screens with controller and UI separation.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/belluga/delphi-ai --skill wf-flutter-create-screen-method
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wf-flutter-create-screen-method
Source: https://github.com/belluga/delphi-ai/tree/main/skills/wf-flutter-create-screen-method
Command: npx skills add https://github.com/belluga/delphi-ai --skill wf-flutter-create-screen-method

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffold a Flutter feature screen with a dedicated controller (state) and Screen (UI) following the Feature-First architecture.

Core Features & Use Cases

  • Deterministic scaffolding of a feature screen, controller, routes, and feature-first structure.
  • Enforces separation of concerns: controller manages state, screen renders UI, widgets/files organized per feature.
  • Use Case: rapidly create a new screen module for a new feature with consistent architecture across the app.

Quick Start

Use the flutter create-screen-method workflow to scaffold a new feature screen with its controller and route.

Frequently Asked Questions about wf-flutter-create-screen-method

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

FAQPage Schema
How do I scaffold a Flutter screen with separate controller and UI files?

Scaffold a Flutter screen by generating a dedicated controller for state and a Screen widget for UI, placing files deterministically under lib/presentation to enforce feature-first architecture.

What is the feature-first architecture approach for Flutter screen modules?

Feature-first architecture separates concerns by dedicating a controller to manage state and a screen to render UI, organizing widgets and routes per feature module for consistent app structure.

How do I create a new Flutter feature module with standardized routing?

Create a standardized Flutter feature module by generating route, module, and widget scaffolds alongside the screen and controller to ensure consistent navigational routing across features.

Can I use this scaffolding workflow for mobile apps requiring state management?

This scaffolding workflow applies to mobile app development requiring standardized screen modules and state management, generating a canonical project structure with dedicated controller state.

Does the Flutter screen scaffolding enforce a specific project structure?

The scaffolding enforces a canonical project structure by deterministically placing generated files under lib/presentation and separating state management controllers from UI screen widgets.

Why separate the controller from the UI when building Flutter screens?

Separating the controller from the UI enforces separation of concerns, allowing the controller to manage state independently while the screen renders UI for scalable feature modules.