Skip to main content

​
AGENTS.md

Neezon.com is a Mintlify site (docs.json, theme linden). This repo is the site only. There is no app server here.

​
Map

  • Smarty Discounts docs: docs/smarty-discounts/. What’s new: docs/smarty-discounts/whats-new.md.
  • App page: apps/smarty-discounts.mdx. Other pages: index.mdx, contact.mdx, privacy-policy.mdx.
  • Snippet: snippets/contact-form.jsx.
  • Images and logos: images/ (Smarty shots in images/smarty/), logo/, favicon.svg.
  • Root CSS and JS: style.css, playful-geometric.css, nav-home.js, footer-attribution.js, software-application-jsonld.js. The live site serves these as Mintlify custom CSS and JS. docs.json does not list them.
  • Nav, theme, and SEO: docs.json.

​
Build, test, lint

No package.json, npm scripts, test suite, or GitHub Actions workflow.
  • Build and content checks: npx --yes mint validate
  • Internal links and anchors: npx --yes mint broken-links --check-anchors
  • Local preview only: npx --yes mint dev
mint validate exits 1 on main for one existing error: it parses .devcontainer/devcontainer.json as OpenAPI and rejects the comments. npx --yes mint validate --disable openapi exits 0 and still notes that disabled-rule failure. mint broken-links warns on that file and exits 0 when links are fine.

​
Deploys

The only GitHub check is the Mintlify app, named Mintlify Deployment. There is no workflow file in the repo. A push to main runs that check. On current main (87337b0) it succeeded: “Your changes are now live at https://neezon.com!” The log validates docs.json, updates the changed pages, builds a snapshot, and marks the build live. On pull requests the same check is skipped: “No eligible deployments found for changes” and “No changes to preview.” GitHub has an environment named staging (created 2026-04-05, no protection rules). No file in this repo references it.

​
Agent rules

  • Edit, commit, push, and open pull requests. Never merge. Never deploy, including mint deploy.
  • Minimal root-cause fixes. Do not add helpers or files the task does not need.
  • A merge to main is what publishes the site. Leave that to a person.