Review Flutter class organization in Claude Code

Apply DiaryUploader conventions for one public class per file, Dart names, import order, and public API documentation.

Install in Claude Code

A Flutter workspace in Claude Code with the project conventions, class responsibilities, and current references.

Review `.claude/skills/flutter-style/SKILL.md` and its requirements at the pinned GitHub commit.
Create `.claude/skills/flutter-style/` in your project and save the reviewed file as `.claude/skills/flutter-style/SKILL.md`.
Start Claude Code from that project's root, then select `/flutter-style` in the slash menu.

Example task

A fictional Dart file defines two public classes, ScheduleItem and ScheduleBlock. The fixture is `{module:'models',classes:['ScheduleItem','ScheduleBlock'],sharedExport:'models'}`. Keep the current shared export.

What to check

Create `[schedule_item.dart, schedule_block.dart]` and export both through models. Keep the public class names, add Dart documentation comments for public APIs, and check references.

Original SKILL.md on GitHub · Updated 2026-11-14

Frequently asked question

How should I organize multiple public classes in one Flutter file?

Use separate snake_case files organized by responsibility and preserve class names. Reuse the project's barrel export, then check references and public documentation comments.