kiro-kit 0.1.0

package/dist/presets/mobile/commands/bootstrap.md

@@ -0,0 +1,16 @@
+---
+description: Bootstrap the mobile project with dependencies, environment setup, and initial configuration
+inclusion: manual
+argument-hint: "[platform]"
+---
+
+## Arguments
+PLATFORM: $1 (default: all, options: all, flutter, react-native)
+
+## Workflow
+1. Detect project type (Flutter or React Native) from project files
+2. Install dependencies (`flutter pub get` or `npm install`)
+3. Verify SDK versions meet requirements
+4. Run code generation if applicable (`build_runner`, `codegen`)
+5. Verify builds compile on target platforms
+6. Report setup status and any issues found

package/dist/presets/mobile/commands/clean.md

@@ -0,0 +1,15 @@
+---
+description: Clean build artifacts, caches, and generated files
+inclusion: manual
+argument-hint: "[scope]"
+---
+
+## Arguments
+SCOPE: $1 (default: all, options: all, build, cache, generated)
+
+## Workflow
+1. Remove build directories (build/, .dart_tool/, android/app/build/)
+2. Clear package caches if requested
+3. Remove generated files (*.g.dart, *.freezed.dart) if requested
+4. Run `flutter clean` or equivalent
+5. Report cleaned directories and freed space

package/dist/presets/mobile/commands/design/figma.md

@@ -0,0 +1,15 @@
+---
+description: Extract design specs from Figma for mobile implementation
+inclusion: manual
+argument-hint: "[figma-url]"
+---
+
+## Arguments
+URL: $1 (required, Figma file or frame URL)
+
+## Workflow
+1. Access Figma design via MCP or API
+2. Extract component specs (colors, spacing, typography)
+3. Map to platform design tokens (Flutter ThemeData / RN StyleSheet)
+4. Generate asset export list with required densities
+5. Document implementation notes for platform-specific adaptations

package/dist/presets/mobile/commands/design/system.md

@@ -0,0 +1,15 @@
+---
+description: Generate or update the mobile design system documentation
+inclusion: manual
+argument-hint: "[scope]"
+---
+
+## Arguments
+SCOPE: $1 (default: all, options: all, colors, typography, spacing, components)
+
+## Workflow
+1. Analyze existing theme configuration (ThemeData, StyleSheet)
+2. Document design tokens (colors, typography scale, spacing grid)
+3. List reusable components with their variants
+4. Generate visual reference documentation
+5. Identify inconsistencies or missing tokens

package/dist/presets/mobile/commands/design/wireframe.md

@@ -0,0 +1,16 @@
+---
+description: Create wireframe specifications for mobile screens
+inclusion: manual
+argument-hint: "[screen-name]"
+---
+
+## Arguments
+SCREEN: $1 (required, name of the screen to wireframe)
+
+## Workflow
+1. Define screen purpose and user goals
+2. Map content hierarchy and information architecture
+3. Specify layout structure (safe areas, scroll behavior)
+4. Define interaction patterns (gestures, transitions)
+5. Note platform-specific adaptations (iOS vs Android)
+6. Document accessibility requirements

package/dist/presets/mobile/commands/docs/architecture.md

@@ -0,0 +1,16 @@
+---
+description: Generate or update architecture documentation for the mobile app
+inclusion: manual
+argument-hint: "[layer]"
+---
+
+## Arguments
+LAYER: $1 (default: all, options: all, presentation, domain, data, platform)
+
+## Workflow
+1. Analyze project structure and module dependencies
+2. Document architectural layers and their responsibilities
+3. Map data flow between layers
+4. Document navigation architecture
+5. Note platform-specific architectural decisions
+6. Generate dependency diagram description

package/dist/presets/mobile/commands/docs/summarize.md

@@ -0,0 +1,15 @@
+---
+description: Analyze the codebase and generate documentation summary
+inclusion: manual
+argument-hint: "[focused-topics]"
+---
+
+## Arguments
+TOPICS: $1 (default: all, specific areas to focus on)
+
+## Workflow
+1. Read existing documentation in `docs/` directory
+2. Analyze project structure and key modules
+3. Identify documentation gaps
+4. Generate summary report with current state
+5. Recommend documentation updates needed

package/dist/presets/mobile/commands/docs/update.md

@@ -0,0 +1,15 @@
+---
+description: Update project documentation based on recent code changes
+inclusion: manual
+argument-hint: "[scope]"
+---
+
+## Arguments
+SCOPE: $1 (default: all, options: all, api, architecture, setup)
+
+## Workflow
+1. Identify recent code changes (git diff)
+2. Determine which documentation is affected
+3. Update relevant documentation files
+4. Verify code examples still compile
+5. Update table of contents and cross-references

package/dist/presets/mobile/commands/fix/build.md

@@ -0,0 +1,15 @@
+---
+description: Diagnose and fix build failures for mobile platforms
+inclusion: manual
+argument-hint: "[platform]"
+---
+
+## Arguments
+PLATFORM: $1 (default: all, options: all, ios, android, web)
+
+## Workflow
+1. Run build and capture error output
+2. Analyze error messages and identify root cause
+3. Check common issues (SDK version, dependencies, signing)
+4. Apply fix and verify build succeeds
+5. Document the issue and resolution

package/dist/presets/mobile/commands/fix/lint.md

@@ -0,0 +1,14 @@
+---
+description: Auto-fix linting and formatting issues
+inclusion: manual
+argument-hint: "[path]"
+---
+
+## Arguments
+PATH: $1 (default: ".", entire project)
+
+## Workflow
+1. Run linter with auto-fix enabled (`dart fix --apply` or `eslint --fix`)
+2. Run formatter (`dart format` or `prettier --write`)
+3. Remove unused imports
+4. Report remaining issues that require manual intervention

package/dist/presets/mobile/commands/fix/tests.md

@@ -0,0 +1,16 @@
+---
+description: Diagnose and fix failing tests
+inclusion: manual
+argument-hint: "[test-path]"
+---
+
+## Arguments
+PATH: $1 (default: test/, path to failing tests)
+
+## Workflow
+1. Run failing tests and capture output
+2. Analyze failure messages and stack traces
+3. Identify root cause (code bug vs test bug)
+4. Apply fix to code or test as appropriate
+5. Re-run tests to verify fix
+6. Report resolution and any remaining issues

package/dist/presets/mobile/commands/git/branch.md

@@ -0,0 +1,16 @@
+---
+description: Create a new feature or fix branch with proper naming
+inclusion: manual
+argument-hint: "[type] [description]"
+---
+
+## Arguments
+TYPE: $1 (default: feature, options: feature, fix, refactor, chore)
+DESC: $2 (required, short description in kebab-case)
+
+## Workflow
+1. Ensure working tree is clean (stash if needed)
+2. Pull latest from main/develop
+3. Create branch with format: `$1/$2`
+4. Switch to new branch
+5. Report branch name and base commit

package/dist/presets/mobile/commands/git/commit.md

@@ -0,0 +1,16 @@
+---
+description: Stage and commit changes with conventional commit message
+inclusion: manual
+argument-hint: "[type] [scope]"
+---
+
+## Arguments
+TYPE: $1 (default: auto-detect, options: feat, fix, docs, refactor, test, chore)
+SCOPE: $2 (optional, e.g., auth, navigation, ui)
+
+## Workflow
+1. Stage relevant files (avoid unrelated changes)
+2. Scan for secrets or credentials in diff
+3. Generate conventional commit message from changes
+4. Commit with proper format: `type(scope): description`
+5. Report commit hash and summary

package/dist/presets/mobile/commands/git/pr.md

@@ -0,0 +1,16 @@
+---
+description: Create a pull request with conventional format
+inclusion: manual
+argument-hint: "[branch] [from-branch]"
+---
+
+## Arguments
+TO_BRANCH: $1 (default: main)
+FROM_BRANCH: $2 (default: current branch)
+
+## Workflow
+1. Verify all tests pass and build succeeds
+2. Generate PR title from branch name and recent commits
+3. Create PR description with changes summary
+4. List affected platforms (iOS, Android, shared)
+5. Create PR using `gh pr create`

package/dist/presets/mobile/commands/lint.md

@@ -0,0 +1,15 @@
+---
+description: Run static analysis and linting on the mobile codebase
+inclusion: manual
+argument-hint: "[path]"
+---
+
+## Arguments
+PATH: $1 (default: ".", the entire project)
+
+## Workflow
+1. Run `flutter analyze` or `npx eslint` based on project type
+2. Check for unused imports and dead code
+3. Verify formatting (`dart format` or `prettier`)
+4. Report issues grouped by severity (error, warning, info)
+5. Suggest auto-fixable issues that can be resolved with `--fix`

package/dist/presets/mobile/commands/mobile/navigation.md

@@ -0,0 +1,34 @@
+---
+description: Add or modify navigation routes and flows
+inclusion: manual
+argument-hint: "[route-name] [type]"
+---
+
+## Arguments
+ROUTE: $1 (required, route name or path)
+TYPE: $2 (default: push, options: push, modal, tab, drawer, bottomSheet)
+
+## Workflow
+
+### Flutter (go_router)
+1. Define route path and parameters
+2. Create GoRoute entry with builder
+3. Add type-safe route helper if using typed routes
+4. Configure transitions based on TYPE
+5. Add deep link path if applicable
+6. Test navigation with widget test
+
+### React Native (React Navigation)
+1. Add screen to appropriate navigator (Stack, Tab, Drawer)
+2. Define route params TypeScript interface
+3. Configure screen options and transitions
+4. Add deep linking configuration
+5. Test navigation flow
+
+## Conventions
+- Use type-safe navigation (no magic strings)
+- Define route parameters with proper types
+- Handle authentication guards where needed
+- Support deep linking for all public routes
+- Configure proper back behavior
+- Add transition animations appropriate to navigation type

package/dist/presets/mobile/commands/mobile/platform.md

@@ -0,0 +1,42 @@
+---
+description: Implement platform-specific features or native integrations
+inclusion: manual
+argument-hint: "[feature] [platforms]"
+---
+
+## Arguments
+FEATURE: $1 (required, feature to implement e.g., camera, notifications, biometrics)
+PLATFORMS: $2 (default: both, options: both, ios, android)
+
+## Workflow
+
+### Flutter Platform Channel
+1. Define MethodChannel interface in Dart
+2. Implement iOS handler in Swift (ios/Runner/)
+3. Implement Android handler in Kotlin (android/app/)
+4. Add required permissions to manifests
+5. Create Dart wrapper with proper error handling
+6. Test on both platforms
+
+### React Native Native Module
+1. Define TypeScript interface for the module
+2. Implement iOS module in Swift/Objective-C
+3. Implement Android module in Kotlin/Java
+4. Configure autolinking or manual linking
+5. Add required permissions
+6. Test on both platforms
+
+## Common Features
+- Camera: permissions, capture, gallery access
+- Notifications: push setup, local notifications, channels
+- Biometrics: Face ID, Touch ID, fingerprint
+- Location: permissions, foreground/background tracking
+- Storage: secure keychain/keystore access
+- Share: system share sheet integration
+
+## Conventions
+- Always check permission status before accessing hardware
+- Provide graceful fallback when feature unavailable
+- Handle permission denial with user-friendly messaging
+- Test on real devices (simulators may not support all features)
+- Document required native setup steps in README

package/dist/presets/mobile/commands/mobile/screen.md

@@ -0,0 +1,46 @@
+---
+description: Generate a new mobile screen with proper architecture layers
+inclusion: manual
+argument-hint: "[screen-name] [framework]"
+---
+
+## Arguments
+NAME: $1 (required, PascalCase screen name)
+FRAMEWORK: $2 (default: flutter, options: flutter, react-native)
+
+## Workflow
+
+### Flutter
+1. Create screen widget at `lib/features/$1/presentation/screens/`
+2. Generate BLoC/Cubit for screen state management
+3. Create screen-specific widgets in `widgets/` subdirectory
+4. Add route registration in router configuration
+5. Create widget test file
+6. Run `flutter analyze` to verify
+
+### React Native
+1. Create screen component at `src/screens/$1/`
+2. Generate screen with TypeScript props interface
+3. Add navigation type definitions
+4. Register in navigation stack
+5. Create test file
+6. Run typecheck to verify
+
+## Output Structure (Flutter)
+```
+lib/features/[name]/
+  presentation/
+    screens/[name]_screen.dart
+    widgets/
+  domain/
+  data/
+test/features/[name]/
+  [name]_screen_test.dart
+```
+
+## Conventions
+- Screens handle layout and composition only
+- Business logic lives in BLoC/Cubit (Flutter) or hooks (RN)
+- Each screen has a corresponding test file
+- Navigation registration is required
+- Handle all states: loading, error, empty, data

package/dist/presets/mobile/commands/mobile/widget.md

@@ -0,0 +1,42 @@
+---
+description: Generate a reusable widget or component with tests
+inclusion: manual
+argument-hint: "[widget-name] [framework]"
+---
+
+## Arguments
+NAME: $1 (required, PascalCase widget name)
+FRAMEWORK: $2 (default: flutter, options: flutter, react-native)
+
+## Workflow
+
+### Flutter
+1. Create widget file at appropriate location
+2. Use const constructor and proper Key parameter
+3. Define typed parameters with documentation
+4. Implement proper theming support (Theme.of)
+5. Create widget test with key interactions
+6. Run `flutter analyze` to verify
+
+### React Native
+1. Create component file with TypeScript interface
+2. Implement with proper accessibility props
+3. Support platform-adaptive rendering if needed
+4. Create test file with React Testing Library
+5. Run typecheck to verify
+
+## Output Structure (Flutter)
+```
+lib/shared/widgets/
+  [name].dart              Widget implementation
+test/shared/widgets/
+  [name]_test.dart         Widget tests
+```
+
+## Conventions
+- Prefer StatelessWidget with const constructor
+- Accept callbacks for user interactions (not internal navigation)
+- Support theming via Theme.of(context)
+- Include semantic labels for accessibility
+- Keep under 100 lines; extract sub-widgets if larger
+- Document public parameters with /// comments

package/dist/presets/mobile/commands/plan/feature.md

@@ -0,0 +1,16 @@
+---
+description: Create an implementation plan for a new mobile feature
+inclusion: manual
+argument-hint: "[feature-name]"
+---
+
+## Arguments
+FEATURE: $1 (required, name of the feature to plan)
+
+## Workflow
+1. Define feature requirements and success criteria
+2. Identify affected layers (UI, logic, data, platform)
+3. Decompose into implementable tasks (30min-2hr each)
+4. Identify platform-specific considerations
+5. Assess risks and dependencies
+6. Generate plan in `plans/YYYYMMDD-HHmm-$1/`

package/dist/presets/mobile/commands/plan/refactor.md

@@ -0,0 +1,17 @@
+---
+description: Plan a refactoring effort with risk assessment
+inclusion: manual
+argument-hint: "[target] [goal]"
+---
+
+## Arguments
+TARGET: $1 (required, module or area to refactor)
+GOAL: $2 (required, what the refactoring should achieve)
+
+## Workflow
+1. Analyze current implementation and its issues
+2. Define refactoring goals and constraints
+3. Identify affected tests and dependent code
+4. Plan incremental steps (each independently deployable)
+5. Assess risk of regressions per step
+6. Generate plan with rollback strategy

package/dist/presets/mobile/commands/release.md

@@ -0,0 +1,17 @@
+---
+description: Prepare a release build with version bumping and changelog
+inclusion: manual
+argument-hint: "[version-type]"
+---
+
+## Arguments
+VERSION: $1 (default: patch, options: major, minor, patch, custom)
+
+## Workflow
+1. Bump version in pubspec.yaml or package.json
+2. Update build number (auto-increment)
+3. Generate changelog entry from recent commits
+4. Run full test suite to verify
+5. Create release build for target platforms
+6. Tag the release in git
+7. Report build artifacts and next steps (store submission)

package/dist/presets/mobile/commands/review/code.md

@@ -0,0 +1,16 @@
+---
+description: Review code changes for quality, performance, and platform conventions
+inclusion: manual
+argument-hint: "[path-or-branch]"
+---
+
+## Arguments
+TARGET: $1 (default: staged changes, or specific file/branch)
+
+## Workflow
+1. Identify changed files and their scope
+2. Review for correctness, bugs, and edge cases
+3. Check platform-specific conventions (Dart style, RN patterns)
+4. Verify error handling and resource cleanup
+5. Check accessibility compliance
+6. Report findings grouped by severity

package/dist/presets/mobile/commands/review/security.md

@@ -0,0 +1,16 @@
+---
+description: Review code for security vulnerabilities and mobile-specific risks
+inclusion: manual
+argument-hint: "[path]"
+---
+
+## Arguments
+PATH: $1 (default: ".", entire project)
+
+## Workflow
+1. Scan for hardcoded secrets, API keys, credentials
+2. Check secure storage usage for sensitive data
+3. Verify network security (certificate pinning, HTTPS)
+4. Check permission usage and data privacy compliance
+5. Review authentication and session management
+6. Report vulnerabilities with severity and remediation

package/dist/presets/mobile/commands/scout/ext.md

@@ -0,0 +1,16 @@
+---
+description: Scout codebase using external agentic tools for faster parallel search
+inclusion: manual
+argument-hint: "[search-query] [scale]"
+---
+
+## Arguments
+QUERY: $1 (required, description of what to find)
+SCALE: $2 (default: 3, number of parallel agents)
+
+## Workflow
+1. Analyze search request and divide into logical sections
+2. Launch external agents (Gemini, OpenCode) in parallel
+3. Each agent searches assigned directories with 3-minute timeout
+4. Collect and deduplicate results
+5. Present organized file list grouped by relevance

package/dist/presets/mobile/commands/scout.md

@@ -0,0 +1,16 @@
+---
+description: Scout the codebase for files relevant to a specific task
+inclusion: manual
+argument-hint: "[search-query] [scale]"
+---
+
+## Arguments
+QUERY: $1 (required, description of what to find)
+SCALE: $2 (default: 3, number of parallel search agents)
+
+## Workflow
+1. Analyze the search request and identify key directories
+2. Divide codebase into logical sections (lib/, test/, ios/, android/)
+3. Launch SCALE parallel agents to search different sections
+4. Synthesize results into organized file list
+5. Report findings grouped by layer (UI, logic, data, platform)

package/dist/presets/mobile/commands/skill/add.md

@@ -0,0 +1,16 @@
+---
+description: Add a new skill or reference files to an existing skill
+inclusion: manual
+argument-hint: "[skill-name] [prompt]"
+---
+
+## Arguments
+SKILL: $1 (required, skill name in kebab-case)
+PROMPT: $2 (required, what to add)
+
+## Workflow
+1. Locate or create skill directory at `.kiro/skills/$1/`
+2. Analyze requirements from prompt
+3. Create or update SKILL.md with proper front-matter
+4. Add reference files if documentation is provided
+5. Verify skill structure is valid

package/dist/presets/mobile/commands/skill/create.md

@@ -0,0 +1,16 @@
+---
+description: Create a new skill from scratch with proper structure
+inclusion: manual
+argument-hint: "[skill-name] [description]"
+---
+
+## Arguments
+NAME: $1 (required, kebab-case skill name)
+DESC: $2 (required, when to activate this skill)
+
+## Workflow
+1. Create directory `.kiro/skills/$1/`
+2. Generate SKILL.md with front-matter and template content
+3. Create optional subdirectories (references/, scripts/, assets/)
+4. Populate with initial guidelines based on description
+5. Verify structure matches skill specification

package/dist/presets/mobile/commands/skill/optimize.md

@@ -0,0 +1,16 @@
+---
+description: Optimize an existing skill for better token efficiency and effectiveness
+inclusion: manual
+argument-hint: "[skill-name]"
+---
+
+## Arguments
+SKILL: $1 (required, skill name to optimize)
+
+## Workflow
+1. Read current skill content and assess token usage
+2. Identify redundant or overly verbose sections
+3. Apply progressive disclosure (move details to references/)
+4. Ensure SKILL.md stays under 100 lines
+5. Verify activation triggers are clear and specific
+6. Present optimization plan for review

package/dist/presets/mobile/commands/test.md

@@ -0,0 +1,17 @@
+---
+description: Run the test suite with coverage reporting
+inclusion: manual
+argument-hint: "[test-type] [path]"
+---
+
+## Arguments
+TYPE: $1 (default: unit, options: unit, widget, integration, all)
+PATH: $2 (default: test/)
+
+## Workflow
+1. Run specified test type with coverage enabled
+2. For Flutter: `flutter test --coverage $PATH`
+3. For React Native: `npx jest --coverage $PATH`
+4. Analyze coverage report and identify gaps
+5. Report results: passed, failed, skipped, coverage percentage
+6. Highlight any flaky tests detected