en un clic
moengage-documentation
moengage-documentation contient 7 skills collectées depuis moengage, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Review Android SDK documentation from the perspective of a junior Android developer performing an integration for the first time. Covers integration correctness, code validity, navigation flow, deprecated APIs, and writing standards. Use when asked to review any page under developer-guide/android-sdk/.
Write, edit, and maintain MoEngage documentation. Use for collaborative drafting, autonomous writing, or improving existing docs. Defaults to collaborative mode where the human makes final decisions. Adapted from Mintlify's doc-author skill for the MoEngage docs repo.
Comprehensive reference for the Mintlify platform as used by the MoEngage docs site. Use when creating pages, configuring docs.json, adding components, setting up navigation, or working with API references. Routes to detailed reference files for all components and configuration options.
Review React Native SDK documentation for writing standards, technical accuracy, RN-specific usability, and Mintlify component correctness. Use when asked to review any page under developer-guide/react-native-sdk/.
Add new pages to the MoEngage docs.json navigation structure. Updates navigation groups based on the correct tab (Home, User Guide, Developer Guide, API Guide) and the user journey. Use when the user asks to add a page to navigation, update docs.json, add to nav, or include a new page in the sidebar.
Review MoEngage Android or iOS SDK changelog files from the perspective of a junior developer who reads them to decide whether to upgrade and what action to take. Covers upgrade decision clarity, content quality, formatting consistency, versioning accuracy, and link correctness for entries post-January 2025.
Read and navigate external documentation efficiently. Invoke when the task requires checking how a specific function, endpoint, or configuration option works; when the user references an API, SDK, library, or third-party tool by name; when any docs URL or documentation site is mentioned; or when implementing something that depends on an external service or package. Adapted from Mintlify's doc-reader skill.