Starlight Design Intelligence
Owned methodology, reusable skill system, premium taste layer.
This repo is the source of truth for how FrankX, Starlight Intelligence Systems, Arcanea, and related products should look, move, explain themselves, and earn release approval.
Operating Thesis
AI can generate interfaces quickly. The scarce layer is judgment: hierarchy, restraint, interaction quality, motion, brand memory, visual proof, and the ability to make every product feel like it belongs to a coherent world.
Starlight Design Intelligence turns that judgment into reusable brand packs, skills, rubrics, examples, and motion systems.
Repo Roles
| Area | Purpose |
|---|---|
brand-packs/ | Brand-specific design, copy, product, token, and motion doctrine. |
skills/ | Canonical executable design-intelligence skills. Personal/plugin installations are derived snapshots. |
plugins/ | Derived installable packages, supporting contracts and offline design tools. |
evals/ | Rubrics and checklists for anti-slop review, premium brand scoring, and UI quality. |
benchmarks/ | Dated external-skill and tool comparisons with explicit adoption boundaries. |
examples/ | Before/after examples showing the quality delta this system should produce. |
scripts/ | Deterministic validators for the kernel and release evidence. |
portfolio/ | Canonical repository-to-brand, core-surface adoption, and toolchain-boundary requirements. |
observatory/ | Governed target registry, hash-only evidence manifests, normalized extractions, abstract patterns, and domain selections. |
Brand Boundaries
| Brand | Visual Mode | Motion Mode | Copy Mode |
|---|---|---|---|
| FrankX | clear, founder-led, commercially sharp | direct, fast, useful | practical, strategic, no mythic language |
| Starlight / SIS | calm operational intelligence | precise, evidence-driven, command-center motion | trustworthy, systems-literate, enterprise-ready |
| Arcanea | mythic creative intelligence | cinematic, ritual, luminous transformation | poetic but concrete, never generic fantasy fog |
| Vibeclubs | embodied creator/social energy | warm, rhythmic, sensory | inviting, participatory, culture-forward |
Relationship To Other Repos
awesome-design-agent-skills: public design-agent curation.awesome-motion-design-agent-skills: public motion-agent curation.motion-design-studio: optional motion-production adapter; it is not a canonical dependency until a real, installable repository exists.visual-intelligence: tooling and GitHub Action layer for asset and visual QA.ux-design: private historical Playwright bootstrap and proprietary license record; preserve as a read-only tooling capsule, not a design authority.starlight-agent-skills: portable substrate skills for Starlight/SIS runtime consumption.
There is no separate starlight-design-agent-skills authority. Creating another canonical layer would increase drift. Installations must retain a source reference to this repository and pass npm test before release.
Living Design plugin
Starlight Living Design connects four proposed visual families to twelve character/role recipes, six design skills, and an offline identity and capability atlas. The six skills under skills/ are canonical; node scripts/sync-living-design-skills.mjs regenerates their package copies. Source tests enforce matching content. Private reference artwork is excluded from Git. Runtime binding, brand acceptance, and product deployment remain separate integration work.
Design Observatory
This repository is also the single portfolio design observatory. Reference sites are separated by stable target IDs, not repositories. Raw third-party screenshots, HTML, and crawler bundles stay in private content-addressed storage; Git contains only provenance, hashes, normalized observations, explicit inferences, abstract patterns, and owned domain direction records.
Every active domain resolves to exactly one matching human-readable and runtime brand pack. observatory/retrieval-index.json provides the deterministic path from domain to brand, selected patterns, and latest supporting snapshots. See observatory/GOVERNANCE.md before capture or synthesis.
Design Contract Mesh
The portfolio shares one release protocol, not one visual costume. A downstream
repository adopts starlight.design_contract.v1 at
.starlight/design-contract.json and calls
.github/workflows/design-contract.yml at a full immutable commit SHA.
The contract pins the raw Git-blob digest of its brand pack, its local design sources, core surfaces, claim classes, and release-evidence convention. The validator owns the canonical kernel, workflow, registry, and brand-pack paths; downstream files cannot redirect those authorities. Brand-local surface modes keep FrankX, SIS, Arcanea, and GenCreator visually distinct.
Adoption is successful only when the reusable workflow verifies the trusted caller repository, exact kernel checkout, brand ownership, full surface set, tracked non-symlink local contracts, and structurally parsed caller workflow. Registry inclusion is the requirement; there is no self-reported “adopted” flag.
Standards
The Starlight material foundations
provide a candidate lab workbench for glass, porcelain, obsidian, texture,
depth and finite star motion. Its bounded token contract is checked by
npm run validate:foundations and normal kernel validation. It extends the owned
identity through inspectable materials; it does not assert portfolio adoption.
- Replace vague taste language with implementation guidance.
- Include motion and reduced-motion rules for every high-value product surface.
- Prefer real product screenshots, workflows, and before/after examples over abstract decoration.
- Preserve brand separation. Arcanea can be mythic; Starlight must remain high-trust.
- Use public repos for authority and discovery; use this repo for owned differentiation.
- Build logos as editable vectors and pass small-size, monochrome, similarity, source, and lockup-family checks before effects or 3D applications.
- Record font identity, files, source, rights evidence, intended uses, specimens, computed production fonts, and fallback behavior before release.
- External agent skills accelerate a named stage; they never become implicit brand authority or production proof.
- A public flagship release requires current desktop/mobile source capture, exactly three visual directions, independent editorial and visual verification, and production/rollback proof.
- Production proof is emitted after deployment as an external CI artifact or a later receipts commit; it is never embedded in the production commit whose SHA it records.
Product outcome evaluation
Product outcome release standard connects the existing design contract to complete customer journeys, deployment-bound verification, portable agent instructions, and accepted-output economics. It is a proposed operational standard; product repositories retain their decisions and require their own verified adoption.
Experience coherence
Use the portfolio experience standard to turn
reference mechanisms into original brand-specific user journeys. The dated
contract and upgrade queue covers all
registered surfaces without claiming identity approval or production adoption.
Run npm run validate:experience; export an exact source bundle with
npm run export:brand -- --brand frankx --out /tmp/frankx-handoff. Existing
release and adoption validators remain authoritative.
Use the Figma template pipeline to pair editable collections with native implementations, explicit component/state maps and rights-cleared asset subsets. It extends the existing App Factory contract and the current Template Studio pilot rather than creating another catalogue.
Integrated design workflow
Portfolio design integration connects journey contracts, committed brand exports, source-pinned Figma imports, change impact planning and private content/asset evidence. These are accepted substrate capabilities; native execution and product adoption require separate proof.
Callable design toolkit
The skills-only plugin bundles the existing kernel with independently callable
Taste, Impeccable, Playwright CLI, Awesome Design and image-to-Three.js adapters.
All six upstream snapshots retain their original scripts, reference closure and
licenses. design-orchestrator routes the full loop while preserving the owning
brand pack. See integration and runtime boundaries.
Run npm run design:toolkit -- verify, npm run design:toolkit -- doctor, or
npm run design:toolkit -- route taste. Build a committed candidate with
npm run build:plugin -- --out /absolute/output.zip. Runtime installation, host
loading, browser execution and downstream production adoption require their own
evidence.