Product manual
Use Lumo by workflow.
These docs are organized around the current app surface: Creator Profile, content calendar, Skills, Artifacts, YouTube subtitles, cover editing, and permissions.
Start in this order
If you are evaluating Lumo for the first time, this path follows the product as it is built today.
Download & Setup
Install iOS 1.3.1 where available, or download the signed Lumo 1.3.1 Mac DMG.
Creator Profile
Save your channel, audience, tone, and past scripts so new drafts start from your voice.
Content Calendar
Plan multi-platform entries and fan out scripts, metadata, and covers.
Skills and Artifacts
Use creator Skills, preview outputs, and keep useful artifacts in one place.
Guides by feature
Each page maps to an actual Lumo surface or workflow.
Getting Started with Lumo
Install on Mac, iPhone, or iPad; choose Cloud, Local Mac, or Remote Mac; then start your first project.
Creator Profile and Past Scripts
How channel info and 1-3 voice samples are reused in Creator Mode prompts.
Content Calendar and Multi-platform Fanout
Create entries, edit status, target platforms, and generate deliverables from a calendar item.
Scripts, Metadata, and Publishing Packs
Use Creator Mode and bundled Skills for scripts, metadata, platform rewrites, and Shorts plans.
Artifacts and Library
Preview Markdown, SRT, content calendars, cover artifacts, CSV, Mermaid, and saved outputs.
Cover Editor and Visual Prep
Generate cover-editor artifacts, adjust layers, add images and AI backgrounds, and export PNGs.
YouTube, Subtitles, and Voice Input
Use YouTube links, official captions, ASR fallback, subtitle actions, and voice transcription.
Skill Management
Install Skills from GitHub, create your own, enable bundled Skills, and trigger slash commands.
Input, Commands, and Context
Use @ context, artifact mentions, queued messages, slash commands, and memory commands.
Settings, Accounts, and Services
Understand account access, model providers, voice settings, YouTube/Gemini keys, and permissions.
Privacy and Permissions
How local sessions, files, artifacts, model requests, and tool approvals should be handled.
Feedback and Support
How to send workflow feedback and report issues that can be acted on.
Need a workflow clarified?
Send the project stage, the material you started with, and the output you expected.
Contact SupportDocs feedback
The most useful feedback is a missing step, a confusing screen name, or a mismatch with your build.
Email Us