Build ChatGPT Apps using the Apps SDK and MCP. Use when users want to: (1) Evaluate if their product should become a ChatGPT App (2) Design and implement MCP servers with widgets (3) Test apps locally and in ChatGPT (4) Prepare for App Store submission Triggers: "ChatGPT app", "Apps SDK", "build for ChatGPT", "ChatGPT integration", "MCP server for ChatGPT", "submit to ChatGPT"
Build production-ready ChatGPT Apps from concept to App Store submission.
New app? → Start at Phase 1 (Fit Evaluation)
Have app-spec.md? → Start at Phase 3 (Implementation)
App built? → Start at Phase 4 (Testing)
Ready to ship? → Start at Phase 5 (Deployment)
Goal: Determine if a ChatGPT App is right for this product.
Ask the user:
Evaluate against three value pillars (see fit_evaluation.md):
| Pillar | Question | Strong Signal |
|---|---|---|
| Know | Does it provide data ChatGPT lacks? | Live prices, user-specific data, internal metrics |
| Do | Can it take real actions? | Create, update, delete, send, schedule |
| Show | Can it display better than text? | Lists, charts, maps, media galleries |
Minimum requirement: At least one pillar must be strong.
Review fit_evaluation.md for:
Draft prompts for discovery testing:
Create the specification file:
# [Product Name] ChatGPT App Spec
## Product Context
- Name: [Product name]
- API Base: [API URL]
- Auth: [Bearer token / OAuth / None]
## Value Proposition
- Know: [What data does it provide?]
- Do: [What actions can it take?]
- Show: [What UI is needed?]
## Golden Prompts
### Direct (should trigger)
1. ...
### Indirect (should trigger)
1. ...
### Negative (should NOT trigger)
1. ...
Output: app-spec.md in project directory
Goal: Define complete technical specification.
Follow one-job-per-tool principle. See chatgpt_app_best_practices.md.
For each tool, specify: