avra-cadavra/async-await-patterns
.cursor/skills/async-await-patterns/SKILL.md
Enforces async/await patterns over .then() chains, proper error handling, mounted checks. Use when writing async code, handling Futures, or working with async operations.
development
Updated Apr 4, 2026
$ install --global
skillsauthnpx skillsauth add avra-cadavra/avrai async-await-patternsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 1:35 AM1.8s1 file scanned
SKILL.md
- name:
- async-await-patterns
- description:
- Enforces async/await patterns over .then() chains, proper error handling, mounted checks. Use when writing async code, handling Futures, or working with async operations.
Async/Await Patterns
Core Rule
✅ ALWAYS use async/await instead of .then() chains
✅ ALWAYS handle errors in async operations (try-catch)
✅ Check mounted before setState() in async callbacks (Flutter widgets)
Basic Pattern
// ✅ GOOD
Future<void> loadData() async {
try {
final data = await repository.fetch();
if (mounted) {
setState(() => _data = data);
}
} catch (e, st) {
developer.log('Failed to load data', error: e, stackTrace: st);
}
}
// ❌ BAD
void loadData() {
repository.fetch().then((data) {
setState(() => _data = data); // Missing mounted check
}).catchError((e) {
// Silent failure
});
}
Error Handling
Always wrap async operations in try-catch:
Future<Result<User>> getUser(String id) async {
try {
final user = await repository.getUser(id);
return Success(user);
} on NetworkException catch (e) {
return Failure('Network error: ${e.message}');
} catch (e, st) {
developer.log('Unexpected error', error: e, stackTrace: st, name: 'UserService');
return Failure('Failed to load user');
}
}
Widget Mounted Checks
Always check mounted before setState() in async callbacks:
class MyWidget extends StatefulWidget {
@override
_MyWidgetState createState() => _MyWidgetState();
}
class _MyWidgetState extends State<MyWidget> {
@override
void initState() {
super.initState();
loadData();
}
Future<void> loadData() async {
try {
final data = await repository.fetch();
if (mounted) { // ✅ Check mounted
setState(() {
_data = data;
});
}
} catch (e, st) {
if (mounted) { // ✅ Check mounted
setState(() {
_error = e.toString();
});
}
}
}
}
Multiple Async Operations
// ✅ GOOD: Sequential with error handling
Future<void> loadAllData() async {
try {
final user = await loadUser();
final settings = await loadSettings();
final preferences = await loadPreferences();
if (mounted) {
setState(() {
_user = user;
_settings = settings;
_preferences = preferences;
});
}
} catch (e, st) {
developer.log('Failed to load data', error: e, stackTrace: st);
}
}
// ✅ GOOD: Parallel with error handling
Future<void> loadAllDataParallel() async {
try {
final results = await Future.wait([
loadUser(),
loadSettings(),
loadPreferences(),
]);
if (mounted) {
setState(() {
_user = results[0];
_settings = results[1];
_preferences = results[2];
});
}
} catch (e, st) {
developer.log('Failed to load data', error: e, stackTrace: st);
}
}
FutureOr Pattern
When method can be sync or async:
FutureOr<String> getData() {
if (_cache != null) {
return _cache!; // Sync return
}
return fetchFromServer(); // Async return
}
Completer Pattern (Rare)
Only use Completer when necessary (prefer async/await):
Future<String> convertCallback() {
final completer = Completer<String>();
someCallbackApi((result) {
completer.complete(result);
});
return completer.future;
}
Anti-Patterns
❌ .then() Chains:
repository.fetch()
.then((data) => processData(data))
.then((processed) => saveData(processed))
.catchError((e) => handleError(e)); // BAD
❌ Missing Error Handling:
Future<void> loadData() async {
final data = await repository.fetch(); // No try-catch - BAD
setState(() => _data = data);
}
❌ Missing Mounted Check:
Future<void> loadData() async {
final data = await repository.fetch();
setState(() => _data = data); // No mounted check - BAD
}
❌ Future.value(null).then():
Future.value(null).then((_) => doSomething()); // Use await instead
Best Practices
- Always use async/await for async operations
- Always wrap async operations in try-catch
- Always check
mountedbeforesetState()in widgets - Use
FutureOr<T>when method can be sync or async - Prefer async/await over Completer when possible
- Use
Future.wait()for parallel operations - Never use
.then()chains in new code
Related Skills
avra-cadavra/.cursor/skills/world-model-development
development
VerifiedTrustedCommunity
--- name: world-model-development description: Guides world model development patterns: state/action encoders, ONNX inference, feature extraction pipeline, latency budgets. Use when implementing world model components, state encoders, action encoders, feature extractors, or ONNX models. Core skill for Phases 3-6. --- # World Model Development Patterns ## Core Principle All world model components follow LeCun's autonomous machine intelligence framework. State observations flow through a percep
SKILL.mdUpdated Apr 4, 2026
avra-cadavra/workflow-controller-pattern
tools
VerifiedTrustedCommunity
Implements base workflow controller patterns for multi-step processes. Use when creating complex workflows that require orchestration of multiple steps with error handling and rollback.
SKILL.mdUpdated Apr 4, 2026
avra-cadavra/.cursor/skills/widget-test-patterns
testing
VerifiedTrustedCommunity
--- name: widget-test-patterns description: Guides widget test patterns: BLoC testing, user interactions, state changes, material app setup. Use when writing widget tests, testing UI components, or validating widget behavior. --- # Widget Test Patterns ## Core Pattern Widget tests verify UI behavior: user interactions, state changes, and visual display. ## Basic Widget Test Setup ```dart testWidgets('widget displays correctly', (WidgetTester tester) async { // Arrange: Create widget awa
SKILL.mdUpdated Apr 4, 2026
avra-cadavra/.cursor/skills/test-template-generation
testing
VerifiedTrustedCommunity
--- name: test-template-generation description: Generates test templates: unit, widget, integration, service tests following project patterns. Use when creating new tests or ensuring tests follow project standards. --- # Test Template Generation ## Available Templates Test templates are located in `test/templates/`: - `unit_test_template.dart` - `widget_test_template.dart` - `integration_test_template.dart` - `service_test_template.dart` ## Unit Test Template ```dart /// SPOTS Component Uni
SKILL.mdUpdated Apr 4, 2026