Field guide / sub-domain

Claude: Settings & Config

27

sources in this field

Updated July 16, 2026

Current thesis

The shortest path to orientation.

Claude Code configuration operates at three layers: environment (--dangerously-skip-permissions for autonomy, Zed 500ms autosave, game-sound hooks, recovery flags CLAUDE_CODE_DISABLE_1M_CONTEXT and CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING), context architecture (CLAUDE.md under 200 lines with declarative behaviors, .claude/rules/ with YAML, _MANIFEST.md with priority loading), and skill design (progressive disclosure, state-machine optimization, self-improving eval loops). Six extension mechanisms: Plugins, Skills, MCPs, Commands, Subagents, Hooks. Opus 4.8 upgrades at 4.7 pricing; /fast mode on $200 plan: 2.5x speed at 3x cheaper cost. Marc Andreessen's anti-sycophancy patterns (expertise positioning, adversarial framing, confidence calibration, no hedging) operationalize output discipline. Convergence on three config files: SOUL.md (voice/values brutally specific—generic instructions produce ChatGPT), USER.md (~4000-word user model), AGENTS.md (operational rules, checks, lookup chains). System engineering beats prompt engineering: ~2 hours context architecture lets subsequent prompts be 10 words. Web fetch uses subagent summarization (can lose detail). Hyper-personalization via plain Markdown (USER.md, MEMORY.md, family/) requires no database. Daily drip questions accumulate context; after 6 weeks, interactions shift from transactional to collaborative. Token management: one focused topic per 30-45 minutes, use Sonnet 99%, write reusable scripts.

Evidence board

Claims worth carrying forward
01

Knowledge systems fail because they optimize for input, not output. A vault without a feedback loop is 'a graveyard with good folders.' The fix is three mechanisms: frictionless capture (<10 seconds), a connection layer (Claude reading across notes), and a daily push of insights back to you.

02

Four-layer architecture: (1) Capture tools—Readwise, Airr, Whisper, Telegram bot; (2) N8N pipeline routing content into vault; (3) Obsidian as permanent markdown storage; (4) Claude as intelligence layer reading across everything. Each layer has one job; nothing overlaps.

03

Telegram-to-Obsidian quick capture: N8N workflow—Node 1: Telegram Trigger (message, bot_id); Node 2: Code node formats markdown (inbox/{{date}}-quick-capture.md); Node 3: Write File to vault /inbox/. Takes 30 minutes to build with Claude Code and N8N. Handles all phone captures permanently after that.

04

CLAUDE.md is the root-level context file Claude reads at session start. Required sections: Who I Am (name, work, focus, goals), Current Projects (active, stuck, next milestone), vault folder map, behavioral instructions (surface connections, challenge assumptions, flag contradictions), and current reading/obsessions. Update Current Projects and Reading sections weekly.

05

Daily brief prompt runs via N8N at 6am on a schedule: reads /inbox (last 24h) and /notes (last 7 days), outputs three things—(1) 3 specific connections between recent and older notes with quoted passages; (2) one pattern across the week's reading; (3) one question worth sitting with today. Saves to /inbox/brief-{{date}}.md automatically.

06

Weekly synthesis prompt asks Claude to identify: (1) emerging thesis forming in your thinking; (2) contradictions between recent saves and prior beliefs (showing both from your own notes); (3) knowledge gaps—what perspective is missing; (4) single highest-leverage action. Framed as 15-minute Monday session. This is where compounding actually occurs.

07

Five-folder vault structure designed to resist collapse: Inbox (raw captures), Notes (processed sources), Ideas (your own thinking), Projects (active work), CLAUDE.md (root). Rule: when in doubt, put it in inbox. Complex folder structures fail because categorization ambiguity raises capture friction until the system breaks.

08

Compound effect timeline: Month 1—useful tool. Month 3—Claude connects notes from 8 weeks ago to current problems you've forgotten. Month 6—full record of beliefs held and changed, patterns recognized before you consciously named them. Six-month head start is not closeable by working harder—only by starting earlier.

Adjacent fields

Key voices

Latest evidence

Recent additions

All synthesized insights →

CyrilXBT

How to Build an Obsidian Knowledge Vault That Gets Smarter Every Day Without You Doing Anything

A detailed 6-step system for building an Obsidian vault that auto-captures content via Readwise, Airr, Whisper, and a Telegram bot, routes everything through N8N pipelines, and uses Claude to generate daily briefings and weekly syntheses. The core thesis: knowledge systems fail because they optimize for input, not output—feedback loops (daily briefs, weekly synthesis) are what turn a dead archive into a thinking partner.

Charlie Hills

Garry Tan's gstack: 23-Skill AI Engineering Team for Claude Code

gstack is Garry Tan's open-source Claude Code setup that transforms a solo AI assistant into a structured 6-role virtual engineering team (CEO, Eng Manager, Designer, QA, Release Engineer, Doc Engineer) via 23 slash-command skills. Tan claims ~810× his 2013 productivity rate measured in normalized logical lines of code, shipping 3 production services and 40+ features in 60 days part-time. The system enforces a think→plan→build→review→test→ship→reflect sprint discipline where each skill feeds context into the next, and supports 10-15 parallel sprints via Conductor.

Aakash Gupta

Team OS in Claude Code: Shared Repo Architecture for Institutional Knowledge

Hannah Stulberg (DoorDash PM) built a shared git repo where every team function checks in context—call summaries, decision logs, analytics queries—queryable in natural language via Claude Code. Four independent implementations (DoorDash, Pendo, Google, solo) converged on the same 3-layer architecture, suggesting a generalizable pattern for solving institutional knowledge loss.

Marc Andreessen 🇺🇸

Marc Andreessen's Production AI System Prompt

Andreessen shares his working custom system prompt for AI assistants, optimized for accuracy over approval: world-class expert framing, step-by-step verification, no sycophancy, no disclaimers, explicit confidence levels, and a rule to lead with the strongest counterargument before supporting any position.

Delba

Claude Code: Building Self-Verification Feedback Loops

Delba Oliveira's guide explains how to encode manual verification steps as Claude Code skills so the agent self-verifies during the agentic loop, reducing babysitting. Two verification layers are recommended: an in-loop skill chain (verify, simplify, design check, CI watch) and a second agent reviewing the PR before merge using a fresh context to avoid first-agent bias.