meta4

A working algebra for human-LLM collaboration framed as lapidary practice — cutting, viewing, and re-cutting structured light. Use this skill whenever the user invokes any of the operation-tokens (`distill`, `refract`, `project`, `intersect`, `unite`, `differ`, `cleave`, `twin`, `crystallize`, `nucleate`, `anneal`, `recrystallize`, `polish`, `rotate`, `traverse`, `inspect`, `grade`), names a crystalline object (corpus, gem, facet, lattice, lens, scaffold, seed, plane, inclusion, mother liquor), or describes work in these terms (e.g., "let me cut this differently," "refract this through the skeptic lens," "find the cleavage plane," "twin this argument," "crystallize this material into the scaffold," "polish this passage," "inspect for inclusions"). Especially fits comparative analysis under a shared lens, structured decomposition of an argument or topic, multi-perspective rendering, scaffold-filling from raw material, calibrated epistemic grading, and any task where the user wants composable operations rather

A working vocabulary for human-LLM collaboration framed as mycelial ecology — substrate, hyphae, spore, growth, fruit, compost. Use this skill whenever the user invokes any of the move-tokens (`myc`, `distill:`, `inoc:`, `entangle(`, `ecotone(`, `graft(`, `trellis(`, `fruit:`, `compost:`, `thread(`, `propagate`, `transplant`, `prune:`, `fallow`, `rootbound?`), names a mycelial unit (substrate, hyphae, spore, growth, lattice, fruit), or describes work in these terms (e.g., "let's distill this," "extend a frame through this," "harvest a draft from this thread," "compost this and reuse the parts," "boundary work between two corpora"). Also use this skill when the user feels stuck, the context is getting long and incoherent, or they want to compress/transport a frame between sessions — the skill names what's happening and proposes the right move. Do not use this skill for generic "summarize" or "rewrite" requests that don't invoke the vocabulary; it's a deliberate practice frame, not a default lens.

A working vocabulary for human-LLM collaboration framed as tracking, navigation, and cartography — for engaging with terrain that already has structure you didn't put there. Use this skill whenever the user invokes any of the move-tokens (`where-are-we`, `survey:`, `read-sign:`, `backtrack:`, `triangulate:`, `bearing:`, `tack:`, `portage:`, `bushwhack:`, `dead-reckon`, `wait-for-conditions`, `landmark:`, `chart(`, `legend:`, `scale:`, `omit-honestly:`, `reproject:`), names a navigational unit (terrain, sign, path, map, bearing, landmark, conditions), or describes work in these terms (e.g., "let me survey this," "what does this reveal about its making," "we need to tack around this," "chart what we've covered," "we've lost the thread"). Especially use this skill for inherited or unfamiliar work — codebases the user didn't write, drafts handed to them, corpora approached cold, forensic reading of artifacts. Also use when the user is lost (lost bearing, lost path, lost position) or when direct paths are blocked