basic-custom-app-build

Coordinate Domo app builds across manifest, data, UI, and publish phases.

19|13|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill basic-custom-app-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: basic-custom-app-build
Source: https://github.com/stahura/domo-ai-vibe-rules/tree/main/skills/%28demo-skills%29/basic-custom-app-build
Command: npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill basic-custom-app-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the end-to-end Domo custom app build process by loading rules, sequencing capability skills, and tracking progress through manifest, data, UI, and publish phases. This skill helps teams start new Domo app projects, take over existing apps, or normalize apps to platform best practices.

Core Features & Use Cases

  • Rule loading and phase orchestration: loads rules and sequences skills across phases.
  • Progress tracking & governance: tracks progress through manifest, data, UI, and publish phases.
  • Onboarding for new or existing apps: used at project kickoff, during app takeovers, or normalization.

Quick Start

Kick off a new Domo app project by loading initial rules and starting the phase sequence for manifest, data, UI, and publish.

Frequently Asked Questions about basic-custom-app-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate an end-to-end Domo custom app build from scratch?

Orchestrate a Domo custom app build by loading initial rules and sequencing capability skills across the manifest, data, UI, and publish phases to enforce standardized development workflows.

What is the best way to normalize an existing Domo app to platform best practices?

Normalize an existing Domo app by loading explicit platform rules and orchestrating phase sequencing to track progress through the manifest, data, UI, and publish phases.

How do I track progress during a Domo app takeover project?

Track Domo app takeover progress by enforcing phase plumbing across the manifest, data, UI, and publish stages to ensure all capability skills are sequenced and executed.

Do I need explicit rules before starting the Domo app-build workflow?

Yes, explicit rules are required before starting the Domo app-build workflow because the orchestration sequence depends on loading them to govern the manifest, data, UI, and publish phases.

Can I use domo-js to automate project kickoffs for brand-new custom apps?

Automate project kickoffs for brand-new Domo custom apps by loading initial rules and triggering the phase sequence to coordinate the manifest, data, UI, and publish capabilities.

What are the limitations of orchestrating Domo app builds without phase sequencing?

Without phase sequencing and explicit rules, Domo app builds lack the standardized orchestration needed to properly track progress through the manifest, data, UI, and publish stages.