Vigil Team Code logo

Vigil Team Code

A Sand Point Studios development platform

What this is

Vigil Team Code is Sand Point Studios' shared development environment: a browser-based VS Code workspace (code-server) per contributor, with Claude Code built in, the SPS persona library pre-installed, and access gated to your SPS Google account. You get a fully configured dev setup by opening a URL — no installs, no environment drift.

This page is for new contributors. It covers how to work with Claude effectively in the shared environment. If you are starting onboarding, check your inbox for the onboarding checklist email — it walks through the account setup (Google, GitHub, Anthropic) step by step.

Working with Claude — the short version

Claude is a teammate, not an autocomplete. The more context you give, the better the work. The less friction between you and a working system, the less time you burn.

Be specific about the goal, not the implementation

Instead of "write a function that iterates through the array and..." — say what problem you are solving and what the output should look like. Claude picks the idiomatic implementation better than you can dictate it line by line.

Weak: "Write a for loop that checks each item in users and if active is true, add to a new list called out, then return it."

Strong: "Give me the list of active users from users."

Show, don't tell — share the file or error

When debugging, paste the actual error output and the file path. When asking for a change, point at the file. Claude in your workspace can read your repo directly — asking it to "look at src/payments/charge.ts" is faster than re-describing the code.

Let it explore before it edits

For any change involving more than one file, ask Claude to read the surrounding code first. A 30-second exploration avoids a 10-minute wrong rewrite. Phrases that work: "read the relevant files first", "plan before changing anything", "use the Explore agent to find..."

Use the personas we have built

Your workspace comes with Scribe (docs / memory / decisions-log specialist) and Scout (read-only codebase exploration) already installed. Type /agents in the Claude Code panel to see them. Delegate to them when the task fits — Scribe for any documentation change, Scout for mapping unfamiliar code. They are faster and more disciplined than asking the main agent to do it.

Scope is your friend

One focused task per turn gives better results than a five-item wishlist. If you must ask for several things, say so explicitly and let Claude plan the order.

Efficient token use

Every contributor's Claude Team seat has a weekly usage limit. You will not run into it doing normal work, but these habits keep you well clear of the ceiling:

Reporting bugs and suggestions

Every SPS product has three ways to give feedback:

  1. In-app bug reporter (when working in an SPS application that has one): use the in-app flow. It captures the page state and the user context automatically.
  2. Email the monitored aliases:
  3. Ask the Claude Code agent in your workspace to record a bug or open a ticket directly. "Log this bug against Wyrdlyre: the audio dropout happens whenever..."

All three paths feed into the same ticketing system (No Wake Zone) eventually. If the fix is straightforward and low-risk, a Claude-powered fix-bot will attempt it automatically in dev; humans review before anything merges.

Your workspace URL

Each contributor has a dedicated workspace at code-<yourname>.sandpointstudios.ltd. It is gated by Cloudflare Access — you sign in with the Google account tied to your SPS email, and only your identity has access to your workspace.

Teagan will send you your specific URL once your account setup is far enough along that it will work.

Getting help

Email [email protected]. The mailbox is monitored by an AI triage layer that drafts responses for Teagan to review — so you get a reply either directly from Teagan or with his approval. During onboarding, expect faster turnaround for setup questions than for anything else.