.cursor/skills/documentation-refactoring-protocol/SKILL.md
--- name: documentation-refactoring-protocol description: Enforces documentation refactoring protocol: phase folders, status tracker updates, proper file placement, naming conventions. Use when creating documentation, organizing docs, or updating documentation structure. --- # Documentation Refactoring Protocol ## Mandatory Protocol **ALL agents MUST follow the Documentation Refactoring Protocol when creating or organizing documentation.** ## Folder Structure ### Phase-Specific Docs ``` doc
npx skillsauth add avra-cadavra/avrai .cursor/skills/documentation-refactoring-protocolInstall 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.
ALL agents MUST follow the Documentation Refactoring Protocol when creating or organizing documentation.
docs/agents/
├── prompts/[phase]/ # Phase-specific prompts
├── tasks/[phase]/ # Phase-specific tasks
└── reports/agent_X/[phase]/ # Agent reports by phase
docs/agents/
├── status/
│ └── status_tracker.md # SINGLE file for all phases
├── protocols/ # Shared protocols
└── reference/ # Shared references
prompts/ and tasks/status/status_tracker.md) with new phase sectionsstatus/, protocols/, reference/docs/ root (e.g., docs/PHASE_3_TASKS.md)docs/agents/prompts/[phase]/ - Prompts for specific phasedocs/agents/tasks/[phase]/ - Tasks for specific phasedocs/agents/reports/agent_X/[phase]/ - Reports by agent and phasedocs/agents/status/status_tracker.md - Status for all phasesdocs/agents/protocols/ - Protocols shared across phasesdocs/agents/reference/ - Reference docs shared across phasesUse SINGLE status tracker file:
# Status Tracker
## Phase 1: MVP Core Functionality
- [ ] Task 1
- [x] Task 2
## Phase 2: Post-MVP Enhancements
- [ ] Task 1
❌ DON'T create: status/phase_1_status.md, status/phase_2_status.md
docs/agents/REFACTORING_PROTOCOL.md - Complete protocol documentationdevelopment
--- 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