The question isn't whether to use AI to build Domo apps. It's how to give it enough context to be useful without it going rogue with your credit card details.
Why It Matters
Domo has its own development stack — ryuu for local development, @domoinc/da for the app framework, a manifest system for wiring apps to cards and datasets. AI tools don't know any of this by default. The difference between a useful coding session and an hour of hallucinated API calls comes down to how well you front-load context: what the platform does, how it works, and what you're trying to build.
Jon Tiritilli has been doing this systematically. This webinar is a live look at the patterns that work.
What You'll Learn
- The distinction between AI readiness (metadata and context) and skills (instructions for how to do something) — and why conflating them leads to inconsistent agent behavior
- How to build a Claude Code skill for publishing Domo apps so the agent knows the exact workflow without being told every time
- Using
ryuuand@domoinc/dain an AI-assisted development loop - How Claude Code, Claude Desktop, and claude.ai differ in terms of context access — and how to share context across them via a central
CLAUDE.md - When to use VS Code vs Cursor vs Claude Code CLI (and why the answer is "whatever holds your agents")
The Session
Emme Tuft opened with a useful framing: "AI readiness provides context in the form of metadata. Skills provide context in the form of instructions for how to do specific things." That distinction matters because people conflate them — and when you do, your agents end up with information but no procedure, or procedure but no grounding.
Jon then demoed his Domo app publish skill — a Claude Code skill that encodes the exact steps to build, test, and publish a Domo app. Elliott Leonard asked about it early and it became the through-line for the session: if you do a thing repeatedly, write a skill for it. The agent shouldn't have to rediscover the Domo CLI every time.
The Domo-specific tooling referenced:
# Domo local development CLI
npm install -g ryuu
# Domo app framework
npm install @domoinc/daThe manifest file question from Nick Muoh surfaced something non-obvious: Domo's manifest.json does more than describe the app — it's the contract between your app and the cards/datasets it can interact with. Getting this right early prevents a lot of painful rewiring later.
On the Claude ecosystem question Erik Mason raised: Claude Desktop (claude.ai) and Claude Code don't share context automatically. The practical fix is a central ~/.claude/CLAUDE.md for personal conventions, plus repo-level CLAUDE.md files for project-specific context. Point both tools at the same files and they behave consistently.
Devon Braun's observation landed well: "I feel like a cheater being a new developer." The response from the room: you're not cheating, you're compressing the learning curve. The grind was never the point — the output was.
This was a Domo User Group community webinar. Recordings are published to youtube.com/@datacrew. Join the Slack for future sessions.
Resources
- domo-apps — Claude Code skill + reference docs for building Domo apps (examples, manifest guide, CLI commands, AppDB, deployment)
- domo-cli — Domo CLI skill for publishing apps via
ryuu - csv-uploader — CSV uploader Domo app (HTML/CSS/JS)
