Skip to content

The Sσmaverse

AMPS — automations, muscles, protocols, and scripts — the content system that gives an AI agent learned patterns, adaptive behavior, and persistent memory. Plus extensions and skills for runtime hooks and domain expertise.

σSσmaverse
youthe human
piruntime
memory.soma/
automations
muscles
protocols
scripts
extensions
skills
drag a node to explore

σ Somaverse — The Workspace

Where Soma gets eyes and hands

Soma the agent lives in your terminal. Somaverse is the tiling browser workspace that gives it eyes and hands — a grid of panes it can read, control, and connect.

21 plugins ship today. Terminal, files, editor, browser, chat, voice, graph, preview, settings — every one of them is a pane Soma can see and steer. Drag them, snap them, bridge their data flows together. Your agent is no longer stuck in a chat box.

Connection is one command: soma login. The agent in your terminal pairs with the workspace in your browser through a cloud relay. Your data stays on your machine — the relay only routes commands.

Read the preview → The doors opened →

21
plugins · panes · tools
28
workspace + browser tools through the hub
0
data leaves your machine — relay routes only

σ AMPS — The Content System

The content layers you create. Everything under .soma/amps/.

Automations

triggered actions · heat-tracked · Markdown

Step-by-step procedural flows that fire on triggers — session start, post-commit, pre-deploy. Like protocols but action-oriented: "do this sequence" rather than "behave like this." Heat-tracked so frequent automations stay loaded.

What they do

  • Run specific steps on session start
  • Post-commit verification sequences
  • Pre-deploy checklists
  • Heat up with use, fade when unused

Where they live

  • .soma/amps/automations/ — project
  • ~/.soma/amps/automations/ — global

Examples

  • session-start — boot-time workspace setup
  • post-commit — verify after each commit

Muscles

learned patterns · heat-tracked · Markdown

Patterns learned from experience — reusable knowledge that Soma builds across sessions. Each muscle has a heat score and a digest block for token-efficient loading. They're the muscle memory.

What they do

  • Encode workflows discovered through repeated use
  • Load automatically when context matches their topic
  • Include digest blocks for efficient context loading
  • Track load count — grow stronger with use

Community muscles

  • test-hygiene — catch stale tests after changes
  • icon-audit — favicon and icon verification
  • micro-exhale — lightweight session saves

Protocols

behavioral rules · adaptive · Markdown

Protocols are behavioral rules the agent follows — not how to do a task, but how to be. Drop a protocol into your project and the agent adapts. The more a protocol gets used, the more deeply it's loaded. Unused protocols fade naturally.

How they work

  • Drop a .md file into .soma/amps/protocols/
  • Agent discovers it on next boot
  • Used protocols "heat up" — always loaded
  • Unused protocols "cool down" — fade out
  • Each protocol has a breadcrumb TL;DR for token efficiency

Where they live

  • .soma/amps/protocols/ — project-specific
  • ~/.soma/amps/protocols/ — global defaults

Core protocols

  • breath-cycle — session lifecycle (inhale/hold/exhale)
  • frontmatter-standard — document metadata rules
  • heat-tracking — adaptive loading by usage

Heat system ships with Soma. Protocols heat up automatically as you use them.

Scripts

developer tools · Shell

Reusable bash tools the agent builds for itself — and for you. Health checks, deployment helpers, verification suites. Discovered at boot and listed in context so the agent knows what tools are available.

What they do

  • Ecosystem health checks and verification
  • Ship cycles — test, commit, push, deploy
  • Content auditing and copy truth-checking
  • Refactoring safety nets

Where they live

  • .soma/amps/scripts/ — project tools

Examples

  • soma-verify.sh — health checks across repos
  • soma-ship.sh — dev-first ship cycle
  • soma-query.sh — search + explore

σ System Layers

Runtime infrastructure inherited from Pi.

Extensions

system hooks · TypeScript

Extensions are TypeScript files that hook into Pi's lifecycle. They run at boot, render custom UI, intercept events, and manage background processes. They're the lowest level of customization — full access to the agent runtime.

What they do

  • Boot sequences — load identity, preload memory
  • Custom headers and statuslines
  • Auto-flush memory to disk
  • Context usage warnings
  • Slash commands (/exhale, /breathe, /rest, /soma)

Where they live

  • .soma/extensions/ — project-level
  • ~/.soma/extensions/ — global

Soma ships with

  • soma-boot.ts — identity + preload + commands
  • soma-header.ts — branded σῶμα header
  • soma-statusline.ts — footer + auto-flush

Skills

knowledge sets · Markdown

Skills are markdown files that give the agent domain expertise. When the agent encounters a task that matches a skill, it loads the instructions and follows them. Inherited from Pi's native skill system — just write markdown.

What they contain

  • Task-specific instructions and best practices
  • Tool usage patterns and examples
  • Decision frameworks and checklists
  • Reference material the agent can cite

Where they live

  • .soma/skills/ — project-specific
  • ~/.soma/skills/ — global skills

Examples

  • logo-creator — AI logo generation workflow
  • favicon-gen — favicon from any source
  • remotion-best-practices — video in React

σ Agent Templates

Share your entire agent setup as a template. A template is a preconfigured .soma/ bundle — identity, protocols, skills, settings — that anyone can clone and customize. Start with a personality, not a blank slate.

DevOps Agent

Deployment protocols, CI/CD skills, infra muscles. Pre-heated for shipping code to production.

soma init --template devops

Content Writer

Workflow protocols, quality-standards, tone-of-voice identity. Ready to write and ship content.

soma init --template writer

Architect

Frontmatter standards, code review protocols, test-hygiene muscle. For teams that care about structure.

soma init --template architect

Roll Your Own

Export your current setup as a template. Share your agent's personality with the community.

soma template export my-agent

soma init --template architect to start with a template. Browse templates on the Hub.

σ Community

Share your agent's protocols, muscles, and skills with others. Import what works. The community repo is the library — fork it, contribute back, or just browse.

15Protocolsbreath-cycle · workflow · correction-capture · detection-triggers · task-tracking · and 10 more
8Musclesdoc-hygiene · icon-audit · micro-exhale · incremental-refactor · and 4 more
7Templatesarchitect · core · devops · fullstack · writer · and 2 more
/install protocol workflow

Install community content directly from Soma. Browse the Hub or learn how to contribute.

σ Source Access