chatgpt-apps
Complete ChatGPT Apps builder - Create, design, implement, test, and deploy ChatGPT Apps with MCP servers, widgets, auth, database integration, and automated deployment
What this skill does
# ChatGPT Apps Builder
Complete workflow for building, testing, and deploying ChatGPT Apps from concept to production.
## Commands
- `/chatgpt-apps new` - Create a new ChatGPT App
- `/chatgpt-apps add-tool` - Add an MCP tool to your app
- `/chatgpt-apps add-widget` - Add a widget to your app
- `/chatgpt-apps add-auth` - Configure authentication
- `/chatgpt-apps add-database` - Set up database
- `/chatgpt-apps validate` - Validate your app
- `/chatgpt-apps test` - Run tests
- `/chatgpt-apps deploy` - Deploy to production
- `/chatgpt-apps resume` - Resume working on an app
---
## Table of Contents
1. [Create New App](#1-create-new-app)
2. [Add MCP Tool](#2-add-mcp-tool)
3. [Add Widget](#3-add-widget)
4. [Add Authentication](#4-add-authentication)
5. [Add Database](#5-add-database)
6. [Generate Golden Prompts](#6-generate-golden-prompts)
7. [Validate App](#7-validate-app)
8. [Test App](#8-test-app)
9. [Deploy App](#9-deploy-app)
10. [Resume App](#10-resume-app)
---
## 1. Create New App
**Purpose:** Create a new ChatGPT App from concept to working code.
### Workflow
#### Phase 1: Conceptualization
1. **Ask for the app idea**
"What ChatGPT App would you like to build? Describe what it does and the problem it solves."
2. **Analyze against UX Principles**
- **Conversational Leverage**: What can users accomplish through natural language?
- **Native Fit**: How does this integrate with ChatGPT's conversational flow?
- **Composability**: Can tools work independently and combine with other apps?
3. **Check for Anti-Patterns**
- Static website content display
- Complex multi-step workflows requiring external tabs
- Duplicating ChatGPT's native capabilities
- Ads or upsells
4. **Define Use Cases**
Create 3-5 primary use cases with user stories.
#### Phase 2: Design
1. **Tool Topology**
- Query tools (readOnlyHint: true)
- Mutation tools (destructiveHint: false)
- Destructive tools (destructiveHint: true)
- Widget tools (return UI with _meta)
- External API tools (openWorldHint: true)
2. **Widget Design**
For each widget:
- `id` - unique identifier (kebab-case)
- `name` - display name
- `description` - what it shows
- `mockData` - sample data for preview
3. **Data Model**
Design entities and relationships.
4. **Auth Requirements**
- Single-user (no auth needed)
- Multi-user (Auth0 or Supabase Auth)
#### Phase 3: Implementation
Generate complete application with this structure:
```
{app-name}/
├── package.json
├── tsconfig.server.json
├── setup.sh
├── START.sh
├── .env.example
├── .gitignore
└── server/
└── index.ts
```
**Critical Requirements:**
- `Server` class from `@modelcontextprotocol/sdk/server/index.js`
- `StreamableHTTPServerTransport` for session management
- Widget URIs: `ui://widget/{widget-id}.html`
- Widget MIME type: `text/html+skybridge`
- `structuredContent` in tool responses
- `_meta` with `openai/outputTemplate` on tools
#### Phase 4: Testing
- Run setup: `./setup.sh`
- Start dev: `./START.sh --dev`
- Preview widgets: `http://localhost:3000/preview`
- Test MCP connection
#### Phase 5: Deployment
- Generate Dockerfile and render.yaml
- Deploy to Render
- Configure ChatGPT connector
---
## 2. Add MCP Tool
**Purpose:** Add a new MCP tool to your ChatGPT App.
### Workflow
1. **Gather Information**
- What does this tool do?
- What inputs does it need?
- What does it return?
2. **Classify Tool Type**
- **Query** (readOnlyHint: true) - Fetches data
- **Mutation** (destructiveHint: false) - Creates/updates data
- **Destructive** (destructiveHint: true) - Deletes data
- **Widget** - Returns UI content
- **External** (openWorldHint: true) - Calls external APIs
3. **Design Input Schema**
Create Zod schema with appropriate types and descriptions.
4. **Generate Tool Handler**
Use `chatgpt-mcp-generator` agent to create:
- Tool handler in `server/tools/`
- Zod schema export
- Type exports
- Database queries (if needed)
5. **Register Tool**
Update `server/index.ts` with metadata:
```typescript
{
name: "my-tool",
_meta: {
"openai/toolInvocation/invoking": "Loading...",
"openai/toolInvocation/invoked": "Done",
"openai/outputTemplate": "ui://widget/my-widget.html", // if widget
}
}
```
6. **Update State**
Add tool to `.chatgpt-app/state.json`.
### Tool Naming
Use kebab-case: `list-items`, `create-task`, `show-recipe-detail`
### Annotations Guide
| Scenario | readOnlyHint | destructiveHint | openWorldHint |
|----------|--------------|-----------------|---------------|
| List/Get | true | false | false |
| Create/Update | false | false | false |
| Delete | false | true | false |
| External API | varies | varies | true |
---
## 3. Add Widget
**Purpose:** Add inline HTML widgets with HTML/CSS/JS and Apps SDK integration.
### 5 Widget Patterns
1. **Card Grid** - Multiple items in grid
2. **Stats Dashboard** - Key metrics display
3. **Table** - Tabular data
4. **Bar Chart** - Simple visualizations
5. **Detail Widget** - Single item details
### Workflow
1. **Gather Information**
- Widget purpose and data
- Visual design (cards, table, chart, etc.)
- Interactivity needs
2. **Define Data Shape**
Document expected structure with TypeScript interface.
3. **Add Widget Config**
```typescript
const widgets: WidgetConfig[] = [
{
id: "my-widget",
name: "My Widget",
description: "Displays data",
templateUri: "ui://widget/my-widget.html",
invoking: "Loading...",
invoked: "Ready",
mockData: { /* sample */ },
},
];
```
4. **Add Widget HTML**
Generate HTML with:
- Preview mode support (`window.PREVIEW_DATA`)
- OpenAI Apps SDK integration (`window.openai.toolOutput`)
- Event listeners (`openai:set_globals`)
- Polling fallback (100ms, 10s timeout)
5. **Create/Update Tool**
Link tool to widget via `widgetId`.
6. **Test Widget**
Preview at `/preview/{widget-id}` with mock data.
### Widget HTML Structure
```javascript
(function() {
let rendered = false;
function render(data) {
if (rendered || !data) return;
rendered = true;
// Render logic
}
function tryRender() {
if (window.PREVIEW_DATA) { render(window.PREVIEW_DATA); return; }
if (window.openai?.toolOutput) { render(window.openai.toolOutput); }
}
window.addEventListener('openai:set_globals', tryRender);
const poll = setInterval(() => {
if (window.openai?.toolOutput || window.PREVIEW_DATA) {
tryRender();
clearInterval(poll);
}
}, 100);
setTimeout(() => clearInterval(poll), 10000);
tryRender();
})();
```
---
## 4. Add Authentication
**Purpose:** Configure authentication using Auth0 or Supabase Auth.
### When to Add
- Multiple users
- Persistent private data per user
- User-specific API credentials
### Providers
**Auth0:**
- Enterprise-grade
- OAuth 2.1, PKCE flow
- Social logins (Google, GitHub, etc.)
**Supabase Auth:**
- Simpler setup
- Email/password default
- Integrates with Supabase database
### Workflow
1. **Choose Provider**
Ask user preference based on needs.
2. **Guide Setup**
- **Auth0:** Create application, configure callback URLs, get credentials
- **Supabase:** Already configured with database setup
3. **Generate Auth Code**
Use `chatgpt-auth-generator` agent to create:
- Session management middleware
- User subject extraction
- Token validation
4. **Update Server**
Add auth middleware to protect routes.
5. **Update Environment**
```bash
# Auth0
AUTH0_DOMAIN=your-tenant.auth0.com
AUTH0_CLIENT_ID=...
AUTH0_CLIENT_SECRET=...
# Supabase (from database setup)
SUPABASE_URL=...
SUPABASE_ANON_KEY=...
```
6. **Test**
Verify login flow and user isolation.
---
## 5. Add Database
**Purpose:** Configure PostgreSQL database using Supabase.
### When to Add
- Persistent user data
- MulRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.