@harness-forge/cli 0.1.0

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

@@ -0,0 +1,25 @@
+---
+paths:
+  - "**/*.ps1"
+  - "**/*.psm1"
+  - "**/*.psd1"
+extends: ../common/coding-style.md
+language: powershell
+layer: language
+---
+# PowerShell Coding Style
+
+> This file extends [common/coding-style.md](../common/coding-style.md) with PowerShell-specific guidance.
+
+## Defaults
+
+- Prefer advanced functions with `[CmdletBinding()]` for reusable automation.
+- Design around the object pipeline, not text scraping, when the source supports objects.
+- Use approved verbs and clear noun names.
+- Avoid implicit global state; keep script/module scope disciplined.
+
+## Parameters
+
+- Validate parameters explicitly.
+- Provide pipeline support only when it makes the function clearer and safer.
+- Prefer structured objects over stringly typed parameter bundles.

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

@@ -0,0 +1,24 @@
+---
+paths:
+  - "**/*.ps1"
+  - "**/*.psm1"
+  - "**/*.psd1"
+extends: ../common/hooks.md
+language: powershell
+layer: language
+---
+# PowerShell Hooks
+
+> This file extends [common/hooks.md](../common/hooks.md) with PowerShell-specific hook suggestions.
+
+## Post-edit hooks
+
+- `Invoke-ScriptAnalyzer` on affected files
+- Pester tests for nearby modules/scripts
+- manifest validation when `.psd1` changes
+
+## Stop hooks
+
+- final script analyzer pass
+- optional smoke run for bootstrap/install scripts
+- warn on credential handling or remoting changes

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

@@ -0,0 +1,23 @@
+---
+paths:
+  - "**/*.ps1"
+  - "**/*.psm1"
+extends: ../common/patterns.md
+language: powershell
+layer: language
+---
+# PowerShell Patterns
+
+> This file extends [common/patterns.md](../common/patterns.md) with PowerShell-specific patterns.
+
+## Recommended patterns
+
+- advanced functions for reusable operations
+- script modules for cohesive command groups
+- small wrappers around external CLIs that normalize output into objects
+- explicit diagnostic/result objects for automation pipelines
+
+## Cross-platform note
+
+- Keep PowerShell 7+ as the default unless a Windows-only dependency is truly required.
+- Call out Windows PowerShell compatibility separately when necessary.

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

@@ -0,0 +1,23 @@
+---
+paths:
+  - "**/*.ps1"
+  - "**/*.psm1"
+extends: ../common/security.md
+language: powershell
+layer: language
+---
+# PowerShell Security
+
+> This file extends [common/security.md](../common/security.md) with PowerShell-specific security guidance.
+
+## Defaults
+
+- Avoid `Invoke-Expression` unless there is a compelling reviewed reason.
+- Validate paths, remoting targets, and CLI arguments.
+- Redact credentials and tokens from logs.
+- Use secure credential flows and managed identities where possible.
+
+## Execution safety
+
+- Support `-WhatIf`/`-Confirm` for destructive operations when appropriate.
+- Prefer explicit allowlists over free-form command construction.

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

@@ -0,0 +1,24 @@
+---
+paths:
+  - "**/*.ps1"
+  - "**/*.psm1"
+extends: ../common/testing.md
+language: powershell
+layer: language
+---
+# PowerShell Testing
+
+> This file extends [common/testing.md](../common/testing.md) with PowerShell-specific testing guidance.
+
+## Defaults
+
+- Use Pester for tests.
+- Test parameter validation, object output shape, error behavior, and idempotent automation flows.
+- Mock external commands and remoting boundaries carefully.
+
+## Coverage priorities
+
+- bootstrap scripts
+- install/repair/uninstall paths
+- admin automation with safety switches
+- module public command behavior

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

@@ -0,0 +1,18 @@
+# TypeScript Knowledge Base
+
+    TypeScript knowledge base for Node services, React/Next frontends, libraries, CLIs, and monorepos.
+Use this pack to deepen rules around typing, runtime validation, testing, security, and framework-specific examples.
+
+    ## What is included
+
+    - `rules/common/` baseline rules copied from the current package
+    - `rules/typescript/` 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/typescript/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/typescript/docs/frameworks.md

@@ -0,0 +1,11 @@
+# Framework Notes
+
+This starter pack keeps the core language rules runtime-agnostic.
+
+## Focus areas
+
+Node services, React, Next.js, monorepos, runtime schema validation.
+
+## 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/typescript/docs/overview.md

@@ -0,0 +1,34 @@
+# TypeScript Overview
+
+    ## Best fit
+
+    TypeScript knowledge base for Node services, React/Next frontends, libraries, CLIs, and monorepos.
+Use this pack to deepen rules around typing, runtime validation, testing, security, and framework-specific examples.
+
+    ## Recommended tooling
+
+    - TypeScript
+- ESLint
+- Prettier
+- Vitest
+- Jest
+- Playwright
+- pnpm
+- Turborepo/Nx
+- Zod
+
+## Framework and ecosystem areas
+
+    - Node.js
+- React
+- Next.js
+- Express/Fastify/Hono style APIs
+- Vite
+
+## Common pitfalls
+
+    - unvalidated external input
+- any leakage
+- console.log left in prod paths
+- mixed server/client assumptions
+- implicit runtime contracts

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

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

@@ -0,0 +1,13 @@
+# Node 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/typescript/examples/02-react-component-library.md

@@ -0,0 +1,13 @@
+# React component library
+
+## 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/typescript/examples/03-nextjs-app.md

@@ -0,0 +1,13 @@
+# Next.js app
+
+## 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/typescript/examples/04-monorepo-shared-types-and-validation.md

@@ -0,0 +1,13 @@
+# Monorepo shared types and validation
+
+## 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/typescript/knowledge-base.json

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

package/knowledge-bases/seeded/typescript/legacy-seed/typescript/coding-style.md

@@ -0,0 +1,199 @@
+---
+paths:
+  - "**/*.ts"
+  - "**/*.tsx"
+  - "**/*.js"
+  - "**/*.jsx"
+---
+# TypeScript/JavaScript Coding Style
+
+> This file extends [common/coding-style.md](../common/coding-style.md) with TypeScript/JavaScript specific content.
+
+## Types and Interfaces
+
+Use types to make public APIs, shared models, and component props explicit, readable, and reusable.
+
+### Public APIs
+
+- Add parameter and return types to exported functions, shared utilities, and public class methods
+- Let TypeScript infer obvious local variable types
+- Extract repeated inline object shapes into named types or interfaces
+
+```typescript
+// WRONG: Exported function without explicit types
+export function formatUser(user) {
+  return `${user.firstName} ${user.lastName}`
+}
+
+// CORRECT: Explicit types on public APIs
+interface User {
+  firstName: string
+  lastName: string
+}
+
+export function formatUser(user: User): string {
+  return `${user.firstName} ${user.lastName}`
+}
+```
+
+### Interfaces vs. Type Aliases
+
+- Use `interface` for object shapes that may be extended or implemented
+- Use `type` for unions, intersections, tuples, mapped types, and utility types
+- Prefer string literal unions over `enum` unless an `enum` is required for interoperability
+
+```typescript
+interface User {
+  id: string
+  email: string
+}
+
+type UserRole = 'admin' | 'member'
+type UserWithRole = User & {
+  role: UserRole
+}
+```
+
+### Avoid `any`
+
+- Avoid `any` in application code
+- Use `unknown` for external or untrusted input, then narrow it safely
+- Use generics when a value's type depends on the caller
+
+```typescript
+// WRONG: any removes type safety
+function getErrorMessage(error: any) {
+  return error.message
+}
+
+// CORRECT: unknown forces safe narrowing
+function getErrorMessage(error: unknown): string {
+  if (error instanceof Error) {
+    return error.message
+  }
+
+  return 'Unexpected error'
+}
+```
+
+### React Props
+
+- Define component props with a named `interface` or `type`
+- Type callback props explicitly
+- Do not use `React.FC` unless there is a specific reason to do so
+
+```typescript
+interface User {
+  id: string
+  email: string
+}
+
+interface UserCardProps {
+  user: User
+  onSelect: (id: string) => void
+}
+
+function UserCard({ user, onSelect }: UserCardProps) {
+  return <button onClick={() => onSelect(user.id)}>{user.email}</button>
+}
+```
+
+### JavaScript Files
+
+- In `.js` and `.jsx` files, use JSDoc when types improve clarity and a TypeScript migration is not practical
+- Keep JSDoc aligned with runtime behavior
+
+```javascript
+/**
+ * @param {{ firstName: string, lastName: string }} user
+ * @returns {string}
+ */
+export function formatUser(user) {
+  return `${user.firstName} ${user.lastName}`
+}
+```
+
+## Immutability
+
+Use spread operator for immutable updates:
+
+```typescript
+interface User {
+  id: string
+  name: string
+}
+
+// WRONG: Mutation
+function updateUser(user: User, name: string): User {
+  user.name = name // MUTATION!
+  return user
+}
+
+// CORRECT: Immutability
+function updateUser(user: Readonly<User>, name: string): User {
+  return {
+    ...user,
+    name
+  }
+}
+```
+
+## Error Handling
+
+Use async/await with try-catch and narrow unknown errors safely:
+
+```typescript
+interface User {
+  id: string
+  email: string
+}
+
+declare function riskyOperation(userId: string): Promise<User>
+
+function getErrorMessage(error: unknown): string {
+  if (error instanceof Error) {
+    return error.message
+  }
+
+  return 'Unexpected error'
+}
+
+const logger = {
+  error: (message: string, error: unknown) => {
+    // Replace with your production logger (for example, pino or winston).
+  }
+}
+
+async function loadUser(userId: string): Promise<User> {
+  try {
+    const result = await riskyOperation(userId)
+    return result
+  } catch (error: unknown) {
+    logger.error('Operation failed', error)
+    throw new Error(getErrorMessage(error))
+  }
+}
+```
+
+## Input Validation
+
+Use Zod for schema-based validation and infer types from the schema:
+
+```typescript
+import { z } from 'zod'
+
+const userSchema = z.object({
+  email: z.string().email(),
+  age: z.number().int().min(0).max(150)
+})
+
+type UserInput = z.infer<typeof userSchema>
+
+const validated: UserInput = userSchema.parse(input)
+```
+
+## Console.log
+
+- No `console.log` statements in production code
+- Use proper logging libraries instead
+- See hooks for automatic detection

package/knowledge-bases/seeded/typescript/legacy-seed/typescript/hooks.md

@@ -0,0 +1,22 @@
+---
+paths:
+  - "**/*.ts"
+  - "**/*.tsx"
+  - "**/*.js"
+  - "**/*.jsx"
+---
+# TypeScript/JavaScript Hooks
+
+> This file extends [common/hooks.md](../common/hooks.md) with TypeScript/JavaScript specific content.
+
+## PostToolUse Hooks
+
+Configure in `~/.claude/settings.json`:
+
+- **Prettier**: Auto-format JS/TS files after edit
+- **TypeScript check**: Run `tsc` after editing `.ts`/`.tsx` files
+- **console.log warning**: Warn about `console.log` in edited files
+
+## Stop Hooks
+
+- **console.log audit**: Check all modified files for `console.log` before session ends

package/knowledge-bases/seeded/typescript/legacy-seed/typescript/patterns.md

@@ -0,0 +1,52 @@
+---
+paths:
+  - "**/*.ts"
+  - "**/*.tsx"
+  - "**/*.js"
+  - "**/*.jsx"
+---
+# TypeScript/JavaScript Patterns
+
+> This file extends [common/patterns.md](../common/patterns.md) with TypeScript/JavaScript specific content.
+
+## API Response Format
+
+```typescript
+interface ApiResponse<T> {
+  success: boolean
+  data?: T
+  error?: string
+  meta?: {
+    total: number
+    page: number
+    limit: number
+  }
+}
+```
+
+## Custom Hooks Pattern
+
+```typescript
+export function useDebounce<T>(value: T, delay: number): T {
+  const [debouncedValue, setDebouncedValue] = useState<T>(value)
+
+  useEffect(() => {
+    const handler = setTimeout(() => setDebouncedValue(value), delay)
+    return () => clearTimeout(handler)
+  }, [value, delay])
+
+  return debouncedValue
+}
+```
+
+## Repository Pattern
+
+```typescript
+interface Repository<T> {
+  findAll(filters?: Filters): Promise<T[]>
+  findById(id: string): Promise<T | null>
+  create(data: CreateDto): Promise<T>
+  update(id: string, data: UpdateDto): Promise<T>
+  delete(id: string): Promise<void>
+}
+```