embed-portal
Build a Domo Embed Portal
This skill runs an end-to-end workflow: it gathers requirements, then delegates to existing capability skills for the Domo-specific implementation details. Do not duplicate content from those skills — read them at the appropriate step.
Sub-skills used:
programmatic-filters— Read-only embed token flow, server-side filters, dataset switchingedit-embed— Edit embed via Identity Broker, JWT auth, Domo rolesjsapi-filters— Client-side filtering, drill events, iframe communication
Phase 1: Gather Requirements
Before writing any code, collect three pieces of information. Ask conversationally — don't dump all questions at once. If answers are already clear from context, skip ahead.
1. Brand Guidelines
Ask: "What branding should the portal use? I need a color palette (primary, secondary, accent), fonts, and a logo if you have one."
More from stahura/domo-ai-vibe-rules
migrate-lovable
Convert SSR-heavy Lovable/v0 apps into client-only Domo apps.
60domo-js
Use ryuu.js (domo.js) APIs for env, events, navigation, and data calls.
59appdb
Toolkit-first AppDB document CRUD, query operators, and collection wiring.
57html-deck
Build a professional HTML slide deck from source content and convert it to a pixel-perfect PDF. Covers slide architecture, layout patterns, print-safe CSS, Puppeteer PDF conversion, and quality verification. Use when creating presentation decks, converting documents to slide format, or generating PDF decks from HTML.
57data-api
High-level entry skill for Domo data access. Routes detailed query work to dataset-query.
56jsapi-filters
Apply runtime filters to embedded Domo dashboards/cards from the host page via the JS API (MessagePort). Covers dynamic filtering, drill events, filter change listeners, iframe resize, pfilter URL params, overrideFilters, and App Studio appData. Use for any client-side Domo embed interaction. Not for server-side programmatic filters (use programmatic-filters).
56