landcube

Plugin landcube from marketplace landcube in conorluddy/Landcube. Commands read from the repo's manifest — 9 days ago.

Skills (18)

• vestige-auto-memorise

  Fires automatically — without the user asking — when the conversation produces something a future session would want. Watch for decisions ("we''ll go with…", "settled — X"), preferences ("I prefer…", "always…", "never…", "make sure to…"), open questions ("TBD", "unclear whether…", "follow-up:"), TIL

• vestige-bootstrap

  Seed an initialized Vestige project's candidate inbox from repository history when asked to bootstrap memory, import past decisions, or catch up a new installation from commits, PRs, and issues.

• vestige-context

  Render the project''s Vestige context pack — summary, recent decisions, open questions, recent activity — as a budget-bounded brief. Use at session start, before unfamiliar work, after a long pause, or when the user says "what''s the state of this project?", "where are we?", "catch me up", "what hav

• vestige-forget

  Soft-delete a Vestige memory by its handle (`mem_<ULID>`) when the memory is wrong, superseded, or stale. Fire when a decision has been reversed, a note is no longer accurate, an open question has been answered, or the user says "forget memory <id>", "that''s outdated", "remove <id>", "drop that mem

• vestige-recall

  Search Vestige memory before a decision, refactor, or library choice — any time you suspect "we already discussed this". Fire when the user says "have we decided this?", "what did we say about X?", "look up our notes on Y", "is this already settled?", "search memory for Z". Lexical (BM25) by default

• vestige-record-decision

  Capture a project decision to Vestige memory when committing to an architectural choice, picking approach A over B, settling a tradeoff, or choosing a library / framework / pattern. Fire on "we''ll go with…", "let''s use…", "decision:…", "I''m choosing X over Y because…", "settled — we use…", "going

• vestige-record-note

  Capture a general project note to Vestige memory for non-trivial facts, workarounds, gotchas, aha moments, TILs, code smells, or durable TODOs — anything worth keeping that isn''t a decision, preference, or open question. Fire on "good to know:", "TIL", "note that…", "heads up:", "FYI:", "turns out…

• vestige-record-preference

  Capture a user preference to Vestige memory when the human expresses a convention, opinion, or "how I like things done". Fire on "I prefer X", "always use Y", "don''t do Z", "we always…", "never…", "I like…", "I don''t like…", "make sure to…", "do not…", "convention:…", "rule:…", "house style:", "in

• vestige-record-question

  Capture an open question to Vestige memory when an ambiguity can''t be resolved now and needs a human, investigation, or later session. Fire on "TBD:", "open question:", "we should figure out…", "unclear whether…", "follow-up:", "to investigate:", "leaving X open", or when the user says "capture tha

• vestige-restore

  Restore a previously soft-deleted Vestige memory by its handle (`mem_<ULID>`). Use when a memory was forgotten in error, when the situation has reverted (a decision that was reversed gets re-affirmed), or the user says "bring back <id>", "restore <id>", "undo that forget", "that memory should still

• vestige-scan-sessions

  Mine recent local coding-agent transcripts for memories worth keeping, using the `vestige_scan_sessions` MCP tool. Fire at session start (to catch up on what happened in prior sessions), when the user says "scan my sessions", "what did we work on recently?", "catch up from my transcripts", "ingest r

• vestige-show

  Expand a Vestige memory at higher fidelity once you have its handle (a `mem_<ULID>` string). Use this skill after `vestige-recall` returns a card whose `one_liner` isn''t enough, when the user says "show me memory <id>", "expand <id>", "what does <id> say in full?", "read me memory <id>", or wheneve

• vestige-sources

  Use this skill when you need the raw source receipts for a memory or candidate — the typed evidence rows, not the narrative walk. Fire when the user says "what sources back mem_X?", "show me the source receipts", "list the sources for mem_X", or "filter sources by kind agent_session". Use `vestige-w

• vestige-trace-list

  Use this skill when you want to audit what queries the agent or CLI has run against project memory. Fire when the user says "what queries did the agent run?", "show recent trace events", "did anyone search for X recently?", or "list traces by caller mcp". Every vestige search, recall, expand, and co

• vestige-trace-replay

  Use this skill to re-run a stored trace against the current memory store and diff the results against the original — answering "would the agent get the same answer today?". Fire when the user says "re-run trace_X", "replay that search", "diff trace_X against current state", or "did the answers drift

• vestige-trace-show

  Use this skill when you want to expand a specific trace to its full detail — the query text, mode requested vs resolved, provider, result IDs, and scores. Fire when the user says "expand trace_X", "show me what trace_X returned", or "what did that search find?". Use vestige-trace-list first to find

• vestige-why

  Use this skill when you want to know where a memory came from, need to explain its provenance, or must audit what was captured and when. Fire when the user says "where did this come from?", "explain that memory", "why do we have mem_X?", "show provenance for X", "what''s the source of mem_X?", or "t

• landcube

  Generate reproducible topographic SVG or PNG assets with the LANDCU.BE CLI. Use for requests for contour-map backgrounds, synthetic terrain artwork, or location-based terrain exports; do not use for ordinary geographic maps or GIS analysis.

MCP servers (1)

• vestige

  runs: vestige mcp

Similar plugins