STACK LIBRARY

28 hand-reviewed instruction-file presets. Each page shows the full AGENTS.md and the four tool files in plain text, explains the stack-specific rules, and loads into the generator with one click.

Zero retention: everything you type stays in this browser. Verify it yourself in DevTools.
Guide

What Is in Each Stack Preset?

Every preset is a complete generator state: languages, framework, database, hosting, test runner, package manager, the exact commands for that ecosystem, a conventional directory layout, and six to ten rules that target the mistakes agents actually make on that stack. The page for each preset explains why those rules are there, so you can keep the ones that apply and delete the rest.

  • Real, current commands, not placeholders.
  • Rules an agent can check, not slogans.
  • The same five files the generator writes, ready to commit.

Which JavaScript and TypeScript Stacks Are Covered?

Which Python Stacks Are Covered?

Which Ruby and PHP Stacks Are Covered?

Which Java, Kotlin and .NET Stacks Are Covered?

Which Go and Rust Stacks Are Covered?

Which Mobile Stacks Are Covered?

How Were the Presets Chosen and Reviewed?

We picked the stacks with the most active projects and the clearest conventions, then wrote each preset by hand from the framework's own documentation and common practice. Each one was reviewed for commands that actually exist, rules that are specific to the stack, and nothing that would be thin or duplicated across pages. Presets that would only have restated the generic rules were left out.

  1. Start from the framework's documented project layout and commands.
  2. Add the rules that prevent the most common agent mistakes on that stack.
  3. Run the result through the linter: every preset passes with no errors or warnings.

What If Your Stack Is Not Listed?

Start from the closest preset or from scratch in the generator. The form covers dozens of frameworks, databases, hosts and test runners, and the house-rules box takes anything specific to your project. If you already have an instruction file, paste it into Convert & Lint instead.

Frequently Asked Questions

Are the stack presets free to use?

Yes. Copy them into any project, commercial or not, with no attribution needed. They are starting points: change the commands and rules to match your repository.

How often are the presets updated?

When a framework changes its default commands or layout. Each preset is plain data in the site source, so updates are reviewed like code.

Can I combine two presets?

Load the closer one into the generator, then add the other stack's commands and rules by hand. For a monorepo, use the Turborepo preset at the root and nested AGENTS.md files in each package.

Why do some presets ask before migrations?

Because schema changes are hard to undo and agents tend to generate and apply them freely. Asking first costs a few seconds and prevents the worst class of mistakes.

Was this helpful?