adaptyteam

Use when rolling a feature out to the next SDK platform ("do it like we did for iOS, but for Android"), identifying which doc articles a dev task or MR affects, deepening a zone's brief through an interview, or looking up where ground truth for a platform's…

Use when documentation needs to be planned and written end-to-end — from a Jira task, feature spec, or verbal description through to a polished draft. Not for review-only or planning-only tasks.

Use when reviewing or writing MDX files in src/content/docs — proofreading, checking technical writing quality, verifying Simplified Technical English compliance, validating links and images, or drafting new doc content.

Use when planning documentation before writing — for new articles, updates to existing docs, or structural changes. Also use when reviewing the structure of an existing article without writing it yet.

Use when improving the search visibility of docs articles, auditing a set of articles for SEO, or reviewing frontmatter title/description/metadataTitle quality — including duplicate titles across SDK platforms, SERP truncation, cannibalizing pages, and thin…

Use when adding a new monthly section to src/content/docs/release-notes/whats-new.mdx — gathers commits to main over a date range, identifies user-facing updates worth featuring, confirms scope with the user, then drafts the section in the existing style.

Use when adding support for a new locale/language to the Adapty docs site. Covers all hardcoded and dynamic locale registration points, translation commands, sitemap setup, Algolia search config, and the step-by-step order to follow.

Use when the user wants the staging ("review") URL for an in-progress feature on the Adapty Dashboard. Accepts a Jira ticket, GitLab MR URL, branch name, or feature description (frontend or backend). Resolves the frontend MR's latest "Deploy to review" job…

Use when a user wants to change an Adapty flow by editing its builder config JSON — add a locale, translate a paywall or onboarding, rewrite copy, add/remove/reorder screens, add tabs or plan pickers, or wire quiz branching. Triggers on "edit my flow config",…

Use when a client asks whether a Flow Builder flow is ready for production, wants it audited or checked, or asks something like "did I forget anything — triggers, products, variables?", "is this ready to publish?", or "check my paywall/flow". Answers one…

Use when someone shares a mobile subscription or purchase screen and wants to know what to change, fix, test or improve — "here's my paywall", "roast this", "what should I test", a competitor screenshot, a design in progress, or an image with almost no text.…

Use when managing Apple Search Ads through the Adapty CLI — reading campaign, ad group, keyword or ad performance, changing bids or budgets, adding or pausing keywords, launching or pausing a campaign, harvesting search terms, or setting up rule-based ad…

Use when a user wants to integrate Adapty SDK into a mobile app, set up in-app purchases with Adapty, add a paywall to their app, or move to Adapty from another purchase system. Triggers on "integrate Adapty", "add Adapty to my app", "set up subscriptions",…

Use when the Adapty CLI needs installing or authenticating before any Apple Search Ads work — a fresh Cowork or cloud session, "adapty: command not found", AuthRequiredError, an expired auth code, or connecting an Apple Search Ads account. Triggers on…

Use when operating a connected Apple Ads account through the Adapty CLI — weekly check-ins, cohort and keyword bid reviews, competitor keyword opportunities from Market Intelligence, search-term harvesting, negative-keyword mining, CPP routing, bids, budgets,…

Use for read-only diagnostics of a connected Apple Ads account: account health, live campaign and ad-group structure, traffic ownership, duplicate exact keywords, missing cross-negatives, serving problems, spend without results, or a simple same-window…

Use when planning Apple Search Ads before there is anything to read — designing an account structure, choosing which campaigns and ad groups to create, building a keyword taxonomy and starting negative list, sizing a starting budget, or deciding whether Apple…

Use when interacting with the already-running Adapty devtools app on the iOS Simulator or an Android emulator/device — pressing its controls, reading its state, checking what the SDK did, or diagnosing SDK behaviour on device. Also use before reaching for a…

Use when upgrading native iOS or Android SDK dependency versions in AdaptySDK-Capacitor. Triggered by requests like "bump ios sdk", "upgrade android native", "update native dependency version".

Start Adapty Devtools app for SDK testing. Use when need to run, launch, or test the devtools example app on iOS or Android simulator/emulator.

Use when upgrading native iOS or Android SDK dependency versions in the AdaptySDK React Native project — bumping the Adapty iOS SPM version or Android gradle dependency versions

Use when upgrading native iOS or Android SDK dependency versions in the AdaptySDK React Native project — bumping Adapty pods version or Android gradle dependency versions

Use when setting up or managing Adapty in-app subscriptions, paywalls, or placements via CLI.

Use when the Adapty CLI needs installing or authenticating before any Apple Search Ads work — a fresh Cowork or cloud session, "adapty: command not found", AuthRequiredError, an expired auth code, or connecting an Apple Search Ads account. Triggers on…

Use when you need to read, understand, or reference the native iOS AdaptySDK-iOS source code — for understanding bridge contracts, porting new features, debugging native behavior, or checking JSON request/response formats

Use when someone asks whether an Apple Ads or subscription metric is unusual, what CPA/CPT/TTR/CR was published for a country, App Store genre, or niche, how Apple Ads subscriber economics compare with other paid channels, or what uplift the 2026 report…