agentleFS
Seriora-ResearchSeriora-Research/seri-agent/.cursor/rules/pstack.mdc

seri-agent / rules

Cursor rule0 starsChanged 2 months agoApache-2.0View on GitHub

pstack/poteto-mode is the conductor for feature and bugfix work. Apply whenever /poteto-mode is in play.

The file

We split this pstack.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Opening a PR runs: Do not skip it.

    line 17
  2. Distinctive:

    After the PR is open, do not dispatch a review subagent unless the user asked.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 6,873 Cursor rule 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
pstack.mdc
---
description: pstack/poteto-mode is the conductor for feature and bugfix work. Apply whenever /poteto-mode is in play.
alwaysApply: true
---

# pstack is the conductor

The pstack plugin stays a plugin. This repo does not vendor `poteto-mode`.

One conductor: `/poteto-mode`. Do not run a second orchestrator on the same work.

## Default path

1. Once per machine: `/setup-pstack` (models in `~/.cursor/rules/pstack-models.mdc`).
2. `/poteto-mode` matching **feature** or **bug fix** (research/plan/perf/refactoring/prototype
   only when the task is that).
3. **Opening a PR runs.** Do not skip it.
4. Repo overlay, in order, before the PR exists:
   - `/blast-radius` — run the code; prove what else can break. The PR body's "Blast Radius"
     heading is not this skill.
   - `/deslop` before commit (cursor-team-kit, not pstack).
   - `/interrogate` when the design is contested, and again as Opening a PR requires.
   - `/no-comments` before review.
5. Skip `shipping` (do not merge). Skip `autopilot-stack` / Graphite unless this repo
   already uses Graphite. Skip `orchestrate` unless the user asked for a multi-PR program.
6. `babysit` only if the user asked to take CI and review threads to merge-ready (still
   no merge).
7. Autonomous phrasing ("going to bed", "run until done", "don't stop") is allowed. Pause
   on irreversible writes (force-push, deploy, data deletion).

Task dispatch: `subagent_type: "poteto-agent"`. If that type is missing, implement
in this context with the same playbook match and the same skip list (`shipping`,
Graphite, `orchestrate`).

After the PR is open, do not dispatch a review subagent unless the user asked.
Gates (lint, typecheck, tests) still run.

## Models

pstack roles: `/setup-pstack` → `~/.cursor/rules/pstack-models.mdc` (user-level).

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.