Configs & templates
Two catalog item types don't fit the skill/agent mold — they're not agent context, they're actual project files.
Configs (2)
type: config items are project-root tooling configs. They carry tokenEstimate: 0 — they're never loaded into agent context, so they don't count against your context budget. Unlike skills/agents, haus apply never writes them automatically; they're distributed one-time via haus scaffold (or the Claude Code flows, which ask before scaffolding).
| Item | What it is |
|---|---|
haus.eslint-config | ESLint 9.x flat config for Haus Tech TypeScript/React projects |
haus.prettier-config | Prettier config + .prettierignore for Haus Tech projects |
Existing project-root config is preserved by default — haus scaffold <id> --force is the only way to replace one you already have. See the Haus Workflow CLI commands reference for the full scaffold behavior.
Templates (4)
type: template items are managed files haus apply writes and keeps in sync — they carry a content hash so local hand-edits are detected and preserved rather than silently overwritten.
| Item | What it is |
|---|---|
haus.agentic-workflow-standard | The workflow methodology every haus-managed project gets: feature loop, NEVER rules, testing standards, ADR process, subagent patterns, security, accessibility. Installed as .haus-workflow/WORKFLOW.md |
haus.lefthook-security | Commit-time secret scanning (gitleaks + grep fallback) wired via Lefthook — complements haus's runtime guards and permissions.deny rules |
haus.decision-template | Copy-paste skeleton for an Architecture Decision Record under docs/decisions/ |
haus.decisions-ci-gate | CI job fragment that runs haus decisions check on pull requests |
haus.agentic-workflow-standard is installed in every project by default (default: true in the manifest) — it's the one template you can expect regardless of stack. The other three are matched by signal (e.g. haus.lefthook-security when Lefthook is detected or recommended).