mcpField
A
ai-app

ai-app

github.com/laguaguDevelopment70191 installsUpdated 2d ago
Repository

About ai-app

A skill for planning and implementing AI applications while retaining the project's existing stack and SDK major. It guides developers through version selection, server-side credentials, user flows, and integration checks.

Key features

  1. 01Resolve AI SDK and provider versions
  2. 02Keep credentials and authorization server-side
  3. 03Build the smallest complete user flow
  4. 04Match server streams to client transport
  5. 05Verify turns, tool states, and failures

Use cases

  1. 01Starting a new AI application
  2. 02Adding chat to an existing stack
  3. 03Implementing an agent dashboard
  4. 04Validating a streamed multi-turn flow

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/laguagu/claude-code-nextjs-skills --skill ai-app

After installing, type/ai-appin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
agent-dashboard.md
chatbot.md
examples.md
project-structure.md

Details

From the project README

AI application setup

Build the requested app around its users, data and operations. Keep the existing stack and SDK major unless migration is part of the task; use Bun for new JavaScript projects.

  1. Resolve the installed AI SDK major through ai-sdk; use ai-sdk-6 or ai-sdk-7 for implementation. For a new app, default to AI SDK 7: ai@7, @ai-sdk/react@4 and each provider package at latest (provider majors differ; Node.js 22+). Keep v6 only when a required dependency pins it. AI Elements still targets v6, and its context.tsx fails a v7 typecheck until patched (see ai-elements). Read version-matched ai/docs/ and provider docs before using web examples.
  2. Use nextjs-shadcn for framework setup and frontend-design for visual direction. Use ai-elements when its components fit the required chat UI; inspect installed source instead of assuming registry props.
  3. Keep provider credentials and authorization on the server. Resolve model IDs from configuration or the selected provider's catalog.
  4. Implement the smallest complete user flow. Add persistence, approvals, attachments, search, suggestions or dashboards when the app needs them.
  5. Match the server stream to the client transport. Verify a second turn, relevant tool states, safe failures and mobile behavior, alongside the project's typecheck/build.

Read for the app being built

  • Chatbot: conversation and stream contracts.
  • Agent dashboard: execution, approval and run state.
  • Examples: current official implementations.
  • Project structure: boundaries without a fixed tree.
  • nextjs-chatbot: durable history, feedback, embedding and production checks.

These references describe requirements, not copyable production templates.

Comments

Markdown supported