Files
claude-config/rules/goals-and-audience.md
T

2.4 KiB

paths
paths
**/README.md
**/.claude-projects/*/goals.md

Goals and Audience

A project's goals and audience live in its goals file (~/.claude/CLAUDE.md → "Vocabulary"): README.md, or a client project's goals.md in its config's folder or its plan epic's description in Jira.

  • Goals state the project's aim and intent, not promises: one numbered line each, like slogans, in priority order; a sub-goal is indented under its goal — "1. Blazing fast performance. 2. Correctness is more important than many features." A goal names no step of the work, such as a check to run first, and rarely an implementation. How a goal is met goes in a method section further down the goals file and names the goal it serves. BANNED as a goal: Kill weak candidates early, with the cheap checks first. GOOD: the goal Keep research on a budget, so it scales in both time and cost., with the cheap checks moved to the method section, naming that goal.
  • Mark each goal **Maintain:** or **Achieve:**. A maintain goal is a state to hold: a change that breaks it is redesigned or dropped, whatever its value to other goals. An achieve goal is a direction to pursue, weighed against the other achieve goals. Under each achieve goal, three indented bullets: Signal: what moving towards it looks like, Counter-signal: what shows it is bought at a wrong price, and Why: one line on how the two connect. A goal with sub-goals states its own signal. A maintain goal has no bullets. BANNED: an unmarked goal; an achieve goal with no signal; **Achieve:** Delivery speed. with the signal faster. GOOD: **Achieve:** Delivery speed. with Signal: hours from a chunk's start to its merge fall., Counter-signal: 🔴 findings per chunk rise. and Why: speed bought by skipping review shows up as defects.
  • Leave code health out of the goals file. ~/.claude/CLAUDE.md → "Shared goal" states it for every project, ranked first, and says when and how a goals file voids it. File an item to drop a goal that restates it: the goals after it renumber, and every Moves cell and decision citing them must follow.
  • Audience names who depends on the project and what they may rely on.
  • Every project's audience includes the contributor: the person who reads the code to change it. The goals file doesn't list them, and drops them only with the **Void:** code health line (~/.claude/CLAUDE.md → "Shared goal").