Symbol

Symbol uses a consistent shorthand syntax for referencing capsules, types, and projects. These references work inside capsule content, AI conversations, and MCP tool calls.

Capsules

Capsules are referenced using the format @type-slug/refId, where type-slug is the URL-friendly version of the type name and refId is the capsule's sequential number within that type.

Format: @type-slug/refId

Examples:

@docker/3 - capsule #3 in the Docker type
@decisions/12 - capsule #12 in the Decisions type
@code-snippets/7 - capsule #7 in the Code Snippets type

When you are already working within a specific type, you can use the shorter form #refId to reference a capsule in that same type:

#3 - capsule #3 in the current type context

Where to use it: Inside capsule content to link related capsules, or in MCP tool calls via the ref parameter of get_capsule_by_ref.

Cross-Referencing

You can reference one capsule from another's content. This lets you build connected knowledge without duplicating information:

"I solved a similar problem in @docker/1, but this case was different because..."

Types

Types are referenced using the format @type:slug, a plain slug, or a plain name. All three resolve to the same type.

Formats:

@type:code-snippets
code-snippets
Code Snippets

The slug is auto-generated from the type name: lowercased, with spaces and special characters replaced by hyphens.

Where to use it: In MCP tool calls via the type_name parameter (e.g. list_capsules, create_capsule).

Projects

Projects are referenced using the format @project:slug or a plain name.

Formats:

@project:wifi-project
WiFi Project

The slug follows the same rules as type slugs: lowercased, spaces and special characters replaced by hyphens.

Where to use it: In MCP tool calls via the project_name parameter (e.g. get_project_context, create_capsule, update_capsule).

Note: #refId (e.g. #3) is a capsule shorthand reference, not a project reference. To load a project's context, use @project:slug or its plain name.

Teams cannot be referenced directly in conversations or tool calls. They are an organizational layer that controls who has access to capsules and projects. Context is always loaded through capsules and projects, not through team membership.

Summary

Resource	Format(s)	Example
Capsule (cross-type)	`@type-slug/refId`	`@docker/3`
Capsule (same-type shorthand)	`#refId`	`#3`
Type	`@type:slug`; plain slug; plain name	`@type:docker`; `docker`; `Docker`
Project	`@project:slug`; plain name	`@project:wifi`; `WiFi Project`

How Slugs Are Generated

Slugs are derived automatically from names using the following rules:

Convert to lowercase
Replace any sequence of non-alphanumeric characters with a hyphen
Strip leading and trailing hyphens

For example: "My Docker Setup" becomes my-docker-setup.

You can also set a custom slug when creating a type or project.

Referencing Resources