Claude Skills by odylith

Use when concrete Odylith failure evidence needs a Casebook bug with grounded repro details.

Use when an Odylith Casebook bug create or update needs prerequisite checks.

Use when a slice shows duplicate helpers, fake modularization, oversized-file pressure, or AI-shaped code slop that needs explicit cleanup discipline.

Use when a bounded execution note needs to be appended into Compass.

Use when Compass state needs a refresh and the current pass must settle.

Use after startup, never in parallel with startup, when a known Odylith anchor needs local context.

Use when Odylith Discipline pressure behavior, zero-credit hard laws, host/lane parity, or benchmark-proved learning-spine contracts need validation.

Use when the current Odylith install needs verification or an approved repair.

Use when a consumer repo needs proposal-first backlog, Registry, and Atlas drafts from new project intent before source exists.

Use when guidance behavior pressure cases or high-risk agent guidance contracts need deterministic validation.

Use when concrete anchors already exist and the local Odylith projection store needs search.

Use when current Odylith state needs a concise session brief.

Use when the operator asks what Odylith can do for a repo, requests an advisory repo demo, or asks for the clean scenario-aware show-me output.

Use first, before context/search fan out, when a task needs repo-local Odylith startup grounding.

Use when changed files need governed Odylith surfaces refreshed.

Use when pinned, active, and locally available Odylith versions need inspection.

Refresh Atlas diagrams from change-watch metadata.

Render Atlas from the Mermaid catalog.

Create grounded Radar backlog workstreams.

Validate Radar backlog and plan linkage contracts.

Capture a new Odylith Casebook bug from concrete failure evidence and grounded repro details.

Investigate an Odylith bug record, gather evidence, and connect it to the right governed surfaces.

Check Odylith Casebook bug prerequisites before creating or updating a bug record.

Enforce the anti-slop contract when duplicate helpers, fake modularization, or oversized-file pressure show up.

Interpret Compass state, standup briefs, and executive summaries for the active Odylith slice.

Append a bounded execution note into Compass.

Refresh Compass and wait for the current pass to settle.

Work with Compass timeline and execution-stream evidence for Odylith sessions.

Update or inspect the Odylith component registry and component dossier truth.

Work with Odylith context-engine packets, retrieval, and routing support flows.

Resolve a known Odylith anchor after startup, never in parallel with startup.

Maintain Odylith delivery and governance surfaces after source-of-truth changes.

Update Atlas diagram catalog truth and related source diagrams for Odylith.

Use when Odylith Discipline pressure behavior, host/lane parity, or credit-safe benchmark proof needs validation.

Verify or repair the current Odylith install.

Use when a consumer repo needs proposal-first backlog, Registry, and Atlas drafts from new project intent before source exists.

Use when Guidance Behavior pressure cases or cross-host guidance contracts need deterministic proof.

Search the local Odylith projection store after concrete anchors exist.

Sync Odylith registry component specs with implementation and governance evidence.

Sync mapped Compass requirement evidence into component living specs.

Validate Registry component inventory contracts.

Define release scope and move backlog workstreams between release targets.

Maintain schema-governance contracts and related Odylith registry truth.

Apply Odylith security-hardening guidance to bounded product changes.

Produce a concise session brief grounded in current Odylith state.

Preserve and resume Odylith session context, handoffs, and continuity across turns.

Use when the operator asks what Odylith can do for a repo, requests an advisory repo demo, or asks for the clean scenario-aware show-me output.

Run the repo-local Odylith startup contract first, before context/search fan out.

Plan Odylith delegation ownership, bounded fanout, and merge-safe orchestration.

Choose local execution versus bounded delegation for Odylith slices and shape routed payloads.