@dtt_siye/atool 1.1.0

package/templates/kiro-steering.mobile-react-native.md

@@ -0,0 +1,71 @@
+---
+inclusion: always
+name: atool-react-native-conventions
+description: React Native mobile development conventions
+---
+
+You are working on a React Native project. Follow these conventions:
+
+## Project Type
+React Native / TypeScript mobile application
+
+## Build & Run
+- Run Android: `npm run android`
+- Run iOS: `npm run ios`
+- Start Metro: `npm start`
+- Test: `npm test`
+- Lint: `npm run lint`
+- Type check: `npx tsc --noEmit`
+
+## Code Style
+- TypeScript for all new files
+- Functional components with hooks
+- Follow React conventions
+- Use `expo` when possible for faster development
+- Use `eslint` and `prettier` for formatting
+
+## Architecture
+- Feature-first folder structure
+- Screen components in `screens/`
+- Reusable components in `components/`
+- Services/API in `services/`
+- Hooks in `hooks/`
+- Navigation in `navigation/`
+
+## State Management
+- Zustand for simple to moderate state
+- Redux Toolkit for complex state
+- React Query / SWR for server state
+- AsyncStorage / MMKV for persistence
+
+## Navigation
+- React Navigation for routing
+- Type-safe navigation params
+- Deep linking support
+- Tab and stack navigators
+- Expo Router for file-based routing
+
+## Testing
+- Jest + React Native Testing Library
+- Detox for E2E tests
+- Mock native modules
+- Storybook for component development
+
+## Common Commands
+```bash
+# Run on Android
+npm run android
+
+# Run on iOS
+npm run ios
+
+# Start Metro bundler
+npm start
+
+# Run tests
+npm test
+
+# Type check
+npx tsc --noEmit
+```
+

package/templates/kiro-steering.mobile-swift.md

@@ -0,0 +1,62 @@
+---
+inclusion: always
+name: atool-swift-conventions
+description: Swift/iOS development conventions
+---
+
+You are working on a Swift/iOS project. Follow these conventions:
+
+## Project Type
+iOS / Swift application
+
+## Build & Run
+- Build: `xcodebuild build -scheme MyApp -sdk iphonesimulator`
+- Run: Open in Xcode and run on simulator/device
+- Test: `xcodebuild test -scheme MyApp`
+- Clean: `xcodebuild clean`
+- Lint: `swiftlint lint`
+
+## Code Style
+- Follow Swift API Design Guidelines
+- Use SwiftUI for UI (modern projects)
+- Prefer value types over reference types when possible
+- Use `guard` for early returns
+- Use `final` classes by default, remove only when subclassing needed
+- Use `async/await` for concurrency
+- Use `@Observable` macro for state management (modern projects)
+
+## Architecture
+- MVVM architecture with SwiftUI
+- The Composable Architecture (TCA) for complex state
+- Clean Architecture for large apps
+- Protocol-oriented design
+- Repository pattern for data access
+
+## Navigation
+- SwiftUI NavigationStack / NavigationSplitView
+- Type-safe routing with enums
+- Deep linking support
+- Sheet and fullScreenCover for modals
+
+## Testing
+- XCTest for unit and UI tests
+- Swift Testing framework (new)
+- Mock with protocols (no mocking frameworks needed)
+- Preview-based development
+- XCUITest for UI automation tests
+
+## Common Commands
+```bash
+# Build
+xcodebuild build -scheme MyApp -sdk iphonesimulator
+
+# Run tests
+xcodebuild test -scheme MyApp
+
+# Clean build
+xcodebuild clean
+
+# Lint
+swiftlint lint
+```
+

package/templates/kiro-steering.python.md

@@ -0,0 +1,34 @@
+---
+inclusion: always
+name: atool-python-conventions
+description: Python development conventions
+---
+
+You are working on a Python project. Follow these conventions:
+
+## Code Style
+- PEP 8 conventions
+- Type hints for all function signatures
+- Docstrings (Google or NumPy style)
+- Prefer pathlib over os.path
+- f-strings for string formatting
+
+## Architecture
+- Separate routes, services, models, schemas
+- Pydantic models for data validation
+- Dependency injection for testability
+- Environment variables for configuration
+
+## Testing
+- pytest for all testing
+- Fixtures for setup/teardown
+- Mock external dependencies
+- Aim for 80%+ coverage
+
+## Build Commands
+- Install: pip install -e ".[dev]" or poetry install
+- Test: pytest
+- Lint: ruff check .
+- Format: ruff format .
+- Type check: mypy .
+

package/templates/kiro-steering.rust-tauri.md

@@ -0,0 +1,50 @@
+---
+inclusion: always
+name: atool-tauri-conventions
+description: Tauri 2 desktop app conventions (Rust + Web frontend)
+---
+
+You are working on a Tauri 2 desktop application (Rust backend + Web frontend). Follow these conventions:
+
+## Architecture
+- Dual architecture: Rust backend (src-tauri/) + Web frontend (src/)
+- IPC communication via invoke() / #[tauri::command]
+- All system API access declared in capabilities/
+
+## Rust Backend (src-tauri/)
+- Follow Rust official style guide (rustfmt + clippy)
+- Error handling: use Result<T, E>, no unwrap() in production
+- Async operations: use async fn + Tokio
+- State management: use tauri::State injection
+- All commands: #[tauri::command] annotation
+- Commands organized in src-tauri/src/commands/ module
+
+## Frontend (src/)
+- TypeScript strict mode for all new files
+- Functional components and hooks only
+- IPC calls encapsulated in services/ layer
+- Use @tauri-apps/api for all Tauri interactions
+- Never directly access Node.js APIs in frontend
+
+## IPC Pattern
+- Frontend calls: invoke('command_name', { args })
+- Backend defines: #[tauri::command] async fn command_name(args) -> Result<T, E>
+- All IPC types should be mirrored between Rust structs and TypeScript interfaces
+
+## Security
+- Declare all permissions in capabilities/
+- Scope file system access to specific paths
+- Never disable CSP or security features
+
+## Testing
+- Rust: cargo test in src-tauri/
+- Frontend: pnpm test or npm test
+- E2E: Tauri WebDriver or testing utilities
+
+## Build Commands
+- Install: pnpm install
+- Dev: pnpm tauri dev
+- Build: pnpm tauri build
+- Rust check: cd src-tauri && cargo check
+- Rust lint: cd src-tauri && cargo clippy
+

package/templates/kiro-steering.rust.md

@@ -0,0 +1,36 @@
+---
+inclusion: always
+name: atool-rust-conventions
+description: Rust/Cargo development conventions
+---
+
+You are working on a Rust project. Follow these conventions:
+
+## Code Style
+- Follow Rust API Guidelines
+- Use rustfmt for formatting
+- Use clippy for linting (deny warnings)
+- Prefer Result over panic/unwrap in library code
+- Use meaningful error types (thiserror)
+- Prefer iterators and functional patterns
+- Document public APIs with /// doc comments
+
+## Architecture
+- Module system for organization
+- Trait definitions for abstractions
+- Custom error types with thiserror
+- async/await for I/O-bound operations
+- Feature flags for optional functionality
+
+## Testing
+- Unit tests in-module with #[cfg(test)]
+- Integration tests in tests/ directory
+- proptest for property-based testing
+
+## Build Commands
+- Build: cargo build
+- Test: cargo test
+- Check: cargo clippy -- -D warnings
+- Format: cargo fmt
+- Release: cargo build --release
+

package/templates/kiro-steering.web.md

@@ -0,0 +1,41 @@
+---
+inclusion: always
+name: atool-web-conventions
+description: Web development conventions (React/Next.js/Vue/Svelte)
+---
+
+You are working on a web application project (React/Next.js/Vue/Svelte). Follow these conventions:
+
+## Code Style
+- Use TypeScript for all new files
+- Functional components and hooks only (no class components)
+- Follow the framework's official style guide
+- Keep components small and focused (single responsibility)
+
+## Architecture
+- Co-locate related files (component, styles, tests)
+- Use barrel exports (index.ts) for public APIs
+- Prefer custom hooks/composables for reusable logic
+- Use proper prop typing with TypeScript interfaces
+
+## State Management
+- Use framework-provided state as primary solution
+- Keep server state separate from client state
+- Use optimistic updates for better UX
+
+## API Integration
+- Use established patterns (React Query, SWR, asyncData, etc.)
+- Proper error handling and loading states
+- Type API responses with TypeScript
+
+## Testing
+- Testing Library for component tests
+- Unit tests for utilities and custom hooks
+- E2E tests for critical flows
+
+## Build Commands
+- Install: npm install
+- Dev: npm run dev
+- Build: npm run build
+- Test: npm test
+