Skip to content
Open sourceQuebec City --:--

npx maisongr-sitemap init, npx maisongr-skills. The next tool is in the works.

2 toolsMIT licencegithub.com/maison-gr

Our open-source tools,the ones we build with.

Two open-source tools published on npm under the MIT licence, built to the same standard as our clients' products. Read our code before you trust us with yours.

01maisongr-sitemap

One sitemap,two readers.

Google and Bing get the XML they need. A person who opens /sitemap.xml gets a page in the site's own colours, fonts, dark mode and language, with every address as a link.

npx maisongr-sitemap init
  1. Next.js 16.0.0 · App Router
  2. Found
  3. done: 6 pages found6 dated from Git
  4. warning: Site address not foundthe request's address is used: pass --site or set SITEMAP_SITE_URL
  5. done: Theme: Studio Sitelight and dark
  6. done: 2 dynamic routes listed from their own static params/journal/[slug], /work/[slug]
  7. Left out 1
  8. /accountprivate page (account)
  9. Wrote
  10. done: app/sitemap.xml/route.js
  11. done: package.jsonadded to the "build" script
  12. Next
  13. warning: No robots.txt names the sitemap.
  14. next: Open http://localhost:3000/sitemap.xmla browser gets the page; curl gets the XML
  15. You can also
  16. next: npx maisongr-sitemap connectrobots.txt, and the files Google, Bing and IndexNow check
  17. next: npx maisongr-sitemap --helpevery command and option
  18. done: Done · 2 to look at above109ms

Then, for search engines

  1. npx maisongr-sitemap connect --site https://www.studio.example --google google1234abcd5678ef90.html --indexnow
  2. done: public/robots.txtcreated, naming the sitemap
  3. done: public/google1234abcd5678ef90.htmlGoogle Search Console's file
  4. done: public/996a982a1357baa0bdbb3969f869de0c.txtthe IndexNow key
  5. next: Deploy, then submit https://www.studio.example/sitemap.xml in Google Search Console
Real output from the command on a demo site, trimmed.
version
1.5.0
runtime dependencies
0
licence
MIT
Node.js
20.9+
  • Finds the pages from your routes, dates each from the last commit that changed it, never the build, and leaves out private pages, saying why.
  • Next.js, Astro, SvelteKit, Nuxt, Express, Vite apps, static sites, and any other language, PHP included, through a crawl.
  • Sets up the rest: robots.txt, Google's and Bing's verification files, IndexNow, and llms.txt for AI assistants.

In production in our products

02maisongr-skills

Agents that ask,then prove it.

Seven principles and ten methods for AI coding agents: understand before building, change only what was asked, and say what was not verified.

npx maisongr-skills
  1. Installed
  2. done: added .claude/skills/maisongr-*10 skills
  3. done: added .agents/skills/maisongr-*10 skills
  4. done: added .claude/agents/maisongr-*.md3 subagents
  5. done: created AGENTS.md
  6. done: created CLAUDE.mdimports AGENTS.md
  7. Next
  8. next: Restart your agent so it picks up the changes
  9. You can also
  10. next: npx maisongr-skills listsee the skills and what each one is for
  11. next: npx maisongr-skills removetake out everything it installed, and keep your own content
  12. done: Done145ms

Then, when the agent reports back

  1. warning: Your report lists commands under “Verified” that this session's record does not support:
  2. npm test: no command like this ran in this session.
  3. next: Run them now and report the real result, or move them to “Not verified” with the reason.
Real output from the command on a demo site, trimmed.
npm downloads, last 12 months
802
version
1.3.0
skills
10
agents supported
5
licence
MIT
  • One source for Claude Code, OpenAI Codex, Cursor, GitHub Copilot and Gemini CLI.
  • Receipts: every command reported as verified is checked against what the session really ran.
  • Installs with one command, and comes out with another without touching your own content.

03Publishing

Published likea product.

Every line is true of both repositories, and you can check it on GitHub.

  1. 01

    MIT licence

    You can use them, change them and ship them inside a commercial product.

  2. 02

    Tested on every change

    Continuous integration runs the tests on every proposed change, and again before every release.

  3. 03

    Scanned

    CodeQL reads the code, and every new dependency is checked against known vulnerabilities before it goes in.

  4. 04

    Published with provenance

    Releases ship from GitHub Actions with no stored token, and npm links each one to the commit that built it.

  5. 05

    A security policy

    A private channel on GitHub to report a vulnerability, and a changelog for every release.

→Maison GR

This standard, on your product.

The same principles apply to every engagement. Let's talk about yours.