.cursor/skills/master-plan-notation/SKILL.md
Enforces Master Plan notation format (Phase.Section.Subsection X.Y.Z). Use when referencing phases, sections, documenting progress, or updating status trackers.
npx skillsauth add avra-cadavra/avrai master-plan-notationInstall 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.
✅ ALWAYS use Phase.Section.Subsection (X.Y.Z) format
Phase 8, Section 3, Subsection 2 - Full format8.3.2 - Shorthand format8.3 - Section only (Phase 8, Section 3)8 - Phase only (Phase 8)Phase 1, Section 1, Subsection 1 = 1.1.1
Phase 8, Section 3 = 8.3
Phase 14 = 14
❌ NEVER use:
✅ ALWAYS use:
This format applies to:
✅ GOOD:
## Phase 8.3.2 Completion
Completed Phase 8, Section 3, Subsection 2 (8.3.2).
### Next Steps
Proceeding to Phase 8, Section 4 (8.4).
// TODO(Phase 8.3.2): Implement feature X
// Completed in Phase 8.3.2
❌ BAD:
## Week 3 Completion
Completed week 3 of Phase 8.
docs/MASTER_PLAN.md - Master Plan documentMANDATORY: Never mix old and new formats. Use only Phase.Section.Subsection format consistently throughout all documentation and code.
development
--- 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
tools
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.
testing
--- 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
testing
--- 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