---
name: ai-app-builder
description: Build complete AI-first applications with product workflow, prompts, model/provider boundaries, data storage, evals, cost controls, safety checks, UI, testing, and deployment readiness. Use when the app is primarily AI-based, includes chat, assistants, agents, RAG, generation, classification, extraction, copilots, workflow automation, or AI-assisted decisions.
title: ai-app-builder
canonical_url: https://skilld.dev/gh/imawais-engineer/skills/ai-app-builder
last_updated: 2026-11-14T09:15:25.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [agents/openai.yaml](https://skilld.dev/api/skills-raw/imawais-engineer/skills/ai-app-builder/agents/openai.yaml).
>
> If the user asked to install this Skill, run `npx skilld install imawais-engineer/skills/ai-app-builder`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/ai-app-builder`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/imawais-engineer/skills/ai-app-builder) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/ai-app-builder`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/ai-app-builder --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/ai-app-builder --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# AI App Builder

## Principle

Use AI intentionally only when it is central to the product. If AI is secondary, ask for approval before adding AI features. Keep the normal application complete: dashboard-first UI, real workflows, persistence, tests, auth after functionality, layered security, docs, and deployment.

## AI Application Blueprint

1. Define the core AI job: generation, extraction, classification, retrieval, recommendation, workflow automation, chat, agentic execution, or decision support.
2. Define the user workflow around the AI job, including inputs, review, editing, saving, exporting, and history.
3. Define required data: user content, prompts, model outputs, feedback, files, embeddings, tool results, cost/usage, and audit logs.
4. Define model/provider requirements without hard-coding current model assumptions. Verify provider docs before implementation.
5. Define safety boundaries: what the AI may do, what requires user approval, and what it must refuse or escalate.
6. Define validation: schema checks, output checks, user confirmation, evals, and fallback behavior.

## Build Order

1. Build the main app workflow and dashboard shell.
2. Build the AI happy path with controlled test data.
3. Store prompts, inputs, outputs, status, usage, and feedback when persistence is required.
4. Add prompt and output validation before saving important results.
5. Add retries, timeouts, streaming, cancellation, and error states where relevant.
6. Add auth, authorization, rate limits, usage quotas, and audit logs before stable release.
7. Add evaluation cases for quality, reliability, safety, and regression.
8. Document setup, environment variables, model/provider configuration, and operational limits.

## Required AI Components

Include these when relevant:

- Prompt templates or prompt builders
- Structured input and output schemas
- Model/provider adapter boundary
- Tool/function contracts
- RAG ingestion, retrieval, and citation path
- Conversation or job history
- Human review and approval flow
- Feedback capture
- Usage and cost tracking
- Safety and abuse controls
- Evaluation fixtures and expected behavior

## Ask Before Implementing

Ask before using external AI APIs, paid models, persistent user data, scraping, file ingestion, agentic actions, email/message sending, payments, or anything that changes external systems.

## Completion Check

AI app work is not done until:

- The core AI workflow works end to end.
- Outputs are validated before critical use.
- Failures are visible and recoverable.
- Required data is stored correctly.
- Cost, rate, and safety boundaries are defined.
- Verification and validation both pass.
