What is flutter-layered-architecture-design-patterns?

A set of Flutter architecture patterns for separating application actions, called use cases, from data access, called repositories. Flutter is a toolkit for building apps, and Dart is the language commonly used with it.

Use it when adding or changing a Flutter use case or repository, defining Request and Result types, connecting them with Riverpod, or separating interfaces from implementations.

It gives new use cases and repositories consistent interfaces, names, inputs, and outputs. It also helps avoid circular dependencies between these layers.

flutter-layered-architecture-design-patterns

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add eaglesakura/agent-skills --skill flutter-layered-architecture-design-patterns

Clone the repo

git clone --depth 1 https://github.com/eaglesakura/agent-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/eaglesakura/agent-skills/flutter-layered-architecture-design-patterns/github.svg)](https://agentmods.dev/skills/eaglesakura/agent-skills/flutter-layered-architecture-design-patterns)

Your own site

<a href="https://agentmods.dev/skills/eaglesakura/agent-skills/flutter-layered-architecture-design-patterns"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/flutter-layered-architecture-design-patterns/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/eaglesakura/agent-skills/flutter-layered-architecture-design-patterns"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/flutter-layered-architecture-design-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 194 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,155 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00194	$0.01155
Opus 5.5	$0.00078	$0.00462
Sonnet 5.5	$0.00039	$0.00231
Haiku 4.5	$0.00019	$0.00115

Measured 2mo ago against content hash d2d4ab2fe914, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

flutter-layered-architecture-design-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/flutter/.apm/skills/flutter-layered-architecture-design-patterns/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Flutter-Layered-Architecture / デザインパターン

Usecase 層・Data（Repository）層の 定番実装パターン を適用する。レイヤー全体の地図は flutter-layered-architecture-design、本 SKILL はパターン詳細。

いつ使うか

Usecase / Repository のインターフェース・実装を新規作成・改修するとき
Request / Result（必要なら sealed Request）の形を決めるとき
Repository と Usecase の相互依存を設計するとき

いつ使わないか

どのレイヤーに置くかだけ → flutter-layered-architecture-design
画面 MVVM の実装手順 → flutter-layered-architecture-screen-mvvm
既存コードの所在調査 → flutter-layered-architecture-code-search
extension type / コメント規約など言語面だけ → flutter-coding-rules

作業手順

対象が Usecase か Repository かを決める
下の原則で IF / 命名 / Request・Result を決める
詳細は対応する references/ だけ読む
Riverpod の Provider.dependencies でクラス循環を避ける

Usecase パターン（要約）

1 インターフェース = 1 機能。メソッドは原則 execute() のみ（他名は例外扱い）
命名は新規 {動詞}{カテゴリ}Usecase（例: SearchKanjiUsecase）
入出力は Request / Result。複数引数パターンは sealed Request
ステートレス（状態は Repository / Datasource 側）
interface と実装は別 package。Riverpod Provider で結線

詳細 → references/usecase-pattern.md

Repository パターン（要約）

名称は {機能グループ名}Repository
同一機能グループなら複数メソッド可（Usecase の 1 機能原則とは違う）
Read/Write・監視（watch / Stream）を窓口として抽象化してよい
入出力は Request / Result を基本とする
interface / 実装は別 package。注入は DataInjection 等で一元化することが多い

詳細 → references/repository-pattern.md

Repository ↔ Usecase の依存

usecase と data は同レベルのため、相互のインターフェース依存は可
クラス循環は不可。Provider.dependencies を把握して組む
実装 package 同士の密結合や、公開 IF への SDK リークを避ける

追加ドキュメント

参照	使うとき
usecase-pattern.md	Usecase IF・実装・Request/Result・package internal Usecase
repository-pattern.md	Repository IF・実装・監視・命名・テスト差し替え

ナレッジベース

DO: Usecase は細かく切る、Repository は機能グループでまとめる

Usecase を肥大化させず、Repository にデータ操作を寄せすぎない／散らしすぎないバランスを取る
Repository / 画面の Delegate 共通処理は package internal Usecase に切る（Delegate in Delegate 禁止）

DO: 公開面は interface、詳細は実装 package

Read the full file on GitHub · 87 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 87 lines · 194 tokens per session scan A d2d4ab2fe914

Subscribe to this mod's changes

flutter-layered-architecture-design-patterns is a skill published in the GitHub repository eaglesakura/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 194 tokens to every session and 1,155 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Mobile

flutter-layered-architecture-design-patterns next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
flutter-layered-architecture-design-patternseaglesakura/agent-skills	Skill	2	1mo ago	MIT	A	194	Claude Code, Codex
orca-emulator-androidstablyai/orca	Skill	118k	today	MIT	A	102	Claude Code, Codex
glance-canonical-layoutsandroid/skills	Skill	10k	2d ago	Apache-2.0	A	56	Claude Code
android-tombstone-symbolicationdotnet/skills	Skill	5.8k	today	MIT	A	176	Claude Code
dogfoodcallstack/agent-device	Skill	5.3k	today	MIT	A	55	Claude Code
winapp-mauimicrosoft/winappCli	Skill	1.4k	today	MIT	A	68	Claude Code
app_remixrome-os/rome	Skill	894	today	MIT	A	50	Claude Code, Codex