35 lines
1.5 KiB
Markdown
35 lines
1.5 KiB
Markdown
# Agent Instructions
|
|
|
|
This repository stores agent-generated artifacts across projects.
|
|
|
|
## Layout
|
|
|
|
- Use `projects/` for project-specific artifacts.
|
|
- Use `projects/<project>/...` where `<project>` is the lowercase basename of the project directory.
|
|
- Use project-specific subdirectories such as `spec/`, `tasks/`, or `adr/` when appropriate.
|
|
- Treat that list as examples, not as an exhaustive or required taxonomy.
|
|
- Use `wiki/` for cross-project Markdown knowledge entries.
|
|
- Do not write to `wiki/` unless the user explicitly instructs you to do so through a dedicated skill.
|
|
- Keep `wiki/` flat.
|
|
- Do not create subdirectories under `wiki/`.
|
|
- Use `tags/` for Markdown tag files.
|
|
- Keep `tags/` flat.
|
|
- Do not create subdirectories under `tags/`.
|
|
- Do not create `.gitkeep` files.
|
|
- Keep user-facing top-level artifact directories limited to `projects/`, `wiki/`, and `tags/`.
|
|
- Hidden tool directories such as `.git/` and `.obsidian/` are allowed.
|
|
|
|
## Tags
|
|
|
|
- Tag files exist only to form clusters in the Obsidian graph view.
|
|
- Keep tag files free of semantic content.
|
|
- A trailing newline is acceptable.
|
|
- Link to tag files with explicit Obsidian wikilinks, such as `[[tags/example]]`.
|
|
- For project-specific artifacts, when they use tag links, place them on a compact first line.
|
|
- Do not define the internal structure of wiki entries yet.
|
|
|
|
## Gotchas
|
|
|
|
- Do not apply project-specific artifact structure rules to wiki entries.
|
|
Wiki entry structure is intentionally undecided.
|