conjure-config

/conjure-config — Manage Conjure Preferences

Conjure reads preferences from two optional plain-text files. Neither is required — conjure works without them.

• User-global: ~/.claude/conjure-config.md — applies across all projects
• Project-local: .claude/conjure-config.md in the current working directory — supplements or overrides global for this project

Both are just markdown files with sections of natural-language instructions. Conjure commands read them at startup and follow whatever is written there. You can say anything — output paths, naming rules, required tools, code style constraints, workflow steps, template content. If Claude can understand it, conjure will follow it.

---

Phase 0: Parse Arguments

Args	Action
(empty)	Interactive intake — ask what they want to configure
show	Print the current config (both files, labeled)
remove <type>	Remove a specific section (skills, agents, hooks, mcp, global)
reset	Clear a config file (confirm scope and confirm deletion)
Any other text	Treat as a description of the desired preference — go to Phase 2

---

Phase 1: Show Current Config (if show)

Read both config files and print them formatted:

~/.claude/conjure-config.md (global)
─────────────────────────────────────
[contents or "(empty)"]

.claude/conjure-config.md (project-local)
─────────────────────────────────────────
[contents or "(not found)"]

Done. No further phases needed.

---

Phase 2: Interactive Intake

If the user gave a description in $ARGUMENTS, use it as starting context. If they gave nothing, ask:

"What do you want conjure to do differently? Describe it however you like — a folder path, a naming rule, a code style requirement, a template, anything."

Then ask targeted follow-up questions via AskUserQuestion to get clarity. Use your judgment about what's ambiguous — not every answer needs follow-up. Common gaps to probe:

• Scope: does this apply to all conjure commands, or just one type (skills / agents / hooks / mcp)?
• Always vs. default: should this always happen, or only when no other instruction applies?
• Path ambiguity: if they gave a relative path, confirm the absolute path
• Condition: does this apply in all situations, or only when a condition is met?
• Conflicts: if this contradicts something already in the config, ask which wins