@harness-forge/cli 0.1.0

package/knowledge-bases/seeded/java/rules/common/hooks.md

@@ -0,0 +1,30 @@
+# Hooks System
+
+## Hook Types
+
+- **PreToolUse**: Before tool execution (validation, parameter modification)
+- **PostToolUse**: After tool execution (auto-format, checks)
+- **Stop**: When session ends (final verification)
+
+## Auto-Accept Permissions
+
+Use with caution:
+- Enable for trusted, well-defined plans
+- Disable for exploratory work
+- Never use dangerously-skip-permissions flag
+- Configure `allowedTools` in `~/.claude.json` instead
+
+## TodoWrite Best Practices
+
+Use TodoWrite tool to:
+- Track progress on multi-step tasks
+- Verify understanding of instructions
+- Enable real-time steering
+- Show granular implementation steps
+
+Todo list reveals:
+- Out of order steps
+- Missing items
+- Extra unnecessary items
+- Wrong granularity
+- Misinterpreted requirements

package/knowledge-bases/seeded/java/rules/common/patterns.md

@@ -0,0 +1,31 @@
+# Common Patterns
+
+## Skeleton Projects
+
+When implementing new functionality:
+1. Search for battle-tested skeleton projects
+2. Use parallel agents to evaluate options:
+   - Security assessment
+   - Extensibility analysis
+   - Relevance scoring
+   - Implementation planning
+3. Clone best match as foundation
+4. Iterate within proven structure
+
+## Design Patterns
+
+### Repository Pattern
+
+Encapsulate data access behind a consistent interface:
+- Define standard operations: findAll, findById, create, update, delete
+- Concrete implementations handle storage details (database, API, file, etc.)
+- Business logic depends on the abstract interface, not the storage mechanism
+- Enables easy swapping of data sources and simplifies testing with mocks
+
+### API Response Format
+
+Use a consistent envelope for all API responses:
+- Include a success/status indicator
+- Include the data payload (nullable on error)
+- Include an error message field (nullable on success)
+- Include metadata for paginated responses (total, page, limit)

package/knowledge-bases/seeded/java/rules/common/performance.md

@@ -0,0 +1,55 @@
+# Performance Optimization
+
+## Model Selection Strategy
+
+**Haiku 4.5** (90% of Sonnet capability, 3x cost savings):
+- Lightweight agents with frequent invocation
+- Pair programming and code generation
+- Worker agents in multi-agent systems
+
+**Sonnet 4.6** (Best coding model):
+- Main development work
+- Orchestrating multi-agent workflows
+- Complex coding tasks
+
+**Opus 4.5** (Deepest reasoning):
+- Complex architectural decisions
+- Maximum reasoning requirements
+- Research and analysis tasks
+
+## Context Window Management
+
+Avoid last 20% of context window for:
+- Large-scale refactoring
+- Feature implementation spanning multiple files
+- Debugging complex interactions
+
+Lower context sensitivity tasks:
+- Single-file edits
+- Independent utility creation
+- Documentation updates
+- Simple bug fixes
+
+## Extended Thinking + Plan Mode
+
+Extended thinking is enabled by default, reserving up to 31,999 tokens for internal reasoning.
+
+Control extended thinking via:
+- **Toggle**: Option+T (macOS) / Alt+T (Windows/Linux)
+- **Config**: Set `alwaysThinkingEnabled` in `~/.claude/settings.json`
+- **Budget cap**: `export MAX_THINKING_TOKENS=10000`
+- **Verbose mode**: Ctrl+O to see thinking output
+
+For complex tasks requiring deep reasoning:
+1. Ensure extended thinking is enabled (on by default)
+2. Enable **Plan Mode** for structured approach
+3. Use multiple critique rounds for thorough analysis
+4. Use split role sub-agents for diverse perspectives
+
+## Build Troubleshooting
+
+If build fails:
+1. Use **build-error-resolver** agent
+2. Analyze error messages
+3. Fix incrementally
+4. Verify after each fix

package/knowledge-bases/seeded/java/rules/common/security.md

@@ -0,0 +1,29 @@
+# Security Guidelines
+
+## Mandatory Security Checks
+
+Before ANY commit:
+- [ ] No hardcoded secrets (API keys, passwords, tokens)
+- [ ] All user inputs validated
+- [ ] SQL injection prevention (parameterized queries)
+- [ ] XSS prevention (sanitized HTML)
+- [ ] CSRF protection enabled
+- [ ] Authentication/authorization verified
+- [ ] Rate limiting on all endpoints
+- [ ] Error messages don't leak sensitive data
+
+## Secret Management
+
+- NEVER hardcode secrets in source code
+- ALWAYS use environment variables or a secret manager
+- Validate that required secrets are present at startup
+- Rotate any secrets that may have been exposed
+
+## Security Response Protocol
+
+If security issue found:
+1. STOP immediately
+2. Use **security-reviewer** agent
+3. Fix CRITICAL issues before continuing
+4. Rotate any exposed secrets
+5. Review entire codebase for similar issues

package/knowledge-bases/seeded/java/rules/common/testing.md

@@ -0,0 +1,29 @@
+# Testing Requirements
+
+## Minimum Test Coverage: 80%
+
+Test Types (ALL required):
+1. **Unit Tests** - Individual functions, utilities, components
+2. **Integration Tests** - API endpoints, database operations
+3. **E2E Tests** - Critical user flows (framework chosen per language)
+
+## Test-Driven Development
+
+MANDATORY workflow:
+1. Write test first (RED)
+2. Run test - it should FAIL
+3. Write minimal implementation (GREEN)
+4. Run test - it should PASS
+5. Refactor (IMPROVE)
+6. Verify coverage (80%+)
+
+## Troubleshooting Test Failures
+
+1. Use **tdd-guide** agent
+2. Check test isolation
+3. Verify mocks are correct
+4. Fix implementation, not tests (unless tests are wrong)
+
+## Agent Support
+
+- **tdd-guide** - Use PROACTIVELY for new features, enforces write-tests-first

package/knowledge-bases/seeded/java/rules/java/coding-style.md

@@ -0,0 +1,22 @@
+---
+paths:
+  - "**/*.java"
+extends: ../common/coding-style.md
+language: java
+layer: language
+---
+# Java Coding Style
+
+> This file extends [common/coding-style.md](../common/coding-style.md) with Java-specific guidance.
+
+## Defaults
+
+- Prefer immutable models and `record` for value types where supported.
+- Use constructor injection, not field injection.
+- Keep package structure aligned with domains or features.
+- Keep APIs explicit and readable rather than overly abstract.
+
+## Modern language features
+
+- Use records, sealed hierarchies, pattern matching, text blocks, and switch expressions when they improve clarity.
+- Avoid introducing modern syntax only for novelty; keep readability first.

package/knowledge-bases/seeded/java/rules/java/hooks.md

@@ -0,0 +1,23 @@
+---
+paths:
+  - "**/*.java"
+  - "**/pom.xml"
+  - "**/build.gradle*"
+extends: ../common/hooks.md
+language: java
+layer: language
+---
+# Java Hooks
+
+> This file extends [common/hooks.md](../common/hooks.md) with Java-specific hook suggestions.
+
+## Post-edit hooks
+
+- format with Spotless or project formatter
+- compile changed modules
+- run nearby tests when behavior changes
+
+## Stop hooks
+
+- final module build
+- dependency vulnerability check when build files change

package/knowledge-bases/seeded/java/rules/java/patterns.md

@@ -0,0 +1,22 @@
+---
+paths:
+  - "**/*.java"
+extends: ../common/patterns.md
+language: java
+layer: language
+---
+# Java Patterns
+
+> This file extends [common/patterns.md](../common/patterns.md) with Java-specific patterns.
+
+## Recommended architecture
+
+- Keep controllers/resources thin.
+- Put orchestration in services/use cases.
+- Keep persistence and transport concerns away from the domain model.
+- Prefer explicit transaction boundaries.
+
+## Build systems
+
+- Support both Gradle and Maven in docs where practical.
+- Do not make framework-specific assumptions in core rules unless the file is clearly framework-scoped.

package/knowledge-bases/seeded/java/rules/java/security.md

@@ -0,0 +1,21 @@
+---
+paths:
+  - "**/*.java"
+extends: ../common/security.md
+language: java
+layer: language
+---
+# Java Security
+
+> This file extends [common/security.md](../common/security.md) with Java-specific security guidance.
+
+## Application security
+
+- Validate external inputs at the web or messaging edge.
+- Use framework security primitives instead of ad hoc auth parsing.
+- Do not expose stack traces, SQL text, or internal paths in responses.
+
+## Data access
+
+- Use prepared statements or framework equivalents.
+- Review ORM fetch strategies and serialization carefully to avoid data leakage.

package/knowledge-bases/seeded/java/rules/java/testing.md

@@ -0,0 +1,23 @@
+---
+paths:
+  - "**/*.java"
+extends: ../common/testing.md
+language: java
+layer: language
+---
+# Java Testing
+
+> This file extends [common/testing.md](../common/testing.md) with Java-specific testing guidance.
+
+## Defaults
+
+- Prefer JUnit 5.
+- Prefer AssertJ for fluent assertions.
+- Use Mockito sparingly; prefer real collaborators when they are cheap to construct.
+- Use Testcontainers for integration tests with real databases or brokers.
+
+## Test layering
+
+- fast domain/unit tests
+- slice tests for web/data boundaries
+- integration tests for full behavior

package/knowledge-bases/seeded/lua/README.md

@@ -0,0 +1,18 @@
+# Lua Knowledge Base
+
+    Lua knowledge base for general scripting, Neovim plugins, OpenResty services, game scripting, and embedded automation.
+Use this pack to add first-class Lua rules, examples, and harness workflows.
+
+    ## What is included
+
+    - `rules/common/` baseline rules copied from the current package
+    - `rules/lua/` starter language pack for the fresh project
+    - `docs/` notes for tooling, frameworks, examples, and review checklists
+    - `examples/` scenario seeds for expanding future project examples
+
+    ## Recommended use
+
+    1. Use the `rules/` files as the starter pack for the fresh project.
+    2. Pull examples into the public docs and scenario examples.
+    3. Extend the review checklist as agent or command quality gates.
+    4. Split framework-heavy content into separate docs if the pack grows too large.

package/knowledge-bases/seeded/lua/docs/examples-guide.md

@@ -0,0 +1,15 @@
+# Example Expansion Guide
+
+Use the starter examples in `examples/` as seeds for:
+
+- scenario docs in `examples/`
+- language-specific rule examples
+- adapter-specific setup examples
+- smoke-test projects for installer validation
+
+## Keep examples useful
+
+- Prefer one clear scenario per example.
+- Include project shape, tooling, test strategy, and hook suggestions.
+- Show where the language pack modifies common defaults.
+- Keep generated or copied example files clearly marked.

package/knowledge-bases/seeded/lua/docs/frameworks.md

@@ -0,0 +1,11 @@
+# Framework Notes
+
+This starter pack keeps the core language rules runtime-agnostic.
+
+## Focus areas
+
+Neovim, OpenResty, LÖVE, embedded runtime adapters.
+
+## Recommendation
+
+Keep core language rules small and stable. Move framework-heavy examples and operational guidance into separate docs or optional packs when the project grows.

package/knowledge-bases/seeded/lua/docs/overview.md

@@ -0,0 +1,30 @@
+# Lua Overview
+
+    ## Best fit
+
+    Lua knowledge base for general scripting, Neovim plugins, OpenResty services, game scripting, and embedded automation.
+Use this pack to add first-class Lua rules, examples, and harness workflows.
+
+    ## Recommended tooling
+
+    - Lua
+- LuaRocks
+- stylua
+- luacheck
+- busted
+- Plenary test harness for Neovim
+
+## Framework and ecosystem areas
+
+    - Neovim plugin development
+- OpenResty
+- LÖVE/game scripting
+- embedded host integrations
+
+## Common pitfalls
+
+    - global state leakage
+- nil handling surprises
+- metatable overuse
+- unsafe shell invocation
+- weak module boundaries

package/knowledge-bases/seeded/lua/docs/review-checklist.md

@@ -0,0 +1,27 @@
+# Lua Review Checklist
+
+Use this when reviewing rules, examples, generated output, or agent guidance for Lua.
+
+## Design
+
+- Are boundaries explicit?
+- Is mutable shared state minimized?
+- Are framework and runtime concerns separated from domain logic?
+
+## Testing
+
+- Are tests behavior-focused?
+- Are failure paths covered?
+- Are integration boundaries tested where silent breakage is likely?
+
+## Security
+
+- Are secrets kept out of source and logs?
+- Is untrusted input validated at the edge?
+- Are risky runtime features called out and constrained?
+
+## Documentation quality
+
+- Do examples compile or run conceptually without missing context?
+- Are framework-specific assumptions clearly labeled?
+- Does the content distinguish rules from examples from optional advice?

package/knowledge-bases/seeded/lua/examples/01-neovim-plugin.md

@@ -0,0 +1,13 @@
+# Neovim plugin
+
+## Scenario
+
+Starter scenario for expanding installer examples, language-pack docs, and review/test guidance.
+
+## Include in the real project
+
+- recommended pack/profile combination
+- expected commands/hooks
+- testing strategy
+- security concerns
+- adapter-specific notes if behavior differs by target

package/knowledge-bases/seeded/lua/examples/02-openresty-request-handler.md

@@ -0,0 +1,13 @@
+# OpenResty request handler
+
+## Scenario
+
+Starter scenario for expanding installer examples, language-pack docs, and review/test guidance.
+
+## Include in the real project
+
+- recommended pack/profile combination
+- expected commands/hooks
+- testing strategy
+- security concerns
+- adapter-specific notes if behavior differs by target

package/knowledge-bases/seeded/lua/examples/03-l/303/266ve-gameplay-module.md

@@ -0,0 +1,13 @@
+# LÖVE gameplay module
+
+## Scenario
+
+Starter scenario for expanding installer examples, language-pack docs, and review/test guidance.
+
+## Include in the real project
+
+- recommended pack/profile combination
+- expected commands/hooks
+- testing strategy
+- security concerns
+- adapter-specific notes if behavior differs by target

package/knowledge-bases/seeded/lua/examples/04-embedded-automation-script.md

@@ -0,0 +1,13 @@
+# embedded automation script
+
+## Scenario
+
+Starter scenario for expanding installer examples, language-pack docs, and review/test guidance.
+
+## Include in the real project
+
+- recommended pack/profile combination
+- expected commands/hooks
+- testing strategy
+- security concerns
+- adapter-specific notes if behavior differs by target

package/knowledge-bases/seeded/lua/knowledge-base.json

@@ -0,0 +1,8 @@
+{
+  "id": "lua-knowledge-base",
+  "language": "lua",
+  "title": "Lua",
+  "intended_use": "starter knowledge base for language rules, examples, hooks, and review guidance",
+  "includes_common_rules": true,
+  "seeded_from_existing_package": false
+}

package/knowledge-bases/seeded/lua/rules/common/agents.md

@@ -0,0 +1,50 @@
+# Agent Orchestration
+
+## Available Agents
+
+Located in `~/.claude/agents/`:
+
+| Agent | Purpose | When to Use |
+|-------|---------|-------------|
+| planner | Implementation planning | Complex features, refactoring |
+| architect | System design | Architectural decisions |
+| tdd-guide | Test-driven development | New features, bug fixes |
+| code-reviewer | Code review | After writing code |
+| security-reviewer | Security analysis | Before commits |
+| build-error-resolver | Fix build errors | When build fails |
+| e2e-runner | E2E testing | Critical user flows |
+| refactor-cleaner | Dead code cleanup | Code maintenance |
+| doc-updater | Documentation | Updating docs |
+| rust-reviewer | Rust code review | Rust projects |
+
+## Immediate Agent Usage
+
+No user prompt needed:
+1. Complex feature requests - Use **planner** agent
+2. Code just written/modified - Use **code-reviewer** agent
+3. Bug fix or new feature - Use **tdd-guide** agent
+4. Architectural decision - Use **architect** agent
+
+## Parallel Task Execution
+
+ALWAYS use parallel Task execution for independent operations:
+
+```markdown
+# GOOD: Parallel execution
+Launch 3 agents in parallel:
+1. Agent 1: Security analysis of auth module
+2. Agent 2: Performance review of cache system
+3. Agent 3: Type checking of utilities
+
+# BAD: Sequential when unnecessary
+First agent 1, then agent 2, then agent 3
+```
+
+## Multi-Perspective Analysis
+
+For complex problems, use split role sub-agents:
+- Factual reviewer
+- Senior engineer
+- Security expert
+- Consistency reviewer
+- Redundancy checker

package/knowledge-bases/seeded/lua/rules/common/coding-style.md

@@ -0,0 +1,48 @@
+# Coding Style
+
+## Immutability (CRITICAL)
+
+ALWAYS create new objects, NEVER mutate existing ones:
+
+```
+// Pseudocode
+WRONG:  modify(original, field, value) → changes original in-place
+CORRECT: update(original, field, value) → returns new copy with change
+```
+
+Rationale: Immutable data prevents hidden side effects, makes debugging easier, and enables safe concurrency.
+
+## File Organization
+
+MANY SMALL FILES > FEW LARGE FILES:
+- High cohesion, low coupling
+- 200-400 lines typical, 800 max
+- Extract utilities from large modules
+- Organize by feature/domain, not by type
+
+## Error Handling
+
+ALWAYS handle errors comprehensively:
+- Handle errors explicitly at every level
+- Provide user-friendly error messages in UI-facing code
+- Log detailed error context on the server side
+- Never silently swallow errors
+
+## Input Validation
+
+ALWAYS validate at system boundaries:
+- Validate all user input before processing
+- Use schema-based validation where available
+- Fail fast with clear error messages
+- Never trust external data (API responses, user input, file content)
+
+## Code Quality Checklist
+
+Before marking work complete:
+- [ ] Code is readable and well-named
+- [ ] Functions are small (<50 lines)
+- [ ] Files are focused (<800 lines)
+- [ ] No deep nesting (>4 levels)
+- [ ] Proper error handling
+- [ ] No hardcoded values (use constants or config)
+- [ ] No mutation (immutable patterns used)

package/knowledge-bases/seeded/lua/rules/common/development-workflow.md

@@ -0,0 +1,38 @@
+# Development Workflow
+
+> This file extends [common/git-workflow.md](./git-workflow.md) with the full feature development process that happens before git operations.
+
+The Feature Implementation Workflow describes the development pipeline: research, planning, TDD, code review, and then committing to git.
+
+## Feature Implementation Workflow
+
+0. **Research & Reuse** _(mandatory before any new implementation)_
+   - **GitHub code search first:** Run `gh search repos` and `gh search code` to find existing implementations, templates, and patterns before writing anything new.
+   - **Library docs second:** Use Context7 or primary vendor docs to confirm API behavior, package usage, and version-specific details before implementing.
+   - **Exa only when the first two are insufficient:** Use Exa for broader web research or discovery after GitHub search and primary docs.
+   - **Check package registries:** Search npm, PyPI, crates.io, and other registries before writing utility code. Prefer battle-tested libraries over hand-rolled solutions.
+   - **Search for adaptable implementations:** Look for open-source projects that solve 80%+ of the problem and can be forked, ported, or wrapped.
+   - Prefer adopting or porting a proven approach over writing net-new code when it meets the requirement.
+
+1. **Plan First**
+   - Use **planner** agent to create implementation plan
+   - Generate planning docs before coding: PRD, architecture, system_design, tech_doc, task_list
+   - Identify dependencies and risks
+   - Break down into phases
+
+2. **TDD Approach**
+   - Use **tdd-guide** agent
+   - Write tests first (RED)
+   - Implement to pass tests (GREEN)
+   - Refactor (IMPROVE)
+   - Verify 80%+ coverage
+
+3. **Code Review**
+   - Use **code-reviewer** agent immediately after writing code
+   - Address CRITICAL and HIGH issues
+   - Fix MEDIUM issues when possible
+
+4. **Commit & Push**
+   - Detailed commit messages
+   - Follow conventional commits format
+   - See [git-workflow.md](./git-workflow.md) for commit message format and PR process

package/knowledge-bases/seeded/lua/rules/common/git-workflow.md

@@ -0,0 +1,24 @@
+# Git Workflow
+
+## Commit Message Format
+```
+<type>: <description>
+
+<optional body>
+```
+
+Types: feat, fix, refactor, docs, test, chore, perf, ci
+
+Note: Attribution disabled globally via ~/.claude/settings.json.
+
+## Pull Request Workflow
+
+When creating PRs:
+1. Analyze full commit history (not just latest commit)
+2. Use `git diff [base-branch]...HEAD` to see all changes
+3. Draft comprehensive PR summary
+4. Include test plan with TODOs
+5. Push with `-u` flag if new branch
+
+> For the full development process (planning, TDD, code review) before git operations,
+> see [development-workflow.md](./development-workflow.md).

package/knowledge-bases/seeded/lua/rules/common/hooks.md

@@ -0,0 +1,30 @@
+# Hooks System
+
+## Hook Types
+
+- **PreToolUse**: Before tool execution (validation, parameter modification)
+- **PostToolUse**: After tool execution (auto-format, checks)
+- **Stop**: When session ends (final verification)
+
+## Auto-Accept Permissions
+
+Use with caution:
+- Enable for trusted, well-defined plans
+- Disable for exploratory work
+- Never use dangerously-skip-permissions flag
+- Configure `allowedTools` in `~/.claude.json` instead
+
+## TodoWrite Best Practices
+
+Use TodoWrite tool to:
+- Track progress on multi-step tasks
+- Verify understanding of instructions
+- Enable real-time steering
+- Show granular implementation steps
+
+Todo list reveals:
+- Out of order steps
+- Missing items
+- Extra unnecessary items
+- Wrong granularity
+- Misinterpreted requirements