domains / families / software-engineering / app-builder

app-builder

combined

Builds and edits a model-driven Power Apps app from a natural-language intent — tables, columns, relationships, adaptive forms with sub-grids, views, Choice-column charts, business rules, business process flows, generative page intents for overview/dashboard surfaces (page `.tsx` generated in generate-pages after plan approval), and an app module + sitemap — via the headless cds-maker-sdk. Runs an interactive, multi-turn authoring flow (env selection, jobs-to-be-done first, then design-only App Spec authoring across confirmed levels, guardrail lint, plan-mode approval, generate-pages, full build) and a narrated build, and can download a deployed app back into an editable spec to change it. Use when the user says "build an app for X", "create a model-driven app", "make me an app to manage Y", "add a business process flow", or "edit/add to my app". This skill stands alone and does not require /genpage — but for a standalone generative page added to an app that already exists, use /genpa… Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.

When to use

When not to use

Skill page

Conflict

The two skills share the name 'app-builder' but describe fundamentally different procedures. The Microsoft skill is a domain-specific tool for building model-driven Power Apps using the cds-maker-sdk, focusing on data models, adaptive forms, and business process flows. The sickn33 skill is a general-purpose orchestrator for full-stack web/mobile applications, focusing on tech stack selection (Next.js, React Native, etc.) and multi-agent coordination. They do not overlap in steps or constraints; one is a specialized vertical tool, the other a horizontal scaffolding framework.