Global configuration
The global~/.claude/settings.json keeps the base minimal and pushes specifics down to projects.
- Theme
dark; workflow-usage warnings skipped. - Enabled plugins:
figmaandlinear(fromanthropics/claude-plugins-official) plushyper.
Hyper session hooks
The most distinctive piece: Hyper — a shared team-memory layer — is wired into the Claude Code session lifecycle so context flows in at the start of a session and observations flow back out at the end.
Permissions pre-allow all
mcp__hyper__* tools and the Hyper token scripts.
Hyper (HTTP,
api.heyhyper.ai) is the only persistent global MCP server. It is the primary cross-agent memory layer.MCP servers
Persistent
hyper — always on, for team memory.On-demand
Notion, Gmail, Google Drive / Calendar, Linear, Vercel, Figma, Chrome control, computer-use, and PowerPoint — loaded via plugins and connectors as needed.
Skills
Global skills are intentionally minimal (correct, mute, find-skills — all Hyper-related). Real skill usage is project-scoped — see the GreekCore workspace pattern for how third-party skills are vendored and content-pinned like dependencies.
No custom global subagents or slash commands — the setup relies on built-ins (
Explore, Plan, general-purpose) plus plugin-provided ones.How Claude Code is actually used
Parallel worktrees
Git worktrees let multiple agents and experiments run without colliding — common across
personal-site, relic-core, and the GreekCore landing.Variant forks
Parallel design exploration via forks:
personal-site / -var-1 / -var-2, mirroring GreekCore-v1 vs greekcore-v2.Per-project launch config
A per-project
.claude/launch.json configures the /run skill’s app-launch behavior.Linear in the loop
The Linear plugin is used actively; Figma is installed but lightly used so far.