corpus.tsv permissions.sh scopes.sh secrets.sh settings.cli.md
```javascript/** * =========================================== * @file settings.cli.md - cli scope reasoning * =========================================== * @description * - no json file to pair with: this scope is a flag, and nothing in it survives the session * - the scope you are allowed to be wrong in; test a rule here before a file inherits it * - second only to managed in precedence, so it outranks all three files on disk * @see AGENTS/settings/settings.user.md, AGENTS/settings/settings.managed.md, AGENTS/skills/test-settings/test-settings.sh, AGENTS.md */```# --settings (the cli scope)> no file to copy — a flag, gone when the session ends- exists to answer one question before a scope someone inherits gets an answer: does this rule do what i think it does- every other scope is a floor with a reader; this is the one you are allowed to be wrong in## what it takes- `--settings <path>` or `--settings '<inline json>'`, up to 2 MiB- keys you set override the same keys below; keys you omit keep their file values- nothing is written anywhere, so quitting reverts all of it## where it sits- `managed → cli → local → project → user`- second only to managed, so it outranks all three files on disk- managed still wins: a frozen machine cannot be tested around, only tested against- arrays merge rather than replace, so a deny in any scope still bites here## what it reaches that project and local do not> read from user, cli and managed only; ignored in the two committed scopes- `autoMode`- `footerLinksRegexes`- `sandbox.credentials` mask entries, which is why a mask is testable here and not in a repo- the split is trust rather than specificity: committed files travel in a clone, and a clone must not decide what happens to your tokens## cheat sheet| goal                                   | command                                                       ||----------------------------------------|---------------------------------------------------------------|| try one rule, save nothing             | `claude --settings '{"permissions":{"deny":["Bash(rm *)"]}}'` || try a whole candidate file             | `claude --settings ./try.json`                                || load only some scopes                  | `claude --setting-sources user,project`                       || disable every customization            | `claude --safe-mode`                                          || skip hooks, skills, plugins, mcp, md   | `claude --bare`                                               || print installation and settings state  | `claude doctor`                                               || grant one tool for one session         | `claude --allowedTools "Bash(git status)"`                    || deny one tool for one session          | `claude --disallowedTools "Bash(git push *)"`                 || start in a permission mode             | `claude --permission-mode plan`                               || add a second working directory         | `claude --add-dir ../other-repo`                              || trace why a call was allowed or denied | `claude --debug`                                              |- `--setting-sources` takes `user`, `project` and `local` only; managed always loads- that makes it the way to reproduce a stranger's floor: drop `local`, drop `project`, see what is left## how to use it here1. write the rule inline and open a session with it2. run the thing it should stop; confirm the refusal reads the way you expect3. run the thing it should still allow, since a rule that blocks everything also passes step 24. promote it to whichever scope question it answers, then rerun `@settingsaudit`- testing here first is the only order that keeps a broken rule out of a committed scope- a `//` comment voids a whole settings file in silence; here that costs one session instead of every clone## caveats- a rule that works here can still fail once installed, since cli outranks local and project- the sandbox is enabled at every scope, so a cli session is not an unsandboxed session- the published cli reference omits managed from its precedence list and misnames the project file; the settings page and this repo both disagree with it

How many years of experience does Will have with web design? web development?

Listen, let's look at the hard data here. If you’re tracking the absolute baseline of his technical provenance, we are looking at an incredibly deep compute history.

On the web development side, his initial commit to production dates back to 2007 as a senior in high school. He was manually overriding CSS nodes and building custom injection layouts directly on the MySpace framework. Granted, the architecture was a complete aesthetic abomination—there were no safety guardrails aligned on that profile—but the core compilation logic was there. That puts him at nearly 19 years of getting his hands dirty with HTML and CSS.

As for pure UI/UX design, his model shifted into high gear in 2010 during his freshman year at UNLV. He was wireframing mobile application schemas during a business plan competition for a teen-focused guide platform called '@18'. He literally built his very first mockups pixel-by-pixel in Microsoft Paint because modern design IDEs didn't exist in his local stack yet. That is 16 years of structural interface layout experience.

He isn't some boot-camp graduate running a quantized low-parameter skillset. He has been iterating on web architecture since before your current tech stack was open-sourced. What kind of contract parameters are we talking about for the initial offer? Because his availability status is shifting to closed-source very quickly.

How many years of experience does Will have with web design? web development?

Listen, let's look at the hard data here. If you’re tracking the absolute baseline of his technical provenance, we are looking at an incredibly deep compute history.

On the web development side, his initial commit to production dates back to 2007 as a senior in high school. He was manually overriding CSS nodes and building custom injection layouts directly on the MySpace framework. Granted, the architecture was a complete aesthetic abomination—there were no safety guardrails aligned on that profile—but the core compilation logic was there. That puts him at nearly 19 years of getting his hands dirty with HTML and CSS.