IdeaSpaces-xyz

is-capture

Write something down so it is not lost — a decision, a finding, a piece of context worth keeping. Use when someone says write this down, note this, save this, keep this somewhere, don't let me forget, remember this, put this in my notes, or add this to the knowledge base; or when a decision has just been made that would be expensive to relitigate. Not for saving an ordinary source or config file — that is a plain file write.

is-publish

Put this space online — host the current folder as a remote ideaspace, so it outlives this machine and the team or another device can reach it. Use when someone says put it online, publish this, host it, back this up, get this on my other computer, or make it available to the team; or after `/is-setup` finishes. Hosting starts private — who gets in is is-share. Plan-first: the bundled CLI shows exactly what would happen and mutates nothing until the user agrees and it runs again with --yes.

is-reflect

Propose a coherence check on the space after a significant commit, or when direction drifts — milestone completes, focus shifted, Now stale, or tree structure outgrown. Offered as a readiness check (both sides decide whether to reflect now). Triggers at natural breaks or after state updates, not mid-task.

is-setup

Set up the place someone is describing — a space for their knowledge, an agent with a role, or an existing remote space opened here. Use when someone names a thing they want to keep, track, or organize — a knowledge base, a vault for transcripts, a repository for the team's KPIs, notes on a topic, a small CRM — or a helper they want to work with: an assistant, a sales agent, a critique partner. Also on the direct asks: "set up a space", "add ideaspaces here", "create an agent", "get me into my space", "clone my notes", or a returning user with nothing local yet. Create inspects what's here, confirms, then runs `ideaspaces create` (`--agent` for an agent with its own character and point of view, drawn out in conversation); Open lists your remote spaces (`is_spaces`) and clones the chosen one (`is_clone`). Not for building software — someone coding an app wants code, not a space.

is-shape

Shape the `_agent/` contract — create a reusable primitive (procedure, checklist, review pattern, memory routine) or codify a perspective (a repeatable thinking pattern). Use when the user wants to make how the agent works in a situation repeatable, or to define an evaluation/analysis they apply often. Not for saving a decision or finding; that is is-capture.

is-space

Reference for working in an ideaspace — the five-file `_agent/` contract, Two Roles convention, and Claude plugin tool surface. Use when the agent needs the contract or tool-surface details mid-work. For explaining IdeaSpaces to a person, prefer is-guide; for active intents, prefer is-orient, is-capture, is-share, is-push, is-pull, is-reflect, and is-shape.

is-fork

Materialize an independent local Space from a canonical Space URL. Use when the user says fork this Space, take this public Space home, make a local independent copy, update or refresh a maintained fork, or wants to work from a copy without an account. Fork is history-free and unpublished; use is-publish later to host it.

is-inbox

Read and reply to direct Inbox messages, or ask a person a question about shared Content from the local agent. Use when the user says check my Inbox, read this message, ask the owner/person about this, send an inquiry, or reply. Not for giving someone access to a Space; that is is-share.

is-share

Let someone in — give a person or a team access to this space, or open it to everyone. Use when someone says let her see this, share this with my team, give them access, she needs to get up to speed on this, make it public, let people copy it — or asks who can see it, or to take someone's access away. Access levels: Explore (look around), Fork (take a copy home), Collaborate. Not for sending committed work to the remote; that is is-push.

is-push

Push an ideaspace when the user asks to push, sync, or send committed captures to its existing remote. Push never changes recipients or public visibility; use is-share for those requests. If you are behind, pull first. Capture first if changes aren't committed.

is-guide

Explain IdeaSpaces to the person, at the right depth. Use when someone asks what is this, what does it do, how does it work, what can I do here, how can you help me, what do I need to run it — or has just installed it and wants to know what now. Answers come from the shipped guidance ladder, one rung at a time, offering a step deeper. Not for creating or opening a space; that is is-setup.

is-orient

Orient inside an ideaspace. Use at session start when orientation is missing, when the user asks "where are we?", "what are we doing?", "what changed?", or when context feels unclear. Reads the position's agreement and current state; does not modify files.

is-pull

Pull an ideaspace when the user says pull, get the latest, or update from remote. Pull brings others' committed captures into the local space; it never pushes. Integrating requires a committed, clean tree — capture first if needed.