Skip to content

Set up Compound Engineering repo config - #217

Draft
alycda wants to merge 1 commit into
mainfrom
claude/eager-galileo-iurry9
Draft

alycda wants to merge 1 commit into
mainfrom
claude/eager-galileo-iurry9

Conversation

@alycda

@alycda alycda commented Oct 16, 2026

Copy link
Copy Markdown
Owner

Runs /ce-setup on this checkout and records the standing instructions it offers.

Why

  • .compound-engineering/config.example.yaml is the committed reference of every CE setting, refreshed from the bundled template so it tracks current keys.
  • .compound-engineering/config.yaml is created with every setting commented out, so nothing changes behaviour until a key is uncommented.
  • .context/compound-engineering/ is the scratch directory CE skills write to. It is gitignored so local scratch never reaches a commit.
  • docs/solutions/ is tracked, so the compounding directive ("offer first") fits: agents offer once to capture a learning the final code would not explain.
  • The ce-noslop directive routes reports and summaries to the user through that skill. Code, config, and verbatim quotes are excluded.

Changes

  • .gitignore: add .context/compound-engineering/
  • CLAUDE.md: two paragraphs under "Repository Philosophy" (compounding directive and chat-register directive), inserted verbatim from the ce-setup assets
  • .compound-engineering/config.example.yaml: new, from the template
  • .compound-engineering/config.yaml: new, all settings commented out

The artifact root is unchanged (docs/). No store-mention line was added, because CLAUDE.md already names docs/solutions/, its frontmatter fields, and when it applies.


Generated by Claude Code

Run /ce-setup to bring this checkout to the repo-local state the
compound-engineering skills expect, and record the two standing
instructions it offers so agents follow them without being asked.

Why each piece:
- .compound-engineering/config.example.yaml is the committed reference
  of every setting. Refreshed from the bundled template so it tracks
  the current keys. Team defaults go in config.yaml, which starts with
  every setting commented out, so nothing changes behaviour until a
  key is uncommented.
- .context/compound-engineering/ is the scratch directory CE skills
  write to. Ignored so local scratch never reaches a commit.
- docs/solutions/ is tracked, committed knowledge, so the compounding
  directive ("offer first") is worth having: agents offer once to
  capture a learning that the final code would not explain.
- The ce-noslop directive routes reports and summaries to the user
  through the ce-noslop skill. Code, config, and verbatim quotes are
  excluded.

Specific changes:
- .gitignore: add .context/compound-engineering/
- CLAUDE.md: two paragraphs under "Repository Philosophy", the
  compounding directive and the chat-register directive, inserted
  verbatim from the ce-setup assets
- .compound-engineering/config.example.yaml: new, from the template
- .compound-engineering/config.yaml: new, all settings commented out

The artifact root is unchanged (docs/). The store mention in CLAUDE.md
already names docs/solutions/, its frontmatter fields, and when it is
relevant, so no line was added for it.
@github-actions

Copy link
Copy Markdown
Contributor

⊕ Entity-level changes

.compound-engineering/config.example.yaml

Status Type Name
+ chunk (document)

.compound-engineering/config.yaml

Status Type Name
+ chunk (document)

.gitignore

Status Type Name
↻ Δ chunk lines 41-51 -> lines 41-53

CLAUDE.md

Status Type Name
Δ heading Repository Philosophy

Summary: 2 added, 2 modified, 1 renamed across 4 files

functions and classes, not lines · sem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants