Index of every page on this site: llms.txt
All skills
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/imawais-engineer/skills/ai-app-builder

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈95 tokens for metadata: the name and description. ≈670 when used: this file. ≈49 more on demand in 1 file.

Description uses 4.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈379 characters, or 4.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts26d2 checks · Risk LOW
  • Socket26d

    No alerts

  • Snyk26d

    Risk: LOW · No issues

Signed by skilld at 5ecc5ec. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 5 days ago.

Activeupdated last week

README badge

README badge for imawais-engineer/skills/ai-app-builder