agentleFS
Fadi88Fadi88/one-man-startup/.cursor/rules/skill-human-steps.mdc

one-man-startup / rules

Cursor rule16 starsChanged 2 days agoMITView on GitHub

Turn the steps only the founder can do (accounts, domains, payments, store listings, secrets, signatures) into a numbered script they follow, with a check after each step. Use whenever work is blocked on something an agent must not or cannot do.

We split this skill-human-steps.mdc into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write them in docs/work/<id>/human-steps.md:

    line 13
  2. Distinctive:

    After each step, a check the founder can run or a thing they should see.

    line 25
  3. Distinctive:

    Keep the file current; hosts move their buttons.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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
skill-human-steps.mdc
---
description: "Turn the steps only the founder can do (accounts, domains, payments, store listings, secrets, signatures) into a numbered script they follow, with a check after each step. Use whenever work is blocked on something an agent must not or cannot do."
alwaysApply: false
---

<!-- Generated by tools/sync_adapters.py from skills/human-steps/SKILL.md. Edit the source, not this file. -->

# Human steps

Some steps are the founder's alone: creating accounts, verifying a domain, adding a card,
signing an agreement, pasting a secret into a host's secret store, submitting to an app store.

Write them in `docs/work/<id>/human-steps.md`:

```markdown
## 1. Create the production database
1. Open <host dashboard URL>, New project, region <region from project.toml>.
2. Copy the connection string. Do not paste it in chat.
3. Add it as DATABASE_URL in <where the secrets live>.
**Check:** run `<command>`; it should print `connected`.
```

- One action per step, in the order the screens appear.
- Say where each value goes; never ask for a password, key or card number in chat.
- After each step, a check the founder can run or a thing they should see.
- Mark which steps cost money, with the price from the provider's own page and the date you read it.
- Keep the file current; hosts move their buttons.

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.

Reviews can't be read right now.

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.