dart-flutter-patterns

Production-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state management frameworks (BLoC, Riverpod, Provider), GoRouter navigation, Dio networking, Freezed code generation, and clean architecture.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is tdg-personal/dart-flutter-patterns

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, token-efficient catalog of copy-paste Dart/Flutter patterns with clear BAD/GOOD contrasts and no conceptual fluff. Its weaknesses are the absence of any sequenced workflow with validation checkpoints and the lack of progressive disclosure — everything lives in one monolithic file with no supporting reference bundle.

Suggestions

Split large reference blocks (e.g. state management, networking, testing) into one-level-deep files under references/ and link to them from a concise overview, so the SKILL.md body stays a navigable index.

Add a short 'How to apply' workflow for the few multi-step patterns that benefit from validation (e.g. Freezed code generation: run build_runner, then validate generated output), with explicit checkpoints.

Confirm the cross-references at the end (flutter-dart-code-review skill, rules/dart/) point to resources that actually exist, or mark them as optional to avoid dead pointers.

Dimension	Reasoning	Score
Conciseness	Dense, mostly code with terse instructive comments ('BAD — crashes at runtime if null', 'GOOD — provide fallback') and no preamble explaining concepts Claude already knows; the 'How It Works' section is a tight numbered list. Every token earns its place.	3 / 3
Actionability	Provides complete, executable, copy-paste-ready Dart examples across all ten concerns (sealed classes, GoRouter redirect, Dio interceptors, BLoC/Riverpod tests), matching the 'fully executable code, copy-paste ready' anchor.	3 / 3
Workflow Clarity	Content is organized into ten clearly numbered topical sections, but it is a reference catalog rather than a sequenced multi-step workflow, and no validation checkpoints or feedback loops are present (none are strictly required since there are no destructive or batch operations).	2 / 3
Progressive Disclosure	No bundle files exist, and all ten sections are inlined in a single ~560-line SKILL.md with only external URLs and skill/rules pointers in the References section; the file is well-sectioned but content that could be split into one-level-deep reference files is inline.	2 / 3
	Total	10 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-targeted description rich in natural trigger terms and concrete framework names, written in third person. Its main weakness is the absence of an explicit 'Use when...' trigger clause, leaving the 'when to use' guidance implicit.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when starting a new Flutter feature, choosing between BLoC/Riverpod/Provider, or writing idiomatic Dart for null safety, sealed types, or async composition.'

Lead with a verb-led capability statement (e.g. 'Provides production-ready Dart and Flutter patterns for...') to make the action orientation explicit in the first phrase.

Dimension	Reasoning	Score
Specificity	Lists many specific concrete capabilities and frameworks (null safety, BLoC, Riverpod, Provider, GoRouter, Dio, Freezed, clean architecture), matching the 'lists multiple specific concrete actions' anchor rather than the narrower score-2 example.	3 / 3
Completeness	Clearly answers 'what' (production-ready patterns covering enumerated concerns) but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Includes natural terms a user would actually say ('Dart', 'Flutter', 'BLoC', 'Riverpod', 'Provider', 'GoRouter', 'Dio', 'Freezed') with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Highly specific to Dart/Flutter with named ecosystem frameworks, giving it a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (565 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/dart-flutter-patterns/SKILL.md
Commit: 754b8dd

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.