Keep development workflow within size budget

Condense the Codex configuration and app-directory guidance while retaining detailed XDG troubleshooting in the headless operation reference.

Author: mraible

skills/development-workflow/SKILL.md

@@ -146,37 +146,20 @@ foundry profile active   # Verify authentication
 foundry apps list        # Check existing apps (avoid name collisions)
 ```
 
-Before treating a missing profile as an authentication failure, normalize the
-configuration lookup for agents that override XDG paths:
-
-```bash
-export XDG_CONFIG_HOME="${XDG_CONFIG_HOME:-$HOME/.config}"
-foundry profile active
-```
-
-The Foundry CLI reads profiles from
-`$XDG_CONFIG_HOME/foundry/configuration.yml`. Do not point
-`XDG_CONFIG_HOME` at the app workspace or copy credentials into it. If the
-profile exists but the assistant cannot access that directory, request write
-access to the existing Foundry configuration directory and retry. If either
-command still fails, see
-[references/headless-operation.md](references/headless-operation.md) for setup
-options (env vars, non-interactive profile creation).
+Before diagnosing a missing profile, export
+`XDG_CONFIG_HOME="${XDG_CONFIG_HOME:-$HOME/.config}"`. Never redirect it into
+the workspace or copy credentials. See
+[headless operation](references/headless-operation.md) for access and
+authentication failures.
 
 ### Step 4: Scaffold the App
 
 **Prerequisite:** User must have confirmed the app name in Step 2. Do not run this without confirmation.
 
-Choose the app location without asking the user:
-
-1. If the current directory contains `manifest.yml`, use it as an existing app.
-2. If the current directory is not inside an unrelated repository, create the
-   app there.
-3. If the current directory is an unrelated repository, create the app as a
-   sibling under that repository's parent directory.
-4. If the selected parent is outside the assistant's writable sandbox, request
-   write access for that directory and retry the CLI command. Do not fall back
-   to putting the app inside the unrelated repository.
+Choose the location automatically: use an existing app when `manifest.yml` is
+present; otherwise create in the current directory, or beside it when the
+current directory is an unrelated repository. Request sandbox write access when
+needed; never put the app inside an unrelated repository as a fallback.
 
 ```bash
 foundry apps create --name "app-name" --description "description" --no-prompt --no-git