cronekorkn/dotfiles
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
dotfiles/agents/AGENTS.md
mwiegand d97d9912b4
feat(agents): split global agent config into shared base + per-agent wrappers 
- agents/AGENTS.md: shared, agent-agnostic personal preferences
- agents/AGENTS-claude.md: Claude Code wrapper (@AGENTS.md + @RTK.md)
- agents/AGENTS-opencode.md: OpenCode wrapper (@AGENTS.md)
- Old claude/CLAUDE.md removed; symlinks updated in ~/.claude and ~/.config/opencode

This lets each agent layer in tool-specific content (e.g. the Agent tool
tiering for Claude Code, RTK hooks) without leaking it into other agents.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-11 22:56:14 +02:00

1.3 KiB
Raw Blame History

Personal preferences

Workflow

  • Specs, plans, and design docs go into the repo they describe. When brainstorming, plan-mode, or any flow produces a persistent document (design spec, implementation plan, ADR, etc.), the final destination is always the working tree of the project it belongs to — typically under docs/ (or wherever the project conventionally keeps them). Scratch locations like ~/.claude/plans/<slug>.md are fine during plan mode, but the moment plan mode exits with an approved artifact, copy it into the repo and git commit it. Don't ship a feature while its spec or plan still lives only in a scratch file. If a project's AGENTS.md / CLAUDE.md specifies a different directory, that wins.

Tooling

  • ccc for semantic code search. Repos containing a .cocoindex_code/ directory are indexed by ccc. Reach for it on conceptual questions ("where is X used / which files do Y / what handles Z"), where a keyword grep would miss indirect usage: ccc search '<concept>' --path '**'. Pass --path '**' — without it, results are filtered to the current working directory's subtree. The ccc skill has the full reference; grep/rg/find remain fine for exact-string lookups.