client-vs-internal

# Client vs Internal > **Style:** Mode-B-lite. **Artifact-gated by default** — inert unless `docs/audience.md` exists or the operator explicitly requests the posture check. ## Purpose Client-facing teams build for two very different audiences. Clients need simplicity and trust (never Salesforce-complex); internal teams need robust controls and power-features. This skill applies the right posture to each surface, using the audiences defined at onboarding (or the audience the operator states when explicitly requesting the check). ## When to invoke - `docs/audience.md` exists AND a UI/app surface is being designed or built. - Operator says "is this for clients or internal", "simplify for the client", "this is an internal tool". ## Do not invoke when - **`docs/audience.md` absent and no explicit operator request** → silent no-op; do not activate or create it. - Non-UI / backend-only work with no audience-facing surface. ## Required inputs | Input | Where it lives | If missing | |---|---|---| | Audience definitions | `docs/audience.md` or the audience stated in an explicit operator posture-check request | **STOP — no-op** only when both are absent. Do not create the file; onboarding (`/onboard`) creates it. | | Surface being built | current task | nothing to classify; exit | ## Procedure 1. **Existence gate (FIRST STEP).** No `docs/audience.md` and no explicit operator posture-check request → exit silently. If the operator explicitly requested the check and stated the a...