@dtt_siye/atool 1.2.1 → 1.3.1

package/templates/CLAUDE.md.generic

@@ -32,3 +32,20 @@ Generic project (no specific technology stack detected)
 - Run `./install.sh --project .` again after setting up your project
 - aTool can auto-detect your stack once you add config files (package.json, Cargo.toml, etc.)
 - Use `/atool-init` to re-run initialization after project setup
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/CLAUDE.md.go

@@ -65,3 +65,20 @@ gofmt -w .
 # Tidy dependencies
 go mod tidy
 ```
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/CLAUDE.md.harmony

@@ -52,3 +52,20 @@ hvigorw clean
 # Run tests
 hvigorw test
 ```
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/CLAUDE.md.java

@@ -54,3 +54,20 @@ Java / Spring Boot project
 # Check for dependency updates
 ./mvnw versions:display-dependency-updates
 ```
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/CLAUDE.md.mobile-flutter

@@ -36,3 +36,20 @@ Follow Flutter and Dart best practices.
 - Widget tests with `flutter_test`
 - Integration tests with `integration_test`
 - Mocktail for mocking
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/CLAUDE.md.mobile-react-native

@@ -35,3 +35,20 @@ Follow React Native and TypeScript best practices.
 - Jest + React Native Testing Library
 - Detox for E2E tests
 - Mock native modules
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/CLAUDE.md.mobile-swift

@@ -38,3 +38,20 @@ Follow Swift and iOS development best practices.
 - Swift Testing framework (new)
 - Mock with protocols
 - Preview-based development
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/CLAUDE.md.python

@@ -63,3 +63,20 @@ ruff format .
 # Type check
 mypy .
 ```
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/CLAUDE.md.rust

@@ -66,3 +66,20 @@ cargo fmt
 # Run with release optimizations
 cargo run --release
 ```
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/CLAUDE.md.rust-tauri

@@ -118,3 +118,20 @@ cd src-tauri && cargo test     # 运行测试
 2. `COMPONENT.md` — 组件/命令 API 和使用示例
 3. `UI_STYLE.md` — 涉及的样式变更
 4. `docs/` — 对应的模块文档
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/CLAUDE.md.web

@@ -61,3 +61,20 @@ npm test
 # Build for production
 npm run build
 ```
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/cursor-rules.android.mdc

@@ -31,3 +31,20 @@ Follow Android and Kotlin best practices.
 - JUnit 5 + MockK for unit tests
 - Compose Test Rule for UI tests
 - Turbine for Flow testing
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/cursor-rules.devops.mdc

@@ -30,3 +30,20 @@ Follow infrastructure best practices.
 - Test before deploy
 - Immutable artifacts
 - Rollback strategy
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/cursor-rules.generic.mdc

@@ -23,3 +23,20 @@ Follow general software development best practices.
 - Write tests for critical functionality
 - Use standard testing frameworks
 - Mock external dependencies
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/cursor-rules.go.mdc

@@ -32,3 +32,20 @@ Follow Go best practices and idioms.
 - testing package + testify/assert
 - mockgen for interface mocking
 - go test -race for race detection
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/cursor-rules.harmony.mdc

@@ -28,3 +28,20 @@ Follow HarmonyOS and ArkTS best practices.
 - Navigation component for routing
 - Define routes in main_pages.json
 - NavPathStack for programmatic navigation
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/cursor-rules.java.mdc

@@ -28,3 +28,20 @@ Follow standard Java conventions and Spring Boot best practices.
 - RESTful conventions
 - Proper HTTP status codes
 - Version with `/api/v1/` prefix
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/cursor-rules.mobile-flutter.mdc

@@ -40,3 +40,20 @@ instructions: |
   - Build iOS: flutter build ios
   - Test: flutter test
   - Analyze: flutter analyze
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/cursor-rules.mobile-react-native.mdc

@@ -41,3 +41,20 @@ instructions: |
   - Run iOS: npm run ios
   - Test: npm test
   - Start Metro: npm start
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/cursor-rules.mobile-swift.mdc

@@ -40,3 +40,20 @@ instructions: |
   - Build: xcodebuild build -scheme MyApp
   - Test: xcodebuild test -scheme MyApp
   - Run: open in Xcode and run
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/cursor-rules.python.mdc

@@ -31,3 +31,20 @@ Follow Python best practices.
 - Ruff for linting and formatting
 - mypy for type checking
 - pytest for testing
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/cursor-rules.rust-tauri.mdc

@@ -65,3 +65,20 @@ const result = await invoke<string>('my_command', { arg: 'value' });
 - Build: `pnpm tauri build`
 - Rust check: `cd src-tauri && cargo check`
 - Rust lint: `cd src-tauri && cargo clippy`
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/cursor-rules.rust.mdc

@@ -28,3 +28,20 @@ Follow Rust best practices and idioms.
 - Integration tests in tests/
 - proptest for property-based testing
 - mockall for mocking
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/cursor-rules.web.mdc

@@ -28,3 +28,20 @@ Follow modern web development best practices.
 - Testing Library for component tests
 - Unit tests for utilities and hooks
 - E2E tests for critical flows
+
+
+## aTool Hard Rules (Non-bypassable)
+
+These rules apply regardless of which skills are invoked or which mode the IDE is in (Plan Mode, normal mode, etc.).
+
+### 1. Documentation Sync Gate
+After modifying any source file, update affected documentation (README.md, COMPONENT.md, UI_STYLE.md, docs/) BEFORE claiming the task done.
+Gate: if docs are stale, the task is NOT done. Invoke /verification-before-completion before completion.
+
+### 2. Verification Gate
+Before claiming any work complete: (a) run tests and verify they pass, (b) check doc freshness, (c) confirm no critical code quality issues.
+If any check fails, the task is NOT done. No exceptions.
+
+### 3. Root Cause Before Fix
+When fixing bugs: investigate and identify root cause BEFORE writing any fix code. Never guess-fix or try multiple changes simultaneously.
+See /systematic-debugging for full methodology.

package/templates/kiro-steering.android.md

@@ -37,3 +37,9 @@ You are working on an Android/Kotlin project. Follow these conventions:
 - Test: ./gradlew test
 - Run: ./gradlew installDebug
 
+
+
+## aTool Hard Rules
+1. **Doc Sync**: Source files changed -> update docs (README/COMPONENT/UI_STYLE/docs/) before done. Stale docs = task NOT done.
+2. **Verification**: Before claiming done: tests pass + docs fresh + no critical issues. Invoke /verification-before-completion.
+3. **Root Cause**: Debug -> find root cause BEFORE fix. Never guess. See /systematic-debugging.

package/templates/kiro-steering.devops.md

@@ -30,3 +30,9 @@ You are working on a DevOps/Infrastructure project. Follow these conventions:
 - Immutable artifacts
 - Rollback strategy
 
+
+
+## aTool Hard Rules
+1. **Doc Sync**: Source files changed -> update docs (README/COMPONENT/UI_STYLE/docs/) before done. Stale docs = task NOT done.
+2. **Verification**: Before claiming done: tests pass + docs fresh + no critical issues. Invoke /verification-before-completion.
+3. **Root Cause**: Debug -> find root cause BEFORE fix. Never guess. See /systematic-debugging.

package/templates/kiro-steering.generic.md

@@ -26,3 +26,9 @@ You are working on a generic project. Follow these conventions:
 - aTool can auto-detect your stack once you add config files
 - Run /atool-init to re-run initialization after project setup
 
+
+
+## aTool Hard Rules
+1. **Doc Sync**: Source files changed -> update docs (README/COMPONENT/UI_STYLE/docs/) before done. Stale docs = task NOT done.
+2. **Verification**: Before claiming done: tests pass + docs fresh + no critical issues. Invoke /verification-before-completion.
+3. **Root Cause**: Debug -> find root cause BEFORE fix. Never guess. See /systematic-debugging.

package/templates/kiro-steering.go.md

@@ -39,3 +39,9 @@ You are working on a Go project. Follow these conventions:
 - Format: gofmt -w .
 - Tidy: go mod tidy
 
+
+
+## aTool Hard Rules
+1. **Doc Sync**: Source files changed -> update docs (README/COMPONENT/UI_STYLE/docs/) before done. Stale docs = task NOT done.
+2. **Verification**: Before claiming done: tests pass + docs fresh + no critical issues. Invoke /verification-before-completion.
+3. **Root Cause**: Debug -> find root cause BEFORE fix. Never guess. See /systematic-debugging.

package/templates/kiro-steering.harmony.md

@@ -34,3 +34,9 @@ You are working on a HarmonyOS/ArkTS project. Follow these conventions:
 - Clean: hvigorw clean
 - Test: hvigorw test
 
+
+
+## aTool Hard Rules
+1. **Doc Sync**: Source files changed -> update docs (README/COMPONENT/UI_STYLE/docs/) before done. Stale docs = task NOT done.
+2. **Verification**: Before claiming done: tests pass + docs fresh + no critical issues. Invoke /verification-before-completion.
+3. **Root Cause**: Debug -> find root cause BEFORE fix. Never guess. See /systematic-debugging.

package/templates/kiro-steering.java.md

@@ -35,3 +35,9 @@ You are working on a Java/Spring Boot project. Follow these conventions:
 - Test: ./mvnw test or ./gradlew test
 - Run: ./mvnw spring-boot:run or ./gradlew bootRun
 
+
+
+## aTool Hard Rules
+1. **Doc Sync**: Source files changed -> update docs (README/COMPONENT/UI_STYLE/docs/) before done. Stale docs = task NOT done.
+2. **Verification**: Before claiming done: tests pass + docs fresh + no critical issues. Invoke /verification-before-completion.
+3. **Root Cause**: Debug -> find root cause BEFORE fix. Never guess. See /systematic-debugging.

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

@@ -71,3 +71,9 @@ flutter build ios
 flutter clean
 ```
 
+
+
+## aTool Hard Rules
+1. **Doc Sync**: Source files changed -> update docs (README/COMPONENT/UI_STYLE/docs/) before done. Stale docs = task NOT done.
+2. **Verification**: Before claiming done: tests pass + docs fresh + no critical issues. Invoke /verification-before-completion.
+3. **Root Cause**: Debug -> find root cause BEFORE fix. Never guess. See /systematic-debugging.

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

@@ -69,3 +69,9 @@ npm test
 npx tsc --noEmit
 ```
 
+
+
+## aTool Hard Rules
+1. **Doc Sync**: Source files changed -> update docs (README/COMPONENT/UI_STYLE/docs/) before done. Stale docs = task NOT done.
+2. **Verification**: Before claiming done: tests pass + docs fresh + no critical issues. Invoke /verification-before-completion.
+3. **Root Cause**: Debug -> find root cause BEFORE fix. Never guess. See /systematic-debugging.

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

@@ -60,3 +60,9 @@ xcodebuild clean
 swiftlint lint
 ```
 
+
+
+## aTool Hard Rules
+1. **Doc Sync**: Source files changed -> update docs (README/COMPONENT/UI_STYLE/docs/) before done. Stale docs = task NOT done.
+2. **Verification**: Before claiming done: tests pass + docs fresh + no critical issues. Invoke /verification-before-completion.
+3. **Root Cause**: Debug -> find root cause BEFORE fix. Never guess. See /systematic-debugging.

package/templates/kiro-steering.python.md

@@ -32,3 +32,9 @@ You are working on a Python project. Follow these conventions:
 - Format: ruff format .
 - Type check: mypy .
 
+
+
+## aTool Hard Rules
+1. **Doc Sync**: Source files changed -> update docs (README/COMPONENT/UI_STYLE/docs/) before done. Stale docs = task NOT done.
+2. **Verification**: Before claiming done: tests pass + docs fresh + no critical issues. Invoke /verification-before-completion.
+3. **Root Cause**: Debug -> find root cause BEFORE fix. Never guess. See /systematic-debugging.

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

@@ -48,3 +48,9 @@ You are working on a Tauri 2 desktop application (Rust backend + Web frontend).
 - Rust check: cd src-tauri && cargo check
 - Rust lint: cd src-tauri && cargo clippy
 
+
+
+## aTool Hard Rules
+1. **Doc Sync**: Source files changed -> update docs (README/COMPONENT/UI_STYLE/docs/) before done. Stale docs = task NOT done.
+2. **Verification**: Before claiming done: tests pass + docs fresh + no critical issues. Invoke /verification-before-completion.
+3. **Root Cause**: Debug -> find root cause BEFORE fix. Never guess. See /systematic-debugging.