agentleFS
Sign inStart free
vasceannievasceannie/slopgate/.cursor/rules/dev-workflow.mdc

slopgate / rules

Cursor rule1 starsChanged 51 days agoMITView on GitHub

Monorepo developer workflow standards - mise tasks, git hooks, CI/CD, release automation

We split this dev-workflow.mdc into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Use mise run tasks instead of direct package manager commands

    line 13
  2. Very specific:

    Run mise install after pulling changes that update runtime versions

    line 14
  3. Distinctive:

    Use parallel tasks for independent operations

    line 15
  4. Distinctive:

    Run lint/test only on apps with changed files

    line 16
  5. Very specific:

    Check mise tasks --all to discover available tasks before running

    line 19
  6. Distinctive:

    Never use direct package manager commands when mise tasks exist

    line 21
  7. Very specific:

    Never modify mise.toml without understanding task dependencies

    line 22
  8. Very specific:

    Never hardcode secrets in mise.toml files

    line 23
  9. Distinctive:

    Never skip reading task definitions before running unfamiliar tasks

    line 24

≈ “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
dev-workflow.mdc
---
description: "Monorepo developer workflow standards - mise tasks, git hooks, CI/CD, release automation"
globs: 
alwaysApply: false
---

<!-- Generated by oh-my-agent. Source: .agents/rules/dev-workflow.md -->

# Developer Workflow Standards

## Core Rules

1. Use `mise run` tasks instead of direct package manager commands
2. Run `mise install` after pulling changes that update runtime versions
3. Use parallel tasks for independent operations
4. Run lint/test only on apps with changed files
5. Validate commit messages with commitlint before committing
6. Configure CI to skip unchanged apps for faster builds
7. Check `mise tasks --all` to discover available tasks before running
8. Pin runtime versions in mise.toml for consistency
9. Never use direct package manager commands when mise tasks exist
10. Never modify mise.toml without understanding task dependencies
11. Never hardcode secrets in mise.toml files
12. Never skip reading task definitions before running unfamiliar tasks

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.

Check your setup, free