llms.txt is an open proposal for a short Markdown file that lists a project's key docs and links, so AI tools can find them without crawling every page.

Where should llms.txt be deployed?

At /llms.txt on your documentation site, or in your repository root. Tools read it when they fetch it; nothing loads it automatically.

# Flutter 3 & Riverpod Architecture Specialist

> Modern Flutter 3 and Riverpod 3 conventions. Enforces sound null safety, pattern matching, const widget constructors, and immutable state.

## Quick Reference

- **Framework**: Flutter 3.x

- **Language**: Dart 3.x (Null-Safe)

- **Styling & UI**: Material 3 / Cupertino

- **Database / Persistence**: Isar / SQLite / REST

- **Architectural Philosophy**: strict

## Core Architectural Invariants

- **Clean Layered Architecture**: Decouple presentation, business logic, and data access layers via interfaces.

- **Guard Clauses & Early Returns**: Exit early from functions to eliminate deeply nested if-else pyramids.

- **Self-Documenting Naming**: Expressive function and variable names over verbose redundant comments.

## Operational Guardrails & Prohibited Patterns

- **Inspect Before Acting**: Always read and understand existing code and imports before suggesting changes.

- **Minimal Surgical Diffs**: Touch only lines relevant to prompt. Preserve existing comments and formatting.

- **Propose Verification Steps**: With every modification, specify concrete commands or tests to verify correctness.

## Mandatory Project Directives

- Separate UI presentation widgets from business repositories and HTTP clients.

- Never use raw StatefulWidget with mutable setState in shared business logic.

## Implementation Reference

### Preferred Patterns

```ts

@immutable

sealed class ViewState<T> { const ViewState(); }

class Loading<T> extends ViewState<T> { const Loading(); }

class Success<T> extends ViewState<T> { final T data; const Success(this.data); }

class ProfileView extends ConsumerWidget {

const ProfileView({super.key});

@override

Widget build(BuildContext context, WidgetRef ref) {

final state = ref.watch(profileProvider);

return Scaffold(

body: switch (state) {

Loading() => const Center(child: CircularProgressIndicator.adaptive()),

Success(:final data) => Center(child: Text('Welcome, ${data.name}')),

);

}

```

### Discouraged Anti-Patterns

```ts

class _BadProfileState extends State<BadProfile> {

var user;

void load() async { user = await fetchUser(); setState(() {}); }

@override

Widget build(BuildContext context) { return Container(child: Text(user!.name)); }

}

```

## Verification Commands & Workflows

1. Always use const constructors on immutable widgets to short-circuit Flutter rebuilds.

2. Manage reactive state with Riverpod 3 code generation (@riverpod, Notifier/AsyncNotifier); StateNotifierProvider and StateProvider are legacy. Check ref.mounted after await before touching state.

3. Leverage Dart 3 pattern matching and sealed classes for exhaustive UI state switching.

4. Enforce strict null safety: ban force-unwrap operator (!) without preceding guard checks.

## Context Documents & Specs

- [System Architecture](ARCHITECTURE.md): Authoritative system design, data flows, and state machine invariants.

- [AI Multi-Agent Spec](AGENTS.md): Universal specification for autonomous coding agent operations.

Frontend · Any LLM tool that fetches it

Flutter 3 & Riverpod / Dart llms.txt

An llms.txt for a Flutter 3 & Riverpod / Dart project: a short Markdown map of what it is and where the key docs and code live.

Path: llms.txt
Loads: Fetched on request
Format: Markdown index (.txt)
Used by: Any LLM tool that fetches it

All llms.txt presets and how llms.txt works

What this file tells the agent

An llms.txt gives language models and agents a short Markdown map of your Flutter 3 & Riverpod / Dart project: what it is and where the key docs and code live, so a tool that fetches it can go straight to the right files.

Always add const constructors wherever possible to maximize Flutter element rebuild caching.
Use Riverpod 3 with code generation (@riverpod, Notifier/AsyncNotifier) or BLoC; ban raw mutable setState() in business logic.
Leverage Dart 3 pattern matching and sealed classes for exhaustive state and error representation.
Enforce sound null safety: avoid force-unwrapping with ! unless proven non-null by a preceding guard clause.
Separate presentation UI widgets from asynchronous repository and API service layers.

Code to avoid, and what to write instead

The rule steers the agent away from the left and toward the right.

avoid

// Discouraged: Mutable setState with force-unwrap and missing const
class BadProfile extends StatefulWidget {
  @override
  _BadProfileState createState() => _BadProfileState();
}
class _BadProfileState extends State<BadProfile> {
  var user;
  void load() async {
    user = await fetchUser();
    setState(() {});
  }
  @override
  Widget build(BuildContext context) {
    return Container(child: Text(user!.name)); // Runtime crash if null!
  }
}

write instead

import 'package:flutter/material.dart';
import 'package:flutter_riverpod/flutter_riverpod.dart';

@immutable
sealed class ViewState<T> {
  const ViewState();
}
class Loading<T> extends ViewState<T> { const Loading(); }
class Success<T> extends ViewState<T> { final T data; const Success(this.data); }
class Failure<T> extends ViewState<T> { final String message; const Failure(this.message); }

class ProfileView extends ConsumerWidget {
  const ProfileView({super.key});

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    final state = ref.watch(profileProvider);
    return Scaffold(
      appBar: AppBar(title: const Text('Profile')),
      body: switch (state) {
        Loading() => const Center(child: CircularProgressIndicator.adaptive()),
        Success(:final data) => Center(child: Text('Welcome, ${data.name}')),
        Failure(:final message) => Center(child: Text('Error: $message')),
      },
    );
  }
}

Install it in one command

01
Go to your project root
The file goes at llms.txt, relative to the root.
02
Download the file
Run the command on the right. It downloads this preset and writes the file.
03
Make sure it gets used
Nothing loads llms.txt automatically. Serve it at your site root, or point agents to it from CLAUDE.md or AGENTS.md.

$ curl -fsSL "https://www.devscratchpad.tech/api/raw/llms-txt/flutter-dart" -o "llms.txt"

writes llms.txt

path

llms.txt

To write the file from your own code instead, use Read your code or Convert Legacy Rules in the editor above.

More for Flutter 3 & Riverpod / Dart

Other formats

Other llms.txt presets

Questions

What is llms.txt?: llms.txt is an open proposal for a short Markdown file that lists a project's key docs and links, so AI tools can find them without crawling every page.
Where should llms.txt be deployed?: At /llms.txt on your documentation site, or in your repository root. Tools read it when they fetch it; nothing loads it automatically.

Target Standard & File Format

Identity & Activation Rules

Technology Stack Context

Engineering Philosophy

Architectural & Code Quality Conventions

Agent Behavioral Guardrails

Step-by-Step Workflow Procedures

Target File Location