Bright bay

agent/customize.mdx

@@ -15,7 +15,7 @@
 Add any instructions that you want the agent to follow. The agent appends these instructions to its system prompt, so the instructions apply to all tasks whether you use the agent in your dashboard, on Slack, or via the API.
 
 <Note>
   The agent only reads `AGENTS.md`. It does not read other agent instruction files that may exist in your repository, such as `CLAUDE.md`, `.cursorrules`, `.github/copilot-instructions.md`, or `GEMINI.md`, even if your `AGENTS.md` references them.
 
   If you use other tools that rely on their own instruction files, consolidate the instructions you want the Mintlify agent to follow into `.mintlify/AGENTS.md`. You can keep your other files for those tools, but duplicate any shared guidance into `AGENTS.md` so the agent picks it up.
 </Note>
@@ -55,4 +55,4 @@
 - Add prerequisite sections to guides when users need API keys, environment setup, or dependencies.
 - Include "Next steps" sections linking to related documentation.
 - Add troubleshooting sections for common issues we see in support tickets.
-```
+```

api-playground/graphql-setup.mdx

@@ -1,12 +1,12 @@
 ---
 title: "GraphQL setup"
-description: "Generate reference pages for your GraphQL API from a schema definition file, with linked types and example queries, mutations, and responses."
+description: "Hello there"
 keywords: ["graphql", "schema", "sdl"]
 ---
 
 ## Add a GraphQL schema
 
 To create pages for your GraphQL API, you need a valid GraphQL schema in SDL (Schema Definition Language) format. Store the schema in your documentation repository or host it at an HTTPS URL that Mintlify can fetch.
 
 ```graphql schema.graphql
 "An object with a stable identifier."
@@ -75,7 +75,7 @@
 </Note>
 
 <ParamField path="source" type="string" required>
   A local path to an SDL file in your documentation repository or an HTTPS URL to a hosted SDL file. Does not accept HTTP URLs.
 </ParamField>
 
 <ParamField path="directory" type="string">
@@ -100,4 +100,4 @@
 
 ## Update your documentation
 
-Mintlify regenerates GraphQL reference pages when you run `mint dev` or when you push changes to your documentation repository. If your schema is hosted at an HTTPS URL, updates to the schema regenerate on the next build.
+Mintlify regenerates GraphQL reference pages when you run `mint dev` or when you push changes to your documentation repository. If your schema is hosted at an HTTPS URL, updates to the schema regenerate on the next build.

automations/create.mdx

@@ -60,4 +60,4 @@ Deleting an automation is permanent and removes its configuration and run histor
 
 1. Open the [Automations](https://app.mintlify.com/products/automations) page in your dashboard.
 2. Click the <Icon icon="settings" /> settings button beside an automation.
-3. Click **Delete**.
+3. Click **Delete**.

quickstart.mdx

@@ -30,15 +30,13 @@
   2. Run `mint --version`. If the command is unavailable, install the CLI with `npm i -g mint` or `pnpm add -g mint`. If the command succeeds, run `mint update`.
   3. Run `mint status` before starting authentication. If it already shows an organization, keep the existing session and do not create another account.
   4. Run `mint login` if the user has an account. Otherwise, ask for their first name, last name, company, and email, then run:
-
      ```bash
      mint signup \
        --firstName <first-name> \
        --lastName <last-name> \
        --company <company> \
        --email <email>
      ```
-
      `mint signup` waits for email verification, so keep it running as a background process when your environment supports background commands. Tell the user to click the verification link and approve the CLI in the browser. Never invent signup details.
   5. After the user finishes verification and onboarding, run `mint status` again. Confirm that it reports their email, organization, and subdomain. If the organization exists but no subdomain appears, ask the user to finish selecting or connecting a GitHub repository in the onboarding browser tab, then retry.
   6. If the user has an existing documentation repository, clone or open it. Preserve its content. For a new local project, scaffold into a new, empty directory with either `mint new <directory> --name <name> --theme <theme>` or `mint new <directory> --template <template-name>`. Ask which theme or template they want if they have not specified one. Do not use `--force` on a directory containing user files.
@@ -71,7 +69,7 @@
 </Visibility>
 
 <Visibility for="agents">
   Use the preceding CLI setup workflow. Initiate the corresponding `mint signup` or `mint login` command. Account verification and GitHub authorization open browser pages; have the user approve them. Continue the setup when they finish. Do not consider setup complete until `mint status` reports a subdomain and the deployed `.mintlify.site` URL loads.
 </Visibility>
 
 ## View your deployed site
@@ -203,4 +201,4 @@
 
 <Card title="Add a custom domain" icon="globe" horizontal href="/customize/custom-domain">
   Use your own domain for your documentation site.
-</Card>
+</Card>