# Claude Code Configuration Overview

Start here when working with the Claude agent scaffold for this project.
This file is a routing map for the skill and rule inventories. For live CLI capability, run `elevasis-sdk cli`.

---

## What Lives Here

| Surface | Purpose                       | Source of truth                                |
| ------- | ----------------------------- | ---------------------------------------------- |
| Skills  | Slash-command entry points    | `.claude/skills/*/SKILL.md`                    |
| Rules   | Path-scoped operating context | `node_modules/@elevasis/sdk/reference/rules/`  |
| Hooks   | Claude lifecycle automation   | `.claude/hooks/*.mjs`, `.claude/settings.json` |
| CLI     | Live command + domain surface | `elevasis-sdk cli` (authoritative, run it)     |

For CLI capability, run `elevasis-sdk cli` — it is the authoritative surface for what commands
and domains are available. For architecture context, read `CLAUDE.md` first.

---

## Operating Model

This project is skill-first with an always-on ambient vibe layer:

1. Load `CLAUDE.md` for project rules, stack, and the Ambient Vibe Layer contract.
2. Every natural-language message is silently classified into an intent (Capture, Query, Describe,
   Transition, Navigate, Codify, Toggle, Operate) before the agent responds — no slash command needed.
3. For explicit work, match intent to a skill in `.claude/skills/{name}/SKILL.md`.
4. Load the relevant bundled rule from `node_modules/@elevasis/sdk/reference/rules/` for the area
   being changed (the local `.claude/rules/*.md` files are thin pointers to these).
5. Use `elevasis-sdk cli` for the live command/domain surface — do not answer "what can I do" from memory.

---

## Skills

**Location:** `.claude/skills/`

Skills are the slash-command surface. Each skill is `.claude/skills/{name}/SKILL.md`:

<!-- @generated:start:sync-overview-skills -->
- **client** -- Client portfolio management -- list, resolve, inspect, and maintain client records and their lineage to companies, contacts, and source deals -- via the elevasis-sdk client:* CLI.
- **dsp** -- Dispatch subagents in parallel for implementation tasks
- **elevasis** -- Elevasis platform operations -- check, deploy, execute, inspect, and debug SDK resources
- **explore** -- Codebase exploration anchored to project documentation
- **git-sync** -- Pull latest changes, surface new sync notes, install when needed, and run baseline verification without auto-reconciling template drift
- **om** -- TRIGGER this skill when any of the following apply: - The user references organization-model entities by name or concept: identity, customers, offerings, roles, goals, techStack, systems, actions, labels, knowledge nodes, governance edges, mounts, playbook, outreach cadence, or any domain in the org model. - The user asks to read, list, find, show, query, navigate, describe, codify, add, edit, update, toggle, enable, or disable any organization-model domain or knowledge node. - The user asks "what governs X?", "what does X control?", "system governs", "what is our identity set to?", "what's our timezone?", "show me all reference docs", "list my roles", "where does outreach-cadence apply?", or similar. - An agent is editing files matching: core/config/organization-model.ts, core/config/organization-model/**, or core/config/knowledge/**. SKIP this skill when the task is purely UI layout, workflow authoring, or infrastructure work with no reference to org-model or knowledge-graph entities.
- **project** -- Portfolio- and project-level work management -- orientation, intent routing, active projects, milestones, tasks, notes, and resume context -- via the elevasis-sdk project:* CLI.
- **run-ui** -- Start the project's Vite UI dev server on port 4300 in the background, surfacing the URL once it's ready. Detects port conflicts and asks before killing the holder.
- **save** -- Auto-manage project documentation and persist task resume context from conversation
- **setup** -- First-time project setup — detect and replace template placeholders, install dependencies, verify build, then hand off to /om for org-model configuration
- **status** -- Quick project health check
- **submit-request** -- Submit a structured request report to the Elevasis platform via CLI — enforces pre-analysis before posting
- **sync** -- Fresh reinstall and cache reset after local dependency or cache drift
- **tutorial** -- Persona-aware onboarding tutorial that forks into a vibe-coder track (zero technical vocabulary, agent does all the work) or a technical track (full SDK depth, code-first). On first invocation, asks one gate question to determine the user's track and persists the choice to .claude/memory/profile.md. Subsequent invocations skip the question and display the track menu with current progress markers. Supports /tutorial switch (flip track) and /tutorial status (display-only).
<!-- @generated:end:sync-overview-skills -->

---

## Rules

**Location:** `node_modules/@elevasis/sdk/reference/rules/` (bundled with `@elevasis/sdk`)

Path-scoped operating context loaded for substantial work in their areas. The project's local
`.claude/rules/*.md` files are thin compatibility pointers; the authoritative content ships with
the SDK and is listed here:

<!-- @generated:start:sync-overview-rules -->
- `node_modules/@elevasis/sdk/reference/rules/active-change-index.md` -- Bridge between stable scaffold docs and higher-volatility in-progress architecture work that may override assumptions for agents working in the template
- `node_modules/@elevasis/sdk/reference/rules/agent-start-here.md` -- Canonical first-read for agents entering the template scaffold -- project continuity, task-class routing, and boundary resolution
- `node_modules/@elevasis/sdk/reference/rules/deployment.md` -- Deployment workflow -- check-first, dev vs prod, version bumping, common errors
- `node_modules/@elevasis/sdk/reference/rules/error-handling.md` -- Error handling -- ExecutionError vs PlatformToolError, retry logic, no auto-retry
- `node_modules/@elevasis/sdk/reference/rules/execution.md` -- Execution model -- timeouts, memory, concurrency, org isolation, runtime constraints
- `node_modules/@elevasis/sdk/reference/rules/frontend.md` -- Frontend conventions -- React, routing, state, styling, testing, pages
- `node_modules/@elevasis/sdk/reference/rules/observability.md` -- Observability -- context.logger API, execution inspection, step-level context
- `node_modules/@elevasis/sdk/reference/rules/operations.md` -- Platform workflows, agents, resource definitions, and deployment for the operations/ surface
- `node_modules/@elevasis/sdk/reference/rules/organization-model.md` -- Edits to the canonical organization model go through /om
- `node_modules/@elevasis/sdk/reference/rules/organization-os.md` -- Organization OS orientation -- the semantic contract layer relating Systems, Actions, ontology, resources, policies, roles, goals, and knowledge; consumed via published @elevasis/core / @elevasis/sdk
- `node_modules/@elevasis/sdk/reference/rules/package-taxonomy.md` -- Package taxonomy (consumer view) -- external projects consume the published @elevasis/* surface only; workspace-internal @repo/elevasis-* packages are not installable here
- `node_modules/@elevasis/sdk/reference/rules/platform.md` -- Platform conventions -- SDK workflows, agents, deployment, resource registry
- `node_modules/@elevasis/sdk/reference/rules/shared-types.md` -- Core type boundary -- what belongs in core/types, import rules, schema conventions
- `node_modules/@elevasis/sdk/reference/rules/task-tracking.md` -- In-progress task conventions -- doc format, status values, auto-save behavior
- `node_modules/@elevasis/sdk/reference/rules/ui.md` -- UI shell, route structure, auth flow, API access, and template customization points for the ui/ surface
- `node_modules/@elevasis/sdk/reference/rules/vibe.md` -- Ambient intent classifier -- routes natural-language input to intent buckets without a slash command; Codify and Toggle delegate to /om, Operate delegates to /elevasis
<!-- @generated:end:sync-overview-rules -->

---

## Skill Boundaries

Use the owning skill instead of guessing from the name alone:

| Need                                                     | Route             |
| -------------------------------------------------------- | ----------------- |
| SDK operations (check, deploy, exec, inspect, debug)     | `/elevasis`       |
| Project and task lifecycle                               | `/project`        |
| Client portfolio (list, resolve, inspect, maintain)      | `/client`         |
| Organization Model read, codify, or governance           | `/om`             |
| First-time project setup (placeholder replacement, deps) | `/setup`          |
| Guided onboarding walkthrough                            | `/tutorial`       |
| Conversation fanout (notes, task save, blockers)         | `/save`           |
| Parallel agent dispatch                                  | `/dsp`            |
| Test, build, commit, push                                | `/deploy`         |
| Codebase exploration                                     | `/explore`        |
| Pull latest, surface sync notes, baseline verify         | `/git-sync`       |
| Project health check                                     | `/status`         |
| Submit a request to the Elevasis team                    | `/submit-request` |
| Fresh reinstall / cache reset                            | `/sync`           |
| Start the Vite dev server on port 4300                   | `/run-ui`         |

---

## Scaffold Maintenance

| Action                                 | Command or file                             |
| -------------------------------------- | ------------------------------------------- |
| Refresh the Skills + Rules lists above | `pnpm gen:overview` (run from the monorepo) |

The Skills section is generated from `external/_template/.claude/skills/*/SKILL.md` frontmatter, and
the Rules section from the bundled rule source `packages/sdk/docs/agent-rules/*.md`, both by the
monorepo `pnpm gen:overview` generator. Do not hand-edit the generated blocks.
