Ardoise

Run Claude on a blank slate. The spawned Claude sees only its training weights and built-in skills — no CLAUDE.md, no custom skills, no hooks, no plugins, no project context. Like a restaurant's ardoise wiped clean.

Two modes:

• Interactive (default) — opens Claude's TUI as a fresh user would see it. For manual testing: plugin installs, onboarding flows, "what does a new user experience?"
• Print (-p) — runs claude -p for automated/scripted use. For surveys, evals, cold critique.

When to Use

• Plugin testing — does claude plugin install work for someone with a default ~/.claude?
• Design research — what verbs, patterns, or names would a Claude naturally produce?
• Skill evaluation — does a naive Claude understand a SKILL.md on first read?
• Eval baselines — "without skill" control group for A/B testing
• Isolation testing — verify a prompt works without your ecosystem's context
• Cold critique — get feedback uncoloured by your conventions

When NOT to Use