Refactor Personal folder structure for improved organization
Consolidated 16+ top-level categories into 8 clear functional groups (AI, Development, Home-Automation, Infrastructure, Lifestyle, PKM, Professional, Backup). Merged duplicate files (OpenRouter.md, Github.md) and archived originals. This simplifies navigation and improves long-term maintainability. (vault changes by Claude Code)
This commit is contained in:
@@ -10,3 +10,8 @@ matrix-bot
|
||||
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
|
||||
```
|
||||
|
||||
local rag:
|
||||
```
|
||||
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
|
||||
```
|
||||
|
||||
|
||||
@@ -1,7 +0,0 @@
|
||||
|
||||
|
||||
|
||||
release token:
|
||||
```
|
||||
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
|
||||
```
|
||||
@@ -0,0 +1,16 @@
|
||||
|
||||
|
||||
access token:
|
||||
```
|
||||
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
|
||||
```
|
||||
|
||||
access token zed:
|
||||
```
|
||||
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
|
||||
```
|
||||
|
||||
release token:
|
||||
```
|
||||
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
|
||||
```
|
||||
@@ -0,0 +1,40 @@
|
||||
# CLAUDE.md
|
||||
|
||||
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
|
||||
|
||||
## Vault Architecture
|
||||
|
||||
This is an Obsidian vault organized using the PARA method:
|
||||
|
||||
- **000-inbox/**: Temporary storage for new notes and clippings awaiting processing
|
||||
- **100-project/**: Active projects with defined outcomes and deadlines
|
||||
- `Personal/`: Personal projects (hardware, VPS, cooking, etc.)
|
||||
- `Work/`: Work-related projects
|
||||
- `Notes Migration/`: Ongoing vault organization work
|
||||
- **200-area/**: Areas of responsibility and ongoing interests (Blog, Finance, Health, House, Job, etc.)
|
||||
- **300-resources/**: Reference materials organized by topic (Development, Cooking, Gaming, PKM, etc.)
|
||||
- **400-archive/**: Completed or inactive items
|
||||
- **Clippings/**: Web clippings and saved articles
|
||||
- **ReadItLater Inbox/**: Articles queued for reading
|
||||
|
||||
The vault uses Smart Connections (`.smart-env/`) for semantic search with local embeddings (TaylorAI/bge-micro-v2).
|
||||
|
||||
## Vault Refactor Operating Rules
|
||||
|
||||
### Non-negotiables
|
||||
- Never delete information. If replacing/merging notes, move originals to `_archive/` and leave a short stub note linking to the merged result.
|
||||
- Changes must be incremental: one batch = one clear objective + small diff.
|
||||
- Before any edits: propose a plan and list exact files to touch.
|
||||
- After edits: produce a change report (moved/renamed/merged files) and run link checks if available.
|
||||
|
||||
### Scope
|
||||
- Treat this Obsidian Vault as data, not an app project.
|
||||
- Do NOT modify `.obsidian/` unless explicitly asked.
|
||||
|
||||
### Refactor conventions
|
||||
- Use consistent frontmatter keys: `title`, `aliases`, `tags`, `created`, `updated`, `source`.
|
||||
- For merges: keep canonical note in `Notes/` and archive duplicates in `_archive/duplicates/`.
|
||||
- For renames/moves: update wikilinks `[[...]]` across the vault.
|
||||
|
||||
### Workflow
|
||||
1) Audit → 2) Plan → 3) Apply one batch → 4) Summarize → 5) Wait for review before next batch
|
||||
Reference in New Issue
Block a user