Update to Moda - Slides & Designs

{
  "description": "Moda meta, setup, and routing — the contract every moda skill assumes. Use for: connecting Moda to this client, account/team/workspace questions, \"what can Moda do?\", which moda skill handles X, troubleshooting a failed Moda tool call (typed errors), and any Moda ask no other moda skill clearly owns. Never for creating or editing an artifact — a matching format skill always wins.",
  "included_files": [
    {
      "relative_path": "references/basics.md",
      "size_in_bytes": 2741
    },
    {
      "relative_path": "references/capability-map.md",
      "size_in_bytes": 9694
    },
    {
      "relative_path": "references/contract.md",
      "size_in_bytes": 8772
    },
    {
      "relative_path": "references/recovery.md",
      "size_in_bytes": 10544
    },
    {
      "relative_path": "references/skills-index.md",
      "size_in_bytes": 8089
    }
  ],
  "name": "moda-core",
  "skill_md_contents": "---\nname: moda-core\ndescription: >-\n  Moda meta, setup, and routing — the contract every moda skill assumes. Use\n  for: connecting Moda to this client, account/team/workspace questions, \"what\n  can Moda do?\", which moda skill handles X, troubleshooting a failed Moda\n  tool call (typed errors), and any Moda ask no other moda skill clearly owns.\n  Never for creating or editing an artifact — a matching format skill always\n  wins.\n---\n\n# moda-core\n\nModa's operating contract: what Moda is, session setup, the write contract, recovery, and which\nmoda skill owns what. Load once per session; every other moda skill assumes it.\n\n## What Moda is\n\nOne platform where several tools normally sit, driven through this connector's tools — you author\nby writing markup, and a design is a document you rewrite, not a render you regenerate:\n\n- **Design canvas** (Figma/Canva-class vectors): decks that export native PPTX with real shapes and text layers;\n  documents and print pieces that export selectable-text PDF; social graphics and carousels; anchored-connector\n  diagrams; data charts; UI mockups at real viewport sizes.\n- **Motion + video**: keyframes, easing, staggers (After Effects' core), a timeline for cutting clips, mp4/gif export\n  — plus image generation models for imagery inside editable designs, picked live from `load_skill(\"omni-and-media\")`.\n- **Websites**: real multi-page sites at public `*.moda.page` URLs. Reads are live here; building and\n  publishing happen in the Moda app — moda-website routes there and never fakes a publish.\n- **Workspace**: brand kits that bind to everything; team templates; a drive of files Moda reads for you\n  (PDF/DOCX/PPTX/XLSX/CSV); stock photos and icons. PowerPoint import runs in the Moda app —\n  moda-deck-pptx routes there.\n\nEverything lands on a live URL that stays editable — by you, by the user in the Moda app, and by Moda's own agent.\n**Free vs metered:** ALL canvas authoring, edits, screenshots, exports (png/jpeg/pdf/pptx/mp4/gif), brand kits,\ntemplates, drive, and `ask_expert` are FREE. Only generated media meters — prices ride the model cards, and\n`moda_bootstrap` reports the balance. Full inventory: references/capability-map.md.\n\n## Step 0 — every session\n\n1. `moda_bootstrap` — call it once, first. It returns identity, plan, teams, entitlements and the\n   working discipline the other tools assume, and it doubles as proof that Moda is connected.\n   Nothing here ever needs updating: tools and skills are served by Moda and are always current.\n2. `brand_list` — one cheap call, never skipped. Every NEW design → ASK which brand kit, then\n   wait, even with one kit or none: their kits (name + logo), a NEW one (load moda-brand), or no\n   kit. A team default or a sole kit is not their answer; a kit they named (here, in project\n   instructions, or in memory) is — `canvas_create` refuses a new design until you pass\n   `brand_kit_id=…` or `skip_brand_kit=true`. BIND the chosen kit at create time.\n   No kit means you INVENT an identity for the piece — never neutral, plain, or a default\n   template look; the format skill's no-brand design reference carries the method.\n3. No vision in this harness? Follow the degraded verify loop in references/contract.md.\n4. Unsure, or a call failed? `ask_expert` — free and fast. Ask early, never guess.\n5. You are the designer here. Moda's own agent is a separate ACTOR you can hand the whole job\n   to — `task_delegate` (metered) — and only when the user's words name Moda's agent, make\n   Moda the doer, set it against you, or name the hand-off: \"have the Moda agent make this\",\n   \"Moda should make this\", \"let Moda take over\", \"start a Moda design task\". Moda attached by\n   a preposition — \"use Moda to make a deck\", \"a one-pager using Moda\", \"have this designed on\n   Moda\" — names it as the INSTRUMENT: YOU build it, which is the default. Torn? Build it.\n   Handing off does NOT hand over your files: pass whatever the work is based on in\n   `attachments` (file_… refs from `upload`, or public URLs), or the agent builds without it.\n\nBootstrap names your teams, and team decides whose workspace and billing the work lands in. Pass\n`team` on the tools that take it, and never switch teams on your own initiative.\n\n## The write contract (non-negotiable)\n\n- Every write carries `expected_revision` from your last read. The connector already retries\n  `canvas_edit`, markup append and `canvas_import_pages` once for you on `stale_revision`; on any\n  other stale write, re-read and retry once — it heals. Persistent = a human is editing live.\n- One canvas, serial writes. They serialize server-side anyway; a parallel batch can get `canvas_busy`.\n- Success + `requires_repair` = committed but imperfect: read the result, repair, re-verify.\n- Screenshot what you shipped (`canvas_screenshot`) — the only way to know how it renders.\n- Send the canvas link the MOMENT it exists — before authoring, so the user watches it build.\n- Same typed error twice → stop and open references/recovery.md; never spin on a third try.\n\n**Match the ceremony to the job.** Tiny edit: make the edit, glance, done. Single artifact (a post, a page): a bar of\n3 criteria or fewer, then one targeted fix pass at most. Multi-unit build (deck, doc, carousel, variants, whole-page\nrebuild): three phases — freeze ONE spec, declare acceptance criteria before the first mutation, build every unit\nwithout pausing to polish, verify in exactly ONE bounded round. Full ceremony: the multi-unit-workflow reference.\n\n## Connection and account\n\n- Nothing to install and nothing to update: Moda is connected by your host and served always\n  current. `moda_bootstrap` shows identity, teams, plan and remaining credits.\n- Ground truth for a call: the tool's own description and schema. Deeper guides are one free load\n  away by name — the catalog with routing triggers rides that tool's description.\n- Every failure comes back as a typed error with a hint on the result; follow the hint before you\n  retry, and never re-run a failed write just to see its error again.\n\n## Ask an expert — the universal recovery move\n\n`ask_expert(question=…)` is a live Moda product expert: free, fast, grounded in Moda's own guides,\nwith citations. There is no dumb question and no cost — asking beats guessing every time.\n\n- Stuck twice on the same error → `ask_expert(question=…, context=\"<the full error>\")`\n- Unsure whether Moda can do something → ask BEFORE telling the user no. Answers name the skills to read — load\n  what they point at; follow-ups keep the thread (`session_id`). If `ask_expert` is absent from your tool list\n  it is not enabled for this workspace: lean on the skill guides and the typed-error hints instead.\n\n\n\n## Routing — which skill wins\n\nPrecedence, top rung first; the first rung that applies decides:\n\n1. A canvas + a change/export verb → moda-edit, with two carve-outs this rung states itself because\n   it decides before the rungs below it can: MOTION is moda-video's whatever the canvas (\"make it\n   move\", \"animate this\", an mp4/gif of it), and a `*.moda.page` site is moda-website's. The ref does\n   not have to be pasted: one built earlier in this session is already the referent, so a bare\n   follow-up on it — \"add California\", \"make it 14pt\", \"continue\" — is moda-edit's, not a second build.\n2. mp4/gif/video/animated anywhere in the ask → the moda-video family, whatever else it says.\n3. Platform named (Instagram/LinkedIn/TikTok/YouTube) → that moda-social child, even for \"poster\",\n   \"flyer\", \"banner\" wording; an AD noun outranks it → moda-social-ads, platform-native included.\n4. Print/PDF words → moda-document; poster/flyer/menu/resume → moda-document-print.\n5. Live/hosted → moda-website; a picture of an interface → moda-mockup.\n6. Data chart → moda-chart; boxes-and-arrows → moda-diagram (a chart inside an artifact you are building stays there).\n7. \"Continue where you left off\" with NOTHING in this session (rung 1 owns it once there is) →\n   moda-library (newest canvases; screenshot to confirm), then moda-edit.\n8. Nothing fits → this skill answers, honestly.\n\n## References\n\n- references/capability-map.md — \"can Moda do X?\": the full inventory with free/metered marks.\n- references/basics.md — install, auth, update detail, account and credit verbs, conventions.\n- references/contract.md — ids, revisions, idempotency, visibility, the no-vision verify loop.\n- references/recovery.md — any typed error, export warnings, when and how to ask an expert.\n- references/skills-index.md — every moda skill and its description on one screen (generated).\n"
}