FRANK
ANAYA
The Ecosystem Map

Four Doors,
One House.

There is not one Claude. There are four interfaces to the same intelligence, each built for a different moment in your work.

↳ The decision framework, the three levels of Obsidian integration, and six skills you can copy today.

Claude · The Ecosystem Map frankanaya.com →
What's inside
Contents
01 The map at a glanceFour doors into the same intelligence, the memory file, and the one voice rule — on one sheet
02 The decision frameworkSix situations, six answers — plus when to delegate to Cowork instead of steering by hand
03 The three levels of Obsidian integrationDirect file access, MCP, and the full system with CLAUDE.md — each level additive
04 Six skills and three systemsCopy-ready workflows and the daily, weekly and Friday routines they chain into
How to use this

Print it or keep it open in a tab. Every page stands alone — but they're ordered, and the order is the method. The full guide this comes from is linked on every page.

Claude · The Ecosystem Mapfrankanaya.com
FRANK
ANAYA
Claude · Ecosystem Map
Which tool for which moment

Four doors, one house.

These are not competing products. They are four entrances to the same thing — and knowing which to use is most of the skill.

1
Claude.ai for thinking
Questions, research, pressure-testing. No setup, no files, no commitment.
2
Claude Code for doing
It reads and writes your actual folders. This is where work happens.
3
Cowork for delegating
Hand off a task and keep working. The point is not speed, it is parallelism.
The map
Which door, when
The whole decision
  • ✓Thinking → Claude.ai
  • ✓Doing → Claude Code
  • ✓Delegating → Cowork
  • ✓Repeating → Skills
CLAUDE.md
Beyond the basics
  • ✓Written rules it follows
  • ✓Structure it respects
  • ✓Voice it protects
  • ✓One file, every session
Custom Skills
When you repeat yourself
  • ✓A repeated prompt is a skill
  • ✓Write it once, invoke by name
  • ✓Lives in the vault, travels with you
What's on this page
4tools
1memory file
5min to first session
1rule: never let it write your voice
The vault behind the workflow
The free Creator Vault ships the structure, the Dashboard and the prompts from this guide.
The Creator Vault
Free · plain Markdown · yours
frankanaya.com →
The decision framework & the three levels
Page 2 · Which door, when
Which Claude tool for which moment
Quick question, no filesClaude.ai. Browser conversation — paste in, get responses. No memory between sessions, no file access.
Read or edit my filesClaude Code. Terminal-based; reads your actual files, edits them directly, remembers you via CLAUDE.md.
Delegate and keep workingClaude Cowork. Assign a task, it runs in the background, you get notified when it's done. Best for well-defined, multi-step work that doesn't need your judgment at every step.
Connect to Obsidian or other appsClaude Code + MCP, or Claude Desktop. Desktop is the native app with built-in MCP support — the connector without the terminal.
Repeatable workflow, one commandClaude Code + a custom skill. Write the instructions once, invoke by name.
Building my own toolClaude API. The building block. Requires programming knowledge.
Claude + Obsidian — three additive levels
Level 1 · File accessYour vault is already a folder of Markdown files. cd in, run claude — read, edit, create, move, search in plain English. No plugin, no setup. Covers 80% of what most people need.
Level 2 · MCPTen minutes of setup connects Claude to Obsidian's running instance: native tag search, backlinks, the graph, the plugin ecosystem.
Level 3 · Skills + CLAUDE.mdAccess becomes understanding. Your CLAUDE.md carries your folder structure, conventions, status system and rules — every prompt already knows how your vault works.
The power move

Use multiple tools in the same day. Claude.ai for morning brainstorming. Claude Code for editing your draft. Cowork for a vault audit running in the background while you write. Skills for your weekly review. That is a system — not just a tool.

Claude · The Ecosystem Mapfrankanaya.com/claude-tutorial/
Six skills & three systems
Page 3 · Copy, paste, use
Six skills you can copy right now
/morning-reviewReads your Daily Notes from the past week; generates a briefing with focus areas, open threads, and today's priorities.
/draft-newsletterTurns scattered notes into an 800-word draft in your voice. Leads with the insight, ends with one actionable takeaway.
/inbox-processClassifies everything in your Inbox — develop, file, or archive — and shows you the plan before executing.
/weekly-reviewAccomplishments, open threads, the theme of the week, and three questions for next week — from your notes and file activity.
/link-auditFinds orphan notes with zero backlinks and suggests 2–3 connections each, with reasons. Flags clusters that need a Map of Content.
/multiplyOne piece of content → LinkedIn post, tweet-thread opener, video outline, email teaser, and three pull quotes.
The three systems they chain into
The Morning PracticeOne command each morning: /morning-review. Two minutes, and you start the day with clarity instead of scanning notes and hoping something clicks.
The Content PipelineCapture all week. On Friday: /draft-newsletter, then /multiply. From scattered notes to a full content week in under 30 minutes.
The Sunday Reset/weekly-review, /inbox-process, and /link-audit — read the review while the rest runs. You end the week with a clean system and a clear picture of what happened.
Chain themA skill can run other skills in sequence — a single /sunday-reset meta-skill triggers all three from one command.
The fastest way to create a skill

Do the workflow manually once with Claude Code. When you get a result you like, say: "Turn the workflow we just did into a reusable skill. Save it at .claude/skills/[name].md with proper frontmatter." Edit the instructions to tighten them, and the skill is ready.

Claude · The Ecosystem Map · 5 pagesfrankanaya.com/claude-tutorial/
Do this the next time you open Claude
The one win

Stop using the wrong door

The tools are not competing — they are four entrances to the same house, and using the wrong one is why AI feels slower than doing it yourself. The decision takes two seconds once you know the rule.

  1. 1
    Name the moment before you start. Thinking, doing, delegating, or repeating. That single word picks the tool.
  2. 2
    Route it. Thinking → Claude.ai. Doing → Claude Code. Delegating → Cowork. Repeating → write a Skill.
  3. 3
    Write the third one down. The moment you do a task twice the same way, it belongs in a skill file, not in your head.

You stop pasting your vault into a chat window and start working where your files already live.

If that worked, here's the rest of it
Frank Anaya
Former Senior Mentor in Tiago Forte's Building a Second Brain · 5× Praxis Fellow · fifteen years building systems for thinking