flutter-context

Enforce Flutter project conventions and build pipelines at session start.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/adona9/flutter-dev-team-skills --skill flutter-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flutter-context
Source: https://github.com/adona9/flutter-dev-team-skills/tree/main/flutter-context
Command: npx skills add https://github.com/adona9/flutter-dev-team-skills --skill flutter-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Foundation for Flutter project conventions, establishing a single source of truth for architecture, tooling, and deployment that all skills inherit.

Core Features & Use Cases

  • Central project constitution defining framework, stack, directory layout, and build pipeline
  • Enforces project naming conventions, approved packages, and a deterministic session start
  • Integrates with flutter-architect, ui-builder, test-writer, and pr-review to align workflows

Quick Start

Load this skill at the start of any Flutter session to apply project conventions.

Frequently Asked Questions about flutter-context

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

FAQPage Schema
How do I enforce consistent Flutter project conventions across a development team?

You can establish a central project constitution that defines a fixed directory layout, approved packages, and naming conventions. This creates a single source of truth for Flutter architecture, tooling, and deployment that your team inherits.

What is the best way to standardize Flutter routing and state management across features?

Standardizing Flutter routing and state management requires enforcing a go_router and riverpod-based setup. By defining this in your project constitution, you ensure all feature scaffolding and architecture tasks use the approved routing configuration.

How do I set up a deterministic Flutter session start for continuous integration?

A deterministic Flutter session start is set up by applying a central project constitution at the beginning of each session. This enforces fixed directory layouts, approved packages, and consistent build pipelines before architecture or deployment tasks begin.

Can I use my preferred packages and custom directory layout with a Flutter project constitution?

No, a Flutter project constitution enforces a fixed directory layout and a specific set of approved packages like riverpod and go_router. Deviating from these approved packages and naming conventions breaks the single source of truth.

When do I need to apply a Flutter project constitution during development?

You need to apply a Flutter project constitution at the start of any Flutter session and during tasks like architecture, feature scaffolding, UI, testing, code review, and iOS deployment to ensure workflows align with project conventions.