Skip to content
Back to Learn
10Creation12 min readIntermediate

GUIDE 10 · CREATION

Create a Full Skin Draft

The Studio collects bounded declarations and source images. A trusted generator, not the author, produces package JavaScript, CSS, archive structure, and digests.

Last verified
Sep 6, 2026
Guide source baseline
0.1.3-alpha.1
Installation status
Check the selected item’s record
Verified scope
  • Studio image and token constraints
  • Declarative FullSkinManifestV3 inputs
  • Simulated-preview boundary
On this page
  1. Work inside the declarative boundary
  2. Understand what the trusted generator owns
  3. Turn a visual idea into a draft

Work inside the declarative boundary

  1. 01

    Upload an eligible source image

    The current Studio accepts decodable JPEG, PNG, or WebP within its byte, pixel, dimension, page-count, and minimum-edge limits.

  2. 02

    Set focus and a controlled preset

    Choose the focal point, then tune glass, outline, or glow parameters. These bounded inputs drive generated output.

  3. 03

    Complete all 13 token pairs

    Provide valid light and dark hexadecimal values for every fixed semantic token and resolve any contrast failures.

  4. 04

    Declare source and rights

    Record whether the image is original, user-owned, licensed, public-domain, or generated. Licensed material needs its required source information.

  5. 05

    Save and submit the draft

    Review the declaration as a draft. Submission starts moderation; it does not turn the simulated preview into release evidence.

Understand what the trusted generator owns

  • Authors submit JSON declarations and image inputs, not CSS, HTML, JavaScript, dependencies, or lifecycle scripts.
  • The generator creates the fixed Host and Client integration, skin CSS, content-addressed WebP assets, manifest, tar, and tgz.
  • Generated CSS can target only the authenticated selector catalog and reference same-package content-addressed assets.
  • Keep the five required roles: background, sidebar, card, preview-light, and preview-dark. Separate dark artwork can add background-dark and sidebar-dark. Runtime screenshots belong in the preview roles; they must not replace the artwork used as the interface background.
  • The final artifact is rebuilt after moderation evidence is complete; a draft digest is not publication authority.

Create and continue

Turn a visual idea into a draft

Choose a clear visual subject and prepare separate light and dark artwork. Use Studio to describe the surfaces and assets, then test the built draft inside the target Harness before requesting publication.

text
Create a Full Skin draft from this artwork with separate light and dark assets. Preserve readable text and visible controls. List source and license information, build the draft, and test it in the target Harness before calling it ready.
A prompt to try

Common questions

Before you make a change

Answers about formats, compatibility, evidence, and rollback.

What does this guide verify?

This guide covers: Studio image and token constraints; Declarative FullSkinManifestV3 inputs; Simulated-preview boundary

What should I do first?

The Studio collects bounded declarations and source images. A trusted generator, not the author, produces package JavaScript, CSS, archive structure, and digests.

Which boundary matters most?

They help position artwork and tune tokens, but they are not screenshots of a final tgz running in DSH. A Full Skin cannot pass publication with simulated preview metadata.

Can I submit only a generated image?

An image can begin the design, but a publishable Skin also needs its declarative configuration, source and rights details, built package, and runtime checks.

Continue learning

Continue from the verified evidence

Compare published artifacts or return to the installation documentation.