skills/flutter/flutter-design-system/SKILL.md
Enforce Design Language System adherence in Flutter. Use when implementing design tokens, preventing hardcoded colors/spacing, or building a DLS.
npx skillsauth add hoangnguyen0403/agent-skills-standard flutter-design-systemInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Zero tolerance for hardcoded design values.
Before UI refactoring, identify project's Theme Archetype:
main.dart: Look for MaterialApp theme configuration.VThemeData(...).toThemeData() or extensive ThemeData overrides → use Theme.of(context).textTheme / theme.textTheme.VTypography.*) only when no global theme bridge exists, or when defining theme itself.VColors.*, AppColors.*), never Color(0xFF...) or Colors.red.VSpacing.*), never magic numbers like 16 or 24.theme.textTheme.* for adaptive UI. Use VTypography.* tokens only for theme definitions or non-contextual logic. Never use inline TextStyle.VBorders.*), never raw BorderRadius.VButton) over raw Material widgets (ElevatedButton) if available.Detailed Examples
Color(0xFF...) strictly forbidden.Colors.blue forbidden in UI code.SizedBox(height: 10) forbidden.TextStyle(fontSize: 14) forbidden.ElevatedButton when VButton exists.mobile-ux-core | flutter/widgets | idiomatic-flutter
development
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
development
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
development
Implements a strict Red-Green-Refactor loop to ensure zero production code is written without a prior failing test. Use when: creating new features, fixing bugs, or expanding test coverage.
testing
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.