Make prompts specific and outcome-focused
Generic prompts like@mintlify Improve the onboarding page apply general best practices, but may not improve content in the specific way that you were picturing.
Try prompts based on outcomes you want your users to achieve or problems that they encounter.
@mintlify A lot of users have trouble installing the CLI. Review the onboarding page and update the docs so that users can easily install the CLI@mintlify Developers keep getting 401 errors when following our authentication guide. Review the auth docs and add clearer examples showing how to properly format the API key
Use broad prompts for maintenance tasks
Use broad prompts for general content maintenance like fixing typos, updating redirects, or renaming a feature throughout your docs.@mintlify Find and fix all typos in the docs@mintlify change all unordered lists to use * instead of -
Specify a domain name for multi-site organizations
If you have multiple documentation sites, include thesubdomain parameter in your message to specify which documentation set the agent should work on.
To find your domain name, look at your dashboard URL for the documentation set you want to update. The domain name is the last part after your organization name. For example, if your dashboard URL is https://dashboard.mintlify.com/org-name/domain-name, your domain name is domain-name.
Use the format @mintlify subdomain=<your-domain-name> <your-prompt> to prompt the agent to work on a specific documentation set.
@mintlify subdomain=public-docs Add a new section to the quickstart about inviting collaborators based on this PR: Prompts the agent to update the quickstart only on thepublic-docssite.@mintlify subdomain=customer-docs Update the auth docs for the new authentication method: Prompts the agent to update the auth docs only on thecustomer-docssite.