Files

Lex Christopherson a97c567b01 feat: add .claude/rules/ for auto-loaded contribution rules

Split GSD style guidance into:
- .claude/rules/style.md - global style rules (always loaded)
- .claude/rules/commands.md - path-scoped for commands/gsd/
- .claude/rules/workflows.md - path-scoped for workflows/
- .claude/rules/templates.md - path-scoped for templates/
- .claude/rules/references.md - path-scoped for references/
- GSD-STYLE.md - comprehensive reference for deep dives

Rules auto-load via Claude Code's .claude/rules/ feature (v2.0.64+).
Path-scoped rules only activate when editing matching files.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-13 15:23:21 -06:00

1.2 KiB

Raw Blame History

paths

get-shit-done/workflows/**/*.md

Workflow Rules

Rules for editing files in get-shit-done/workflows/.

No Frontmatter

Workflows don't use YAML frontmatter. Content starts immediately.

Common XML Tags

These tags appear across workflows, but not all workflows use all of them:

<purpose> — What this workflow accomplishes
<when_to_use> — Decision criteria (some workflows use <trigger> instead)
<required_reading> — Files to read before starting
<process> — Container for execution steps
<step> — Individual step within process

Some workflows also use domain-specific tags like <philosophy>, <references>, <planning_principles>, <decimal_phase_numbering>.

Step Elements

When using <step> elements:

name attribute: snake_case (e.g., name="load_project_state")
priority attribute: Optional ("first", "second")

Conditional Logic

<if mode="yolo">
  Content for yolo mode
</if>

Conditions reference .planning/config.json values.

Key Principle

Workflows contain detailed execution logic. Commands are thin wrappers that delegate to workflows.

Match the style of the specific workflow you're editing — patterns vary across files.

1.2 KiB Raw Blame History