Skip to main content
rule CX Codex

steering-principles — Claude Code rule: what it does, how to install

steering-principles defines standards for project memory files, capturing architecture patterns without cluttering context with exhaustive file catalogs.

MIT ★ 3,774 updated 2026-10-22

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/rules/steering-principles.md
Open on GitHub

What steering-principles does

This rule treats steering documents as project memory rather than full specifications. If new code follows established patterns, steering files should remain untouched. The instructions focus on organizational conventions and import strategies while forbidding component-by-component listings.

The framework covers product.md, tech.md, structure.md, and custom topics. Sensitive data like database URLs, credentials, or internal IPs must stay out. Each document targets a single domain and typically stays within 100-200 lines.

Updates are additive by default. Agents must preserve existing user sections, add an updated_at timestamp, and explain why changes occurred. Tooling directories like .cursor/ or .claude/ are explicitly excluded from project memory.

What it helps with

  • Keep context memory files within maintainable 100-200 line limits
  • Record architectural standards without enumerating every file in the tree
  • Prevent credentials and internal IP addresses from leaking into context files
  • Preserve custom user sections when automated updates touch documentation

Example prompts for the agent

  • Create a structure.md file following steering-principles standards
  • Review tech.md and remove detailed lists of every single dependency
  • Update product.md additively, keeping custom notes and adding updated_at

How to install steering-principles

Manually: put the files in place

.claude/rules/steering-principles.md

The paths frontmatter field limits the files

Step by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use

Questions about steering-principles

How do I install steering-principles in Claude Code?

Place the instructions into .claude/rules/steering-principles.md inside your repository.

What does steering-principles do?

It enforces guidelines for memory files so agents focus on high-level patterns instead of granular component lists.

What information is prohibited in steering files?

Do not include passwords, API keys, internal IP addresses, complete file trees, or details of agent folders like .claude/.

Source text

steering-principles.md · MIT
# Steering Principles

Steering files are **project memory**, not exhaustive specifications.

---

## Content Granularity

### Golden Rule
> "If new code follows existing patterns, steering shouldn't need updating."

### ✅ Document
- Organizational patterns (feature-first, layered)
- Naming conventions (PascalCase rules)
- Import strategies (absolute vs relative)
- Architectural decisions (state management)
- Technology standards (key frameworks)

### ❌ Avoid
- Complete file listings
- Every component description
- All dependencies
- Implementation details
- Agent-specific tooling directories (e.g. `.cursor/`, `.gemini/`, `.claude/`)
- Detailed documentation of `.kiro/` metadata directories (settings, automation)

### Example Comparison

**Bad** (Specification-like):
```markdown
- /components/Button.tsx - Primary button with variants
- /components/Input.tsx - Text input with validation
- /components/Modal.tsx - Modal dialog
... (50+ files)
```

**Good** (Project Memory):
```markdown
## UI Components (`/components/ui/`)
Reusable, design-system aligned primitives
- Named by function (Button, Input, Modal)
- Export component + TypeScript interface
- No business logic
```

---

## Security

Never include:
- API keys, passwords, credentials
- Database URLs, internal IPs
- Secrets or sensitive data

---

## Quality Standards

- **Single domain**: One topic per file
- **Concrete examples**: Show patterns with code
- **Explain rationale**: Why decisions were made
- **Maintainable size**: 100-200 lines typical

---

## Preservation (when updating)

- Preserve user sections and custom examples
- Additive by default (add, don't replace)
- Add `updated_at` timestamp
- Note why changes were made

---

## Notes

- Templates are starting points, customize as needed
- Follow same granularity principles as core steering
- All steering files loaded as project memory
- Light references to `.kiro/specs/` and `.kiro/steering/` are acceptable; avoid other `.kiro/` directories
- Custom files equally important as core files

---

## File-Specific Focus

- **product.md**: Purpose, value, business context (not exhaustive features)
- **tech.md**: Key frameworks, standards, conventions (not all dependencies)
- **structure.md**: Organization patterns, naming rules (not directory trees)
- **Custom files**: Specialized patterns (API, testing, security, etc.)

© gotalab · MIT · gotalab/cc-sdd

Similar IDE rules

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

From the same set12

The whole set →
design-synthesis design-synthesis is a rule for analyzing gathered requirements before writing a design document. It uses generalization, build-or-adopt, and simplification to set the solution's scope. CX Codex +1 ★ 3,774repo stars tasks-parallel-analysis The tasks-parallel-analysis rule sets checks for marking tasks in tasks.md as parallel work. Use it when an agent drafts an implementation plan and needs to account for dependencies. CX Codex +1 ★ 3,774repo stars requirements-review-gate The requirements-review-gate rule halts work and requires fixing the requirements draft before requirements.md is written. It validates scope coverage, EARS format compliance, and structural quality. CX Codex +1 ★ 3,774repo stars design-review-gate design-review-gate audits draft architectures before generating design.md. It links requirement IDs to concrete components and prevents speculative interfaces. CX Codex +1 ★ 3,774repo stars ears-format The ears-format rule formats acceptance criteria with EARS patterns. Use it when a specification needs clear conditions, subjects, and system responses. CX Codex +1 ★ 3,774repo stars design-discovery-full The design-discovery-full rule systematically maps requirements, existing code, technologies, and risks before design begins. It ensures architectural choices rest on facts rather than assumptions. CX Codex +1 ★ 3,774repo stars design-review design-review reviews technical design documents before coding starts and issues a GO/NO-GO verdict. Caps feedback at three critical issues tied directly to project requirements. CX Codex +1 ★ 3,774repo stars cc-sdd-new-agent The cc-sdd-new-agent skill guides a new coding-agent integration in cc-sdd, from official-format research and planning to implementation checks. CX Codex +1 ★ 3,774repo stars

More in the catalog

Project sponsors

Companies that keep this analytics open