omni-context-cli 0.0.90 → 0.0.91

package/dist/clients/web/assets/stateDiagram-v2-4FDKWEC3-CNCP3dFh.js

@@ -1 +0,0 @@
-import{s as r,b as s,a as e,S as t}from"./chunk-DI55MBZ5-Bfv0NfQG.js";import{_ as i}from"./index-p16PXaGU.js";import"./chunk-55IACEB6-DVkBB5tN.js";import"./chunk-QN33PNHL-BV-_VgzY.js";var n={parser:e,get db(){return new t(2)},renderer:s,styles:r,init:i(r=>{r.state||(r.state={}),r.state.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{n as diagram};

package/dist/skills/landmark/SKILL.md

@@ -1,12 +0,0 @@
----
-name: landmark
-description: Review code areas explored in this session and update the landmark navigation index.
----
-
-Review the code areas explored or changed in this session and save any durable navigation knowledge to the landmark system. Start with LandmarkList so you can see the current layers and avoid duplicates. LandmarkUpdate replaces every pin on the layer, so when a related layer already exists, read it first with LandmarkRead and pass back the full pin set you want to keep along with the new ones.
-
-Only record areas that revealed real structure: a bug fix that touched multiple files, feature work in a new subsystem, a refactor that moved or renamed important pieces, or an investigation that clarified how components fit together. Skip trivial single-file edits that do not add much navigation value.
-
-For each area worth keeping, update an existing matching layer when one already exists. When a new feature or subsystem spans multiple files, create a dedicated layer for it instead of scattering pins across existing layers. Use a short descriptive name and a clear scope. Pin the important files, directories, and symbols, and give each pin a brief note that explains why it matters.
-
-If this session deleted, renamed, or moved files that appear in any layer, those layers should already have been fixed immediately after each change. Verify now that no stale pins remain.