Agent operating model
Margo projects are deliberately legible to coding agents: the configuration, source slides, assets, theme, archetypes, and agent guidance live in the deck directory. Generated dist/ output is not the source of truth.
An agentic workflow should read AGENTS.md, select the deck or theme-authoring skill, make narrow source changes, run margo build, and report the result. Theme templates and shortcodes are trusted local project code, so an agent should inspect imported theme content before running it.
The desktop app can prepare a prompt for a repository-local skill with deck root, active theme, selected slide/source paths, skill instructions, and referenced Markdown. The author copies that prompt to an agent with access to the same project; Margo Desktop does not execute the agent or modify a theme to enable tiling.
