@harness-forge/cli 0.1.0

package/knowledge-bases/seeded/dotnet/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/dotnet/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/dotnet/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/dotnet/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/dotnet/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/dotnet/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/dotnet/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/dotnet/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/dotnet/rules/dotnet/coding-style.md

@@ -0,0 +1,38 @@
+---
+paths:
+  - "**/*.cs"
+  - "**/*.csproj"
+  - "**/*.sln"
+  - "**/Directory.Build.*"
+extends: ../common/coding-style.md
+language: dotnet
+layer: language
+---
+# .NET Coding Style
+
+> This file extends [common/coding-style.md](../common/coding-style.md) with .NET-specific guidance.
+
+## Design defaults
+
+- Enable nullable reference types and treat nullability warnings as actionable design feedback.
+- Prefer small, focused types and explicit access modifiers.
+- Use `record`/`record struct` for immutable value-like models and `class` for entities or lifecycle-heavy types.
+- Keep domain logic out of controllers, endpoints, and EF Core entity configuration.
+
+## API boundaries
+
+- Public methods SHOULD expose explicit parameter and return types.
+- Async public APIs SHOULD accept `CancellationToken`.
+- Avoid `dynamic` in application code; prefer generic constraints, interfaces, or explicit DTOs.
+
+## Project layout
+
+- Separate `src/` and `tests/`.
+- Group by feature or bounded context rather than by technical layer when practical.
+- Keep one primary type per file.
+
+## Preferred idioms
+
+- Use guard clauses for invalid inputs.
+- Use immutable DTOs and `with` expressions for updates.
+- Use dependency injection at composition roots, not deep inside domain code.

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

@@ -0,0 +1,24 @@
+---
+paths:
+  - "**/*.cs"
+  - "**/*.csproj"
+  - "**/*.sln"
+extends: ../common/hooks.md
+language: dotnet
+layer: language
+---
+# .NET Hooks
+
+> This file extends [common/hooks.md](../common/hooks.md) with .NET-specific hook suggestions.
+
+## Post-edit hooks
+
+- `dotnet format` for edited projects or solutions.
+- `dotnet build` for affected project graphs.
+- `dotnet test --no-build` for nearby test projects when behavior changes.
+
+## Stop hooks
+
+- final `dotnet build`
+- warn on modified `appsettings*.json`
+- optional dependency audit for package changes

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

@@ -0,0 +1,30 @@
+---
+paths:
+  - "**/*.cs"
+extends: ../common/patterns.md
+language: dotnet
+layer: language
+---
+# .NET Patterns
+
+> This file extends [common/patterns.md](../common/patterns.md) with .NET-specific patterns.
+
+## Recommended architecture
+
+- Use feature-oriented folders for APIs and application services.
+- Keep controllers/minimal endpoints thin.
+- Put validation at the edge.
+- Keep EF Core concerns out of domain types when the domain should remain persistence-agnostic.
+
+## Common patterns
+
+- Request/handler or service-based application flow for non-trivial APIs.
+- Options pattern for configuration.
+- Repository only when it adds real value beyond the ORM/query layer.
+- Background workers for scheduled or queue-driven processes.
+
+## API response pattern
+
+```csharp
+public sealed record ApiResponse<T>(bool Success, T? Data = default, string? Error = null, object? Meta = null);
+```

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

@@ -0,0 +1,28 @@
+---
+paths:
+  - "**/*.cs"
+  - "**/appsettings*.json"
+extends: ../common/security.md
+language: dotnet
+layer: language
+---
+# .NET Security
+
+> This file extends [common/security.md](../common/security.md) with .NET-specific security guidance.
+
+## Secrets
+
+- Never store real credentials in `appsettings*.json`.
+- Use environment variables, user secrets for local development, and managed secret stores in deployed environments.
+
+## APIs
+
+- Validate DTOs before business logic.
+- Use built-in authentication/authorization handlers rather than custom token parsing.
+- Never log raw tokens or unredacted PII.
+
+## Data access
+
+- Use parameterized queries always.
+- Review dynamic sorting and filtering carefully.
+- Prefer least-privilege database accounts and scoped credentials.

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

@@ -0,0 +1,31 @@
+---
+paths:
+  - "**/*.cs"
+  - "**/*.csproj"
+extends: ../common/testing.md
+language: dotnet
+layer: language
+---
+# .NET Testing
+
+> This file extends [common/testing.md](../common/testing.md) with .NET-specific testing guidance.
+
+## Defaults
+
+- Prefer xUnit for tests.
+- Prefer FluentAssertions for assertions.
+- Use Testcontainers for integration tests that need real infrastructure.
+- Test API behavior over HTTP for ASP.NET Core rather than bypassing middleware.
+
+## Coverage priorities
+
+- domain logic
+- validation
+- auth and authorization behavior
+- serialization boundaries
+- database query behavior that can fail silently
+
+## Naming
+
+- Name tests by behavior, not implementation.
+- Keep Arrange/Act/Assert visible.

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

@@ -0,0 +1,18 @@
+# Java Knowledge Base
+
+    Java knowledge base for service applications, libraries, Spring Boot APIs, message-driven systems, and test-heavy enterprise backends.
+Use this pack to deepen rules, examples, hooks, and review checklists.
+
+    ## What is included
+
+    - `rules/common/` baseline rules copied from the current package
+    - `rules/java/` 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/java/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/java/docs/frameworks.md

@@ -0,0 +1,11 @@
+# Framework Notes
+
+This starter pack keeps the core language rules runtime-agnostic.
+
+## Focus areas
+
+Spring Boot, Gradle/Maven, modules, web/data/security test slices.
+
+## 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/java/docs/overview.md

@@ -0,0 +1,34 @@
+# Java Overview
+
+    ## Best fit
+
+    Java knowledge base for service applications, libraries, Spring Boot APIs, message-driven systems, and test-heavy enterprise backends.
+Use this pack to deepen rules, examples, hooks, and review checklists.
+
+    ## Recommended tooling
+
+    - JDK
+- Gradle
+- Maven
+- JUnit 5
+- AssertJ
+- Mockito
+- Testcontainers
+- Spotless
+- google-java-format
+
+## Framework and ecosystem areas
+
+    - Spring Boot
+- Jakarta
+- Micrometer
+- Testcontainers
+- Gradle multi-module builds
+
+## Common pitfalls
+
+    - field injection
+- framework leakage into domain
+- overly generic exceptions
+- hidden N+1 queries
+- too much mutable shared state

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

@@ -0,0 +1,27 @@
+# Java Review Checklist
+
+Use this when reviewing rules, examples, generated output, or agent guidance for Java.
+
+## 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/java/examples/01-spring-boot-rest-api.md

@@ -0,0 +1,13 @@
+# Spring Boot REST API
+
+## 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/java/examples/02-event-consumer-service.md

@@ -0,0 +1,13 @@
+# Event consumer service
+
+## 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/java/examples/03-gradle-multi-module-backend.md

@@ -0,0 +1,13 @@
+# Gradle multi-module backend
+
+## 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/java/examples/04-library-module-with-strong-domain-tests.md

@@ -0,0 +1,13 @@
+# Library module with strong domain tests
+
+## 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/java/knowledge-base.json

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