ai-qakit 1.0.0

package/templates/.claude/skills/knowledge-base/knowledge-base.md

@@ -0,0 +1,212 @@
+# Knowledge Base Skill
+
+Skill for managing project knowledge base - capturing, analyzing, and organizing business documentation from multiple sources.
+
+## Overview
+
+The Knowledge Base (KB) system provides:
+- Structured storage for business documentation
+- Multi-source capture (Jira, Confluence, designs, videos)
+- Automatic analysis and rule extraction
+- Conflict detection and resolution
+- Cross-referencing between documents
+
+## Directory Structure
+
+```
+docs/
+├── _index.md              # Master index (auto-generated)
+├── _glossary.md           # Terms & definitions
+├── _sources.json          # Source registry
+├── features/              # Feature documentation
+│   └── {feature-name}.md
+├── flows/                 # Business/user flows
+│   └── {flow-name}.md
+├── rules/                 # Business rules
+│   ├── _shared-rules.md   # Cross-feature rules
+│   └── {domain}-rules.md
+├── assets/                # Media files
+│   ├── screenshots/
+│   ├── designs/
+│   └── videos/
+└── sources/               # Raw source backups
+    └── jira/
+    └── confluence/
+```
+
+## Document Frontmatter Schema
+
+```yaml
+---
+id: feature-id                    # Unique identifier (kebab-case)
+title: Feature Title              # Human-readable title
+type: feature|flow|rule|glossary  # Document type
+status: draft|active|deprecated   # Document status
+sources:                          # Source tracking
+  - type: jira|confluence|design|video|manual
+    id: "LG-4018"
+    url: "https://..."
+    captured: "2024-12-24"
+    hash: "abc123"                # Content hash for change detection
+related:                          # Related documents
+  - "[[other-feature]]"
+  - "[[flow-name]]"
+tags: [tag1, tag2]                # Searchable tags
+created: "2024-12-24"
+updated: "2024-12-24"
+---
+```
+
+## Business Rule Schema
+
+```markdown
+| ID | Rule | Sources | Status | Confidence |
+|----|------|---------|--------|------------|
+| BR-001 | Rule description | LG-4018, PRD-123 | ✅ Active | High (2 sources) |
+| BR-002 | Another rule | LG-4019 | ⚠️ Conflict | - |
+```
+
+### Rule Status Values
+- ✅ Active - Confirmed and in use
+- ⚠️ Conflict - Multiple sources disagree
+- 🔄 Pending - Needs verification
+- ❌ Deprecated - No longer valid
+
+### Confidence Levels
+- High - 2+ sources agree
+- Medium - 1 source, verified
+- Low - 1 source, unverified
+
+## Conflict Detection
+
+When capturing from multiple sources, detect conflicts by:
+
+1. **Semantic similarity** - Rules with >80% similarity
+2. **Keyword matching** - Same entities, different behaviors
+3. **Source freshness** - Newer source may override older
+
+### Conflict Resolution Format
+
+```markdown
+### ⚠️ Conflict: BR-002
+
+**Source 1 (LG-4018, 2024-12-20):**
+> Panel auto-closes after 30 seconds
+
+**Source 2 (PRD-123, 2024-12-15):**
+> Panel stays open until user closes
+
+**Resolution:** [Pending|Resolved]
+**Decision:** Use Source 1 (confirmed with PM on 2024-12-24)
+**Resolved by:** hung.nguyen
+```
+
+## Source Registry (_sources.json)
+
+```json
+{
+  "version": "1.0",
+  "lastUpdated": "2024-12-24T10:00:00Z",
+  "sources": [
+    {
+      "id": "LG-4018",
+      "type": "jira",
+      "url": "https://company.atlassian.net/browse/LG-4018",
+      "title": "Maps Resource Toggle",
+      "captured": "2024-12-24T10:00:00Z",
+      "hash": "abc123def456",
+      "linkedDocs": [
+        "docs/features/maps-resource-toggle.md"
+      ],
+      "extractedRules": ["BR-001", "BR-002"],
+      "status": "active"
+    }
+  ],
+  "conflicts": [
+    {
+      "id": "CONF-001",
+      "rules": ["BR-002"],
+      "sources": ["LG-4018", "PRD-123"],
+      "status": "pending",
+      "created": "2024-12-24"
+    }
+  ]
+}
+```
+
+## Linking Documents
+
+Use wiki-style links for cross-references:
+
+```markdown
+## Related
+- [[feature-name]] - Description
+- [[flows/user-login]] - Login flow
+- [[rules/_shared-rules#BR-001]] - Specific rule
+```
+
+## Capture Workflow
+
+### From Jira
+1. Fetch ticket + subtasks + linked issues
+2. Parse description (ADF format)
+3. Extract acceptance criteria as rules
+4. Identify related features
+5. Check for duplicates/conflicts
+6. Create/update feature doc
+7. Update index and sources
+
+### From Confluence
+1. Fetch page content
+2. Parse HTML/storage format
+3. Extract requirements, rules
+4. Link to existing features
+5. Update sources
+
+### From Design (Image)
+1. Save image to assets/
+2. Analyze UI elements (if AI vision available)
+3. Extract states, components
+4. Link to feature doc
+5. Update sources
+
+### From Video
+1. Save video link/file reference
+2. Add timestamp notes
+3. Extract key moments
+4. Link to feature doc
+
+## Deduplication Strategy
+
+1. **Rule deduplication**
+   - Compare rule text similarity
+   - Merge if >85% similar
+   - Keep all source references
+
+2. **Feature deduplication**
+   - Check by Jira ticket ID
+   - Check by feature name similarity
+   - Prompt user for merge decision
+
+3. **Flow deduplication**
+   - Extract shared flows to separate docs
+   - Reference from multiple features
+
+## Search & Query
+
+Support searching by:
+- Full text search
+- Tags
+- Source type
+- Status
+- Date range
+- Related features
+
+## Integration with Test Generation
+
+When generating tests, KB provides:
+1. Business rules for test scenarios
+2. User flows for E2E tests
+3. UI states from designs
+4. Edge cases from conflicts/discussions
+5. Glossary for consistent terminology

package/templates/.claude/skills/mobile-development/SKILL.md

@@ -0,0 +1,212 @@
+---
+name: mobile-development
+description: "Cross-platform and native mobile development. Frameworks: React Native, Flutter, Swift/SwiftUI, Kotlin/Jetpack Compose. Capabilities: mobile UI, offline-first architecture, push notifications, deep linking, biometrics, app store deployment. Actions: build, create, implement, optimize, test, deploy mobile apps. Keywords: iOS, Android, React Native, Flutter, Swift, Kotlin, mobile app, offline sync, push notification, deep link, biometric auth, App Store, Play Store, iOS HIG, Material Design, battery optimization, memory management, mobile performance. Use when: building mobile apps, implementing mobile-first UX, choosing native vs cross-platform, optimizing battery/memory/network, deploying to app stores, handling mobile-specific features."
+license: MIT
+version: 1.0.0
+---
+
+# Mobile Development Skill
+
+Production-ready mobile development with modern frameworks, best practices, and mobile-first thinking patterns.
+
+## When to Use
+
+- Building mobile applications (iOS, Android, or cross-platform)
+- Implementing mobile-first design and UX patterns
+- Optimizing for mobile constraints (battery, memory, network, small screens)
+- Making native vs cross-platform technology decisions
+- Implementing offline-first architecture and data sync
+- Following platform-specific guidelines (iOS HIG, Material Design)
+- Optimizing mobile app performance and user experience
+- Implementing mobile security and authentication
+- Testing mobile applications (unit, integration, E2E)
+- Deploying to App Store and Google Play
+
+## Technology Selection Guide
+
+**Cross-Platform Frameworks:**
+- **React Native**: JavaScript expertise, web code sharing, mature ecosystem (121K stars, 67% familiarity)
+- **Flutter**: Performance-critical apps, complex animations, fastest-growing (170K stars, 46% adoption)
+
+**Native Development:**
+- **iOS (Swift/SwiftUI)**: Maximum iOS performance, latest features, Apple ecosystem integration
+- **Android (Kotlin/Jetpack Compose)**: Maximum Android performance, Material Design 3, platform optimization
+
+See: `references/mobile-frameworks.md` for detailed framework comparisons
+
+## Mobile Development Mindset
+
+**The 10 Commandments of Mobile Development:**
+
+1. **Performance is Foundation, Not Feature** - 70% abandon apps >3s load time
+2. **Every Kilobyte, Every Millisecond Matters** - Mobile constraints are real
+3. **Offline-First by Default** - Network is unreliable, design for it
+4. **User Context > Developer Environment** - Think real-world usage scenarios
+5. **Platform Awareness Without Platform Lock-In** - Respect platform conventions
+6. **Iterate, Don't Perfect** - Ship, measure, improve cycle is survival
+7. **Security and Accessibility by Design** - Not afterthoughts
+8. **Test on Real Devices** - Simulators lie about performance
+9. **Architecture Scales with Complexity** - Don't over-engineer simple apps
+10. **Continuous Learning is Survival** - Mobile landscape evolves rapidly
+
+See: `references/mobile-mindset.md` for thinking patterns and decision frameworks
+
+## Reference Navigation
+
+**Core Technologies:**
+- `mobile-frameworks.md` - React Native, Flutter, Swift, Kotlin, framework comparison matrices, when to use each
+- `mobile-ios.md` - Swift 6, SwiftUI, iOS architecture patterns, HIG, App Store requirements, platform capabilities
+- `mobile-android.md` - Kotlin, Jetpack Compose, Material Design 3, Play Store, Android-specific features
+
+**Best Practices & Development Mindset:**
+- `mobile-best-practices.md` - Mobile-first design, performance optimization, offline-first architecture, security, testing, accessibility, deployment, analytics
+- `mobile-debugging.md` - Debugging tools, performance profiling, crash analysis, network debugging, platform-specific debugging
+- `mobile-mindset.md` - Thinking patterns, decision frameworks, platform-specific thinking, common pitfalls, debugging strategies
+
+## Key Best Practices (2024-2025)
+
+**Performance Targets:**
+- App launch: <2 seconds (70% abandon if >3s)
+- Memory usage: <100MB for typical screens
+- Network requests: Batch and cache aggressively
+- Battery impact: Respect Doze Mode and background restrictions
+- Animation: 60 FPS (16.67ms per frame)
+
+**Architecture:**
+- MVVM for small-medium apps (clean separation, testable)
+- MVVM + Clean Architecture for large enterprise apps
+- Offline-first with hybrid sync (push + pull)
+- State management: Zustand (React Native), Riverpod 3 (Flutter), StateFlow (Android)
+
+**Security (OWASP Mobile Top 10):**
+- OAuth 2.0 + JWT + Biometrics for authentication
+- Keychain (iOS) / KeyStore (Android) for sensitive data
+- Certificate pinning for network security
+- Never hardcode credentials or API keys
+- Implement proper session management
+
+**Testing Strategy:**
+- Unit tests: 70%+ coverage for business logic
+- Integration tests: Critical user flows
+- E2E tests: Detox (React Native), Appium (cross-platform), XCUITest (iOS), Espresso (Android)
+- Real device testing mandatory before release
+
+**Deployment:**
+- Fastlane for automation across platforms
+- Staged rollouts: Internal → Closed → Open → Production
+- Mandatory: iOS 17 SDK (2024), Android 15 API 35 (Aug 2025)
+- CI/CD saves 20% development time
+
+## Quick Decision Matrix
+
+| Need | Choose |
+|------|--------|
+| JavaScript team, web code sharing | React Native |
+| Performance-critical, complex animations | Flutter |
+| Maximum iOS performance, latest features | Swift/SwiftUI native |
+| Maximum Android performance, Material 3 | Kotlin/Compose native |
+| Rapid prototyping | React Native + Expo |
+| Desktop + mobile | Flutter |
+| Enterprise with JavaScript skills | React Native |
+| Startup with limited resources | Flutter or React Native |
+| Gaming or heavy graphics | Native (Swift/Kotlin) or Unity |
+
+## Framework Quick Comparison (2024-2025)
+
+| Criterion | React Native | Flutter | Swift/SwiftUI | Kotlin/Compose |
+|-----------|--------------|---------|---------------|----------------|
+| **Stars** | 121K | 170K | N/A | N/A |
+| **Adoption** | 35% | 46% | iOS only | Android only |
+| **Performance** | 80-90% native | 85-95% native | 100% native | 100% native |
+| **Dev Speed** | Fast (hot reload) | Very fast (hot reload) | Fast (Xcode Previews) | Fast (Live Edit) |
+| **Learning Curve** | Easy (JavaScript) | Medium (Dart) | Medium (Swift) | Medium (Kotlin) |
+| **UI Paradigm** | Component-based | Widget-based | Declarative | Declarative |
+| **Community** | Huge (npm) | Growing | Apple ecosystem | Android ecosystem |
+| **Best For** | JS teams, web sharing | Performance, animations | iOS-only apps | Android-only apps |
+
+## Implementation Checklist
+
+**Project Setup:**
+- Choose framework → Initialize project → Configure dev environment → Setup version control → Configure CI/CD → Team standards
+
+**Architecture:**
+- Choose pattern (MVVM/Clean) → Setup folders → State management → Navigation → API layer → Error handling → Logging
+
+**Core Features:**
+- Authentication → Data persistence → API integration → Offline sync → Push notifications → Deep linking → Analytics
+
+**UI/UX:**
+- Design system → Platform guidelines → Accessibility → Responsive layouts → Dark mode → Localization → Animations
+
+**Performance:**
+- Image optimization → Lazy loading → Memory profiling → Network optimization → Battery testing → Launch time optimization
+
+**Quality:**
+- Unit tests (70%+) → Integration tests → E2E tests → Accessibility testing → Performance testing → Security audit
+
+**Security:**
+- Secure storage → Authentication flow → Network security → Input validation → Session management → Encryption
+
+**Deployment:**
+- App icons/splash → Screenshots → Store listings → Privacy policy → TestFlight/Internal testing → Staged rollout → Monitoring
+
+## Platform-Specific Guidelines
+
+**iOS (Human Interface Guidelines):**
+- Native navigation patterns (tab bar, navigation bar)
+- iOS design patterns (pull to refresh, swipe actions)
+- San Francisco font, iOS color system
+- Haptic feedback, 3D Touch/Haptic Touch
+- Respect safe areas and notch
+
+**Android (Material Design 3):**
+- Material navigation (bottom nav, navigation drawer)
+- Floating action buttons, material components
+- Roboto font, Material You dynamic colors
+- Touch feedback (ripple effects)
+- Respect system bars and gestures
+
+## Common Pitfalls to Avoid
+
+1. **Testing only on simulators** - Real devices show true performance
+2. **Ignoring platform conventions** - Users expect platform-specific patterns
+3. **No offline handling** - Network failures will happen
+4. **Poor memory management** - Leads to crashes and poor UX
+5. **Hardcoded credentials** - Security vulnerability
+6. **No accessibility** - Excludes 15%+ of users
+7. **Premature optimization** - Optimize based on metrics, not assumptions
+8. **Over-engineering** - Start simple, scale as needed
+9. **Skipping real device testing** - Simulators don't show battery/network issues
+10. **Not respecting battery** - Background processing must be justified
+
+## Performance Budgets
+
+**Recommended Targets:**
+- **App size**: <50MB initial download, <200MB total
+- **Launch time**: <2 seconds to interactive
+- **Screen load**: <1 second for cached data
+- **Network request**: <3 seconds for API calls
+- **Memory**: <100MB for typical screens, <200MB peak
+- **Battery**: <5% drain per hour of active use
+- **Frame rate**: 60 FPS (16.67ms per frame)
+
+## Resources
+
+**Official Documentation:**
+- React Native: https://reactnative.dev/
+- Flutter: https://flutter.dev/
+- iOS HIG: https://developer.apple.com/design/human-interface-guidelines/
+- Material Design: https://m3.material.io/
+- OWASP Mobile: https://owasp.org/www-project-mobile-top-10/
+
+**Tools & Testing:**
+- Detox E2E: https://wix.github.io/Detox/
+- Appium: https://appium.io/
+- Fastlane: https://fastlane.tools/
+- Firebase: https://firebase.google.com/
+
+**Community:**
+- React Native Directory: https://reactnative.directory/
+- Pub.dev (Flutter packages): https://pub.dev/
+- Awesome React Native: https://github.com/jondot/awesome-react-native
+- Awesome Flutter: https://github.com/Solido/awesome-flutter