sc-provider

# /sc-provider — provider + secret control plane ## Language Keep durable instructions in English. **Reply in the user's language** unless they request another language. Use this whenever an agent needs to discover, configure, rotate, remove, or consume API/provider credentials. ## Non-technical default UX — mandatory SI-Coder is primarily for people who want a working web app, not an infrastructure lesson. **Lead with the outcome, hide the plumbing.** A valid user request can be as simple as: > "Create a salon booking app and put it on my domain." From that sentence, the agent should normally choose the stack, database/data service, hosting route, repository strategy, deployment method, domain records, and verification approach itself. Rules: 1. **Speak in goals:** "publish the app", "connect the account", "connect the domain", "store the app data". Do not lead with terms such as environment variable, DNS record, deploy key, compose, container, build pipeline, or provider routing. 2. **One user action at a time.** Never dump a setup checklist when only one permission/account connection blocks progress. 3. **Do not ask users to choose technology** unless they explicitly care. Choose sensible defaults and keep the technology name in optional technical details. 4. **Do not ask a question that tools/repo state can answer.** Inspect first, then ask only the unresolved product/domain/account decision. 5. **Credentials are framed as permissions, not secrets.** Say "I nee...