One knowledge base, many ways to use it.
Symbol adapts to how you work: encode your process, carry your context across every AI tool, keep your whole team in sync, publish a curated library as a public page, and remember every problem you have already solved.
Tell AI how you work, once.
Save your process as a Type. Its guidance travels with every capsule inside it, so any AI follows your steps instead of guessing.
- Encode SOPs, checklists, and house rules as guidance
- AI reads your instructions, not just your notes
- Update the Type once; every AI stays in sync
Always follow these steps, in order:
- 1Run the full test suite
- 2Bump the version & update the changelog
- 3Tag the release and open the PR
Your context, in every AI tool.
Save it once as a capsule. Mention it in any MCP-connected tool and the full context loads instantly: no copy-paste, no re-explaining.
- Reference @type/ref in ChatGPT, Claude, Cursor, and more
- Switch tools mid-project; your context comes with you
- Stop pasting the same brief into every new chat
Sarah Chen
Founder of Chen & Co Studio, a minimalist-modern architecture practice in Brooklyn.
Loads in
- ChatGPT
- Claude
- Cursor
- Gemini
One source of truth for your team.
Share Types and capsules across your workspace so everyone's AI works from the same context, with role-based access you control.
- Shared workspaces keep the whole team aligned
- Role-based access: Owner, Editor, Viewer
- Onboard teammates (and their AI) in minutes
Voice, values, and visual guidelines: one source every teammate's AI reads from.
- Maya PatelOwner
- Tom LeeEditor
- Ana RuizViewer
Publish a whole library, not one prompt at a time.
Share a Type or a Collection and every capsule inside it becomes one public page people can browse, filter, and search. Set an expiry or a view limit, and revoke it whenever you want.
- One link publishes the whole set, not each capsule
- Visitors filter by tag and search across everything shared
- Expiring links and view limits, revocable at any time
- Bug triageEngineering
- Blog outlineWriting
- Weekly reportOps
Anyone with the link can read and copy. No account needed.
Never debug the same thing twice.
Write down what broke, what caused it, and what actually fixed it. Next time anyone hits it, the answer comes from your own history instead of a fresh guess.
- Capture incidents, postmortems, and dead ends while they are fresh
- Ask any AI about a bug and it recalls your fix, not a generic one
- New teammates get the fix and the reasoning behind it
Symptom
Checkout hung for 30s, then timed out.
Cause
A retry loop held the payment lock open.
Fix
Release the lock before the retry, cap it at three.
Put your context to work.
Save it once. Use it in every AI tool, with your whole team.