2026-06-19T18-02-20-576Z-manifest-overlay

Imported from XposeMarket/PromSRC (workspace/skills/.history/prometheus-ash-archive-style/2026-06-19T18-02-20-576Z-manifest-overlay/SKILL.md). Install upstream with npx skills add XposeMarket/PromSRC --skill 2026-06-19T18-02-20-576Z-manifest-overlay. Copyright stays with the author.

Prometheus Ash & Archive Style

Use this skill when creating or judging Prometheus brand visuals, HyperFrames promos, website hero motion, launch videos, UI art direction, or any visual surface that should feel like Prometheus rather than generic AI software.

One-sentence direction

Prometheus should feel like an ancient intelligence operating through a modern local command center: part industrial field manual, part archival control room, part living desktop OS.

What this style is

Ash & Archive is a Prometheus-native visual language built from:

• archival documentary evidence;
• industrial/laboratory field manuals;
• pale bureaucratic dossier UI;
• local desktop/process proof;
• black negative-space boot moments;
• restrained mythic fire/ember symbolism;
• serious typography and machine traces.

The viewer should feel: this system is already working on the machine in front of me.

What this style is not

Do not make Prometheus look like:

• purple/blue/cyan AI SaaS gradients;
• neon glass dashboard reels;
• generic dark orb/particle/glow videos;
• friendly chatbot bubble branding;
• cyberpunk hacker cosplay;
• fake scientific HUD labels with no meaning;
• over-rounded glass cards everywhere.

Visual thesis

Prometheus is not another chatbot tab. It is a local operating layer: browser, desktop, memory, tasks, teams, creative tools, approvals, files, schedules, and external apps coordinated through one durable intelligence.

The style should make that coordination visible as evidence.

Core palette

Use the bundled palettes/ash-archive.md tokens by default:

• Obsidian black for boot/command scenes.
• Bone/off-white for dossier scenes.
• Charcoal/ash for rules and dark panels.
• Ember orange as Prometheus fire/action accent.
• Oxblood red for stamps/warnings/approval gates.
• Machine green for live/completed status.
• Brass only as a rare mythic seal/accent.

No default blue/purple gradients.

Typography system

Use three voices:

1. Myth / authority — editorial serif or engraved-feeling serif for identity moments and big claims.
2. Machine voice — monospace for logs, file paths, route IDs, timestamps, tool traces, memory indexes, and status lines.
3. Human/document voice — readable serif or serious sans for dossier cards, explanations, and UI proof.

Avoid generic Inter-only SaaS hierarchy unless the actual product UI requires it.

Texture system

Use texture to make the work feel found, recorded, and physical:

• paper grain;
• printer marks;
• light scanlines;
• photocopy degradation;
• subtle CRT/screen-capture softness;
• ruled forms, stamps, table rows;
• industrial/manual annotation lines.

Keep texture subtle enough that text stays readable.

UI language

Prometheus visuals should include actual or plausible product/process proof:

• file paths;
• local URLs;
• tool call traces;
• task cards;
• memory cards;
• approval gates;
• browser/desktop capture frames;
• generated artifact cards;
• team run status;
• schedule/automation rows.

Use thin rules, sharp blocks, paper slabs, status dots, stamps, and document panels. Rounded cards are allowed only when purposeful and not every panel.

Motion language

Prefer authored, intentional motion:

• document slides/reveals;
• mechanical shutters/wipes;
• stamped labels;
• cursor/log ticks;
• row-by-row activation;
• measured pan over UI evidence;
• abrupt confident editorial cuts;
• final quiet ember pulse.

Avoid making every object float, pulse, drift, glow, and scale. Motion should reveal structure and evidence.

Prometheus promo structure

A strong Ash & Archive Prometheus video usually follows this pattern:

1. Cold boot — black space, wake phrase, tiny ember mark, local status traces.
2. Operation proof — browser/desktop/files/tools/memory visible as real work.
3. Dossier mode — off-white UI panels, task rows, approvals, artifacts.
4. Scale layer — teams, schedules, external apps, creative, automations.
5. Meaning — not another chatbot; one operating layer for work and life.
6. Final mark — restrained Prometheus identity in darkness.

Copy tone

Use short, declarative lines:

• “A local intelligence layer.”
• “Browser. Desktop. Memory. Teams.”
• “Every action leaves evidence.”
• “Approvals stay human.”
• “The machine works where you work.”

Avoid vague hype like “unlock your potential” or “revolutionize productivity.”

QA checklist

Before shipping, verify:

• Dominant palette is not purple/blue/cyan gradient AI SaaS.
• The frame contains concrete Prometheus process proof, not just atmosphere.
• Any HUD/label text maps to real concepts.
• Rounded/glass panels are not the default surface language.
• Text remains readable over grain/scanlines.
• Motion reveals system structure rather than decorating empty space.
• The final identity moment is restrained and memorable.

HyperFrames-specific rule

For HyperFrames videos, combine this skill with hyperframes, hyperframes-cli, and the hyperframes resource references/avoid-ai-video-tells.md. Always render/export-verify the final MP4 before calling the video done.