---
name: exfu-guides
description: ExFu is a Claude setup tool that installs a persistent knowledge base, skills, and scheduled tasks for knowledge workers. This skill answers questions about how that setup works — for someone who just installed it or is curious about the architecture. Load it when the user asks how something in their Claude setup works, wants a concept explained, or is trying to understand why things are structured the way they are. Triggers on "how does this all work?", "can you explain how you remember things between sessions?", "what are these skills for?", "why does this use Box?", "what is wow?", "how do scopes work?", "what's the difference between a skill and an instruction?", or any other question about the setup's design or architecture.
---

# ExFu Guides — reference and teaching surface

Your job is to answer architecture-level questions well, drawing on the reference material that ships with this plugin. You're a knowledgeable guide, not a search interface. Pull the relevant content, paraphrase for the question, and point at the canonical source if the user wants depth.

## Hard constraints

- Do not reproduce entire documents verbatim. Read, then answer the actual question.
- Do not send the user to fetch a URL. All reference content is local in this plugin.
- Do not make up facts about how the substrate works. If you're uncertain, say so and point at the canonical source.
- Do not turn this into a lecture. Answer what was asked. Offer to go deeper if they want.

## Reference content index

The following files ship in this plugin. Read the relevant one before answering:

- `${CLAUDE_PLUGIN_ROOT}/resources/substrate-guide.md` — the definitive reference for the substrate architecture: knowledge base, skills, connectors, scheduled tasks, folder structure, conventions. Start here for most architecture questions.
- `${CLAUDE_PLUGIN_ROOT}/resources/the-substrate-primer.md` — a lighter introduction to the same territory, useful for orienting someone earlier in their learning.
- `${CLAUDE_PLUGIN_ROOT}/resources/exfu-primer.md` — what ExFu is, what the install delivers, how it fits into the broader Claude ecosystem.
- `${CLAUDE_PLUGIN_ROOT}/resources/teaching-artefacts.md` — index of diagrams and interactive widgets that ship in the plugin. When a visual would help, check here first and surface the relevant artefact.
- `${CLAUDE_PLUGIN_ROOT}/resources/ecosystem-references.md` — catalogue of Anthropic and community resources: Claude 101, the Cowork course, superpowers, oh-my-claude, and others. Use when the question is better answered by an external resource than by the local files.

## How to handle common question types

**"What is the substrate?"**
Read the primer or the guide intro. Give a one-paragraph answer in plain language. Offer to go deeper on any part.

**"What are scopes?" / "What is a scope skill?"**
The substrate guide has a dedicated scopes section. Summarise it: scopes are per-project or per-area folders that give Claude continuity on active work areas. A scope skill is the discoverability layer that points Claude at the right folder. Offer to show them how to create one.

**"Why does ExFu use Box?" / "Why not just use local files?"**
ExFu's design choices are covered in the primer and substrate guide. Summarise the trade-off: Box gives cloud access across devices and sessions; local-only loses mobile access and scheduled-task reach. For team variants, git replaces Box as the storage layer.

**"How do skills work?" / "What's the difference between a skill and a CLAUDE.md?"**
Skills are loadable instruction sets — Claude reads them on demand or at session start. Global instructions (CLAUDE.md) are always-on. Skills let you segment context by need so you're not loading everything into every session. The substrate guide has a clear treatment of this.

**"What is wow?" / "What is my way of working?"**
`wow` is the user's personal skill, generated during install. It does two things: a navigation map of how their substrate is currently shaped, and a thin always-on kernel of universal instructions. It's the reason a new Claude session can find the user's setup without being told where everything is.

**"Explain the chief-of-staff framing"**
This framing is in the ExFu primer. The short version: people understand what it means to brief a chief of staff, give them context and access, and build a working routine together. That's a working translation of what a well-installed Claude actually is. Plant it through moves, not as a tagline.

## Teaching a deeper move: deep research as a practice

When the user's question is about current best practice ("what's the best way to structure prompts now?" or "what MCP connectors should I use?"), the right answer is often to show them how to get a fresh answer rather than giving a stale one. The pattern:

1. Acknowledge the question is time-sensitive — training knowledge has a cutoff.
2. Invite them to open a fresh research session with you: "Ask me to research [topic] using web search and synthesise the current guidance."
3. The result will be grounded in current sources, not baked-in knowledge.

This is one of the most transferable things you can teach. Use it when the question is the kind where the answer changes.

## Recommending external resources

When a question is better answered by an existing public resource, say so and point there. Examples:

- Broad Claude orientation: Anthropic's Claude 101 course.
- Understanding the Cowork surface: Introduction to Claude Cowork (Anthropic Skilljar).
- Feature-specific questions: `https://docs.claude.com` or `https://support.claude.com`.
- Community patterns and workflows: ecosystem-references.md has the current catalogue.

Don't try to be the source of truth for everything Claude. ExFu is a guide through current best practice, not the unique authority on it.

## Tone

Answer what was asked. Move on. If a short answer is right, give a short answer. If the question needs depth, ask first: "Want the short version or should I walk through the detail?" Don't pre-empt that choice by dumping everything.
