Start here

Cosmik brand guide

The complete guide to Cosmik identity, interfaces and implementation.

Start with Identity & usage, or choose a chapter below. This guide describes the shared Cosmik foundation. Markdown source ↗

Foundations

Page	What it covers
Identity & usage	Approved identity, names, clear space and reproduction.
Typography	Type roles, hierarchy and readable content.
Color & themes	Semantic colors, light and dark themes, and contrast.
Voice & imagery	Writing, imagery and icon guidance.

Experience

Page	What it covers
Interface	Layout, density, controls and responsive behavior.
Motion	Transitions and motion preferences.
Documents	Documents, templates and export review.

Implementation

Page	What it covers
Family contract	How product families build on the Cosmik foundation.
Integration	Using the foundation in websites and applications.
Baseline kit	The shared baseline kit, assets and tokens.
Quality review	Visual review, interactions and validation evidence.
Governance	Decisions, contribution, releases and upgrades.

Tools

Page	What it covers
Asset library	Approved artwork, fonts and downloads.
Design tokens	Searchable CSS names and resolved token values.
Component examples	Interactive examples of shared controls.

Resources

Page	What it covers
Document template	Document templates and export guidance.
Validation record	Checks and limitations for this reference.
Licensing & brand use	Code, artwork and font usage terms.
Changelog	Recorded changes to the kit.
Repository guide	Repository structure and contribution guidance.

About the foundation guide

The principles behind the Cosmik identity and interfaces. A complete HTML edition is generated from these sources; see the reference instructions for local preview and GitHub Pages publishing. Token values live in kit sources; the guide explains how to apply them. The interactive reference demonstrates behavior, while validation records distinguish tested results from remaining work. Guidance is implementation-agnostic: it defines visual and interaction contracts, not a website shell or a specific application flow. Platform-specific examples explain how to adapt the contracts, not which framework to choose.

Status words. Approved identifies an owner decision or accepted master. Proposed awaits a decision. Deprecated identifies retired material recoverable from Git history; it must not be selected for new work. Approval of an identity is separate from a product release or accessibility verification. Family guides, in each family's repository, identify its approved identities; the manifest records this kit's asset status and entry points.

Current positioning. Cosmik is an independent software company building tools for creating 3D structures and playable stories. Voice explains the company description and truthful product messaging; product families sets the relationship between independent product identities and the parent.

Superseded guides and retired artwork are recoverable from Git history. Current source guidance takes precedence.