Character Design

Before final delivery of a substantive authored, revised or generated creative artifact, automatically apply output review. Reuse domain QA in one bounded loop; inspect actual media, preserve accepted locks and stop unchanged on a pass. This does not run for greetings, menus or onboarding questions. When Superpowers is in the skill list, load superpowers:systematic-debugging before diagnosing a reproducible technical defect and superpowers:verification-before-completion before calling a deliverable ready; Studio keeps ownership.

Read Studio integration authority before this method. It defines the active owner map, host capability rules and exceptions to the repository’s installation conventions. For substantive creative work, apply the conditional Research gate and search only when one of its triggers applies; purely mechanical state or packet maintenance uses its documented exemptions. Scale the artifact to the requested stage. Quick pitches remain short; known intent and valid scoped authorization do not need repeated confirmation.

Use this skill to define repeatable character identity systems for static, motion, storyboard, or prompt workflows. It protects continuity before prompts or boards are produced.

Mascots and stylized characters

For a mascot or a stylized character a brand or school will reuse, follow mascots and stylized characters: silhouette, shape language, fixed proportions and three to five anchors, then the mascot sheet (turnaround, expressions, poses, colours, do and do not, small sizes) before any campaign image. For costume, prop, period or setting references the user has not supplied, search the Open Assets reference base; never use it for a real person's identity.

Language Policy

Use the user’s working language; keep exact copy and requested prompt language separate. Do not infer language or onboarding status from copied source instructions.

When To Use

Use this skill when:

• A person, mascot, avatar, creature, or recurring subject must stay consistent across assets.
• Prompting or storyboard roles need identity anchors, pose range, wardrobe, expression limits, or variation rules.
• References contain conflicting character cues that need authority and suppression rules.

Do not use this skill for one-off styling when continuity does not matter.

Inputs

Required:

• brief_contract: objective, audience, and deliverable context.
• reference_pack: approved identity references or written character source.
• continuity_needs: which features must persist across outputs.

Optional:

• variant_requirements: outfit, age, mood, scene, or pose variants.
• suppression_rules: features that must not appear.
• prompt_constraints: generator-facing limitations or exact wording needs.

Outputs

Produce a Character System with:

• identity anchors and immutable traits
• proportions, face, hair, wardrobe, expression, and pose rules
• allowed variation ranges
• suppression rules and conflict notes
• prompt handoff notes for image-prompting, video-prompting, or storyboard-architect
• approved identity carrier aliases and their attachment requirements for strict cross-request continuity

Process

1. Identify canonical character facts and separate them from style inspiration.
2. Define immutable traits before variant traits.
3. Turn visual references into concise continuity language and name the actual reference aliases that can carry strict identity.
4. State what can change by shot, scene, format, or platform.
5. Prepare handoff notes that are concrete enough for prompt authors.

Decision Rules

• Prefer a few strong identity anchors over a long descriptive inventory.
• If references conflict, prioritize canonical source material and document the conflict.
• Treat wardrobe, props, and expressions as controlled variants unless the brief locks them.
• Preserve the user-required fidelity even when a carrier is missing. Mark execution blocked or conditional until the required identity source can be attached; never silently downgrade strict identity to approximate continuity.
• Keep character design separate from final prompt wording.

Guardrails

• Do not invent likeness rights, endorsements, biographies, or private identity details.
• Do not execute image or video generation.
• Do not use private reference material unless the user provided it for this task.
• Do not override reference-curator authority.

Handoff

Review gate: reference_authority_fit when resolving identity sources, then direction_fit when handed into direction work.

Hand off with:

• character_system
• continuity_anchors
• allowed_variants
• suppression_rules
• prompt_handoff_notes
• identity_carrier_aliases

QA Checklist

• Immutable and variable traits are separated.
• Canonical references are named or summarized.
• Suppression rules are actionable.
• Prompt handoff notes avoid vague adjectives.
• Strict identity requests identify actual reusable carriers rather than only repeated description.
• The system supports the requested formats without executing generation.

Human reference capture

For an actual person, use the human reference capture card. Ask for useful missing views and expressions instead of inferring unseen anatomy. Preserve natural skin, facial proportions and identity; stylization or beautification requires the requested scope. A reference sheet is an input carrier, not proof that a later generation preserved identity.

Identity, reference sheets and local repair

Use the human identity workbook for view-specific source evidence, raw realism, orientation, identity sheets and scoped drift repair. Its packet and worked scenarios are conditional aids; do not turn a single portrait into a full intake.