← ClaudeAtlas

nulnul-harnesslisted

Turn a project idea or recurring workflow into a minimal, personally evolving agent system. Before activating, inspect any user-named local task contract such as TASK.md; do not activate when it already provides explicit local inputs, outputs, constraints, and a runnable completion check. Use for project setup, skill or plugin selection, external-write planning, multi-session checkpointing, or evidence-gated agent evolution, and when implementation lacks a coherent repository setup or complete task contract. Inspect the repository, verify existing capabilities before creating new ones, complete the original task, and promote only independently verified improvements. Trigger on a plain setup request in any language, including "set up the harness", "하네스 세팅해줘", "하네스 구성해줘", "配置一下 harness", "设置这个项目的 harness", "ハーネスをセットアップして", and "ハーネスを構成して". Do not use for simple read-only questions or isolated work already covered by those contracts.
SeoNaRu/nulnul-harness · ★ 34 · AI & Automation · score 77
Install: claude install-skill SeoNaRu/nulnul-harness
# nulnul harness Erase process, not judgment. Let the user describe the result; absorb capability discovery, setup, coordination, and self-improvement behind a small, removable project-local meta-harness. ## Product decision gate When an empty or evidence-poor repository and a broad request leave the intended user or recurring outcome open, inspect first and then ask one concise blocking question. Do not invent the product, stack, data source, or success metric. A request to adopt, install, or upgrade the harness in a repository that already contains work is not an open product decision. The observable result is the upgraded setup itself: an inspected capability roster, an adopted or upgraded agent team, and the project's own checks still passing. Do not ask the user what to build, and do not treat the setup request as too broad to act on. ## Claude Code unattended guard In a Claude Code print, SDK, headless, or otherwise non-interactive session, classify `.claude/**` as read-only before inspecting the roster. Never issue `Write`, `Edit`, or a shell command that targets anything under `.claude/**`; a denied write attempt is still a failed setup. Upgrade existing roles through `CLAUDE.md` and `docs/nulnul/`, and reserve profile edits for a later explicit manual request. If session mode is uncertain and the agent cannot ask permission interactively, use this read-only rule. ## Host entry ownership Detect the active host before any root-guidance write. A Codex run may cr