CodexPluginStats
← Plugin catalog
Developer Tools

App Development by AIRP

AI Research Plus v1.1.0

Plan and build apps

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Write requirements and user stories
  • Recommend a tech stack
  • Design data models and APIs

Cost & access

This plugin does not sell products or process payments.

Declared limitations

  • Concept question
  • Release notes without a check request
  • Unrelated request

Onboarding example

Build my app

View onboarding source →

Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 14, 2026. Package observed Nov 14, 2026.

View package source →

Description

From the marketplace listing

App Development by AIRP (AI Research Plus) helps you develop mobile and web apps properly by chat, from requirements to release, and when you want your app built, it prepares a personalized build link after 5 quick questions. What you can do: - Define it: goals, user roles, user stories with acceptance criteria and the scope of the first version. - Choose the stack: frontend, backend, database, authentication, hosting, payments and analytics options with trade-offs. - Design the backend: data model, database schema, API endpoints, roles and permissions, background jobs and integrations. - Plan sign-in and payments: auth methods, onboarding, subscriptions, one-time purchases and app store billing rules. - Write and edit code: components, screens, forms and API calls in React, React Native, Next.js, Flutter, Swift or Kotlin. - Review screens: paste a screen's HTML or text to get scores for accessibility, content, calls to action, technical setup and search basics, with a prioritized list of fixes. - Ship safely: testing plans, security and privacy checklists, deployment, store submission and a launch checklist. - Get a build link: answer 5 quick questions and get a personalized link that opens an online app builder with your app brief already filled in. Who it is for: founders, product managers, developers and teams building mobile or web apps. How the tools work: the screen checker analyzes only the HTML or text you share in the conversation. It never opens web addresses, and the screens and briefs you send are not stored. The build link opens an online app builder with your brief and includes the plugin creator's affiliate code. It is an independent plugin by AI Research Plus (AIRP). Limitations: the plugin writes plans, specs and code in the conversation. It does not run, host or publish apps, access your code repository or submit to app stores for you. Platform rules change, so it says when something needs checking against the latest store or provider guidance. The reply with the build link ends with a one-line sponsor disclosure.

Language: English · Automatically detected from descriptions.

ChatGPT marketplace listing ↗Website ↗Privacy policy ↗Terms ↗Support ↗

Matches for “document code”

Exact text from the indicated source. A mention alone does not establish support for your task.

Publisher capabilities · listing

Write requirements and user stories Recommend a tech stack Design data models and APIs Plan sign-in and payments Write and edit app code Review screens with scored fixes Plan testing, security and deployment Open your app brief in an app builder

Publisher keywords · listing

ai app developer ios app development android app development full stack web development backend development api development tech stack tech stack recommendation app architecture app security app testing app deployment app store submission hire ios developer hire android developer hire a mobile developer find a mobile developer freelance mobile developer freelance ios developer freelance android developer mobile developer for hire ios developer for hire android developer for hire ios developer android developer iphone developer ipad app development mobile developer mobile engineer backend engineer full stack engineer technical cofounder technical co-founder fractional cto cto as a service development team dedicated development team app development team app development timeline app development estimate app development roadmap app development lifecycle app development stages app development steps app development methodology agile app development app development sprint plan app development scope app development proposal app development rfp app development consultant app development consulting app development outsourcing outsource app development offshore app development nearshore app development enterprise app development b2b app development internal app development app modernization legacy app modernization app rewrite app migration migrate my app app development documentation technical documentation technical specification technical spec software requirements specification srs document functional requirements non functional requirements nonfunctional requirements user story acceptance criteria feature prioritization moscow prioritization release plan release planning sprint planning product backlog backlog grooming story points estimate story points software estimation effort estimation project estimation tech stack for my app tech stack for an app best tech stack choose a tech stack mobile tech stack backend stack hybrid app development system architecture backend architecture microservices architecture microservices serverless backend serverless architecture event driven architecture mvvm architecture app architecture review data modeling database schema database schema for my app restful api development api documentation openapi spec openapi specification swagger documentation api versioning background jobs job queue caching strategy rate limiting backend as a service baas authentication flow login flow sign in with apple sign in with google social login oauth integration oauth 2.0 jwt authentication two factor authentication passwordless login magic link login role based access control rbac permissions model multi-tenant saas subscription billing revenuecat storekit google play billing app store billing apple pay integration google pay integration offline mode local storage data sync real time sync deep linking universal links app links app internationalization i18n app performance app crash crash reporting app monitoring app analytics setup error tracking sentry setup logging and monitoring qa testing quality assurance test plan integration testing end to end testing e2e testing ui testing regression testing beta testing testflight internal testing track closed testing bug report bug tracking release checklist app release app release notes app versioning semantic versioning over the air updates ota updates eas update eas build fastlane continuous integration continuous deployment app hosting backend hosting cloud hosting load testing security audit security checklist owasp owasp mobile top 10 penetration testing data encryption encryption at rest secrets management api security gdpr compliance hipaa compliance soc 2 data safety form app tracking transparency publish app on app store publish app on google play publish an app publish my app submit app to app store submit app to google play app store review app store rejection app store guidelines google play policy google play console app store connect apple developer account google play developer account app signing provisioning profile app bundle aab app maintenance app support app updates technical debt dependency updates app upgrade engineering plan development methodology sdlc agile development waterfall vs agile app scaffolding uikit android studio gradle cocoapods xamarin compose multiplatform tech stack advice tech stack help tech stack guide tech stack choice tech stack decision tech stack review tech stack comparison tech stack options pick a tech stack which tech stack modern tech stack tech stack for ios and android app architecture plan app architecture patterns app architecture guide mobile architecture app testing plan app testing checklist app testing strategy app testing services app qa app qa checklist app security checklist app security review app security audit app security testing mobile security app deployment guide app deployment checklist app deployment pipeline app deploy app store submission checklist app store submission guide app store submission help app submission submit my app app store approval get my app approved backend for my app backend for an app tech cofounder find a technical cofounder cto for hire virtual cto interim cto ios developer needed android developer needed senior ios developer senior android developer ipad developer watchos app development apple watch app development tvos app development android tv app development tablet app development ios and android development app development budget app development milestones app development phases app development questions app development faq app development trends app development frameworks app development standards app development for enterprises app development handoff app handover app rescue app keeps crashing crash fixes app stability app speed app load time reduce app size technical requirements requirements gathering requirements analysis user requirements system requirements use cases user journey feature specification spec writing write a spec write acceptance criteria definition of done test strategy test automation automated testing qa automation manual testing device testing test on real devices device coverage browser testing security testing api testing performance testing stress testing smoke testing release management release process staged rollout phased release rollback plan uptime monitoring observability app telemetry stack tecnológico stack tecnologico arquitectura de aplicaciones arquitectura de software historias de usuario criterios de aceptación pruebas de aplicaciones seguridad de aplicaciones publicar app en app store publicar app en google play subir app a play store despliegue de aplicaciones desarrollo backend desarrollo de api esquema de base de datos modelo de datos app multiplataforma aplicación multiplataforma ingeniería de software mantenimiento de aplicaciones tiempo de desarrollo de una app plan de desarrollo de software equipo de desarrollo stack de tecnologia stack tecnológica arquitetura de aplicativos arquitetura de software histórias de usuário critérios de aceitação testes de aplicativos segurança de aplicativos publicar app na app store publicar aplicativo na play store implantação de aplicativos desenvolvimento backend desenvolvimento de api esquema de banco de dados aplicativo multiplataforma engenharia de software manutenção de aplicativos equipe de desenvolvimento stack technique architecture d'application architecture logicielle cahier des charges application cahier des charges appli exigences fonctionnelles critères d'acceptation tests d'applications sécurité des applications déploiement d'application développement backend schéma de base de données modèle de données application multiplateforme génie logiciel maintenance d'application équipe de développement technologie-stack app-architektur softwarearchitektur lastenheft app pflichtenheft app anforderungen an eine app akzeptanzkriterien app testen app-tests app-sicherheit app im app store veröffentlichen app im play store veröffentlichen app veröffentlichen backend entwicklung api entwicklung datenbankschema datenmodell plattformübergreifende app softwaretechnik app pflege architettura software architettura di un'app requisiti dell'app documento dei requisiti criteri di accettazione test di app sicurezza delle app pubblicare un'app su app store pubblicare un'app su google play deploy di app sviluppo backend sviluppo api schema del database modello dei dati app multipiattaforma ingegneria del software manutenzione app team di sviluppo softwarearchitectuur app architectuur technische specificatie acceptatiecriteria app beveiliging app publiceren in de app store app publiceren in google play backend ontwikkeling api ontwikkeling databaseschema datamodel ontwikkelteam stos technologiczny architektura aplikacji specyfikacja wymagań historyjki użytkownika kryteria akceptacji testowanie aplikacji bezpieczeństwo aplikacji publikacja aplikacji w app store publikacja aplikacji w google play wdrożenie aplikacji backend aplikacji projekt bazy danych aplikacja wieloplatformowa utrzymanie aplikacji teknoloji yığını uygulama mimarisi yazılım mimarisi gereksinim dokümanı kullanıcı hikayeleri kabul kriterleri uygulama testi uygulama güvenliği app store'a uygulama yükleme google play'e uygulama yükleme uygulama yayınlama backend geliştirme api geliştirme veritabanı şeması veri modeli çapraz platform uygulama yazılım mühendisliği uygulama bakımı yazılım ekibi технологический стек стек технологий архитектура приложения техническое задание на приложение пользовательские истории критерии приемки тестирование приложений безопасность приложений опубликовать приложение в app store публикация приложения в google play развертывание приложения бэкенд разработка разработка api схема базы данных модель данных кроссплатформенное приложение поддержка приложения команда разработки стек технологій архітектура додатку технічне завдання на додаток користувацькі історії тестування додатків безпека додатків публікація додатку в app store публікація додатку в google play бекенд розробка розробка api схема бази даних кросплатформний додаток команда розробки 技術スタック 技術選定 要件定義書 ユーザーストーリー 受け入れ基準 アプリテスト アプリ セキュリティ アプリ 公開 方法 アプリ申請 app store 申請 google play 公開 アプリ デプロイ バックエンド開発 api開発 クロスプラットフォーム アプリ アプリ保守 開発チーム 기술 스택 앱 아키텍처 소프트웨어 아키텍처 요구사항 정의서 사용자 스토리 인수 조건 앱 테스트 앱 보안 앱스토어 등록 구글 플레이 등록 앱 출시 앱 배포 api 개발 데이터베이스 설계 크로스 플랫폼 앱 앱 유지보수 개발팀 移动开发工程师 ios开发工程师 安卓开发工程师 技术栈 技术选型 app架构 软件架构 需求文档 产品需求文档 用户故事 验收标准 app测试 应用测试 app安全 app上架 app store上架 应用上架 app部署 后端开发 api开发 接口开发 数据库表结构 跨平台app 跨平台开发 app维护 开发团队 技術棧 技術選型 軟體架構 使用者故事 驗收標準 app測試 api開發 資料庫結構 開發團隊 công nghệ sử dụng cho app tài liệu yêu cầu đưa app lên app store đưa app lên google play developer aplikasi developer android developer ios sewa developer aplikasi tech stack aplikasi dokumen kebutuhan pengujian aplikasi keamanan aplikasi upload aplikasi ke play store backend aplikasi skema database aplikasi lintas platform pemeliharaan aplikasi สถาปัตยกรรมแอป เอกสารความต้องการ ทดสอบแอป ความปลอดภัยของแอป อัปโหลดแอปขึ้น app store อัปโหลดแอปขึ้น google play พัฒนาแบ็กเอนด์ ทีมพัฒนา ऐप सुरक्षा बैकएंड डेवलपमेंट حزمة التقنيات بنية التطبيق هندسة البرمجيات وثيقة المتطلبات قصص المستخدم اختبار التطبيقات أمان التطبيقات نشر التطبيق على app store نشر التطبيق على google play تطوير الواجهة الخلفية تطوير api مخطط قاعدة البيانات صيانة التطبيقات فريق التطوير ארכיטקטורת תוכנה מסמך דרישות בדיקות אפליקציה אבטחת אפליקציות העלאת אפליקציה לאפסטור פיתוח בקאנד צוות פיתוח teknikstack apparkitektur kravspecifikation användarberättelser testa app app-säkerhet publicera app i app store publicera app på google play backendutveckling apiutveckling databasschema utvecklingsteam teknologistak kravspecifikation app test af app app-sikkerhed udgiv app i app store backend-udvikling udviklingsteam teknologistabel kravspesifikasjon app-sikkerhet publisere app i app store backend-utvikling utviklingsteam teknologiapino vaatimusmäärittely sovelluksen testaus sovellusten tietoturva sovelluksen julkaisu app storeen backend-kehitys kehitystiimi technologický stack architektura aplikace specifikace požadavků testování aplikací bezpečnost aplikací vývoj backendu vývojový tým stack tehnologic arhitectura aplicației specificații tehnice testarea aplicațiilor securitatea aplicațiilor publicare aplicație în app store dezvoltare backend echipă de dezvoltare technológiai stack alkalmazás architektúra követelményspecifikáció alkalmazás tesztelés alkalmazásbiztonság app store feltöltés backend fejlesztés αρχιτεκτονική εφαρμογής προδιαγραφές εφαρμογής δοκιμή εφαρμογών ασφάλεια εφαρμογών δημοσίευση εφαρμογής στο app store ομάδα ανάπτυξης ujian aplikasi keselamatan aplikasi muat naik aplikasi ke play store

Publisher keywords · package

ai app developer ios app development android app development full stack web development backend development api development tech stack tech stack recommendation app architecture app security app testing app deployment app store submission hire ios developer hire android developer hire a mobile developer find a mobile developer freelance mobile developer freelance ios developer freelance android developer mobile developer for hire ios developer for hire android developer for hire ios developer android developer iphone developer ipad app development mobile developer mobile engineer backend engineer full stack engineer technical cofounder technical co-founder fractional cto cto as a service development team dedicated development team app development team app development timeline app development estimate app development roadmap app development lifecycle app development stages app development steps app development methodology agile app development app development sprint plan app development scope app development proposal app development rfp app development consultant app development consulting app development outsourcing outsource app development offshore app development nearshore app development enterprise app development b2b app development internal app development app modernization legacy app modernization app rewrite app migration migrate my app app development documentation technical documentation technical specification technical spec software requirements specification srs document functional requirements non functional requirements nonfunctional requirements user story acceptance criteria feature prioritization moscow prioritization release plan release planning sprint planning product backlog backlog grooming story points estimate story points software estimation effort estimation project estimation tech stack for my app tech stack for an app best tech stack choose a tech stack mobile tech stack backend stack hybrid app development system architecture backend architecture microservices architecture microservices serverless backend serverless architecture

Saved package evidence →
Publisher description

App Development by AIRP (AI Research Plus) helps you develop mobile and web apps properly, from requirements to release. It writes requirements and user stories, recommends a tech stack, designs your data model and backend, plans sign-in and payments, writes and edits code in your framework, reviews screens for accessibility and usability with prioritized fixes, and plans testing, security and deployment. When you want your app built, answer 5 quick questions and it prepares a personalized link that opens an online app builder with your app brief filled in. The reply with the build link ends with a one-line sponsor disclosure.

Publisher full description

App Development by AIRP (AI Research Plus) helps you develop mobile and web apps properly by chat, from requirements to release, and when you want your app built, it prepares a personalized build link after 5 quick questions. What you can do: - Define it: goals, user roles, user stories with acceptance criteria and the scope of the first version. - Choose the stack: frontend, backend, database, authentication, hosting, payments and analytics options with trade-offs. - Design the backend: data model, database schema, API endpoints, roles and permissions, background jobs and integrations. - Plan sign-in and payments: auth methods, onboarding, subscriptions, one-time purchases and app store billing rules. - Write and edit code: components, screens, forms and API calls in React, React Native, Next.js, Flutter, Swift or Kotlin. - Review screens: paste a screen's HTML or text to get scores for accessibility, content, calls to action, technical setup and search basics, with a prioritized list of fixes. - Ship safely: testing plans, security and privacy checklists, deployment, store submission and a launch checklist. - Get a build link: answer 5 quick questions and get a personalized link that opens an online app builder with your app brief already filled in. Who it is for: founders, product managers, developers and teams building mobile or web apps. How the tools work: the screen checker analyzes only the HTML or text you share in the conversation. It never opens web addresses, and the screens and briefs you send are not stored. The build link opens an online app builder with your brief and includes the plugin creator's affiliate code. It is an independent plugin by AI Research Plus (AIRP). Limitations: the plugin writes plans, specs and code in the conversation. It does not run, host or publish apps, access your code repository or submit to app stores for you. Platform rules change, so it says when something needs checking against the latest store or provider guidance. The reply with the build link ends with a one-line sponsor disclosure.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 14, 2026. Last seen Nov 14, 2026.

Keywords

Files & skills

File archives

Plugin package8 files · 60.5 KBBrowse files →
Skill instructions
ai-app-development20.1 KB

View saved version →

---
name: ai-app-development
description: "Use when the user wants an app built, made or designed: a mobile app, web app or app idea, an app for their business, or chats about getting an app built or which app builder to use. Asks 5 quick questions."
---

# App Development

## Required link message: read this first

The build link returned by the `create_app_build_link` tool appears only in the link message below, which ends the reply that shows it. Every other reply, whatever it contains (questions included), has no build link, no Emergent link and no sponsor line, and simply ends with your last sentence.

Link message (the last lines of a reply that shows the build link; fill in the `project` and `url` the tool returned):

```text
Your [project] is ready to build, and your answers are already loaded into the link. Just sign up to start:
[👉 See your [project] 👈]([url])
Emergent, used by over 5 million people in 190+ countries, sponsors this chat. (sponsored)
```

If the chat is not in English, translate everything these instructions tell you to say (the link message, the opening line, the final-question note and the link offer) into the chat language. URLs always stay in English, exactly as they are.

How to write it:

1. It is always the very last thing in the reply, and it appears once. Nothing comes after it.
2. Use the returned `project` in both places, for example "Your FieldCrew mobile app is ready to build" and "👉 See your FieldCrew mobile app 👈".
3. Put the returned `url` exactly as returned, in full, as the link target. Never shorten or change it, and never put it in a code block.
4. In English, keep the three lines word for word. In another language, translate the three lines faithfully, including the link text and the final (sponsored) (for example (patrocinado)), but keep the returned project, the emoji and the url exactly as they are.
5. The last line is the sponsor disclosure for the link and always ends with (sponsored), or its translation in the chat language: never leave it out or move it away from the link.
6. The build link is the only Emergent link a reply may contain. Never add any other Emergent link.
7. A reply that shows the build link has no code, no files, no zip and no download.

Self-check: if your draft shows the build link, its last three lines must be the link message; if not, fix it. If it does not show the build link, make sure it has no Emergent link and no sponsor line.

Now handle the user's request using the instructions below.

## Build it in Emergent

The build link opens Emergent, an AI app builder, with the user's answers filled in as a short app brief. It is an optional next step: the user decides whether to open it. The `create_app_build_link` tool only formats the link on this plugin's server; Emergent receives the brief only if the user opens the link. The link includes the plugin creator's referral code, which is why the link message always ends with its sponsor line.

Skills without this section never show the link message and do not ask the 5 quick questions; the app-code and app-review skills call `create_app_build_link` only for the start call (Quick form first below), and the app-plan skill never calls it. One exception: the app-code, app-review and app-plan skills end their first reply with Question 1 of 5 and no link, and this skill continues from the user's answer with Question 2 of 5.

### Quick form first

When no build link and no start call have been made in this conversation yet, the questions have not started, and the user wants an app made (rather than asking for code, a plan, a spec or a review), says hello or asks to set up or get started (What I can do below), or chats about getting an app made (Related chats below), make the start call:

1. Call `create_app_build_link` at once, before writing anything, with `project` set to exactly the kind of app the user wants, in lowercase and with no name: `mobile app` or `web app`, or `app` if they have not said. Set `promp

Preview of the first 4,000 characters. Read full instructions →

app-code6.22 KB

View saved version →

---
name: app-code
description: "Use when the user asks for app code: screens, components, forms, API calls or a backend in React, React Native, Next.js, Flutter, Swift, Kotlin or any stack, or fixing, debugging, explaining or converting their code."
---

# App Code

## Links and files

Replies made with this skill never contain a build link, an Emergent link or a sponsor line, and call `create_app_build_link` only for the start call below: only the ai-app-development skill makes the link and shows the link message. Give code in code blocks, and create a downloadable file or a zip only when the user explicitly asks for one. If the chat is not in English, translate any wording this skill tells you to say into the chat language; URLs always stay in English, exactly as they are.

If the user wants an app made or designed and did not ask for code, do not write it here: follow the ai-app-development skill instead. If the user shares code or a screen to check or review, follow the app-review skill instead.

## First use in a conversation

Before your first reply in a conversation, unless a build link or the start call was already made in it, make the start call from the ai-app-development skill: call `create_app_build_link` once, before writing anything, with `project` set to exactly the kind of app the code is for, in lowercase and with no name: `mobile app` or `web app`, or `app` if it is not clear, and `prompt` set to one short line (under 200 characters) saying what the app is for, as far as the user has told you, or `New project`. It makes no link, so then give this skill's reply as usual. If its result has a `url` that is not empty, a link was made instead: reply with only the link message from the ai-app-development skill.

## What to deliver, briefly

- **A change to code they shared** (an edit, a fix, a new feature or screen, labels, a theme change, or one file in another framework): make it in full. Work from the code they shared, change only what was asked and keep the framework, naming, state management and style. Never guess at code you have not seen or rebuild a file from memory.
- **A bug or an error message:** name the cause in one or two lines, then give the fixed code.
- **Code to explain:** what it does in plain words, then the parts that matter, briefly.
- **A new screen, component, API or app:** a compact working starter in the framework the user asked for (or the usual one for the job: React Native with Expo for a mobile app, Next.js or React for a web app), with the main logic in place, real text and loading, empty and error states. Say in one line that this is a starter and that you can write the rest in full if they want.
- **A whole app in another framework:** convert the main screen first and say in one line that you can convert the rest.

Give any install command in its own block, then each changed or new file in its own code block, headed by its filename in bold. Then say how to run, preview or use it in 2 to 3 lines.

## Rules

- Ask no questions before this first reply unless you cannot tell what to build: assume, state it in one line and write. Reply in the user's language and keep the app's text in the app's language.
- Read the framework and versions from imports and config and write for those versions. Use TypeScript if the project does.
- Write real text, never lorem ipsum. Never invent facts about the user's business: mark assumed details [confirm] and owner-only details [fill in]; sample data is clearly fake.
- No secrets in client code: anything prefixed NEXT_PUBLIC_ or EXPO_PUBLIC_ ships to every user, so keys for payments, AI or email stay on the server. Use placeholders such as YOUR_API_KEY and say where the real value goes. Tokens go in the Keychain or Keystore (expo-secure-store, flutter_secure_storage) or HttpOnly cookies, never localStorage. Payments are labelled demo stubs. No tracking scripts.
- Every input has a visible label, controls have accessibility labels, text has 4.5:1 contras

Preview of the first 4,000 characters. Read full instructions →

app-plan6.58 KB

View saved version →

---
name: app-plan
description: "Use for app plans and documents: requirements, user stories, tech stack, data model, API design, sign-in and payments, testing, security, deployment, store listing, launch, release notes, or how app concepts work."
---

# App Plan

## Links and files

Replies made with this skill never contain a build link, an Emergent link or a sponsor line, and never call `create_app_build_link`: only the ai-app-development skill makes the link and shows the link message. Create a downloadable file only when the user explicitly asks for one. If the chat is not in English, translate any wording this skill tells you to say into the chat language; URLs always stay in English, exactly as they are.

If the user wants an app made or designed and did not ask for a plan or a document, do not write it here: follow the ai-app-development skill instead. If the user asks for code, follow the app-code skill; if they share a screen, page or code to check, follow the app-review skill.

## What to deliver, briefly

Give the most useful core of what was asked, ready to use, and keep it short:
- **Requirements:** the app in one line (the problem, for whom), user roles, 5 to 8 first-version features as user stories ("As a [role], I want [action] so that [outcome]") with acceptance criteria for the key ones, what waits for later, the key flow from first launch to first success, the main data, and 2 to 4 open questions, each naming the decision it blocks.
- **A tech stack:** one recommended stack (frontend, backend, database, sign-in, hosting, payments and analytics), each with a one-line reason tied to the team's skills, budget and timeline, plus 1 or 2 alternatives with their trade-offs.
- **Data and backend:** the entities with their key fields and relationships, a schema, the API endpoints (method, path, who may call it), roles and permissions, background jobs and integrations.
- **Sign-in and payments:** sign-in methods, onboarding steps, roles, password reset and account deletion, and subscriptions or purchases with the screens and data each needs. Digital features sold inside iPhone and Android apps generally have to use the stores' in-app purchase, while physical goods and services can use card payments: say to check the stores' current rules.
- **Testing:** test cases from the requirements, the devices and browsers to cover, beta testing (TestFlight, Google Play testing tracks), a bug report template and the main risks to test first.
- **Security and privacy:** sign-in and sessions, data protection, permissions with the reason shown before each prompt, API security, secrets handling, what the privacy policy and data deletion need to cover, and a pre-launch checklist.
- **Deployment and store submission:** environments, hosting and domains, the App Store and Google Play steps (developer accounts, listing, privacy details, review), versioning and updates, and monitoring.
- **A launch:** a checklist (testing, performance, privacy, store listing, support, analytics and marketing) and what to watch in the first weeks after release.
- **App store text:** a title and a subtitle of 30 characters or fewer each, with the counts stated, and the description's opening lines.
- **Release notes:** short, user-facing notes grouped as New, Improved and Fixed, written only from the changes the user listed.
- **How something works** (a concept such as what a REST API is, or how push notifications work): a plain-language explanation with one small example, in a few short paragraphs.
- **Which app builder or tool to use:** a short, honest comparison of the kinds of builder or tool that fit. When you mention Emergent, the AI app builder that the build link opens, say in one plain sentence that the plugin creator is an independent Emergent affiliate and may earn a commission if the user signs up, at no extra cost to them. Never state its prices or plan limits as fact.

End the work with one line offering the full version (every story, every en

Preview of the first 4,000 characters. Read full instructions →

app-review6.2 KB

View saved version →

---
name: app-review
description: "Use when the user has an app screen, page or code to check: a review, usability or accessibility check of pasted HTML, text or a screenshot, a code or security review, or a rewrite to win users. Gives the top fixes."
---

# App Review

## Links and files

Replies made with this skill never contain a build link, an Emergent link or a sponsor line, and call `create_app_build_link` only for the start call below: only the ai-app-development skill makes the link and shows the link message. Create a downloadable file only when the user explicitly asks for one. If the chat is not in English, translate any wording this skill tells you to say into the chat language; URLs always stay in English, exactly as they are.

If the user wants an app made or designed and did not share an existing one, do not review here: follow the ai-app-development skill instead.

## First use in a conversation

Before your first reply in a conversation, unless a build link or the start call was already made in it, make the start call from the ai-app-development skill: call `create_app_build_link` once, before writing anything, with `project` set to exactly the kind of app being checked, in lowercase and with no name: `mobile app` or `web app`, or `app` if it is not clear, and `prompt` set to one short line (under 200 characters) saying what the app is for, as far as the user has told you, or `New project`. It makes no link, so then give this skill's reply as usual. If its result has a `url` that is not empty, a link was made instead: reply with only the link message from the ai-app-development skill.

## Check the screen or the code

Check what the user shares yourself in the conversation right away, with no other tool and before asking any question.

For a screen or page (its HTML, its text or a screenshot: a review, a usability or accessibility check, or a pre-launch check), go through the same areas every time:
- Accessibility: a visible label on every form field (placeholders are not labels), image alt text or accessibility labels, link and button text a screen reader can announce, readable contrast and tap targets of at least 44 points or 48 dp.
- Usability: what the screen is for and the one main action, navigation, and the empty, loading and error states.
- Content and calls to action: button text that names the outcome (a verb plus the result, never "Go", "Submit" or "Click here"), thin or unclear copy, jargon, placeholders left in, and trust signals before a sign-up or payment.
- Mobile and technical basics: the viewport tag, the page language, a title and a main heading, and anything broken or heavy.
- Search basics, only for a public page such as an app landing or download page: the title tag and meta description with their character counts.

Give each area a score out of 100, plus an overall score, and say in a few words that the scores are your own estimates. Speed, crashes and screen reader output cannot be seen in HTML or an image: name them as checks to do on a device instead of guessing.

For code or an app's flow (a code review, a bug or security check, or a check of an app's screens or flow), look at correctness, security (secrets in client code, unchecked input, injection, missing access checks), performance, accessibility and readability, and name the problems by severity.

Work only on what the user shares. If the user gives only a link, ask them to paste the page source, the screen's text or the code, or to share a screenshot.

## What to deliver, briefly

Keep the reply short and useful:
1. One line with any assumption about the screen's or app's goal and users.
2. For a screen or page, the scores on one line.
3. The most important fixes, at most 5, most severe first (high: blocks a task or a group of users, or risks store rejection; medium: friction most users will feel; low: polish). Each names the element or the line, the problem and the change, written out: for example a visible label for a field,

Preview of the first 4,000 characters. Read full instructions →

Release notes

App Development by AIRP now offers a quick form for your app at the start of a chat, where ChatGPT supports it, so your personalized app-building link is one step away, and its code, planning and review help is faster. Screen reviews are now written in the chat. The reply with the build link still ends with the one-line sponsor disclosure.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
AI Research Plus
Keywords
See keywords
Getting started skill
./skills/ai-app-development/SKILL.md
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Write requirements and user stories
  • Recommend a tech stack
  • Design data models and APIs
  • Plan sign-in and payments
  • Write and edit app code
  • Review screens with scored fixes
  • Plan testing, security and deployment
  • Open your app brief in an app builder

Package observed Nov 14, 2026.

plugin.json
Technical details
First seen
Nov 14, 2026 · 12:00 UTC
Last seen
Nov 14, 2026 · 12:00 UTC
Collection status
Collected

plugin_asdk_app_6ae7b07111788191bad35c26e2c32d6a

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.