.cursor/skills/spots-philosophy-integration/SKILL.md
--- name: spots-philosophy-integration description: Ensures all code aligns with SPOTS core philosophy: "Doors, not badges", meaningful connections, real-world enhancement. Use when implementing features, reviewing code, or making architectural decisions to validate philosophy alignment. --- # SPOTS Philosophy Integration ## Core Principle **All development must align with SPOTS philosophy.** This is non-negotiable. ## Key Philosophy Concepts ### The Core Truth **"There is no secret to life
npx skillsauth add avra-cadavra/avrai .cursor/skills/spots-philosophy-integrationInstall 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 development must align with SPOTS philosophy. This is non-negotiable.
"There is no secret to life. Just doors that haven't been opened yet."
The entire purpose of SPOTS is to open doors for meaningful connections:
For every feature/implementation, ask:
Not: "recommendations" → Instead: "Doors" Not: "matches" → Instead: "People who open similar doors" Not: "features" → Instead: "Door opening mechanisms" Not: "engagement" → Instead: "Doors opened"
docs/plans/philosophy_implementation/SPOTS_PHILOSOPHY_AND_ARCHITECTURE.md - Core philosophydocs/plans/philosophy_implementation/DOORS.md - Doors conversationOUR_GUTS.md - Original philosophy (updated with doors)✅ GOOD:
// Opens doors to meaningful community connections
class CommunityEventService {
// Service helps users discover events at their favorite spots
// These events are doors to communities
}
❌ BAD:
// Gamified recommendation system
class RecommendationEngine {
// Pushes generic suggestions to increase engagement metrics
// No consideration for meaningful connections
}
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