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…