dart-flutter-patterns

Production-ready Dart and Flutter patterns covering null safety, immutable state with Freezed, async composition, widget architecture, state management (BLoC, Riverpod, Provider), GoRouter navigation with auth guards, Dio networking, error handling, and testing. Use when writing or reviewing Dart and Flutter code — state, widgets, navigation, networking, or architecture.

Quality

89%

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

Quality

Content

78%Weight 40%Scale 1-5

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

A strong, code-first pattern catalog: concrete and copy-paste-ready across all nine concerns with no wasted conceptual explanation. The main weaknesses are duplicated examples in the opening Examples section and a monolithic single-file layout with two in-bundle references that don't resolve in this skill's directory.

Suggestions

Split the per-concern sections (state management, navigation, networking, testing) into one-level-deep reference files under references/ and keep SKILL.md as an indexed overview, which would also shrink the token cost of loading the skill.

Remove or correct the pointers to "Skill: flutter-dart-code-review" and "Rules: rules/dart/" — neither exists in this bundle, so they currently lead nowhere.

Drop the duplicate GoRouter and cartTotal snippets from the Examples section (they repeat sections 6–7 nearly verbatim) and delete the filler "Practical, production-ready patterns..." line between the horizontal rules.

Dimension	Reasoning	Score
Conciseness	The body is code-dominant with terse BAD/GOOD comments and assumes Claude's competence, but the Examples section duplicates the GoRouter and cartTotal snippets already shown in sections 6–7, and the stray "Practical, production-ready patterns..." line between dividers is filler that could be trimmed. This fits the 'efficient with minor instances to trim' anchor rather than the lean anchor at 5 or the noticeably-verbose anchor at 3.	4 / 5
Actionability	Every section provides copy-paste-ready Dart — sealed-state hierarchies with exhaustive switches, a Freezed model with copyWith/fromJson, a Cubit with error handling, Riverpod notifiers and derived providers, a Dio interceptor with a one-time token-refresh retry guard, and blocTest/widget-test scaffolds. The examples cover the common cases concretely, matching the 'fully executable, copy-paste ready' anchor.	5 / 5
Workflow Clarity	The content is well-sequenced for a reference catalog — 'When to Use' → 'How It Works' numbered map of the nine concerns → per-concern sections → References — and each pattern is unambiguous. No validation checkpoints are needed since nothing here is a destructive or batch operation, but there is no explicit selection workflow (e.g., choosing between BLoC and Riverpod), leaving minor gaps against the anchor-5 checklist standard.	4 / 5
Progressive Disclosure	Roughly 550 lines of per-concern patterns are inlined in SKILL.md that would fit naturally in one-level-deep reference files (e.g., references/state-management.md), and the References section points to a "Skill: flutter-dart-code-review" and "Rules: rules/dart/" that do not exist in this bundle (references/, scripts/, assets/ are absent). Structure via numbered section headers is good, but the inlining volume and unresolvable in-bundle pointers place this at the 'could be better organized' anchor rather than the well-split anchor at 4.	3 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

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

The description is a model example: it enumerates concrete capabilities with specific packages, provides an explicit third-person 'Use when' trigger clause with the natural phrases users say, and occupies a distinct Dart/Flutter niche. No vague fluff, over-claims, or padding are present.

Dimension	Reasoning	Score
Specificity	"Production-ready Dart and Flutter patterns covering null safety, immutable state with Freezed, async composition, widget architecture, state management (BLoC, Riverpod, Provider), GoRouter navigation with auth guards, Dio networking, error handling, and testing" lists ten concrete capability areas with named packages, matching the comprehensive-coverage anchor rather than the 'several actions, minor gaps' anchor at 4.	5 / 5
Completeness	The first sentence explicitly answers 'what' (production-ready patterns across ten named concerns) and "Use when writing or reviewing Dart and Flutter code — state, widgets, navigation, networking, or architecture" explicitly answers 'when' with concrete trigger phrases, mirroring the anchor-5 example structure.	5 / 5
Trigger Term Quality	Natural terms a Flutter developer would actually say — "Dart and Flutter", "state", "widgets", "navigation", "networking", "architecture", "writing or reviewing" — plus ecosystem synonyms (BLoC, Riverpod, Provider, GoRouter, Dio, Freezed). This matches the comprehensive-synonyms anchor; no common variation is missing.	5 / 5
Distinctiveness Conflict Risk	"Dart and Flutter patterns" with named ecosystem packages carves a clear niche; only a generic Dart code-review skill could plausibly overlap, and the 'writing or reviewing' trigger with package names keeps conflict risk minimal.	5 / 5
	Total	20 / 20 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: c70874f

Reviewed: 1 day 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.