agentleFS
Sign inStart free
GitHubKnown publishergithub/replica/hub/AGENTS.md

replica / hub

AGENTS.md117 starsChanged 10 days agoMITView on GitHub

Replica Hub is a self-hosted Rails application where teams review prototype branches. GitHub owns source code and repository access. Hub stores Builds and review data. Prototype code runs on isolated preview origins. Read the root instructions and shared guides, then the Hub documentation index and guides for the work:

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 instructions and shared guides, then the Hub documentation index and guides for the work:

    line 7
  2. Distinctive:

    Use the devcontainer for Ruby and Node commands.

    line 19
  3. Distinctive:

    Follow the root Git workflow for checkout checks and publishing steps.

    line 21

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

Working on Replica Hub

Replica Hub is a self-hosted Rails application where teams review prototype branches. GitHub owns source code and repository access. Hub stores Builds and review data. Prototype code runs on isolated preview origins.

Start here

Read the root instructions and shared guides, then the Hub documentation index and guides for the work:

  • Development for the devcontainer and local runtime.
  • Coding conventions for Rails, TypeScript, and interface rules.
  • Shared documentation conventions for discussions, product decisions, prose, and handoffs.
  • Testing and operations for review and verification.
  • Architecture and the affected product guide for system boundaries and current behavior.
  • Storybook for UI changes, story coverage and cleanup, and PR screenshots.

Working rules

  • Extend the existing architecture instead of creating a parallel source, Build, preview, or review flow.
  • Use the devcontainer for Ruby and Node commands.
  • Keep the top-level HubThemeProvider around Hub and Storybook content. It synchronizes the resolved light/dark mode to <html data-color-mode> so portals into document.body inherit Brand and --hub-* tokens. React context alone does not carry CSS inheritance across a portal; do not add a fixed light theme to an overlay.
  • Follow the root Git workflow for checkout checks and publishing steps.

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