agentleFS
GetBrewGetBrew/growth-engineer/AGENTS.md

growth-engineer

AGENTS.md218 starsChanged 47 days agoMITView on GitHub

Read development conventions for the full invariants and validation for local workflow. Keep this root guide below 200 lines and 8 KiB. This is the open-source catalog of companies, tools and workflows. The catalog is the repository: companies/, workflows/ and tags.yml. Reads are public. Every tool is one function tied to an MCP tool, CLI command or API endpoint; every workflow is a sequence of tools. Do not invent facts or commands. Catalog edits touch source files, never rendered output.…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository3 other files it gives its agents.

The file

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

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read development conventions for the full invariants and validation for local workflow.

    line 3
  2. Distinctive:

    Keep this root guide below 200 lines and 8 KiB.

    line 5
  3. Distinctive:

    Every tool is one function tied to an MCP tool, CLI command or API endpoint.

    line 11
  4. Distinctive:

    Read the development guide before changing proxy, redirects or MCP routes.

    line 34
  5. Very specific:

    Use Tailwind flex gap-*, shared typography roles and Hugeicons.

    line 54
  6. Distinctive:

    Update the closest documentation when moving a boundary.

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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

Agent guidelines — growth.engineer

Read development conventions for the full invariants and validation for local workflow. Keep this root guide below 200 lines and 8 KiB.

Sources and ownership

This is the open-source catalog of companies, tools and workflows. The catalog is the repository: companies/, workflows/ and tags.yml. Reads are public. Every tool is one function tied to an MCP tool, CLI command or API endpoint; every workflow is a sequence of tools. Do not invent facts or commands.

Catalog edits touch source files, never rendered output. Start at CONTRIBUTING.md, the company format, and the workflow format. Local skills: add-workflow and research-company.

Critical boundaries

  • lib/content/read-tree.ts owns tree reads; buildCatalog(files) is pure. Strict schemas report all invalid content paths. Test negative cases before implementing new validation rules.
  • One render path: lib/catalog/render-markdown.ts and render-tag.ts, called at build time by lib/content/build-documents.ts. Rendered documents are never hand-edited. Change format and golden fixtures together.
  • Public keys are paths and remain stable. Renames use aliases and real 308 redirects. Draft tools/workflows have no public page, file or list.
  • The pure catalog layer imports no Node, server-only or content reader code. Definitions, derived fields, relations and SEO metadata each have one owner.
  • Pages prerender known keys. Do not add dynamic, revalidate, dynamicParams or request-time catalog rendering. Copy-count holes are the caching exception. Read the development guide before changing proxy, redirects or MCP routes.
  • Internal page navigation uses next/link. File endpoints and external URLs use ordinary anchors. Search/filter state lives in links and GET forms.
  • The catalog has no backend database or auth provider. Optional Redis counts copies; the newsletter calls Brew from the server. Environment access goes through lib/env.ts; secrets never reach browsers or logs.

Validation

  • Batch pnpm exec biome check --write <touched files> once per coherent edit.
  • Changed behavior: pnpm test:run tests/<exact file>. Prove regression tests fail before implementing pure-function changes. Renderer edits require the markdown golden tests.
  • Catalog changes: pnpm content:check. Docs: pnpm docs:check.
  • Code changes use the owning pnpm check/pnpm tsc and pnpm lint according to the detailed validation guide. CI owns full build and hygiene checks.
  • Heavy checks queue through scripts/heavy-lock.mjs; never bypass it with bare Vitest, TypeScript, Next builds, knip or raw scripts. Use pnpm dev for servers; preserve other sessions and active caches.

Use Tailwind flex gap-*, shared typography roles and Hugeicons. Preserve the existing module, naming and file-size conventions. Keep security/compatibility explanations; remove obsolete narration and duplicate configuration comments. Update the closest documentation when moving a boundary.

References

Data model, markdown contract, architecture, setup, CI, performance, and logos.

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.