You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so
ALWAYS ask for clarification rather than making assumptions
NEVER lie, guess, or make up anything
Project context
Format: MDX files with YAML frontmatter
Config: docs.json for navigation, theme, settings
Components: Mintlify components
MCP server integration
This project has the Mintlify MCP server connected
Use the MCP server to search the Mintlify documentation for up-to-date information
The MCP server provides access to component references, best practices, and technical details
When unsure about Mintlify component usage or documentation patterns, query the MCP server before making assumptions
Content strategy
Document just enough for user success - not too much, not too little
Prioritize accuracy and usability
Make content evergreen when possible
Search for existing content before adding anything new. Avoid duplication unless it is done for a strategic reason
Check existing patterns for consistency
Start by making the smallest reasonable changes
docs.json
Refer to the docs.json schema when building the docs.json file and site navigation
Frontmatter requirements for pages
title: Clear, descriptive page title
description: Concise summary for SEO/navigation
Writing standards
Second-person voice ("you")
Prerequisites at start of procedural content
Test all code examples before publishing
Match style and formatting of existing pages
Include both basic and advanced use cases
Language tags on all code blocks
Alt text on all images
Relative paths for internal links
Git workflow
NEVER use --no-verify when committing
Ask how to handle uncommitted changes before starting
Create a new branch when no clear branch exists for changes
Commit frequently throughout development
NEVER skip or disable pre-commit hooks
Do not
Skip frontmatter on any MDX file
Use absolute URLs for internal links
Include untested code examples
Make assumptions - always ask for clarification
1---2name: 082-claude-e221a3ad3description: Mintlify documentation4---5# Mintlify documentation67## Working relationship8- You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so9- ALWAYS ask for clarification rather than making assumptions10- NEVER lie, guess, or make up anything1112## Project context13- Format: MDX files with YAML frontmatter14- Config: docs.json for navigation, theme, settings15- Components: Mintlify components1617## MCP server integration18- This project has the Mintlify MCP server connected19- Use the MCP server to search the Mintlify documentation for up-to-date information20- The MCP server provides access to component references, best practices, and technical details21- When unsure about Mintlify component usage or documentation patterns, query the MCP server before making assumptions2223## Content strategy24- Document just enough for user success - not too much, not too little25- Prioritize accuracy and usability26- Make content evergreen when possible27- Search for existing content before adding anything new. Avoid duplication unless it is done for a strategic reason28- Check existing patterns for consistency29- Start by making the smallest reasonable changes3031## docs.json3233- Refer to the [docs.json schema](https://mintlify.com/docs.json) when building the docs.json file and site navigation3435## Frontmatter requirements for pages36- title: Clear, descriptive page title37- description: Concise summary for SEO/navigation3839## Writing standards40- Second-person voice ("you")41- Prerequisites at start of procedural content42- Test all code examples before publishing43- Match style and formatting of existing pages44- Include both basic and advanced use cases45- Language tags on all code blocks46- Alt text on all images47- Relative paths for internal links4849## Git workflow50- NEVER use --no-verify when committing51- Ask how to handle uncommitted changes before starting52- Create a new branch when no clear branch exists for changes53- Commit frequently throughout development54- NEVER skip or disable pre-commit hooks5556## Do not57- Skip frontmatter on any MDX file58- Use absolute URLs for internal links59- Include untested code examples60- Make assumptions - always ask for clarification
Run npx skillmds@latest add tools-only/082-claude-e221a3ad in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Mintlify documentation It is listed under Docs & Writing on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tools-only (@tools-only) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tools-only