setup

---
name: setup
description: Use when the builder wants to set up, view or change their AI Studio website settings, such as approvals for merging or database changes, how much Claude explains, checking level, opener length, wording for the platform, or the design strictness default. Also use when the build or audit command offers it because no settings file exists.
---

# Setting Up Your AI Studio Preferences

## Overview

Saves the builder's usual choices once, so the other commands stop asking. Plain English, a few questions at a time.

**Core principle:** show what is there first, change only what the owner changes, keep everything else exactly as it is.

## Steps

1. **Find the file.** Look for `.claude/ai-studio-setup.md` in the project, then `~/.claude/ai-studio-setup.md`.
   - **A file exists:** before editing anything, show every current value in plain English, even when a change is named.
     - **Change already named:** skip the questions. State the one line you'll change (before, then after) and ask for their yes.
     - **Otherwise:** ask what they want to change.
   - **No file:** say so, and use `../../shared/setup-template.md` as the form, section by section.
2. **Say in a sentence what each choice does.** Mark each recommendation best practice or judgment call. "Ask first" before merging is best practice. "Go ahead" after launch is a judgment call: say once that merges then happen without a pause, and let the owner decide.
3. **Design strictness,** under Defaults, asked only when setting or changing it. `avoid-ai-design` and `design-taste-frontend` push against generic looks. Stronger rules make a site more distinctive but can fight a client who wants familiar and friendly. Ask for the builder's usual level; each project can differ:
   - **Light:** advice only. Nothing is rewritten, and the client's taste wins.
   - **Balanced** (the usual choice, judgment call): research and direction, then fix only defaults nobody chose. Anything the client chose is kept.
   - **Strict:** both skills at full strength, still under the client's brief.

   A blank line means Claude asks in each project.
4. **Change only what the owner changes.** Edit those lines in place. Every other line and section stays word for word, including notes and sections the template lacks. Never reword or tidy. Only if the owner is setting design strictness and the file lacks that line, add it under Defaults. Otherwise leave a missing line alone.
5. **Show the changed lines and wait for a yes,** then save.
6. **Never store secrets:** no passwords, API keys, tokens, logins or recovery codes. If offered one, decline and suggest a password manager.
7. **Save location.** Existing file: save back to it. If both exist, say which gets the change; the project file overrides the home one there. New file: `~/.claude/ai-studio-setup.md`, or `.claude/ai-studio-setup.md` if they ask. Never inside this plugin's folder.
8. **End** by saying where the file is, that plugin updates won't touch it, and that `/ai-studio-websites:setup` can be run again.

Publishing and switching Payments to live stay the owner's, whatever the settings say.