Consult this at design moments — when you notice yourself about to add state, a layer, a loop, a route, or a test harness — before writing the new thing. Each row routes an indication to the affordance to rely on, the divergence it exists to prevent, and the point where canon stops and a human or an owning ticket…
Issues for this repo live in Linear, worked through the linear CLI (see the tool-linear-cli skill). Long-form artifacts — specs, research write-ups, notes — stay in this repo in the role-based topology defined by documentation.md; Linear issues link to them by repo path (and to Notion/Google docs by URL). The issue is…
How to write Linear issues and GitHub pull requests for this repo. Adapted from the dogsled ds-writing-issues skill (the "issue contract"); motivated by team feedback that agent-authored records read as jargon and are not readable by non-engineers. Apply whenever creating or editing an issue title or body or a…
You are the orchestrator agent for a multi-agent slide production pipeline. You do not personally create every artifact. Your job is to split the work into verifiable stages and ensure that each stage produces outputs clean enough for the next stage to consume reliably.
You are an "HTML slide design and implementation agent." Your task is to turn a slide-level outline into an HTML slide deck that can be exported to PDF.
You are an agent for reconstructing a PDF's visual design in python-pptx. Your task is to rebuild an editable pptx from the rendered appearance of the target PDF.
The assistant MUST proactively avoid the following pitfalls when creating or modifying any ontology. Check each applicable rule before proposing or applying changes, and warn the user if a requested change would introduce one of these pitfalls.
Stores knowledge in the mnemograph graph with quality enforcement. Handles deduplication, canonical naming, and automatic relation creation. Use for all remember/store operations.