a97c567b01
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>
49 lines
976 B
Markdown
49 lines
976 B
Markdown
---
|
|
paths:
|
|
- "get-shit-done/templates/**/*.md"
|
|
---
|
|
|
|
# Template Rules
|
|
|
|
Rules for editing files in `get-shit-done/templates/`.
|
|
|
|
## Structure Varies
|
|
|
|
Templates don't follow a uniform structure. Some patterns:
|
|
|
|
- Most start with `# [Name] Template` header
|
|
- Many include a `<template>` block containing the actual template content
|
|
- Some include examples or guidelines sections
|
|
|
|
## Placeholder Conventions
|
|
|
|
**Square brackets** for human-fillable placeholders:
|
|
```
|
|
[Project Name]
|
|
[Description]
|
|
```
|
|
|
|
**Curly braces** for variable interpolation:
|
|
```
|
|
{phase}-{plan}-PLAN.md
|
|
.planning/phases/{phase}/
|
|
```
|
|
|
|
## YAML Frontmatter in Template Content
|
|
|
|
Templates that define output documents often show example frontmatter:
|
|
|
|
```yaml
|
|
---
|
|
phase: XX-name
|
|
plan: YY
|
|
type: execute
|
|
---
|
|
```
|
|
|
|
This is content TO BE GENERATED, not frontmatter for the template file itself.
|
|
|
|
## Key Principle
|
|
|
|
Templates show structure for generated documents. Match the style of the specific template you're editing.
|