version: "1.0.4" name: customize description: > Guided customization of your Legal Builder Hub profile — change one thing without re-running the whole cold-start interview. Adjust practice profile, installed starter pack, watched registries, update preferences, or QA strictness. Use when the user says "change my [thing]", "add a registry", "update my profile", "edit my config", or "customize". argument-hint: "[section name, or describe what you want to change]"

/customize

When this runs

The user typed /legal-builder-hub:customize. They want to change something in their Builder Hub profile — a watched registry, update notification preferences, a practice area for recommendations — without re-running the whole cold-start interview and without hand-editing YAML.

What to do

1. Read the config. Read

~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md (and ~/.claude/plugins/config/claude-for-legal/company-profile.md one level up). If the plugin config does not exist or still contains [PLACEHOLDER] values, say:

> You haven't run setup yet. Run /legal-builder-hub:cold-start-interview > first — customize is for adjusting a profile you already have.

1. Show the customizable map. List what's in the profile, grouped, with a

one-line summary of the current value:

• Company / who you are — name, industry, jurisdictions, stage, practice

setting (shared across all 12 plugins — changes flow through `company-profile.md`)

• Your practice profile — practice areas in scope, used to recommend

community skills

• Installed starter pack — which plugins and skills are installed via

the hub, with install source

• Watched registries — GitHub repositories / URLs the hub pulls

community skills from

• Update preferences — check cadence (daily / weekly / on demand),

notification channel (Slack / in-session), auto-update vs. prompt

• QA strictness — how aggressively /skills-qa flags issues on a candidate

skill before install (lenient / middle / strict), and which failure-mode checks are on

• Skill install defaults — install scope (user / project), whether

to run /skills-qa automatically before install

• Integrations — Slack / document storage status, fallbacks

1. Ask what they want to change.

> What would you like to adjust? Pick a section, or describe the change in > your own words.

1. Make the change. Show the current value, ask for the new value, explain

what changes downstream, confirm, write it to the config.

Examples:

• Adding a new watched registry: "/registry-browser will search this registry

alongside the existing ones. /auto-updater will check it on its next run."

• QA strictness strict → middle: "/skills-qa will report the same findings

but not block install on the medium band unless you confirm."

• Auto-update on → off: "The hub will prompt you before applying

updates instead of applying them automatically."

1. For shared-profile changes (company name, industry, jurisdictions,

practice setting, stage): write to ~/.claude/plugins/config/claude-for-legal/company-profile.md and note:

> This change affects all 12 plugins — any plugin that reads your > jurisdiction footprint now sees [new value].

1. Close.

> Done. Your next output will reflect the change. Anything else? You can > run /legal-builder-hub:customize anytime.

Guardrails

• Never delete a section. If the user wants to "remove" a watched

registry, offer to mark it [Paused] and explain that pausing keeps the install history but stops update checks.

• Flag internal inconsistency. If the change would make the profile

inconsistent (e.g., auto-update on + QA strictness off; or practice profile that doesn't match any installed plugin), flag the tension.

• Flag guardrail degradation. The Legal Skill Design Framework checks

(nine design parameters, three legal failure modes, trust-surface check) are what /skills-qa exists to run — turning them off defeats the point. If the user wants to lower strictness, recommend the middle band rather than disabling the check.

• One change at a time. Don't re-ask the whole interview.