Refactor workspace structure and documentation

- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md
- Updated opencode.json to remove references to deleted files.
- Revised profile.md to clarify the status of legacy paths and communication evidence.
- Adjusted prompts to reflect new file paths and improve clarity.
- Enhanced daily logs with focus, work-items, and blockers properties.
- Updated work-item notes to include systems, workstreams, people, and related properties.
- Improved context maintenance guidelines to ensure accurate and durable project knowledge.
- Refined base filters to exclude template files and ensure only relevant notes are displayed.
- Updated daily templates to ensure proper formatting and consistency.
- Modified workflows to align with the new vault structure and improve context synchronization.
This commit is contained in:
2026-04-16 16:28:30 -06:00
parent b82194bc55
commit 374991a568
148 changed files with 214 additions and 3576 deletions

View File

@@ -18,10 +18,10 @@ Use this skill when the user wants a prompt for another AI assistant, GitHub Cop
- test strategy
- story/PR drafting
2. Pull only the relevant context:
- `ai/work-items/` for ticket-specific context
- `ai/context/systems/` for component context
- `ai/context/workstreams/` for recurring constraints
- `ai/context/ios/` for Swift/iOS guidance
- `vault/02-work-items/` for ticket-specific context
- `vault/03-context/systems/` for component context
- `vault/03-context/workstreams/` for recurring constraints
- `vault/03-context/ios/` for Swift/iOS guidance
3. Make the prompt self-contained.
4. Tell the target AI what to inspect before acting.
5. State constraints, non-goals, and validation expectations.