kiro-kit 0.1.0

package/dist/presets/mobile/skills/frontend-design/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: frontend-design
+description: Create distinctive, production-grade mobile interfaces with high design quality. Use when building screens, widgets, or components that need polished visual design.
+---
+
+# Frontend Design
+
+Activate this skill when creating mobile UI that requires high visual quality and design thinking.
+
+## When to Use
+
+- Building new screens or features that need visual design decisions
+- Creating widget libraries or design systems
+- Implementing responsive layouts for multiple form factors
+- Designing interactive elements with proper states and transitions
+- Reviewing existing UI for design improvements
+
+## Design Principles
+
+- Platform-native feel (iOS HIG, Material Design 3)
+- Visual hierarchy through typography, spacing, and color
+- Consistent spacing using 4px/8px grid system
+- Purposeful use of whitespace for readability
+- Progressive disclosure of complex information
+- Accessible color contrast (WCAG 2.1 AA minimum)
+
+## Implementation Guidelines
+
+- Use platform-native components as foundation
+- Implement proper focus states for accessibility
+- Add hover/press states for interactive elements
+- Use platform-appropriate transitions (300ms max)
+- Respect reduced motion preferences
+- Test across screen sizes before considering complete
+
+## Quality Standards
+
+- Minimum 44pt touch targets
+- 4.5:1 contrast ratio for normal text
+- 3:1 contrast ratio for large text and UI elements
+- Support dark mode and dynamic type
+- Never use color as sole indicator of state

package/dist/presets/mobile/skills/frontend-development/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: frontend-development
+description: Build mobile UI with Flutter widgets or React Native components following platform conventions. Use when implementing screens, layouts, or interactive features.
+---
+
+# Frontend Development
+
+Activate this skill when implementing mobile UI components and screens.
+
+## When to Use
+
+- Building new screens or features
+- Implementing complex layouts and animations
+- Creating reusable widget/component libraries
+- Integrating UI with state management
+- Implementing platform-adaptive interfaces
+
+## Flutter UI Development
+
+- Use Material 3 or Cupertino widgets based on platform
+- Implement responsive layouts with LayoutBuilder/MediaQuery
+- Use CustomScrollView with slivers for complex scrolling
+- Implement Hero animations for screen transitions
+- Use AnimatedBuilder for custom animations
+- Keep widget trees shallow (extract sub-widgets)
+
+## React Native UI Development
+
+- Use platform-adaptive components
+- Implement responsive layouts with Dimensions/useWindowDimensions
+- Use FlatList/SectionList for performant lists
+- Implement Reanimated for smooth animations
+- Use StyleSheet.create for optimized styles
+
+## Quality Standards
+
+- All UI must handle loading, error, and empty states
+- Responsive across phone and tablet form factors
+- Support both portrait and landscape orientations
+- Keyboard avoidance for input screens
+- Proper safe area handling (notches, home indicators)
+- Smooth scrolling at 60fps

package/dist/presets/mobile/skills/mcp-builder/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: mcp-builder
+description: Guide for creating MCP (Model Context Protocol) servers that enable LLMs to interact with external services. Use when building MCP server integrations.
+---
+
+# MCP Builder
+
+Activate this skill when building MCP servers to integrate external APIs or services.
+
+## When to Use
+
+- Creating new MCP server integrations
+- Exposing mobile development tools via MCP
+- Building custom tool servers for Flutter/Dart tooling
+- Integrating device management or emulator control
+
+## Process
+
+1. Define the tools the server should expose
+2. Choose implementation language (TypeScript or Python)
+3. Implement tool handlers with proper input validation
+4. Add error handling and timeout management
+5. Document tool schemas and usage
+6. Test with MCP inspector
+
+## Rules
+
+- Tools must have clear, descriptive names
+- Input schemas must validate all parameters
+- Errors must be informative and actionable
+- Keep tool count focused (5-15 per server)
+- Document environment variables required

package/dist/presets/mobile/skills/mcp-management/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: mcp-management
+description: Manage MCP servers -- discover, analyze, and execute tools from configured servers. Use when working with MCP integrations or discovering available capabilities.
+---
+
+# MCP Management
+
+Activate this skill when managing or using MCP server integrations.
+
+## When to Use
+
+- Discovering available MCP capabilities
+- Configuring MCP servers for the project
+- Troubleshooting MCP connection issues
+- Filtering MCP tools for specific tasks
+- Managing multi-server configurations
+
+## Process
+
+1. List configured servers from mcp.json
+2. Verify server availability and health
+3. Discover available tools per server
+4. Execute tools with proper parameters
+5. Handle errors and timeouts gracefully
+
+## Rules
+
+- Always verify server is running before tool calls
+- Document required environment variables
+- Keep mcp.json organized and commented
+- Never commit actual API keys in mcp.json
+- Test tool availability before relying on it

package/dist/presets/mobile/skills/media-processing/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: media-processing
+description: Process multimedia files with FFmpeg and ImageMagick. Use when converting formats, optimizing assets, generating thumbnails, or preparing media for mobile apps.
+---
+
+# Media Processing
+
+Activate this skill when processing images, video, or audio assets for mobile applications.
+
+## When to Use
+
+- Generating app icons at multiple densities
+- Optimizing images for mobile (compression, format conversion)
+- Creating splash screen assets
+- Processing video for in-app playback
+- Generating thumbnails and previews
+- Converting between image formats (PNG, WebP, AVIF)
+
+## Image Processing (ImageMagick)
+
+- Resize for density buckets (1x, 2x, 3x / mdpi, hdpi, xhdpi, xxhdpi)
+- Convert to WebP for smaller file sizes
+- Generate adaptive icon layers (foreground, background)
+- Batch process asset directories
+
+## Video Processing (FFmpeg)
+
+- Transcode for mobile playback (H.264, HEVC)
+- Generate video thumbnails
+- Compress for bandwidth efficiency
+- Extract audio tracks
+
+## Mobile Asset Guidelines
+
+- iOS: @1x, @2x, @3x in asset catalogs
+- Android: mdpi (1x), hdpi (1.5x), xhdpi (2x), xxhdpi (3x), xxxhdpi (4x)
+- Flutter: 1.0x, 2.0x, 3.0x, 4.0x in assets directory
+- Prefer vector (SVG) where possible for resolution independence

package/dist/presets/mobile/skills/mobile-development/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: mobile-development
+description: Build mobile applications with Flutter and React Native. Use when implementing screens, widgets, navigation, platform-specific features, or optimizing for mobile constraints.
+---
+
+# Mobile Development
+
+Activate this skill when building mobile applications with Flutter or React Native.
+
+## When to Use
+
+- Implementing new screens or widgets
+- Setting up navigation and routing
+- Integrating platform APIs (camera, location, sensors)
+- Implementing offline-first data persistence
+- Optimizing for mobile constraints (battery, memory, network)
+- Handling platform-specific behavior differences
+- Configuring build variants and signing
+
+## Flutter Guidelines
+
+- Use Dart 3+ with sound null safety
+- Prefer StatelessWidget with const constructors
+- Use BLoC or Riverpod for state management
+- Follow effective Dart style guide
+- Keep build methods under 80 lines
+- Use go_router for navigation
+- Implement proper widget keys for lists
+- Use freezed for data classes
+
+## React Native Guidelines
+
+- TypeScript strict mode required
+- Functional components with hooks only
+- React Navigation for routing
+- Use Reanimated for animations
+- Platform-specific files: `.ios.tsx` / `.android.tsx`
+- Hermes engine for production builds
+
+## Platform Considerations
+
+- iOS: follow Human Interface Guidelines
+- Android: follow Material Design 3
+- Minimum touch targets: 44x44 points
+- Support dynamic type / font scaling
+- Handle safe areas and notches
+- Support dark mode and system themes
+- Test on real devices, not just simulators

package/dist/presets/mobile/skills/mobile-testing/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: mobile-testing
+description: Write and run mobile tests including widget tests, integration tests, and golden tests. Use when implementing test strategies for Flutter or React Native apps.
+---
+
+# Mobile Testing
+
+Activate this skill when writing or running tests for mobile applications.
+
+## When to Use
+
+- Writing widget/component tests
+- Implementing integration tests
+- Setting up golden (snapshot) tests
+- Testing navigation flows
+- Mocking platform channels or native modules
+- Testing offline behavior
+
+## Flutter Testing
+
+- Widget tests: `flutter test` with WidgetTester
+- Integration tests: `flutter test integration_test/`
+- Golden tests: `matchesGoldenFile` for visual regression
+- Use `mockito` or `mocktail` for dependency mocking
+- Use `bloc_test` for BLoC testing
+- Test with different screen sizes using `binding.window`
+
+## React Native Testing
+
+- Unit tests: Jest with `@testing-library/react-native`
+- Component tests: render and query by accessibility labels
+- Integration tests: Detox for E2E
+- Mock native modules in `jest.setup.js`
+- Snapshot tests for visual regression
+
+## Rules
+
+- Test behavior, not implementation details
+- Mock platform dependencies, not business logic
+- Golden tests need baseline images committed to repo
+- Integration tests should run on CI with emulators
+- Cover critical user flows with integration tests
+- Keep unit tests fast (under 1 second each)

package/dist/presets/mobile/skills/native-integration/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: native-integration
+description: Integrate native platform features via platform channels, native modules, or FFI. Use when accessing device hardware, OS APIs, or third-party native SDKs.
+---
+
+# Native Integration
+
+Activate this skill when bridging between cross-platform code and native platform APIs.
+
+## When to Use
+
+- Implementing platform channels (Flutter MethodChannel/EventChannel)
+- Creating native modules (React Native Turbo Modules)
+- Integrating third-party native SDKs (payments, analytics, maps)
+- Accessing device hardware (camera, biometrics, NFC)
+- Implementing background processing or services
+- Using Dart FFI for C/C++ library integration
+
+## Flutter Platform Channels
+
+- MethodChannel: request-response communication
+- EventChannel: streaming data from native to Dart
+- BasicMessageChannel: simple message passing
+- Use pigeon for type-safe code generation
+- Handle PlatformException gracefully
+
+## React Native Native Modules
+
+- Turbo Modules: JSI-based, synchronous access
+- Fabric: new architecture native components
+- Legacy bridge modules (for backward compatibility)
+- Use codegen for type-safe interfaces
+
+## Rules
+
+- Minimize channel/bridge crossings (batch operations)
+- Handle platform-not-supported gracefully
+- Test on real devices (simulators may not support all hardware)
+- Document required native setup steps (Podfile, build.gradle)
+- Keep native code minimal -- business logic stays in Dart/JS
+- Handle permission requests before accessing hardware

package/dist/presets/mobile/skills/offline-first/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: offline-first
+description: Implement offline-first architecture with local storage, sync strategies, and conflict resolution. Use when building apps that must work without network connectivity.
+---
+
+# Offline First
+
+Activate this skill when implementing offline-capable mobile features.
+
+## When to Use
+
+- Designing data persistence strategy
+- Implementing local-first data storage
+- Building sync mechanisms with remote servers
+- Handling conflict resolution for concurrent edits
+- Implementing optimistic updates with rollback
+- Caching network responses for offline access
+
+## Storage Options
+
+- SQLite (drift/sqflite): relational data, complex queries
+- Hive: fast key-value, good for settings and small datasets
+- Isar: NoSQL, good for large datasets with indexing
+- SharedPreferences: simple key-value for settings
+- Secure storage: credentials and tokens
+
+## Sync Strategies
+
+- Queue-based: store operations, replay when online
+- Timestamp-based: last-write-wins with conflict detection
+- CRDT-based: conflict-free for collaborative data
+- Delta sync: send only changes since last sync
+
+## Rules
+
+- Always design for offline-first, online as enhancement
+- Handle sync conflicts explicitly (never silently overwrite)
+- Show clear UI indicators for sync status
+- Implement retry with exponential backoff
+- Test with airplane mode and intermittent connectivity
+- Encrypt sensitive data stored locally

package/dist/presets/mobile/skills/planning/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: planning
+description: Plan technical solutions that are scalable, secure, and maintainable. Use when you need to decompose features, evaluate approaches, or create implementation plans.
+---
+
+# Planning
+
+Activate this skill when planning features, evaluating approaches, or creating implementation strategies.
+
+## When to Use
+
+- Starting a new feature or project
+- Evaluating multiple technical approaches
+- Decomposing complex requirements into tasks
+- Assessing risks and dependencies
+- Creating time-boxed implementation plans
+
+## Process
+
+1. Define success criteria and constraints
+2. Research relevant patterns and prior art
+3. Decompose into phases (3-7 typical)
+4. Identify dependencies and critical path
+5. Assess risks and define mitigations
+6. Create actionable task list with time estimates
+7. Document unresolved questions
+
+## Output Format
+
+Plans go in `plans/YYYYMMDD-HHmm-plan-name/`:
+- `plan.md`: overview, phase list, status tracking
+- `phase-XX-name.md`: detailed phase specifications
+
+## Rules
+
+- Every task should be completable in 30 min to 2 hours
+- Plans must be actionable, not aspirational
+- Include rollback strategy for risky phases
+- Apply YAGNI: plan only what is needed now

package/dist/presets/mobile/skills/problem-solving/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: problem-solving
+description: Apply systematic problem-solving techniques for complexity spirals, innovation blocks, recurring patterns, and scale uncertainty. Use when stuck or facing novel challenges.
+---
+
+# Problem Solving
+
+Activate this skill when facing complex problems that resist straightforward solutions.
+
+## When to Use
+
+- Complexity spirals (solution keeps growing)
+- Innovation blocks (cannot find a good approach)
+- Recurring patterns (same problem keeps appearing)
+- Assumption constraints (stuck due to false assumptions)
+- Scale uncertainty (unsure how solution will scale)
+
+## Techniques
+
+- Simplification cascade: strip to minimum viable solution
+- Collision-zone thinking: combine unrelated ideas
+- Meta-pattern recognition: identify the pattern behind patterns
+- Inversion exercise: assume the opposite of constraints
+- Scale game: test solution at 10x and 0.1x scale
+
+## Rules
+
+- Try simplification first before adding complexity
+- Question every assumption explicitly
+- If stuck for more than 2 attempts, try a fundamentally different approach
+- Document what was tried and why it failed
+- Prefer reversible decisions over perfect decisions

package/dist/presets/mobile/skills/repomix/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: repomix
+description: Package code repositories into single AI-friendly files for analysis. Use when you need to understand unfamiliar codebases or create repository snapshots.
+---
+
+# Repomix
+
+Activate this skill when you need to package or analyze entire codebases.
+
+## When to Use
+
+- Analyzing unfamiliar mobile project structures
+- Creating repository snapshots for review
+- Packaging codebases for AI analysis
+- Understanding third-party library internals
+- Preparing for security audits
+
+## Usage
+
+```bash
+# Local project
+repomix
+
+# Remote repository
+repomix --remote https://github.com/user/repo
+
+# With filters
+repomix --include "lib/**/*.dart" --exclude "**/*.g.dart"
+```
+
+## Rules
+
+- Use include/exclude patterns to focus on relevant code
+- Exclude generated files (*.g.dart, *.freezed.dart, build/)
+- Output goes to `repomix-output.xml` by default
+- Use for understanding, not for copying code verbatim

package/dist/presets/mobile/skills/research/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: research
+description: Research technical topics, evaluate libraries, and gather information for informed decision-making. Use when investigating new technologies or comparing approaches.
+---
+
+# Research
+
+Activate this skill when you need to investigate technologies, evaluate options, or gather technical information.
+
+## When to Use
+
+- Evaluating packages or libraries for a specific need
+- Investigating platform API capabilities
+- Comparing architectural approaches
+- Understanding new framework features
+- Assessing security implications of dependencies
+
+## Process
+
+1. Define research questions clearly
+2. Search official documentation first
+3. Check package registries (pub.dev, npm) for health metrics
+4. Cross-reference multiple sources
+5. Evaluate trade-offs and compatibility
+6. Synthesize into actionable recommendation
+
+## Rules
+
+- Prefer official documentation over blog posts
+- Verify information currency (check dates)
+- Note version compatibility requirements
+- Distinguish stable from experimental features
+- Document sources for future reference
+- Do NOT implement -- only research and recommend

package/dist/presets/mobile/skills/sequential-thinking/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: sequential-thinking
+description: Apply structured, reflective problem-solving for complex tasks requiring multi-step analysis and revision. Use for complex decomposition or when you need to think step by step.
+---
+
+# Sequential Thinking
+
+Activate this skill for complex problems requiring structured, step-by-step reasoning.
+
+## When to Use
+
+- Complex problem decomposition
+- Multi-step analysis requiring course correction
+- Problems with unclear scope or requirements
+- Hypothesis-driven investigation
+- Architecture decisions with many trade-offs
+
+## Process
+
+1. State the problem clearly in one sentence
+2. Identify what you know and what you need to find out
+3. Break into sequential steps, each building on the previous
+4. At each step, validate assumptions before proceeding
+5. If a step reveals new information, revise earlier conclusions
+6. Summarize findings and recommended action
+
+## Rules
+
+- Each step must be independently verifiable
+- Revise earlier steps when new evidence contradicts them
+- State confidence level at each step
+- Identify decision points and their trade-offs
+- Keep the chain of reasoning visible and traceable

package/dist/presets/mobile/skills/skill-creator/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: skill-creator
+description: Guide for creating effective skills that extend capabilities with specialized knowledge, workflows, or tool integrations. Use when building new skills.
+---
+
+# Skill Creator
+
+Activate this skill when creating or updating skills.
+
+## When to Use
+
+- Creating a new skill for specialized knowledge
+- Updating an existing skill with new capabilities
+- Structuring skill documentation for optimal use
+- Adding reference files or scripts to skills
+
+## Skill Structure
+
+```
+skills/<skill-name>/
+  SKILL.md              Main skill file with front-matter
+  references/           Reference documentation
+  scripts/              Executable scripts
+  assets/               Static assets
+```
+
+## SKILL.md Requirements
+
+- Front-matter: `name` (kebab-case) and `description` (when to activate)
+- Clear "When to Use" section
+- Concise guidelines and rules
+- Token-efficient (progressive disclosure)
+
+## Rules
+
+- Keep SKILL.md under 100 lines for token efficiency
+- Use references/ for detailed documentation
+- Description must clearly state activation triggers
+- Name must be kebab-case
+- Avoid duplicating information available elsewhere

package/dist/presets/mobile/skills/template-skill/SKILL.md

@@ -0,0 +1,23 @@
+---
+name: template-skill
+description: Template for creating new skills. Copy this directory and customize for your specific domain.
+---
+
+# Template Skill
+
+This is a template for creating new skills. Copy this directory and customize.
+
+## When to Use
+
+- [Describe when this skill should be activated]
+
+## Guidelines
+
+- [Add domain-specific guidelines]
+- [Add rules and constraints]
+- [Add process steps]
+
+## Rules
+
+- [Add rules that must be followed]
+- [Add quality standards]

package/dist/presets/mobile/skills/ui-styling/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: ui-styling
+description: Create platform-adaptive mobile interfaces with proper theming, responsive layouts, and design system components. Use when styling widgets or implementing design tokens.
+---
+
+# UI Styling
+
+Activate this skill when styling mobile interfaces or implementing design systems.
+
+## When to Use
+
+- Implementing design tokens and theme systems
+- Creating responsive layouts for different screen sizes
+- Building platform-adaptive components (iOS vs Android styling)
+- Implementing dark mode support
+- Creating custom animations and transitions
+- Establishing consistent spacing and typography scales
+
+## Flutter Styling
+
+- Use ThemeData for global theming
+- Implement ColorScheme for Material 3 colors
+- Use TextTheme for typography scale
+- Leverage MediaQuery for responsive layouts
+- Use LayoutBuilder for constraint-based sizing
+- Implement custom painters for complex visuals
+
+## React Native Styling
+
+- Use StyleSheet.create for performance
+- Implement design tokens as constants
+- Use Platform.select for platform-specific styles
+- Leverage Dimensions API for responsive sizing
+- Use Reanimated for animated styles
+
+## Design Principles
+
+- 4px/8px spacing grid system
+- Platform-native typography (SF Pro for iOS, Roboto for Android)
+- Consistent elevation/shadow system
+- Color semantics (primary, secondary, error, surface)
+- Support for RTL layouts
+- Accessible color contrast (4.5:1 minimum)
+
+## Quality Standards
+
+- All styles must support dark mode
+- Typography must scale with system font size
+- Layouts must handle different screen sizes gracefully
+- Animations must respect reduced motion preferences
+- Colors must meet WCAG 2.1 AA contrast requirements