obscura-launch-assets

name	obscura-launch-assets
description	Use when creating, revising, or reviewing Obscura branding assets, SVG logo/icon/favicon work, website images, screenshots, social previews, or Loom/hero motion video assets.

Obscura Launch Assets

Use this skill for Obscura logo/icon/favicon work, generated website imagery, real app screenshots, and Loom-style hero video planning.

Read First

1. docs/DESIGN.md
2. assets/branding/
3. docs/marketing/launch-asset-brief.md
4. docs/marketing/asset-logo-video-production-prompt.md
5. docs/marketing/motion-video-brief.md
6. docs/marketing/live-site-content-pack.md

Asset Rules

• Logo, app mark, icon source, and favicon source are SVG-first.
• Raster exports are allowed from the SVG source for Windows .ico, PNG app icons, social previews, screenshots, and generated website imagery.
• Generated images are allowed for the website hero, social preview, texture, and video backgrounds, but they must not pretend to be real app screenshots.
• Real app screenshots must come from the running app and must not show API keys, local private prompts, private paths, SQLite data, or generated media Jeff does not want public.
• Do not replace tracked app identity assets without updating README, CODEMAP, release docs, and packaging references.

Visual Direction

• Near-black digital darkroom.
• Violet exposure accent #7C5CFF.
• Cyan safelight accent #29C2C9.
• Off-white text #E6E8EF.
• Dense, precise, useful desktop software.
• Avoid mascots, cute camera cartoons, generic AI swirls, glossy 3D, and random unreadable UI text.

Website Video Rules

• A Loom-style hero video may be used for the external website.
• Prefer real app capture or clearly labeled mock/demo footage.
• If using generated imagery, keep it as atmosphere around real UI, not a fake product demo.
• Create both 16:9 and vertical crops only after the desktop hero cut works.
• Do not publish video files without Jeff's explicit approval.

Deliverables To Log

• Asset filenames and paths.
• Source prompts or capture instructions.
• Screenshots/videos captured and whether they are real, demo, or generated.
• GitHub issue comments for #5 website/docs and #6 launch assets when relevant.
• DEVLOG and CODEMAP updates for committed files.