ftk-scaffold-feature

Files (1)

• SKILL.md

SKILL.md (first lines)

Add one feature module following the project's existing conventions.

Resolve the toolkit root from `toolkitPath` in `~/.config/flutter-tools-kit/ftk-settings.json`, then read `knowledge/architecture.md` and `knowledge/riverpod-patterns.md` from it.

## Before generating

1. Inspect `lib/features/` for an existing feature and mirror its exact structure, naming, and state-management style. Existing project conventions override FTK defaults.
2. If the project is empty of features, use the layout from `knowledge/architecture.md`.
3. Ask what the feature's first screen and primary data source are (API endpoint, local, none) if not stated.

## Generate

Create under `lib/features/<feature>/`:

- `data/models/` — one model for the primary entity with `fromJson`/`toJson`.
- `data/repositories/<feature>_repository.dart` — repository class with the first fetch method, exposed via a Riverpod provider.
- `presentation/providers/<feature>_provider.dart` — notifier or FutureProvider wired to the repository per `knowledge/riverpod-patterns.md`.
- `presentation/screens/<feature>_screen.dart` — screen consuming the provider with full `AsyncValue.when` handling.
- Register the route in the project's router and add a route-name constant.

Skip `domain/` when the entity equals the DTO; create it when mapping is non-trivial.

## Verify

`flutter analyze` must be clean. Add one unit test for the notifier/repository seam per `knowledge/testing.md` and run it. Report created files and the route path.

From adiwirya/flutter-tools-kit, MIT.

More from adiwirya/flutter-tools-kit