/flutter-design-system
Enforce Design Language System adherence in Flutter. Use when implementing design tokens, preventing hardcoded colors/spacing, or building a DLS.
$ npx -y skills add hoangnguyen0403/agent-skills-standard --skill flutter-design-system --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/flutter-design-system
Context preview
The summary Claude sees to decide when to auto-load this skill.
Enforce Design Language System adherence in Flutter. Use when implementing design tokens, preventing hardcoded colors/spacing, or building a DLS.
SKILL.md
flutter-design-system.SKILL.mdname: flutter-design-system
description: Enforce Design Language System adherence in Flutter. Use when implementing design tokens, preventing hardcoded colors/spacing, or building a DLS.
metadata:
triggers:
files:
- '**/theme/**'
- '**/*_theme.dart'
- '**/*_colors.dart'
- '**/*_dls/**'
- '**/foundation/**'
- '**/presentation/**'
- '**/ui/**'
- '**/widgets/**'
keywords:
- ThemeData
- ColorScheme
- AppColors
- VColors
- VSpacing
- AppTheme
- design tokenFlutter Design System Enforcement
**Priority: P0 (CRITICAL)**
Zero tolerance for hardcoded design values.
**Phase 0: Context Discovery (MANDATORY)**
Before UI refactoring, identify project's Theme Archetype:
1. **Check `main.dart`**: Look for `MaterialApp` theme configuration. 2. **Determine Pattern**:
- **Theme-Driven (Adaptive)**: `VThemeData(...).toThemeData()` or extensive `ThemeData` overrides → use `Theme.of(context).textTheme` / `theme.textTheme`.
- **Token-Driven (Static)**: Use static tokens (`VTypography.*`) only when no global theme bridge exists, or when defining theme itself.
Guidelines
- **Colors**: Use tokens (`VColors.*`, `AppColors.*`), never `Color(0xFF...)` or `Colors.red`.
- **Spacing**: Use tokens (`VSpacing.*`), never magic numbers like `16` or `24`.
- **Typography**: Prioritize `theme.textTheme.*` for adaptive UI. Use `VTypography.*` tokens only for theme definitions or non-contextual logic. Never use inline `TextStyle`.
- **Borders**: Use tokens (`VBorders.*`), never raw `BorderRadius.`
- **Components**: Use DLS widgets (`VButton`) over raw Material widgets (`ElevatedButton`) if available.
[Detailed Examples](references/usage.md)
Anti-Patterns
- **No Hex Colors**: `Color(0xFF...)` strictly forbidden.
- **No Color Enums**: `Colors.blue` forbidden in UI code.
- **No Magic Spacing**: `SizedBox(height: 10)` forbidden.
- **No Inline Styles**: `TextStyle(fontSize: 14)` forbidden.
- **No Raw Widgets**: Don't use `ElevatedButton` when `VButton` exists.
Related Topics
mobile-ux-core | flutter/widgets | idiomatic-flutter
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
- ElevatedButton
- SizedBox
- VColors
- magic number
- Additional task-grounded exact anchors: TextStyle
Read more
name: flutter-design-system
description: Enforce Design Language System adherence in Flutter. Use when implementing design tokens, preventing hardcoded colors/spacing, or building a DLS.
metadata:
triggers:
files:
- '**/theme/**'
- '**/*_theme.dart'
- '**/*_colors.dart'
- '**/*_dls/**'
- '**/foundation/**'
- '**/presentation/**'
- '**/ui/**'
- '**/widgets/**'
keywords:
- ThemeData
- ColorScheme
- AppColors
- VColors
- VSpacing
- AppTheme
- design tokenFlutter Design System Enforcement
**Priority: P0 (CRITICAL)**
Zero tolerance for hardcoded design values.
**Phase 0: Context Discovery (MANDATORY)**
Before UI refactoring, identify project's Theme Archetype:
1. **Check `main.dart`**: Look for `MaterialApp` theme configuration. 2. **Determine Pattern**:
- **Theme-Driven (Adaptive)**: `VThemeData(...).toThemeData()` or extensive `ThemeData` overrides → use `Theme.of(context).textTheme` / `theme.textTheme`.
- **Token-Driven (Static)**: Use static tokens (`VTypography.*`) only when no global theme bridge exists, or when defining theme itself.
Guidelines
- **Colors**: Use tokens (`VColors.*`, `AppColors.*`), never `Color(0xFF...)` or `Colors.red`.
- **Spacing**: Use tokens (`VSpacing.*`), never magic numbers like `16` or `24`.
- **Typography**: Prioritize `theme.textTheme.*` for adaptive UI. Use `VTypography.*` tokens only for theme definitions or non-contextual logic. Never use inline `TextStyle`.
- **Borders**: Use tokens (`VBorders.*`), never raw `BorderRadius.`
- **Components**: Use DLS widgets (`VButton`) over raw Material widgets (`ElevatedButton`) if available.
[Detailed Examples](references/usage.md)
Anti-Patterns
- **No Hex Colors**: `Color(0xFF...)` strictly forbidden.
- **No Color Enums**: `Colors.blue` forbidden in UI code.
- **No Magic Spacing**: `SizedBox(height: 10)` forbidden.
- **No Inline Styles**: `TextStyle(fontSize: 14)` forbidden.
- **No Raw Widgets**: Don't use `ElevatedButton` when `VButton` exists.
Related Topics
mobile-ux-core | flutter/widgets | idiomatic-flutter
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
- ElevatedButton
- SizedBox
- VColors
- magic number
- Additional task-grounded exact anchors: TextStyle
The portable SDLC standards layer for AI coding agents. Sync once, then work in your own runtime.
Repo: hoangnguyen0403/agent-skills-standard
Other skills on agent-skills-standard.
- /android-agp-upgrade
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
Open skill - /android-architecture
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow
Open skill - /android-background-work
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
Open skill - /android-compose-migration
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
Open skill - /android-compose
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
Open skill - /android-concurrency
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes,
Open skill

