@smicolon/ai-kit 0.3.2 → 0.4.0

package/packs/dev-loop/skills/tdd-planner/references/good-example.md

@@ -1,260 +0,0 @@
-# Good Plan Example: Flutter Riverpod Migration
-
-This is a reference example of a well-structured dev-loop plan. Use this as a quality benchmark when generating plans.
-
----
-
-## What Makes This Plan Good
-
-1. **Specific Context** - Lists exact providers to migrate, not just "migrate to Riverpod"
-2. **Measurable Criteria** - "81+ tests", "No Provider imports remain"
-3. **File Paths** - Every task mentions exact file paths
-4. **Code Snippets** - Shows actual implementation structure
-5. **Expected Behavior** - "should FAIL (providers don't exist yet)"
-6. **Tables** - Files to Modify + New Files to Create
-7. **Framework-Specific** - Uses Flutter/Dart patterns correctly
-8. **Stuck Handling** - Specific to Riverpod, not generic
-
----
-
-## The Plan
-
-```markdown
-# Dev Loop Plan: Migrate to Riverpod State Management
-
-## Context
-- **Framework**: Flutter
-- **Current State Management**: Provider with ChangeNotifierProvider
-- **Test Command**: `flutter test`
-- **Lint Command**: `flutter analyze`
-- **Providers to Migrate**:
-  - `AppStateProvider` (settings, prayer reminders)
-  - `NetworkService` (connectivity status)
-  - `SyncService` (cloud sync status)
-
-## Success Criteria
-- [ ] All existing tests pass (81+ tests)
-- [ ] `flutter analyze` shows no issues
-- [ ] App starts correctly with ProviderScope
-- [ ] Settings load and persist correctly
-- [ ] Network status updates reactively
-- [ ] Sync status updates reactively
-- [ ] No Provider imports remain (clean migration)
-
----
-
-## Phase 1: Red - Setup and Infrastructure Tests
-
-**Goal:** Add Riverpod dependency and write failing tests for core providers
-
-**Tasks:**
-- [ ] Add `flutter_riverpod` to pubspec.yaml
-- [ ] Run `flutter pub get`
-- [ ] Create `test/providers/app_state_provider_test.dart` with failing tests
-- [ ] Create `test/providers/network_provider_test.dart` with failing tests
-
-**Verification:** `flutter test test/providers/` should FAIL (providers don't exist yet)
-
-**Expected Output:** Test failures because Riverpod providers not implemented
-
-**Self-correction:** If tests pass, they are not testing the right thing - add assertions
-
----
-
-## Phase 2: Green - Implement Core Providers
-
-**Goal:** Create Riverpod providers that pass the tests
-
-**Tasks:**
-- [ ] Create `lib/providers/app_state_provider.dart` with StateNotifierProvider
-- [ ] Create `lib/providers/network_provider.dart` with StateNotifierProvider
-- [ ] Create `lib/providers/sync_provider.dart` with StateNotifierProvider
-- [ ] Create `lib/providers/providers.dart` barrel file
-
-**Provider Structure:**
-```dart
-// App State
-final appStateProvider = StateNotifierProvider<AppStateNotifier, AppState>((ref) {
-  return AppStateNotifier();
-});
-
-// Network
-final networkProvider = StateNotifierProvider<NetworkNotifier, NetworkState>((ref) {
-  return NetworkNotifier();
-});
-
-// Sync (depends on network)
-final syncProvider = StateNotifierProvider<SyncNotifier, SyncState>((ref) {
-  final network = ref.watch(networkProvider);
-  return SyncNotifier(isOnline: network.isOnline);
-});
-```
-
-**Verification:** `flutter test test/providers/` should PASS
-
-**Self-correction:** If tests still fail, check state classes match expected structure
-
----
-
-## Phase 3: Red - Widget Migration Tests
-
-**Goal:** Write failing tests for widget provider consumption
-
-**Tasks:**
-- [ ] Update `test/widget_test.dart` to use ProviderScope
-- [ ] Add test for PrayerTimesScreen with Riverpod
-- [ ] Add test for OfflineIndicator with network provider
-
-**Verification:** `flutter test test/widget_test.dart` should FAIL
-
-**Self-correction:** Ensure test wraps widgets in ProviderScope
-
----
-
-## Phase 4: Green - Migrate main.dart and Widgets
-
-**Goal:** Replace MultiProvider with ProviderScope and migrate widgets
-
-**Tasks:**
-- [ ] Update `lib/main.dart`:
-  - Replace `MultiProvider` with `ProviderScope`
-  - Remove old Provider imports
-  - Add Riverpod imports
-- [ ] Migrate `lib/screens/prayer_times_screen.dart`:
-  - Change to ConsumerStatefulWidget
-  - Replace `context.watch<>` with `ref.watch()`
-  - Replace `context.read<>` with `ref.read()`
-- [ ] Migrate `lib/widgets/offline_indicator.dart`:
-  - Replace Provider consumption with Riverpod
-- [ ] Migrate `lib/screens/notification_settings_screen.dart`:
-  - Replace Provider consumption with Riverpod
-
-**Verification:** `flutter test` should PASS
-
-**Self-correction:** If widget tests fail, verify ConsumerWidget/ConsumerStatefulWidget usage
-
----
-
-## Phase 5: Refactor - Clean Up Old Provider Code
-
-**Goal:** Remove old Provider code and ensure clean architecture
-
-**Tasks:**
-- [ ] Delete or rename old `lib/services/app_state_provider.dart`
-- [ ] Remove `provider` package from pubspec.yaml (if no longer needed)
-- [ ] Update all remaining imports
-- [ ] Run `flutter analyze` to catch any issues
-- [ ] Update CLAUDE.md documentation
-
-**Verification:**
-```bash
-flutter analyze && flutter test
-```
-
-**Self-correction:** If analyze shows errors, fix import paths
-
----
-
-## Phase 6: Integration Testing
-
-**Goal:** Verify full app works end-to-end
-
-**Tasks:**
-- [ ] Run app on simulator/device
-- [ ] Verify settings load correctly
-- [ ] Verify offline indicator works
-- [ ] Verify sync status updates
-- [ ] Verify prayer times screen works
-- [ ] Test hot reload works
-
-**Verification:** Manual testing + all automated tests pass
-
-**Self-correction:** If app crashes, check initialization order in main.dart
-
----
-
-## Final Verification
-
-```bash
-flutter analyze && flutter test
-```
-
-**Expected Results:**
-- `flutter analyze`: No issues found!
-- `flutter test`: All tests passed!
-
----
-
-## Completion
-
-When all criteria met: <promise>DONE</promise>
-
----
-
-## Stuck Handling
-
-### If same test keeps failing:
-1. Read the exact error message
-2. Check if state class matches test expectations
-3. Verify ref.watch vs ref.read usage
-4. Check ProviderScope is at root
-
-### If app won't start:
-1. Check ProviderScope wraps entire app
-2. Verify no circular dependencies in providers
-3. Check async initialization is handled
-
-### If hot reload breaks:
-1. ConsumerStatefulWidget may need widget rebuild
-2. Check provider isn't being disposed incorrectly
-
-### Alternative approaches if blocked:
-1. Keep hybrid approach (both Provider and Riverpod) temporarily
-2. Migrate one screen at a time
-3. Use ChangeNotifierProvider adapter in Riverpod for gradual migration
-
----
-
-## Files to Modify
-
-| File | Action |
-|------|--------|
-| `pubspec.yaml` | Add flutter_riverpod |
-| `lib/main.dart` | Replace MultiProvider with ProviderScope |
-| `lib/services/app_state_provider.dart` | Migrate to Riverpod or delete |
-| `lib/services/network_service.dart` | Keep service, add Riverpod wrapper |
-| `lib/services/sync_service.dart` | Keep service, add Riverpod wrapper |
-| `lib/screens/prayer_times_screen.dart` | Use ConsumerStatefulWidget |
-| `lib/widgets/offline_indicator.dart` | Use Consumer/ConsumerWidget |
-| `lib/screens/notification_settings_screen.dart` | Use Consumer/ConsumerWidget |
-| `test/widget_test.dart` | Wrap in ProviderScope |
-
----
-
-## New Files to Create
-
-| File | Purpose |
-|------|---------|
-| `lib/providers/providers.dart` | Barrel file for all providers |
-| `lib/providers/app_state_provider.dart` | Riverpod app state |
-| `lib/providers/network_provider.dart` | Riverpod network state |
-| `lib/providers/sync_provider.dart` | Riverpod sync state |
-| `test/providers/app_state_provider_test.dart` | Provider tests |
-| `test/providers/network_provider_test.dart` | Provider tests |
-```
-
----
-
-## Checklist for Quality Plans
-
-Use this checklist when reviewing generated plans:
-
-- [ ] **Context** lists specific items to work on (not just "the feature")
-- [ ] **Success Criteria** are measurable (numbers, specific behaviors)
-- [ ] **Every task** has a file path
-- [ ] **Code snippets** show implementation structure
-- [ ] **Verification** has expected output (PASS/FAIL + why)
-- [ ] **Self-correction** is phase-specific, not generic
-- [ ] **Files to Modify** table exists
-- [ ] **New Files to Create** table exists
-- [ ] **Stuck Handling** is framework/task-specific

package/packs/dev-loop/skills/tdd-planner/references/plan-template.md

@@ -1,275 +0,0 @@
-# Dev Loop Plan Template
-
-Use this template when generating dev-loop plans. Every section is **required** unless marked optional.
-
----
-
-## Quality Checklist
-
-Before saving a plan, verify:
-
-- [ ] Context lists **specific items** to work on (not just "the feature")
-- [ ] Success criteria are **measurable** (numbers, specific behaviors)
-- [ ] **Every task** has a file path
-- [ ] **Code snippets** show implementation structure
-- [ ] Verification has **expected output** (PASS/FAIL + why)
-- [ ] Self-correction is **phase-specific**, not generic
-- [ ] **Files to Modify** table exists
-- [ ] **New Files to Create** table exists
-- [ ] Stuck handling is **framework/task-specific**
-
----
-
-## Template
-
-```markdown
-# Dev Loop Plan: {{GOAL}}
-
-Generated: {{TIMESTAMP}}
-
----
-
-## Context
-
-- **Framework**: {{FRAMEWORK}}
-- **Current State**: {{CURRENT_STATE}} (e.g., "Provider with ChangeNotifierProvider")
-- **Test Command**: `{{TEST_COMMAND}}`
-- **Lint Command**: `{{LINT_COMMAND}}`
-- **Coverage Command**: `{{COVERAGE_COMMAND}}` (optional)
-- **Items to Work On**:
-{{#WORK_ITEMS}}
-  - `{{ITEM_NAME}}` ({{ITEM_DESCRIPTION}})
-{{/WORK_ITEMS}}
-
----
-
-## Success Criteria
-
-All of the following must be true:
-
-{{#SUCCESS_CRITERIA}}
-- [ ] {{CRITERION}}
-{{/SUCCESS_CRITERIA}}
-- [ ] All tests pass (`{{TEST_COMMAND}}`)
-- [ ] Linter clean (`{{LINT_COMMAND}}`)
-
----
-
-## Acceptance Criteria (Optional but Recommended)
-
-User-facing behaviors to verify:
-
-{{#ACCEPTANCE_CRITERIA}}
-### {{AC_NUMBER}}. {{AC_TITLE}}
-- **Given**: {{GIVEN}}
-- **When**: {{WHEN}}
-- **Then**: {{THEN}}
-{{/ACCEPTANCE_CRITERIA}}
-
----
-
-## Files to Modify
-
-| File | Action |
-|------|--------|
-{{#FILES_TO_MODIFY}}
-| `{{FILE_PATH}}` | {{ACTION}} |
-{{/FILES_TO_MODIFY}}
-
----
-
-## New Files to Create
-
-| File | Purpose |
-|------|---------|
-{{#NEW_FILES}}
-| `{{FILE_PATH}}` | {{PURPOSE}} |
-{{/NEW_FILES}}
-
----
-
-## Progress Tracking
-
-**IMPORTANT:** After completing each task, update this file by checking the box:
-- Change `- [ ]` to `- [x]` for completed tasks
-- This tracks progress across iterations and prevents redoing work
-
----
-
-## Phases
-
-{{#PHASES}}
-
-### Phase {{PHASE_NUMBER}}: {{PHASE_TYPE}} - {{COMPONENT}}
-
-**Goal:** {{PHASE_GOAL}}
-
-**Tasks:**
-{{#TASKS}}
-- [ ] {{TASK_DESCRIPTION}}
-  {{#TASK_DETAILS}}
-  - {{DETAIL}}
-  {{/TASK_DETAILS}}
-{{/TASKS}}
-
-**Implementation Structure:** (include code snippet for Green phases)
-```{{LANGUAGE}}
-{{CODE_SNIPPET}}
-```
-
-**Verification:**
-```bash
-{{VERIFICATION_COMMAND}}
-```
-**Expected:** {{EXPECTED_RESULT}}
-
-**Self-correction:**
-- {{PHASE_SPECIFIC_CORRECTION}}
-
-{{/PHASES}}
-
----
-
-## Final Verification
-
-```bash
-{{FINAL_VERIFICATION}}
-```
-
-**Expected Results:**
-{{#FINAL_EXPECTATIONS}}
-- `{{COMMAND}}`: {{EXPECTATION}}
-{{/FINAL_EXPECTATIONS}}
-
----
-
-## Completion
-
-When ALL criteria met: <promise>DONE</promise>
-
----
-
-## Stuck Handling
-
-### If same test keeps failing:
-{{#STUCK_TEST_TIPS}}
-1. {{TIP}}
-{{/STUCK_TEST_TIPS}}
-
-### If app/server won't start:
-{{#STUCK_START_TIPS}}
-1. {{TIP}}
-{{/STUCK_START_TIPS}}
-
-### Alternative approaches if blocked:
-{{#ALTERNATIVE_APPROACHES}}
-1. {{APPROACH}}
-{{/ALTERNATIVE_APPROACHES}}
-
----
-
-## Rollback Strategy (Optional)
-
-If migration/feature fails completely:
-1. {{ROLLBACK_STEP_1}}
-2. {{ROLLBACK_STEP_2}}
-
----
-
-## Dependencies & Prerequisites
-
-{{#DEPENDENCIES}}
-- {{DEPENDENCY}}: {{VERSION_OR_NOTES}}
-{{/DEPENDENCIES}}
-
----
-
-## Notes
-
-{{ADDITIONAL_NOTES}}
-```
-
----
-
-## Example: Populated Template
-
-See `references/good-example.md` for a complete, high-quality example.
-
----
-
-## Variable Reference
-
-### Required Variables
-
-| Variable | Description | Example |
-|----------|-------------|---------|
-| `{{GOAL}}` | High-level objective | "Migrate to Riverpod State Management" |
-| `{{FRAMEWORK}}` | Detected framework | "Flutter", "Django 5.0", "Next.js 14" |
-| `{{CURRENT_STATE}}` | What exists now | "Provider with ChangeNotifierProvider" |
-| `{{TEST_COMMAND}}` | Test runner command | "flutter test", "pytest" |
-| `{{LINT_COMMAND}}` | Linter command | "flutter analyze", "ruff check ." |
-| `{{WORK_ITEMS}}` | Specific items to work on | List of components, providers, endpoints |
-| `{{FILES_TO_MODIFY}}` | Existing files to change | Table with file paths and actions |
-| `{{NEW_FILES}}` | Files to create | Table with file paths and purposes |
-
-### Phase Variables
-
-| Variable | Description | Example |
-|----------|-------------|---------|
-| `{{PHASE_TYPE}}` | Red, Green, or Refactor | "Red", "Green", "Refactor" |
-| `{{COMPONENT}}` | What's being built | "Core Providers", "Widget Migration" |
-| `{{CODE_SNIPPET}}` | Implementation structure | Actual code showing pattern |
-| `{{EXPECTED_RESULT}}` | What success looks like | "should FAIL (providers don't exist yet)" |
-| `{{PHASE_SPECIFIC_CORRECTION}}` | Phase-specific stuck handling | "If tests pass, they're not testing the right thing" |
-
-### Task Detail Pattern
-
-Tasks should include file paths and specifics:
-
-**Bad:**
-```markdown
-- [ ] Create login view
-```
-
-**Good:**
-```markdown
-- [ ] Create `lib/screens/login_screen.dart`:
-  - ConsumerStatefulWidget
-  - Form with email/password fields
-  - Calls `ref.read(authProvider.notifier).login()`
-  - Navigates to home on success
-```
-
----
-
-## Framework-Specific Patterns
-
-### Flutter
-- Use `ConsumerWidget` / `ConsumerStatefulWidget`
-- Wrap app in `ProviderScope`
-- Test with `ProviderScope` in tests
-
-### Django
-- Use absolute imports (`import users.models as _models`)
-- UUID primary keys on all models
-- Service layer for business logic
-
-### Next.js
-- Use `"use client"` directive for client components
-- TanStack Query for data fetching
-- Zod schemas for validation
-
-### NestJS
-- Barrel exports (`index.ts` in each folder)
-- Absolute imports from `src/`
-- DTOs with class-validator
-
----
-
-## Anti-Patterns to Avoid
-
-1. **Vague tasks**: "Implement the feature" (no file paths)
-2. **Generic self-correction**: "If it fails, try again" (not specific)
-3. **Missing code snippets**: No structure shown for implementation
-4. **No file tables**: Unclear what files are affected
-5. **Unmeasurable criteria**: "App works well" (how do you verify?)

package/packs/django/CHANGELOG.md

@@ -1,39 +0,0 @@
-# Changelog
-
-All notable changes to the smi-django plugin will be documented in this file.
-
-## [Unreleased]
-
-### Changed
-- Renamed from `smi-django` to `django` as part of ai-kit migration
-- Moved from `plugins/smi-django/` to `packs/django/`
-
-## [2.1.0] - 2025-01-02
-
-### Added
-- 8 auto-enforcing skills for convention compliance
-  - `import-convention-enforcer` - Absolute modular imports
-  - `model-entity-validator` - UUID, timestamps, soft delete
-  - `security-first-validator` - Permissions, authentication
-  - `test-coverage-advisor` - 90%+ coverage guidance
-  - `performance-optimizer` - N+1 detection
-  - `migration-safety-checker` - Safe migrations
-  - `test-validity-checker` - Test quality
-  - `red-phase-verifier` - TDD red phase
-
-## [2.0.0] - 2024-12-01
-
-### Changed
-- BREAKING: Renamed `@django-dev` to `@django-builder`
-- Updated import conventions to use module aliases
-
-### Added
-- `@django-feature-based` agent for large-scale architecture
-- `/api-endpoint` command
-
-## [1.0.0] - 2024-10-01
-
-### Added
-- Initial stable release
-- 5 agents: architect, builder, feature-based, tester, reviewer
-- 3 commands: model-create, api-endpoint, test-generate

package/packs/django/README.md

@@ -1,92 +0,0 @@
-# Django Development Standards Plugin
-
-Smicolon company standards for Django projects.
-
-## Installation
-
-```bash
-# Add Smicolon marketplace
-/plugin marketplace add https://github.com/smicolon/ai-kit
-
-# Install Django plugin
-/plugin install django
-```
-
-## What's Included
-
-### 5 Specialized Agents
-
-- `@django-architect` - System architecture design and planning
-- `@django-builder` - Feature implementation with best practices
-- `@django-feature-based` - Large-scale feature-based architecture
-- `@django-tester` - Test writing (90%+ coverage target)
-- `@django-reviewer` - Security and code review
-
-### 8 Auto-Enforcing Skills
-
-Skills automatically activate based on context - no manual invocation needed:
-
-**Core Validators:**
-- `import-convention-enforcer` - Auto-fixes import patterns to use absolute modular imports
-- `model-entity-validator` - Auto-enforces BaseModel inheritance (UUID, timestamps, soft delete)
-- `security-first-validator` - Auto-checks API endpoints for security requirements (permissions, validation)
-
-**Quality Enforcers:**
-- `test-coverage-advisor` - Auto-suggests missing tests to achieve 90%+ coverage
-- `performance-optimizer` - Auto-detects N+1 queries and suggests optimizations
-- `migration-safety-checker` - Auto-validates migrations are production-safe (no data loss)
-
-**TDD Helpers:**
-- `test-validity-checker` - Validates tests are meaningful and not trivial
-- `red-phase-verifier` - Ensures tests fail before implementation (TDD red phase)
-
-**How Skills Work:**
-- Auto-invoke based on what you're doing (writing models, creating APIs, etc.)
-- Proactively fix violations without being asked
-- Explain WHY conventions exist
-- Block unsafe operations (insecure endpoints, data-loss migrations)
-
-### Automatic Convention Enforcement
-
-Skills automatically enforce:
-
-**Import Pattern:**
-```python
-# CORRECT - Absolute modular imports with aliases
-import users.models as _users_models
-import users.services as _users_services
-
-user = _users_models.User.objects.get(id=user_id)
-
-# WRONG - Never use
-from .models import User
-from users.models import User
-```
-
-**Model Standards:**
-- UUID primary keys
-- Timestamps (created_at, updated_at)
-- Soft deletes (is_deleted)
-- Service layer for business logic
-- Type hints required
-- Permission classes on all views
-
-## Usage
-
-```bash
-# Start with architecture
-@django-architect "Design a payment processing system"
-
-# Implement features
-@django-builder "Implement payment processing"
-
-# Write tests
-@django-tester "Write tests for payment system"
-
-# Review for security
-@django-reviewer "Review payment code for security issues"
-```
-
-## Documentation
-
-See the main [Smicolon Claude Infra repository](https://github.com/smicolon/ai-kit) for complete documentation.