Claude Code Rules for Flutter — Production-Ready CLAUDE.md

Zero setup

CLAUDE.md ships at the project root — Claude Code reads it on every session automatically.

Architecture-aware

3-layer pattern, Riverpod conventions, folder structure — every rule encoded for the AI.

Yours to extend

Plain Markdown — fork, scope, layer your team conventions on top of the defaults.

They trust us

Why you need AI coding rules

Without explicit rules, AI assistants default to generic Flutter patterns. With them, every suggestion follows your conventions — saving review time, preventing drift, and onboarding both humans and AIs from the same source of truth.

Stop fixing generic code

AI starts from your conventions, not Stack Overflow defaults. Less re-prompting, less rewriting.

Consistency across sessions

Every chat, every developer, every agent — same patterns. No more "which style won today?".

Onboard humans AND agents

New devs read the same file Claude reads. One source of truth, zero docs duplication.

Survives team turnover

Your conventions are codified. They outlive any single contributor and scale with the team.

AI RULES

Rules that ship with your project

A set of rules that sits at the root of every ApparenceKit-generated project. Claude Code reads it on every conversation — the AI inherits the kit's tech stack, architecture, naming conventions, and known gotchas before writing a single line of code. No more generic boilerplate, no more battles to enforce your patterns.

Flutter & Dart

A set of rules that ensure good practices of generated code for Flutter and Dart

Conventions encoded

File naming, layer boundaries, state patterns — the AI follows them by default

Design

Use the kit theme for consistent styling and UI components

Internationalization

Generate localization alongside features

ARCHITECTURE

Aligned with the 3-layer pattern

The rules teach Claude exactly where Data, Domain, and Presentation logic belong. Ask for a new feature and the generated code lands in the right folder, uses the right repository pattern, and exposes a Riverpod notifier shaped like the rest of your codebase. Read more on the architecture template.

Layer boundaries

Claude knows the Data layer talks to APIs, the Domain layer holds business logic, the Presentation layer reads state

Riverpod-first

Generated code uses Riverpod notifiers and providers, never setState spaghetti

Testable by default

Claude scaffolds unit tests alongside features — mock repositories, override providers

Customize all rules and commands for your team

EXTEND

Customize without losing the baseline

Rules and commands are plain Markdown files you own. Add team-specific sections, override defaults, scope rules to subfiles. ApparenceKit ships sane defaults so you don't start from a blank file — but every line is yours to amend.

Plain Markdown

Edit in your IDE, version-control like any other file

Modular sections

Override or extend parts without rewriting the whole file

Team conventions

Add naming, review, and shipping rules on top of the defaults