.cursor/skills/meaningful-connections-check/SKILL.md
Ensures features support meaningful connections, not gamification or engagement metrics. Use when implementing features, reviewing UX, or validating that features serve meaningful connections.
npx skillsauth add avra-cadavra/avrai meaningful-connections-checkInstall 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.
Meaningful connections is THE core philosophy (after "Opening Doors").
The entire purpose of SPOTS is to open doors for meaningful connections.
SPOTS opens doors to:
Technology enhances the real world experience, doesn't replace it.
❌ Engagement Optimization:
// BAD: Optimizes for time in app
class EngagementTracker {
void trackTimeSpent() {
// Tracks how long user stays in app
// Violates meaningful connections principle
}
}
✅ Door Opening:
// GOOD: Opens doors to meaningful connections
class CommunityDiscoveryService {
Future<List<Event>> discoverEvents(User user) async {
// Discovers events at user's favorite spots
// Opens doors to communities
// Leads to real-world experiences
}
}
docs/plans/philosophy_implementation/SPOTS_PHILOSOPHY_AND_ARCHITECTURE.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