.cursor/skills/doors-philosophy-validation/SKILL.md
Validates that features align with "opening doors" concept, meaningful connections, user journey flow. Use when implementing features, reviewing code, or ensuring features serve the doors philosophy.
npx skillsauth add avra-cadavra/avrai doors-philosophy-validationInstall 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.
For every feature, ask these questions:
/// Event Discovery Service
///
/// Opens doors to community events at user's favorite spots.
/// Users discover events → attend events → find communities → find their people.
class EventDiscoveryService {
// Helps users discover events (doors to communities)
// Adapts to user's door history
// Works offline
// Respects privacy
}
/// Engagement Optimizer
///
/// Increases app usage and time in app.
class EngagementOptimizer {
// Focuses on metrics, not doors
// Doesn't open doors to meaningful connections
// Violates "doors, not badges" philosophy
}
Ensure features support the journey:
Find YOUR Spots (Doors)
↓
Those spots have communities
↓
Those communities have events
↓
You find YOUR people
↓
You find YOUR life
docs/plans/philosophy_implementation/SPOTS_PHILOSOPHY_AND_ARCHITECTURE.mddocs/plans/philosophy_implementation/DOORS.mddevelopment
--- 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