flutter-bloc-forms
Manage form state, validation, and input handling through dedicated FormBlocs. Use when building forms with real-time validation, multi-step flows, or complex input patterns like search debouncing.
What this skill does
# Form Architecture with BLoC
- Manage form state in a dedicated `FormBloc` — NOT in widget `setState`
- Each form field maps to a property in the BLoC state
- Validate on field change (real-time) or on submit (batch) depending on UX requirements
- Emit `FormSubmitting`, `FormSuccess`, `FormError` states for submission flow
## Form Events
- `FieldChanged(field, value)` — update a single field in state
- `FormSubmitted` — trigger validation and submission
- `FormReset` — clear all fields and errors
## Form State
- Use a single state class with all field values, field-level errors, and form status:
```dart
sealed class FormStatus { initial, submitting, success, failure }
```
- Field errors: `Map<String, String?>` keyed by field name — `null` means valid
# Validation Patterns
- Validate in the domain layer — NOT in widgets or BLoCs
- Create pure validator functions that return `String?` (null = valid, string = error message):
```dart
String? validateEmail(String value) =>
value.contains('@') ? null : 'Invalid email';
```
- Compose validators: `String? validate(String v) => validateRequired(v) ?? validateEmail(v)`
- Use localized error messages via `context.l10n` — no hardcoded validation strings
# Input Widgets
- Use `TextFormField` with `InputDecoration` for consistent styling
- Always set `textInputAction` for proper keyboard behavior (`next`, `done`)
- Always set `keyboardType` matching the field type (`emailAddress`, `phone`, `number`)
- Use `inputFormatters` to restrict input (e.g., `FilteringTextInputFormatter.digitsOnly`)
- Assign `Key('feature_fieldName')` to every form field for test access
- Use `AutofillHints` for login/signup forms (email, password, name)
- Wrap form fields with `Focus` or `FocusTraversalGroup` for proper tab order
# Controller Lifecycle
- Declare `TextEditingController` as `late final` in `initState()` — dispose in `dispose()`
- Sync controllers to BLoC via `onChanged` callback or controller listener
# Form Submission
- Disable submit button while `FormStatus.submitting` to prevent double-submission
- Show inline field errors below each field — not just a top-level error
- On success: navigate, show success feedback, and reset form if staying on same page
- On failure: show error feedback via `SnackBar` or inline, keep form data intact
# Common Form Patterns
- **Search**: Use `debounce` transformer on search events (300-500ms delay)
- **Multi-step**: Each step is a separate form state within one `FormBloc`, validated independently
- **Dependent fields**: Update dependent field options in `on<FieldChanged>` handler (e.g., country → city)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.