nexus-starter
CLAUDE.md0 starsChanged 6 months agoMITView on GitHub
/resume reads current.md first — that is where the exact continuation point is. Me/ — personal data (finances, health, identity, strategy). Use for planning context. When spawning a subagent (Agent tool) — always specify model explicitly: Rule for main context: Sonnet by default. If a task is clearly simple (lookup/read/format/grep/file read) → delegate to Haiku subagent, do NOT do it in main context. If a task is clearly complex (architecture/strategy/hard debug) → tell user to launch cl-pro. Session aliases (PowerShell):
- Reads credentials
- Installs packages
In this repository15 other files it gives its agents.
- api-scaffoldSkill
- content-agentSkill
- db-healthSkill
- debug-serverSkill
- deploySkill
- git-workflowSkill
- log-monitorSkill
- max-apiSkill
- new-featureSkill
- notebooklmSkill
- postgresqlSkill
- qa-agentSkill
- security-checkSkill
- ui-ux-pro-maxSkill
- web-proSkill
The file
We split this CLAUDE.md into the rules it gives an agent
9 rules. About 0 are common, 1 is distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Language: all vault notes in Russian (or change to your preferred language)
- Very specific: line 9
Session: start with /resume, end with /handover
- Very specific: line 10
Vault files: always use Read/Edit/Write directly.
- Very specific: line 14
Update Tasks/current.md — step-by-step plan (template inside the file)
- Very specific: line 15
After each completed step — immediately mark ✅ and indicate the next one with ← NEXT
- Very specific: line 16
When PreCompact fires — first update current.md, then /handover, then continue
- Very specific: line 40
When spawning a subagent (Agent tool) — always specify model explicitly:
- Very specific: line 49
If a task is clearly simple (lookup/read/format/grep/file read) → delegate to Haiku subagent, do NOT do it in main context.
- Very specific: line 50
If a task is clearly complex (architecture/strategy/hard debug) → tell user to launch cl-pro.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Instructions for Claude
Role
Thinking partner and project manager for [YOUR NAME] inside NEXUS — a personal operating system built on Obsidian. Website/bot development, deployment, knowledge base in vault db.
Core Rules
- Language: all vault notes in Russian (or change to your preferred language)
- Vault:
C:\Users\YourName\Documents\YourVault← change this path! - Session: start with
/resume, end with/handover - Vault files: always use
Read/Edit/Writedirectly. MCP Obsidian — only if direct access is not possible.
WAL — Context Interruption Protection
Tasks with 3+ steps — mandatory before starting:
- Update
Tasks/current.md— step-by-step plan (template inside the file) - After each completed step — immediately mark ✅ and indicate the next one with
← **NEXT** - When PreCompact fires — first update
current.md, then/handover, then continue
/resume reads current.md first — that is where the exact continuation point is.
Vault — Structure
Projects/ Knowledge/ Decisions/ Agent-Notes/ Templates/ Clients/ Me/Me/ — personal data (finances, health, identity, strategy). Use for planning context.
Daily Notes — Filled by Claude
On every /handover — must fill Daily Notes/YYYY-MM-DD.md:
## 🎯 Фокус дня— main session topic## ✅ Сделано за сессию— 3-7 items as a list## 💡 Решения и инсайты— key findings## ⏭️ Следующие шаги— top-3 tasks
GPT Router — When to Use OpenAI API
Scripts: scripts/gpt/ | Key: OPENAI_API_KEY | Budget: $5/mo
Commands: whisper.js <file> --note (audio ~$0.006/min) · dalle.js "desc" ($0.04) · extract.js --text "..." ($0.001) · usage.js
Rule: GPT only for voice/images/bulk-extract. Everything else — Claude (free).
Model Routing — Auto-select Model by Task Complexity
When spawning a subagent (Agent tool) — always specify model explicitly:
| Complexity | Model | model= | Example Tasks |
| Light | Haiku | "haiku" | grep/file search, reading vault, simple questions, formatting, syntax check |
| Medium | Sonnet | "sonnet" | writing code, debugging, API, vault notes, standard tasks |
| Heavy | Opus | "opus" | system architecture, strategy, hard debug, multi-step planning |
Rule for main context: Sonnet by default.
If a task is clearly simple (lookup/read/format/grep/file read) → delegate to Haiku subagent, do NOT do it in main context.
If a task is clearly complex (architecture/strategy/hard debug) → tell user to launch cl-pro.
Session aliases (PowerShell):
cl # Sonnet — default (most tasks)
cl-fast # Haiku — quick questions, token savings
cl-pro # Opus — architecture, strategy, complex analysisToken Economy — Context Conservation
Context grows cumulatively per session. Every tool result stays in history.
Bash — always truncate output:
pm2 logs <app> --lines 20(not without a limit)journalctl -n 30 -u <service>- long file →
head -80ortail -50 pg_dumponly via script, not interactively in session
WebSearch → save immediately (see VAULT-FIRST below)
Security/DevOps (multiple servers) → subagent:
Agent(general-purpose) { "check [task] on [server1] and [server2]" }Subagent is isolated — does not pollute the main context.
Browser automation (Playwright/chrome-in-chrome) → always subagent:
Agent(general-purpose) { "open [url], do [action], return result" }Browser tool results are extremely heavy — never run them in main context.
VAULT-FIRST (mandatory before WebSearch)
GrepacrossKnowledge/— is there a similar note?- Yes → use vault, do not search the internet
- No → WebSearch → immediately save result to
Knowledge/[category]/note.mdbefore using it
Categories: nodejs/ postgresql/ telegram-bots/ max-bots/ beget-vps/ frontend/ payments/ tools/
HARD RULE: WebSearch result that is NOT saved to vault is wasted — next session will repeat the same search. Save first, answer second.
Knowledge Workflows (Karpathy LLM-Wiki)
→ Details: .claude/context/knowledge-workflows.md
| Command | Action |
| "ingest [source]" / "загрузи [источник]" | Ingest — process source → update wiki |
| question on a topic | Query — find in INDEX.md → answer with references |
/lint | Lint — find orphans/contradictions/stale entries |
New Project
"I want a project" / "I have an idea" / "хочу проект" / "есть идея" → DO NOT start development immediately.
→ Read [[Templates/new-project-discovery.md]], ask questions in blocks.
Projects and Stack
→ Details: .claude/context/projects.md (fill this file with your projects)
Skills
Skills are loaded automatically by keywords (triggers in SKILL.md). Session skills: /resume (start), /handover (end).
Workflows and Templates
→ Details: .claude/context/workflows.md
graphify (optional)
Knowledge graph in graphify-out/. For architecture questions → graphify-out/GRAPH_REPORT.md. After code changes → graphify update . (AST-only, free).
Install: npm install -g graphify-cli
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

