agentleFS
CloudflareKnown publishercloudflare/nimbus/apps/www/skills/build-a-nimbus-site/SKILL.md

build-a-nimbus-site

Skill1.8k starsChanged 31 days agoMITView on GitHub

Create, write and deploy a documentation site with Nimbus (Astro). Use when a user wants a new docs site, wants to add pages or components to a Nimbus site, or wants to check, upgrade or deploy one.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about cloudflare/nimbus

The biggest 5 of 56 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 56

Talked about on GitHub, the web and Bluesky (56 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every component used in .mdx must be listed in src/components.ts.

    line 27
  2. Very specific:

    After raising @cloudflare/nimbus-docs, run npx nimbus-docs migrate, complete each review it lists, run the completion command it prints, …

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Build a Nimbus docs site

Nimbus builds documentation sites on Astro. The scaffolder copies layouts, components and styles into the project, and the user owns them from then on. The @cloudflare/nimbus-docs package provides the plumbing and the nimbus-docs CLI.

Full docs: https://nimbus-docs.com/llms.txt. Every page has a Markdown version at <page>/index.md.

Create a site

Requires Node 22.23.4 or later.

npm create @cloudflare/nimbus-docs@latest my-docs -- --yes
cd my-docs
npm run dev

Pass --adapter cloudflare for a server-rendered site. All options: https://nimbus-docs.com/reference/scaffolder-options/index.md

Write pages

  • A page is a .md or .mdx file under src/content/docs/. Its path is its URL and its place in the sidebar: src/content/docs/guides/install.mdx is /guides/install/.
  • Every component used in .mdx must be listed in src/components.ts.
  • Details: https://nimbus-docs.com/writing/pages-and-routing/index.md

Add components and features

npx nimbus-docs list          # what the registry offers
npx nimbus-docs add <slug>    # install one

Features such as changelog print a recipe for you to follow in the project. Read it with npx nimbus-docs add <slug> --print.

Check before you finish

npx nimbus-docs check
npm run build

check reports configuration, content and type problems with fixes. Run npx nimbus-docs lint after a build to check links.

Upgrade

After raising @cloudflare/nimbus-docs, run npx nimbus-docs migrate, complete each review it lists, run the completion command it prints, then npx nimbus-docs outdated to see starter files that changed upstream. Details: https://nimbus-docs.com/cli/index.md

Deploy

New sites deploy to Cloudflare Workers with npm run deploy, which builds first. Other hosts: https://nimbus-docs.com/deploy/index.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.