flutter-add-page-workflow

Standardize new Flutter page creation with import rules and navigation checks.

5|3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/ZHLX2005/fr --skill flutter-add-page-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flutter-add-page-workflow
Source: https://github.com/ZHLX2005/fr/tree/main/.claude/skills/flutter-add-page-workflow
Command: npx skills add https://github.com/ZHLX2005/fr --skill flutter-add-page-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating new pages in a Flutter project often suffers from inconsistent folder structures, import paths, and navigation setup, leading to wasted time and integration errors.

Core Features & Use Cases

  • Standardized directory layout: place pages under lib/screens and widgets under lib/widgets to keep code organized.
  • Import path guidance: ensure correct relative imports between screens, widgets, and providers.
  • Safety nets: prevent duplicate page files, validate navigation wiring in HomePage, and enforce commit hygiene.
  • Reusable workflow: apply the same procedure for new modules or nested pages to maintain consistency across the app.

Quick Start

Create a new page under lib/screens, wire it into HomePage navigation, and run flutter analyze to catch path or duplication issues.

Frequently Asked Questions about flutter-add-page-workflow

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

FAQPage Schema
How do I standardize Flutter page creation and fix inconsistent import paths?

Standardize Flutter page creation by placing new screens under lib/screens and widgets under lib/widgets, ensuring correct relative imports between modules. This maintains a consistent directory layout and prevents integration errors across your codebase.

What is the best way to wire a new Flutter page into existing navigation?

Wire Flutter navigation by integrating the new page entry directly into HomePage navigation. This workflow validates the navigation wiring to ensure the new screen routes correctly and prevents duplicate page files during creation.

How do I prevent duplicate Flutter page files when adding new screens?

Prevent duplicate Flutter page files by applying standardized workflow checks during screen creation. The workflow enforces safety nets that detect existing files and validate the project structure before integrating the new page into the app.

Does this Flutter page workflow apply to nested pages and new submodules?

Yes, this Flutter page workflow applies to adding nested pages and new submodules. The reusable procedure maintains structural consistency by enforcing the same directory layout, import rules, and navigation checks across the app.

Why should I run flutter analyze after creating a new Dart page?

Run flutter analyze after creating a new Dart page to catch import path issues and duplication problems. The workflow enforces code analysis and commit hygiene to ensure the new navigation entry integrates cleanly without errors.