← all repositories
Bhartendu-Kumar/rules_template

Stop rewriting your AI rules for every IDE

A template that makes Cursor, CLINE, and RooCode share one Agile workflow, one memory bank, and fewer wasted tokens.

rules_template
Not currently ranked — collecting fresh signals.
star history

What it does

This repository is a template of markdown rule files and directory scaffolding meant to standardize how AI coding assistants behave. It drops into Cursor, CLINE, or RooCode to enforce an Agile-style development workflow, maintain shared project memory across tools, and auto-update documentation after every planning or coding session. The premise is that prompt quality is a first-class dependency: better instructions in, better code out.

The interesting bit

The whole setup hinges on symbolic links: one canonical .cursor/rules/ directory feeds RooCode and CLINE via symlinks, so you maintain a single source of truth instead of three divergent prompt files. The author also ships custom IDE modes—Chat, Write, and MCP—that strip each assistant down to the bare minimum tools needed for the job, which they claim keeps token usage lean without sacrificing capability.

Key highlights

  • Cross-platform via symlinks: edit rules once and they propagate to Cursor, RooCode, and CLINE simultaneously.
  • On-demand loading: only mode-specific .mdc rule files are injected, avoiding the cost of hauling in irrelevant prompts.
  • Shared memory bank: a common docs/ and tasks/ structure keeps context consistent when you switch between AI assistants mid-project.
  • Auto-documentation: the prompts are designed to force the AI to update architecture and planning docs after every change.
  • Token-saving custom modes for RooCode and Cursor restrict tool access to exactly what the current task requires.

Caveats

  • CLINE support is second-class: the README concedes there is “not much support there to save tokens for custom prompts,” and the lean custom modes don’t apply to it.
  • RooCode’s mode switching resets prompt caching mid-task, which can waste the tokens the template is designed to conserve.
  • You must keep the .cursor/rules/ directory as the canonical source even if you don’t use Cursor, because RooCode and CLINE rely on those originals via symbolic links.

Verdict

If you are juggling multiple AI IDEs on the same project and tired of rewriting system prompts, this template is worth a look. If you are a solo Cursor user who never touches CLINE or RooCode, it is probably over-engineered for your needs.

Frequently asked

What is Bhartendu-Kumar/rules_template?
A template that makes Cursor, CLINE, and RooCode share one Agile workflow, one memory bank, and fewer wasted tokens.
Is rules_template open source?
Yes — Bhartendu-Kumar/rules_template is an open-source project tracked on heatdrop.
How popular is rules_template?
Bhartendu-Kumar/rules_template has 1.1k stars on GitHub.
Where can I find rules_template?
Bhartendu-Kumar/rules_template is on GitHub at https://github.com/Bhartendu-Kumar/rules_template.

heatdrop uses Google Analytics to see which pages get read — nothing else. Your call. How we handle data.