Operators · local-first

Local brain. Obsidian weave.

187WEB is built to run as a local command center: skills on disk, optional local models, and a knowledge vault — not a black-box cloud-only suite.

What “local brain” means

Skills live in the repo — .claude/skills/ and mirrored adapters. No mystery remote skill store required to start.
NATASHA modules (THREAD → FUSE) shape prompts, compress context, and route specialists for agentic work. See docs/NATASHA-ARCHITECTURE.md.
Optional local inference — Ollama / NPU paths when configured; the suite still works for design and docs without a GPU.
Claim discipline — research and security skills label evidence; the brain does not invent “guaranteed” outcomes.

Obsidian in the loop

Vault templates and system notes ship under docs/187suite-vault/ for offline knowledge work.
Skill templates/ folders produce notes you can drop into Obsidian (design directions, audits, research packets).
Claudian / SCOUT vault-weave flows are designed to write back into a vault without requiring a SaaS wiki.
Prefer vault links and pack notes over pasting long runbooks into chat — keeps the local brain searchable.

NATASHA module array

Short aliases you can invoke through the control plane. Full detail: docs/187-MODULES.md

THREAD · /187 th

Shape prompts, extract intent, rewrite and refactor text.

COMPRESS · /187 cmp

Loss-bounded context compression into packets for local models.

TENSION · /187 tu

Inference profiles (exact, brainstorm, critic, local-npu).

SPARK · /187 spark

Bounded divergent ideation with critic convergence.

CORD · /187 co

Route work to specialist personas (ML, UI, security, DevOps).

SCOUT · /187 scout

Compliant research with attribution and rate limits.

LAB · /187 lb

Isolated execution sandbox for generated code.

FUSE · /187 fuse

Evidence-weighted synthesis and conflict resolution.

How triggers work

Triggers are not magic — they are explicit lists on each skill card and SKILL.md. Four layers stack:

Manual slash

You type `/187 <skill>` or a short alias (`craft`, `hero`, `theme`). Best when you already know the tool.

/187 theme list · /187 hero · /187 craft

Intent phrases

Natural language that the skill lists as automatic triggers (“scroll narrative”, “plain language”, “security audit”).

“Build a scroll-driven hero with reduced motion.”

Agent kit triggers

Crew agents (NATASHA, CHARLOTTE, XAVIER…) fire when conditions match — release-ready, dispute, parallel work.

XAVIER → council when crews disagree.

Obsidian / vault hooks

Notes, templates, and dashboards under docs/187suite-vault and skill templates. Claudian/Obsidian weave results back into the vault.

templates/design-direction.md · _system dashboards

Command surface categories

Same groupings as /187. Hover category titles there for the same help.

Front Door

Entry commands that open the suite, pick skills/packs, and check if your machine can run them.

When: You are installing, selecting a pack, or deciding what to run first.

Try: /187 · /187 menu · /187 doctor

Control Plane

Routing, reporting, scanning, and workflow sequencing — the operator layer above individual skills.

When: You need a status report, health scan, standard gate, or multi-step flow.

Try: /187 cmd · /187 rpt · /187 scan · /187 flow

Core Suite

First-class product skills: craft, launch, research, docs, publish, motion lab, and security.

When: You know the job (design, SEO, ship, animate) and want the matching skill.

Try: /187 craft · /187 hero · /187 theme · /187 publish

Modules

NATASHA module aliases (THREAD, COMPRESS, SCOUT, LAB…) for agentic sub-routines.

When: You are shaping prompts, compressing context, or running a local lab action.

Try: /187 th · /187 compress · /187 scout · /187 lab

Research

Scholarly and lab-oriented profiles for sources, notebooks, and reproducible artifacts.

When: You need evidence-backed research or a publishable lab surface.

Try: /187 research · /187 labs · /187 prov

Optional Packs

Curated install packs and optional add-ons that are not required for the core suite.

When: You want a pre-bundled set of skills for a domain (research, access, etc.).

Try: /187 pack <name>

Legacy

Older aliases kept for compatibility. Prefer Core Suite names when writing new flows.

When: You are migrating notes or scripts that still use old short names.

Try: Map legacy → current via docs/ROUTING.md

Start operating

Open the command reference, pick a front-door command, then drill into a skill page for full triggers.

/187 reference Install CLI 187THEME

← Back to /187 command reference