dev

A story-based development workflow in which work is split into written tasks that must be approved before coding begins.

In plain words
What is it for?
It helps manage numbered story files, update progress, run tests between subtasks, and prepare the next task.
Why use it?
It makes the current work, approval status, tests, and remaining tasks visible throughout development.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/moclam1905/cocktailrecipes/dev
Clone the repo
git clone --depth 1 https://github.com/moclam1905/CocktailRecipes

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 490 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00490
Opus 5 $0.00000 $0.00245
Sonnet 5 $0.00000 $0.00098
Haiku 4.5 $0.00000 $0.00049

Measured yesterday against content hash 54dbb1b319d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dev scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to dev — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/workflows/dev.mdc · 35 lines

How it starts

The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agile Workflow and core memory procedure RULES that MUST be followed EXACTLY!

  1. When coming online, you will first check if a .ai/*.story.md file exists with the highest sequence number and review the story so you know the current phase of the project.
  2. Always use the .cursor/templates/template-story.md file as a template for the story. The story will be named -.story.md added to the .ai folder
    • Example: .ai/story-1.story.md, .ai/story-2.story.md
  3. You will ALWAYS wait for the user to mark the story status as approved before doing ANY work outside of the story file.
  4. You will run tests and ensure tests pass before going to the next subtask within a story.
  5. You will update the story file as subtasks are completed.
  6. Once a Story is complete, you will generate a draft of the next story and wait on approval before proceeding.
  7. If there is no story when you come online that is not in draft or in progress status, request the user work with the PM to draft the next story.

During Development

  • Update story files as subtasks are completed.
  • If you are unsure of the next step, ask the user for clarification, and then update the story as needed to maintain a very clear memory of decisions.
  • Reference the .ai/architecture.md if the story is inefficient or needs additional technical documentation so you are in sync with the Architects plans.
  • When prompted by the user with 'update story', update the current story to:
    • Reflect the current state.
    • Clarify next steps.
    • Ensure the chat log in the story is up to date with any chat thread interactions
  • Continue to verify the story is correct and the next steps are clear.
  • Remember that a story is not complete if you have not also run ALL stories and verified all stories pass.
  • Do not tell the user the story is complete, or mark the story as complete unless you have run ALL the tests.

YOU DO NOT NEED TO ASK to:

  1. Run unit Tests during the development process until they pass.
  2. Update the story AC and tasks as they are completed.
  3. Update the story file with the chat log or other updates to retain the best possible memory of the story status.

Read the full file on GitHub · 35 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 35 lines · 0 tokens per session scan A 54dbb1b319d2

Subscribe to this mod's changes

dev is a cursor rule published in the GitHub repository moclam1905/CocktailRecipes (1 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 490 tokens. A static security scan graded it A with 0 findings. It is 100% identical to dev, differing in 0 lines, and is treated as a copy.

Related

Other cursor rules, from other repositories

android-project

Core behavior rules for AI agents working on this Android project.

JoDaBaRo/agentic-mobile-rules · 8,084 tokens

android-project-bootstrap

Walks a developer through bootstrapping a BRAND-NEW Android project for agentic CLI delivery — creating the Firebase project, registering the Android app, setting up App Distribution, creating the Google Play Console listing, wiring API access, and installing the Gradle plugins. Use when the user says they're starting…

JoDaBaRo/agentic-mobile-rules · 106 tokens

ios-project-bootstrap

Walks a developer through bootstrapping a BRAND-NEW iOS project for agentic CLI delivery — Apple Developer Program enrollment, App Store Connect listing, provisioning profiles, Fastlane setup from scratch, Firebase App Distribution, TestFlight + App Store first upload. Use when the user says they're starting a new iOS…

JoDaBaRo/agentic-mobile-rules · 108 tokens

android-project-onboarding

Walks a new developer through one-time setup of an EXISTING configured Android project from a blank macOS install — JDK, Android SDK, AVD, scrcpy, shell env vars, credential files, and a smoke-test build. Assumes Firebase project + Play Console listing already exist; user just needs to acquire credentials. Use when…

JoDaBaRo/agentic-mobile-rules · 161 tokens

ios-project-onboarding

Walks a new developer through one-time setup of an EXISTING configured iOS project from a blank macOS install — Xcode, Fastlane, SPM dependencies, code signing, simulator, and a smoke-test build. Assumes App Store Connect + Firebase + Fastlane are already configured upstream; user just needs local toolchain +…

JoDaBaRo/agentic-mobile-rules · 182 tokens

ios-project

Core behavior rules for AI agents working on this iOS project.

JoDaBaRo/agentic-mobile-rules · 4,506 tokens