mcp-steroid / website
CLAUDE.md82 starsChanged 3 months agoApache-2.0View on GitHub
This directory contains the Hugo source for the MCP Steroid website at https://mcp-steroid.jonnyzzz.com Scope note: the public website targets end users — install instructions, demo videos, the strategy page. Agent-facing design tenets live in docs/PHILOSOPHY.md (canonical, mirrored at runtime as mcp-steroid://skill/design-philosophy); contributor guidance for the plugin / prompts / tests lives in the per-folder CLAUDE.md and AGENTS.md files. Site copy and agent docs evolve on different cadences and to different audiences; don't conflate them. The website is built from this…
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jonnyzzz/mcp-steroidword for word, first seen Aug 5, 2026
Other versions1 project uses a version of this.
Word for word · 1
- jonnyzzz/mcp-steroid★ 78100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- prompts/AGENTS.mdAGENTS.md
- test-integration/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- ij-plugin/CLAUDE.mdCLAUDE.md
- installer-gen/CLAUDE.mdCLAUDE.md
- test-experiments/CLAUDE.mdCLAUDE.md
- test-integration-agent-launch/CLAUDE.mdCLAUDE.md
- website-gen/CLAUDE.mdCLAUDE.md
- promptSkill
The file
We split this CLAUDE.md into the rules it gives an agent
7 rules. About 0 are common, 1 is distinctive, and 6 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.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 56
Create new markdown docs under content/docs/.
- Very specific: line 73
If description is missing, the docs list uses the first paragraph as a summary.
- Very specific: line 105
After running make build, commit and push changes in mcp-steroid-public/:
- Very specific: line 122
What's New: Add new entries to [[params.whatsnew]] in hugo.toml with date and text fields.
- Very specific: line 124
Featured Videos: Update the [[params.featuredVideos]] entries in hugo.toml to change which videos appear on the homepage.
- Distinctive: line 147
Verify nav fit at small widths before changing the brand.
- Very specific: line 171
Responsive checks: Verify the homepage has no horizontal overflow at 320 / 390 / 768 / 1280px (Playwright: compare …
≈ “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.
Files
MCP Steroid Website
This directory contains the Hugo source for the MCP Steroid website at https://mcp-steroid.jonnyzzz.com
Scope note: the public website targets end users — install instructions, demo videos, the strategy page. Agent-facing design tenets live in
docs/PHILOSOPHY.md(canonical, mirrored at runtime asmcp-steroid://skill/design-philosophy); contributor guidance for the plugin / prompts / tests lives in the per-folderCLAUDE.mdandAGENTS.mdfiles. Site copy and agent docs evolve on different cadences and to different audiences; don't conflate them.
Architecture Overview
The website is built from this directory using Hugo and deployed via GitHub Pages.
Deploys from the website branch, not main. GitHub Pages (.github/workflows/github-pages.yml)
builds on a push to the long-lived website branch. website tracks main (advanced via
git merge main → website, normally often) but can deliberately lag it so website changes that depend
on an unreleased devrig binary — e.g. a new install.sh/install.ps1 CLI contract — stay off the
live site until a matching GitHub release exists. A push to main does NOT deploy. The release process
advances website after publishing the release (release/release-instructions.md → "Stage 7c").
website is origin-only (never synced to jb).
What is mcp-steroid-public/?
The mcp-steroid-public/ directory is a separate clone of the same repository (jonnyzzz/mcp-steroid). This setup allows:
- Hugo builds to
mcp-steroid-public/docs/- Hugo outputs the static site here - GitHub Pages serves from
docs/folder - The main repository'sdocs/folder is served at https://mcp-steroid.jonnyzzz.com - Independent commits - Website changes can be committed and pushed separately from plugin code changes
This is a common pattern for GitHub Pages deployment where the source (Hugo markdown) and output (HTML) live in different places but the same repository.
Note: The mcp-steroid-public/ directory is ignored in .gitignore - it's a local clone used only for building and publishing.
Requirements
- Docker and Docker Compose (for Hugo builds)
- JDK 25 (for the
:website-genGradle task that generatesversion.json+updatePlugins.xml). Nogh,uv,jq, or Python needed —:website-genresolves the GitHub release itself over HTTP.
Directory Structure
hugo.toml- Hugo configuration with site parameters and featured videoslayouts/- Hugo templatesstatic/- Static assets (logo, CNAME) + the generatedversion.json/updatePlugins.xmlcontent/- Content files (markdown)mcp-steroid-public/- Checkout of the public repository (build output destination)
version.json + updatePlugins.xml are generated by the :website-gen Kotlin module (repo root,
website-gen/), invoked from the Makefile's update-config as ./gradlew :website-gen:generateWebsite.
Adding Documentation Pages
Create new markdown docs under content/docs/. Front matter is optional, but recommended:
---
title: "My Doc Page"
description: "Short summary shown on the docs landing page"
weight: 3
---
Intro paragraph...
## Overview
Details go here.Notes:
- If
descriptionis missing, the docs list uses the first paragraph as a summary. - Nested folders under
content/docs/are supported; pages are listed byweightthen title.
Quick Start
# Start development server with live reload at http://localhost:1313
make dev
# Build the site to mcp-steroid-public/docs
make buildManual Setup (if needed)
# Explicitly clone the public repository
make setupDevelopment
# Start development server with live reload at http://localhost:1313
make dev
# Build the site to mcp-steroid-public/docs
make buildPublishing
After running make build, commit and push changes in mcp-steroid-public/:
cd mcp-steroid-public
git add docs README.md
git commit -m "Update website"
git push origin mainImportant Notes
- Version Sync: The release version is read from
../VERSIONto find the GitHub release and updatehugo.toml. The actual plugin version used inupdatePlugins.xmlcomes from the JAR artifact'splugin.xml(e.g.0.89.0-b8388824), not from the VERSION file. - Build Output Layout: The website root lives under
mcp-steroid-public/docs. Do not create apublic/folder in this repository. - Public Repository README: The public repository at https://github.com/jonnyzzz/mcp-steroid contains issues and is user-facing. The README.md in that repository should be kept in sync with the website content and provide similar information about the plugin.
- What's New: Add new entries to
[[params.whatsnew]]inhugo.tomlwithdateandtextfields. Entries are displayed in the order they appear in the file (newest first). - Featured Videos: Update the
[[params.featuredVideos]]entries inhugo.tomlto change which videos appear on the homepage. - CNAME: The
static/CNAMEfile configures the custom domain. Do not remove it. - version.json: Published at
/version.jsonwith the current version. Generated automatically during build. - updatePlugins.xml: Published at
/updatePlugins.xml— IntelliJ custom plugin repository XML. Generated automatically during build by the:website-genKotlin module (website-gen/). It resolves the published GitHub release forVERSIONover the REST API, downloads themcp-steroid-*.zip, extracts theij-plugin-*.jar, readsMETA-INF/plugin.xmlfor the exact plugin version +since-build, and renders the XML (DOM) with the change-notes fromrelease/notes/<version>.md. The version + URL always match the actual artifact. The build fails if the release doesn't exist or URL/version validation fails — no fallbacks. Unit-tested offline inWebsiteArtifactsTest(the network is an injected seam).- ZIP selection (since 0.100): the GitHub release carries two zips — the plugin (
mcp-steroid-*.zip) and the devrig CLI (devrig-*.zip).:website-genmatchesstartsWith("mcp-steroid")specifically; a bare.zipmatch would wrongly pickdevrig-*.zip.
- ZIP selection (since 0.100): the GitHub release carries two zips — the plugin (
- Release Pages: Releases are sorted by numeric semantic version (
partials/releases-sorted.html, used by bothreleases/list.htmlandreleases/single.html), newest first. Do not revert to.ByTitle.Reverse— that string-sorts titles, sov0.95.0outranksv0.100("9" > "1"), which wrongly promotes an old release as "Latest" and flags the newest as obsolete. The latest release is the featured tile; older releases get an auto-generated obsolete banner (single.html). No manual obsolete banners in content files.- Support footer: the release-page sponsor footer and the homepage
#supportsection both renderpartials/support-section.html(single source of truth). Release content.mdfiles must not carry their own "Support the Project" block.
- Support footer: the release-page sponsor footer and the homepage
- Plugin Repository Promotion: The custom plugin repository URL (
https://mcp-steroid.jonnyzzz.com/updatePlugins.xml) is promoted on the releases list page and in the Download section of release pages (starting from 0.88.0).
Homepage, branding & the devrig diagram (0.100+)
The site is devrig-first: the homepage hero leads with the devrig CLI (primary CTA),
the plugin is the stable secondary path. Conventions established for that:
- Top-left brand badge.
layouts/partials/nav.htmlshows the MCP Steroid logo + name + adevriggradient pill (.nav-devriginstatic/css/site.css). Because the brand row is now wider, the hamburger breakpoint was raised from 768px → 960px (the@mediablock insite.cssthat flips.nav-toggle/.nav-links); below that the menu would overlap the badge. Verify nav fit at small widths before changing the brand. - The shared bridge diagram —
static/devrig-bridge.svgis the single source. It renders the "one bridge → every IDE at once" story (AI Agent →devrig(CLI + MCP) → IntelliJ IDEA / PyCharm / Managed backend). It is referenced as an<img>by three places — the homepage devrig section (layouts/index.html), the devrig docs page (content/docs/devrig.md), and the rootREADME.md(relativewebsite/static/devrig-bridge.svg, since GitHub strips inline<svg>). Edit the one file and all three update. Design constraints (from a 3-agent review): labels must stay legible at social-thumbnail size (titles 16–18px/700, subtitles ~12.5px, bright#c7c4d6), the panel needs a visible border (#2e2e50on#1b1b34) so it doesn't melt into the page gradient, and keep theviewBoxtight (currently0 0 780 280). - Social/OG preview image.
og:image/twitter:image(inlayouts/_default/baseof.html) point tostatic/og-devrig.png(1200×630) — a branded card built FROM the bridge diagram (MCP Steroid logo + name +devrigbadge + slogan + the diagram). The olderog-image.png/og-image.svgare kept in place but are no longer the active preview. To regenerateog-devrig.png: render an HTML composition with Playwright (page.setContent(...), viewport 1200×630,deviceScaleFactor: 2, screenshot). Gotcha:file://images do NOT load undersetContent— inline the SVG markup (readpluginIcon.svg+devrig-bridge.svgwithfsand embed) rather than<img src="file://…">. - Footer copyright.
layouts/partials/footer.htmlcarries© 2025–2026 Eugene Petrenko(name links to jonnyzzz.com) + the JetBrains-independence line (.footer-copyrightinsite.css). - Responsive checks. Verify the homepage has no horizontal overflow at 320 / 390 / 768 / 1280px
(Playwright: compare
document.documentElement.scrollWidthtoinnerWidth). Known pre-existing issue: docs content pages (e.g./docs/devrig/) overflow at ≤~600px — the.docs-contentcolumn is effectively fixed-width; this is independent of the marketing pages and not yet fixed.
Workflow Summary
┌─────────────────────────────────────────────────────────────────┐
│ Main Repository (jonnyzzz/mcp-steroid) │
│ ┌─────────────────────────────────────────────────────────────┐│
│ │ website/ ││
│ │ ├── content/ ← Hugo source (markdown) ││
│ │ ├── layouts/ ← Hugo templates ││
│ │ ├── hugo.toml ← Configuration ││
│ │ └── mcp-steroid-public/ ← Clone of main repo (ignored) ││
│ │ └── docs/ ← Hugo build output ││
│ └─────────────────────────────────────────────────────────────┘│
└─────────────────────────────────────────────────────────────────┘
│
make build │ (Hugo outputs to docs/)
▼
┌─────────────────────────────────────────────────────────────────┐
│ GitHub Pages serves from jonnyzzz/mcp-steroid:main/docs/ │
│ → https://mcp-steroid.jonnyzzz.com │
└─────────────────────────────────────────────────────────────────┘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
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.

