Add new pages to docs.json navigation structure. Updates navigation groups based on user journey (Customize, Deploy, etc.). 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.
Scanned 2/12/2026
Install via CLI
openskills install mintlify/docs---
name: update-nav
description: Add new pages to docs.json navigation structure. Updates navigation groups based on user journey (Customize, Deploy, etc.). 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.
---
# Update Navigation
Add new documentation pages to the docs.json navigation structure.
## Instructions
1. **Identify the page**: Determine which page needs to be added to navigation
- If not specified, ask the user which file/page to add
- Confirm the file path is correct (relative to docs root)
2. **Determine navigation group**: Figure out where in the navigation this belongs
- Ask which navigation group it should go in if not specified
- Common groups align with user journey: "Get started", "Customize", "Deploy", "Settings", etc.
- Read docs.json to see current navigation structure and group names
3. **Read current docs.json**:
- Understand the existing navigation structure
- Find the correct group to add to
- Note the format and patterns used
4. **Update docs.json**:
- Add the new page entry to the appropriate navigation group
- Maintain consistent formatting
- Preserve alphabetical or logical ordering within the group if applicable
- Ensure proper JSON syntax
5. **Show changes**:
- Show the user what was added to docs.json
- Confirm the placement is correct
## Navigation structure notes
- Pages are organized by user journey, not by file structure
- Navigation group names should match existing patterns
- Each entry typically includes just the file path (e.g., "content/components/accordions")
- Only update the English language section of the docs.json navigation. Updates to all translated content, including docs.json, are handled automatically after changes are made to English language files
## Example
If user says "Add the new dark-mode.mdx page to the Customize navigation":
1. Verify file exists at the specified path
2. Read docs.json to find the "Customize" group
3. Add "content/settings/dark-mode" to the appropriate location in that group
4. Show the diff for confirmation
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
Drive the full internationalization journey for a project — detect the stack, recommend a library, set up the chosen library, wrap existing strings, and optionally connect a translation platform. Use when the user asks to add or configure i18n, internationalization, localization, multi-language support, or translations — including when they explicitly mention LinguiJS, Lingui, next-intl, "wrap strings", "find hardcoded text", "make my app translatable", or "set up translations". Triggers on g...
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.