How to Use Setuproll: The Complete Guide

Setuproll is a tier list for AI coding setups. A build is the whole rig wrapped around a model: the memory file, the rules, the MCP servers, the subagents and the hooks. This page walks you through every part of the site, first as a reader and then as a contributor. Keep it open in a second tab while you click around.

Browsing builds

Start at /builds. Every card is one published build with its tier badge, the model it runs on, and a short summary of what is inside it. Use the search box to match by name or tool, and use the filter pills to narrow by tier, category or stack.

1. Open /builds from the top navigation.
2. Type in the search box, or tap a filter pill such as Cursor, Claude Code or MCP.
3. Click any card to open its detail page.
4. On the detail page, scroll to read the memory, rules, MCP config and the author's notes.

Comparing builds

When two builds look close, put them side by side. Open /compare and pick up to four builds. Setuproll lines up their model, memory size, MCP servers, subagents and tier so the differences jump out. To start a fresh comparison from scratch, use /compare/new and add builds one at a time.

1. Go to /compare/new.
2. Search and add the first build, then add a second.
3. Add a third or fourth if you want a wider field.
4. Read down each row to see where the setups actually differ.

Saving builds

When a build is worth keeping, hit the Save button on its card or detail page. Everything you save lands at /saved, your private shortlist. Saving does not change the public ranking; it is just your own bookmark drawer.

Creating stacks

A stack is a named collection of builds that belong together, for example everything you use for a Next.js project or a Python data pipeline. Stacks live at /stacks and you can keep them private or publish them for others.

1. Open /stacks and click New stack.
2. Give it a name and a one-line description.
3. From any build, use Add to stack and pick your stack.
4. Reorder the builds inside, then publish if you want to share it.

Taking the Academy course

If you are new to all of this, go to /learn. The Academy is a short course that walks you from your first memory file to MCP servers, subagents and hooks. Each lesson is a few minutes, with a checkpoint at the end so you can track progress.

1. Open /learn and start at Lesson 1.
2. Work through each lesson in order; they build on each other.
3. Complete the checkpoint to mark a lesson done.
4. Come back any time; your progress is saved to your account.

Reading guides and news

The Guides section, where you are reading this, lives under /guides. It holds reference articles on memory files, rules, MCP and more. The News feed keeps you current on model releases and tooling changes. Both are free to read and need no account.

Contributing: write an article

Setuproll grows from what the community shares. The editor is block based, which means an article is a stack of typed blocks rather than one wall of text. You add a heading, then a paragraph, then maybe a code sample, and the page renders each block cleanly.

Here is what each block type is for, so you choose the right one as you write.

1. Click Write from your profile menu to open a blank article.
2. Add a title, a one-line excerpt and a category.
3. Build the body block by block in the order you want it read.
4. Use Preview to see the rendered page, then Publish.

Contributing: add a build

To submit your own setup, open /builds and click Add build. Give it a name, pick the model it runs on, and paste in the pieces: your memory file, your rules, your MCP config and any subagents. The fastest way to fill the form is to export an existing build and edit the JSON.

{
  "name": "Next.js Full Stack Rig",
  "model": "claude-sonnet",
  "memory": { "file": "CLAUDE.md", "lines": 24 },
  "rules": [".cursor/rules/api.mdc", ".cursor/rules/react.mdc"],
  "mcpServers": ["github", "playwright", "context7"],
  "subagents": ["reviewer", "planner"],
  "hooks": ["prettier-on-edit", "test-on-stop"],
  "tags": ["nextjs", "typescript", "fullstack"]
}

Adding screenshots, code, links and videos

These four block types do most of the heavy lifting in a good article. Here is how each one works inside the editor.

• Screenshots: you do not upload an image. Choose a screenshot block, pick a window style (editor, chat or pane), and type the rows. Setuproll renders a crisp fake window that never goes stale.
• Code: add a code block, set the language and an optional filename, and paste the snippet. Readers get a copy button for free.
• Links: use a link block for a repo or resource card, or just add an inline link inside any paragraph by selecting text and pasting the URL.
• Videos: add a video block and paste the YouTube id (the part after v=). Add a title and channel so the card reads well.

Commenting

Every build and article has a comment thread at the bottom. Comments are where the real knowledge shows up: someone notes a rule that broke on Windows, someone else shares a tweak that made a build faster. Be specific and link to your evidence.

1. Scroll to the comment box under any build or article.
2. Write your note; basic Markdown and inline code are supported.
3. Mention the author with @ to start a reply thread.
4. Post. You can edit or delete your own comments later.

That is the whole site. Read and compare at /builds and /compare, keep your shortlist at /saved, group your favorites into /stacks, learn the basics at /learn, and when you have a setup worth sharing, write it up and add the build. The best contributions are specific, honest and easy to copy.