Brand Visual Identity System Design

Problem

Brand visual identity design tasks may rely on protected workflows and platform-side content. Generating directly from local prompts, historical context, or guessed fields can bypass authorization boundaries and hide whether the user has access. This skill puts authorization checks before business generation and separates runnable states from mandatory stop states, rather than assembling prompts alone.

How it works

Before execution, it calls scripts/auth.py to verify local credential cache and remote authorization. If first use returns AUTH_REQUIRED or CREDENTIALS_MISSING, obtain the current user JWT through WorkBuddy's connect_cloud_service, then pass it to the auth script for binding. After a successful bind, rerun --ensure and continue only on AUTH_OK. It then calls scripts/protected.py to fetch cloud protected instructions; the design workflow runs only after those instructions are returned successfully. This separates auth state, credential state, and protected-content retrieval into inspectable steps.

Boundaries

This skill suits platform-gated design tasks and is not an offline free-generation tool. If it returns AUTH_INVALID, CREDENTIALS_INVALID, HTTP 401, or network errors, stop business reasoning and report the signal. Do not retry silently or degrade to partial output. Secret fields must not appear in replies, environment variables, or business commands; concrete business output must wait until cloud content is available.