/flutter-security
Secure Flutter token/PII storage, build-time secrets, network trust, and release hardening using OWASP Mobile practices. Use for secure storage, secret injection, certificate pinning, jailbreak/root risk, or release builds—not generic form validation, API error handling,
$ npx -y skills add hoangnguyen0403/agent-skills-standard --skill flutter-security --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-security
Context preview
The summary Claude sees to decide when to auto-load this skill.
Secure Flutter token/PII storage, build-time secrets, network trust, and release hardening using OWASP Mobile practices. Use for secure storage, secret injection, certificate pinning, jailbreak/root risk, or release builds—not generic form validation, API error handling,
SKILL.md
flutter-security.SKILL.mdname: flutter-security
description: Secure Flutter token/PII storage, build-time secrets, network trust, and release hardening using OWASP Mobile practices. Use for secure storage, secret injection, certificate pinning, jailbreak/root risk, or release builds—not generic form validation, API error handling, auth-provider setup, or tests of existing security services.
metadata:
triggers:
files:
- 'lib/infrastructure/**'
- 'pubspec.yaml'
keywords:
- secure_storage
- obfuscate
- jailbreak
- pinning
- PII
- OWASPMobile Security
**Priority: P0 (CRITICAL)**
Implementation Workflow
1. **Store secrets securely** — Use `flutter_secure_storage` for tokens/PII. Never use `shared_preferences` for sensitive data. 2. **Externalize secrets** — Never store API keys in Dart code. Use `--dart-define` or `.env` files. 3. **Obfuscate releases** — Build `--obfuscate --split-debug-info=./symbols`. Deterrent only — move sensitive logic to backend. 4. **Pin certificates** — `dio_certificate_pinning` for high-security apps to prevent MITM. 5. **Root detection** — `flutter_jailbreak_detection` for root/jailbreak checks in financial/sensitive apps. 6. **Mask PII** — Redact PII (email, phone) from all logs and analytics.
Secure Storage & Release Build Examples
See [implementation examples](references/implementation.md) for secure storage usage and obfuscated release build commands.
Reference & Examples
SSL Pinning & Secure Storage: [references/REFERENCE.md](references/REFERENCE.md).
Anti-Patterns
- **No Secrets in SharedPreferences**: Use `flutter_secure_storage` for tokens and PII
- **No Hardcoded API Keys**: Use `--dart-define` or secure vaults for all secrets
- **No Unobfuscated Releases**: Always build with `--obfuscate --split-debug-info`
- **No PII in Logs**: Mask or omit sensitive data from all logs and analytics events
Related Topics
common/security-standards | layer-based-clean-architecture | performance
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
- certificate pinning,SSL pinning
Remediation anchors
- Remediation anchors: root/jailbreak detection, --obfuscate, --split-debug-info
Read more
name: flutter-security
description: Secure Flutter token/PII storage, build-time secrets, network trust, and release hardening using OWASP Mobile practices. Use for secure storage, secret injection, certificate pinning, jailbreak/root risk, or release builds—not generic form validation, API error handling, auth-provider setup, or tests of existing security services.
metadata:
triggers:
files:
- 'lib/infrastructure/**'
- 'pubspec.yaml'
keywords:
- secure_storage
- obfuscate
- jailbreak
- pinning
- PII
- OWASPMobile Security
**Priority: P0 (CRITICAL)**
Implementation Workflow
1. **Store secrets securely** — Use `flutter_secure_storage` for tokens/PII. Never use `shared_preferences` for sensitive data. 2. **Externalize secrets** — Never store API keys in Dart code. Use `--dart-define` or `.env` files. 3. **Obfuscate releases** — Build `--obfuscate --split-debug-info=./symbols`. Deterrent only — move sensitive logic to backend. 4. **Pin certificates** — `dio_certificate_pinning` for high-security apps to prevent MITM. 5. **Root detection** — `flutter_jailbreak_detection` for root/jailbreak checks in financial/sensitive apps. 6. **Mask PII** — Redact PII (email, phone) from all logs and analytics.
Secure Storage & Release Build Examples
See [implementation examples](references/implementation.md) for secure storage usage and obfuscated release build commands.
Reference & Examples
SSL Pinning & Secure Storage: [references/REFERENCE.md](references/REFERENCE.md).
Anti-Patterns
- **No Secrets in SharedPreferences**: Use `flutter_secure_storage` for tokens and PII
- **No Hardcoded API Keys**: Use `--dart-define` or secure vaults for all secrets
- **No Unobfuscated Releases**: Always build with `--obfuscate --split-debug-info`
- **No PII in Logs**: Mask or omit sensitive data from all logs and analytics events
Related Topics
common/security-standards | layer-based-clean-architecture | performance
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
- certificate pinning,SSL pinning
Remediation anchors
- Remediation anchors: root/jailbreak detection, --obfuscate, --split-debug-info
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

