What is feature-screen?

A workflow for adding a new screen or page to a Flutter app, including its navigation route and any needed state. Flutter is a toolkit for building apps from one shared codebase.

Use it to create feature folders, page widgets, routes, asynchronous state, navigation events, and related generated code in the expected project locations.

It gives a new screen the same folder structure, navigation setup, state handling, and code-generation process as the rest of the app.

How strvcom/flutter-template configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to strvcom/flutter-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/strvcom/flutter-template/master/.agents/skills/feature-screen/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/strvcom/flutter-template

Made for: Claude Code.

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/strvcom/flutter-template/feature-screen/github.svg)](https://agentmods.dev/skills/strvcom/flutter-template/feature-screen)

Your own site

<a href="https://agentmods.dev/skills/strvcom/flutter-template/feature-screen"><img src="https://agentmods.dev/badge/skills/strvcom/flutter-template/feature-screen/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/strvcom/flutter-template/feature-screen"><img src="https://agentmods.dev/badge/skills/strvcom/flutter-template/feature-screen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 730 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.00051	$0.00730
Opus 5.5	$0.00020	$0.00292
Sonnet 5.5	$0.00010	$0.00146
Haiku 4.5	$0.00005	$0.00073

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

Security

Grade A, and why

feature-screen 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.

.agents/skills/feature-screen/SKILL.md · 71 lines

How it starts

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

Flutter Template Feature Screen

Use this skill when adding a new screen or route to this repository.

Read First

AGENTS.md
docs/PROJECT_OVERVIEW.md
docs/PROJECT_GUIDELINES.md
lib/app/navigation/app_router.dart

Default Output

Create work inside lib/features/<feature>/.

Prefer this shape when the screen owns state:

lib/features/<feature>/
  <feature>_page.dart
  <feature>_page_content.dart
  <feature>_state.dart
  <feature>_event.dart

For simple static screens, *_state.dart and *_event.dart may be unnecessary.

Workflow

Inspect nearby features with a similar level of complexity.
Create the new feature folder under lib/features/.
Add the route widget with @RoutePage().
Put larger widget trees into *_page_content.dart.
If the screen has async state, create a freezed state plus @riverpod notifier in *_state.dart.
If the screen needs one-off navigation, snackbar, or dialog effects, create a freezed event union in *_event.dart and listen in the page widget.
Register the route in lib/app/navigation/app_router.dart.
Use shared widgets and extensions before adding new abstractions.
If data is needed, add DTOs, entities, and use cases in the shared locations instead of doing IO in widgets.
Check narrow and wide layout behavior for the page content. Use LayoutBuilder for parent constraint-driven layouts, wrap flexible Row content in Expanded/Flexible, and avoid fixed dimensions that can overflow localized text.
Run make gen, then fvm flutter analyze, then relevant tests.

Conventions To Keep

Keep *_page.dart thin.
Prefer CustomAppBar, shared components, and shared compositions.
Use context.colorScheme, context.textTheme, and context.locale.
Use DTOs in lib/common/data/dto/ and entities in lib/common/data/entity/.
Put IO-oriented behavior in lib/common/usecase/.
Use AsyncValueExtension.mapState or mapContentState for async UI.
Do not hand-edit generated files.

Read the full file on GitHub · 71 lines

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 · 71 lines · 51 tokens per session scan A 990a2ba0139b

Subscribe to this mod's changes

feature-screen is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 730 once invoked, about $0.0002 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-30.

Mobile

feature-screen next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
feature-screenstrvcom/flutter-template	Skill	24	4mo ago	MIT	A	51	Claude Code
orca-emulator-androidstablyai/orca	Skill	117k	yesterday	MIT	A	102	Claude Code, Codex
glance-canonical-layoutsandroid/skills	Skill	10k	yesterday	Apache-2.0	A	56	Claude Code
android-tombstone-symbolicationdotnet/skills	Skill	5.8k	yesterday	MIT	A	176	Claude Code
dogfoodcallstack/agent-device	Skill	5.3k	yesterday	MIT	A	55	Claude Code
winapp-mauimicrosoft/winappCli	Skill	1.4k	yesterday	MIT	A	68	Claude Code
app_remixrome-os/rome	Skill	889	yesterday	MIT	A	50	Claude Code, Codex

flutter-template: Skill for Claude Code