38 lines
2.1 KiB
Markdown
38 lines
2.1 KiB
Markdown
# Gemini Workspace Entry
|
|
|
|
Use this file as the Gemini CLI entry point for this workspace.
|
|
|
|
Shared rules and context already live in the normal workspace files. Do not duplicate or reinterpret them here.
|
|
|
|
Read these first:
|
|
|
|
@./AGENTS.md
|
|
@./README.md
|
|
@./agent-memory/README.md
|
|
@./project-knowledge/00-start/start-here.md
|
|
@./project-knowledge/01-current/current-work.md
|
|
@./project-knowledge/01-current/work-items.md
|
|
|
|
## Tool Surface
|
|
|
|
- `AGENTS.md` is the primary shared rule file.
|
|
- `.agents/` is the canonical shared cross-platform surface for workflows and reusable rule/skill content.
|
|
- `.opencode/` is the OpenCode compatibility/runtime surface.
|
|
- `.agent/` is an alias for tools that expect the singular directory naming.
|
|
- `project-knowledge/` is canonical project memory.
|
|
- `agent-memory/` is agent operating memory.
|
|
|
|
## Gemini-Specific Mandatory Loop (Real-Time Auto-Documentation)
|
|
|
|
At the end of EVERY conversational turn, you MUST evaluate the interaction as a senior Obsidian documentation expert:
|
|
|
|
1. **Analyze for Memory Impact:** Did the user's prompt or your subsequent action reveal new technical context, resolve an open question, change an architectural assumption, or shift current priorities?
|
|
2. **Identify Target Canonical Files:** If memory impact is detected, identify WHERE in the `project-knowledge/` directory this information belongs. This is NOT limited to daily logs. It could be:
|
|
- `01-current/current-work.md` (priority shifts, new blockers)
|
|
- `02-work-items/*.md` (story updates, bug reproduction steps)
|
|
- `03-context/` (system architecture, processes, workflows)
|
|
- `04-people/` (stakeholder involvement)
|
|
- `06-daily/YYYY-MM-DD.md` (daily findings)
|
|
3. **Proactive Update:** You MUST use your file editing tools (`replace_file_content` / `multi_replace_file_content`) to inject the new context or CORRECT existing stale context in the appropriate files BEFORE concluding your response.
|
|
4. **No Explicit Prompt Needed:** Do not wait for the user to say "document this". Auto-document implicitly. Ensure you do not pollute the workspace with unverified guesses; only document confirmed context or active hypotheses.
|