harness init

AI Community

Skill notes

Purpose

Set up the full Claude Code harness layer — rules, hooks, memory, agent routing. Not project scaffolding (use /project-init for that). This is the AI orchestration layer. Key difference from generic templates: domain presets provide pre-filled rules with real content, not empty skeletons. Every harness includes reject-by-default and violation testing. Dominant variable: 생성된 ai-constitution.md의 Tier 0 규칙이 violation testing을 통과하는가 — 테스트 없는 규칙은 장식이다.

Existing File Check (overwrite protection)

Check each target file before generating: File · If exists ~/.claude/rules/ai-constitution.md · Read it. Offer: update (extend) or replace. Default: update. ~/.claude/rules/agents.md · Read it. Merge new agent definitions, never replace existing ones. ~/.claude/rules/output-style.md · Read it. Offer: update or replace.

Q1 — Domain Preset

After Q1, load the matching preset (see Presets section below). Show the user what's pre-loaded and ask: "Anything to add, change, or remove?"

Q2 — Agent Complexity (adapts based on Q1)

If Q2 = Minimal → skip Q3. Go to Phase 2. If Q2 = Standard → ask Q3 simplified. If Q2 = Orchestrated → ask Q3 full.

Q3 — Review Gates (only if Q2 >= Standard)

Standard version: Orchestrated version (two questions): Q3a — Gate selection: Q3b — Per-gate config (ask separately for each selected gate): Agent existence check (before generating agents.md):

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 0: Prerequisites

Phase 0: Prerequisites

02
Phase 1: Domain Selection (determines everything else)

Phase 1: Domain Selection (determines everything else)

03
Phase 2: Harness Summary

Present the full configuration for approval: Wait for explicit approval before generating.

04
Phase 3: File Generation

Phase 3: File Generation

05
Phase 4: Violation Testing

After generating all files, run verification:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.