agentleFS
Sign inStart free
jonnyzzzjonnyzzz/mcp-steroid/website-gen/CLAUDE.md

mcp-steroid / website-gen

CLAUDE.md78 starsChanged 3 months agoApache-2.0View on GitHub

Guidance for the :website-gen module. Instructions here override the root guide for this folder. Read the root CLAUDE.md too (project-wide rules). :website-gen is build-tooling, not plugin runtime — no IntelliJ dependencies. One job: - Website artifacts (WebsiteArtifacts.kt, task generateWebsite) — resolves the published GitHub release and writes version.json + updatePlugins.xml (the IntelliJ custom-plugin-repository XML) into website/build/generated-static, and copies EULA + LICENSE there too. The task knows all paths (VERSION + release notes from the project layout); CI/Makefile invoke it with…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the root CLAUDE.md too (project-wide rules).

    line 4

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
CLAUDE.md

website-gen/CLAUDE.md

Guidance for the :website-gen module. Instructions here override the root guide for this folder. Read the root CLAUDE.md too (project-wide rules).

What this module is

:website-gen is build-tooling, not plugin runtime — no IntelliJ dependencies. One job:

  • Website artifacts (WebsiteArtifacts.kt, task generateWebsite) — resolves the published GitHub release and writes version.json + updatePlugins.xml (the IntelliJ custom-plugin-repository XML) into website/build/generated-static, and copies EULA + LICENSE there too. The task knows all paths (VERSION + release notes from the project layout); CI/Makefile invoke it with no args. The plugin version + since-build come from the ACTUAL published artifact (the release ZIP's ij-plugin-*.jar META-INF/plugin.xml), never a literal.

The website Make contract is a SINGLE task. make update-config runs only :website-gen:generateWebsite, and that task emits EVERY static file the site serves — into website/build/generated-static (a build/ dir, gitignored, merged by Hugo via its staticDir list). So generateWebsite dependsOn :installer-gen:generateInstaller (which writes install.sh + install.ps1 into the same dir) and copies EULA/LICENSE itself. Adding a new generated static file = make generateWebsite depend on the task that produces it (or copy it in generateWebsite); never add a second task to the Makefile, and never write generated files into the tracked website/static.

Dependencies

  • The ONLY project() dependency is :installer-gen — the lower build-tooling module that owns the shared HTTP/cache infra. WebsiteArtifacts reuses its KtorHttpFetcher (so this module has no Ktor dependency of its own). :installer-gen has no IntelliJ deps, so generateWebsite still never builds the plugin side of the project — it stays fast.
  • JDK detection / the installer-script generation used to live here; both moved to :installer-gen.

Testing

  • Tests are hermetic (the Url*Fetcher seam is injected). Run: ./gradlew :website-gen:test.
  • Covered by ciBuildPluginTests (guarded — see root build.gradle.kts).
  • ZIP/XML use the JDK built-ins; version.json/GitHub-API JSON use kotlinx.serialization. When comparing generated updatePlugins.xml to the published file, mind the standalone="no" omission + trailing newline (see WebsiteArtifactsTest).

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.

Check your setup, free