Skip to main content
rule

003-workflow — Claude Code rule: development standards

003-workflow — a rule that enforces atomic commits, AI context management, and change discipline. Use it with Claude Code, Cursor, or GitHub Copilot to keep your development process consistent and intentional.

MIT ★ 97 updated 2026-06-11

Install into Cursor · Manually: put the files in place All methods and platforms ↓
.cursor/rules/003-workflow.mdc
Open on GitHub

What 003-workflow does

The rule codifies nine standards: atomic changes for traceability and rollback, conventional commit format (feat, fix, docs, etc.), and strict scope discipline—modify only files relevant to the current task, no unsanctioned improvements. It manages AI context windows by encouraging modular files and file-scoped commands instead of project-wide operations.

Other principles: never touch production configs, maintain separate DEV, TEST, PROD setups. Transparent reasoning—when generating code, reference which rule influenced the decision. No new dependencies without explicit approval. Optimize context by referencing docs instead of pasting them. Comment only complex logic and critical functions, not the obvious. After code generation, argue against your own solution and look for redundancy or simpler alternatives.

The rule installs to Cursor (.cursor/rules/003-workflow.mdc), Claude Code (.claude/rules/003-workflow.md), GitHub Copilot (.github/instructions/003-workflow.instructions.md), and Cline (.clinerules/003-workflow.md).

What it helps with

  • enforce consistent commit messages across a team
  • prevent accidental changes to unrelated files
  • stay within AI context window limits
  • keep production configuration out of AI system prompts
  • control dependency bloat

Example prompts for the agent

  • Add 003-workflow to your Claude Code and verify commits follow feat(auth): add token validation format
  • Tell Claude that 003-workflow is active and ask it to only touch files directly tied to your task
  • When Claude generates code, request that it reference which parts of the rule it applied

How to install 003-workflow

Manually: put the files in place

.cursor/rules/003-workflow.mdc

Frontmatter: description, globs, alwaysApply

Step by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules

Questions about 003-workflow

How do I install 003-workflow in Claude Code?

Copy the rule file to .claude/rules/003-workflow.md in your project root. Claude Code will pick it up automatically on your next session.

What does 003-workflow do?

It defines nine standards for AI interaction: atomic commits, change scope discipline, context window management, separate environment configs, transparent reasoning, and self-review before commit.

Does installation differ between Cursor and GitHub Copilot?

Yes. Cursor uses .cursor/rules/003-workflow.mdc, GitHub Copilot uses .github/instructions/003-workflow.instructions.md, and Cline uses .clinerules/003-workflow.md. Copy the file to the appropriate folder for your tool.

Source text

003-workflow.mdc · MIT
---
description: Development workflow standards and AI interaction patterns
globs:
alwaysApply: true
---

# Workflow Standards

## Atomic Changes (AC)
Make small, self-contained modifications for traceability and rollback.

## Commit Discipline (CD)
Use conventional commit format: type(scope): description
Types: feat, fix, docs, style, refactor, test, chore

## Change Scope Discipline (CSD)
Only modify files directly related to the current task.
Never make unrelated "improvements" without explicit permission.

## Context Window Management (CWM)
- Be mindful of AI context limitations
- Keep files focused and modular
- Use file-scoped commands for individual changes
- Only run project-wide commands when explicitly requested

## Environment Awareness
- Never modify production environment configurations
- Maintain separate configs for DEV, TEST, PROD
- Never hardcode environment-specific values

## Transparent Reasoning (TR)
When generating code, explicitly reference which rules influenced decisions.

## Dependency Governance
Never add new dependencies without explicit approval or compelling justification.

## Token Efficiency
Use file-scoped commands. Reference docs instead of pasting. Optimize context window usage.

## Industry Standards
Follow established conventions for the relevant language and tech stack.

## Strategic Documentation
Comment only complex logic or critical functions. Avoid documenting the obvious.

## Self-Review Before Commit
After generating code, argue against your own solution. Check for redundancy, unnecessary complexity, or simpler alternatives.

© obviousworks · MIT · obviousworks/vibe-coding-ai-rules

Similar IDE rules

All IDE rules for Agent setup: memory, context, orchestration →

From the same set7

Project sponsors

Companies that keep this analytics open