Claude Skills by OutlineDriven

Use when writing, reviewing, or generating Terraform HCL that must pass fmt and validate. Not for module authoring, state operations, `terraform apply`, or remote state.

Use when the user runs /toolchain-health and wants a trustworthy green/yellow/red verdict on the installed toolchain with ranked repairs. Not for tasks that require source or remote-system changes.

Use when a verified non-trivial fix lands or existing solution docs need refresh. Not for unverified fixes.

Use when the human returns after a gap, cannot follow the project, asks what happened, or wants a visual HTML recap page. Not for onboarding: use onboard. Not for handoff: use handoff.

Use when a long session has accumulated stale or conflicting context or the user asks to refresh it. Not for remote, credential, publish, deploy, or irreversible changes.

Use when asked to mine prior chats on a scheduled or watcher tick and maintain project memory. Not for remote, credential, publish, deploy, or irreversible mutation.

Use when a user wants to record why one world won over the others, as a decision-diary entry. Not for remote, credential, publish, deploy, or irreversible changes.

Use when making an architectural decision, changing a public API, shipping a feature, or recording a codebase term. Not for domain language: use domain-modeling. Not for docs: use docs-writing.

Use when pinning down domain terminology, maintaining the domain model, or when a term conflicts or needs sharpening.

Use when a user requests an engineering retrospective for a period. Not for agent-environment retrospectives: use agent-environment-retrospective. For learning milestones: use learning-retrospective.

Use when a repository decision needs an interview plus durable terminology and decision records. Not for remote, credential, publish, deploy, or irreversible changes.

Use when a user resumes work and needs an orientation card without full human recall. Not for packaging context for another agent or session: use handoff. Never source or remote-system changes.

Use when work reaches a session boundary or the user asks to hand off, delegate, or get a clipboard-ready prompt. Mode brief packages continuity; mode prompt builds the delegation prompt.

Use when the user asks to remove a session or note from recall, or to unforget or list exclusions. Not for remote, credential, publish, deploy, or irreversible changes.

Use when a user asks to audit what recall fed agents. Not for source or remote-system changes.

Use when the user says remember this or settles one durable fact. Not for remote, credential, publish, deploy, or irreversible changes.

Use when a user requests the reasoning behind one matched session by query or handle. Not for peer transfer: use history-sync. Not for store registration: use history-source-registry.

Use when a coding-agent session store is added or its format drifts, to document its layout, roles, quirks. Not for recalling a session: use history-recall. Not for peer transfer: use history-sync.

Use when the user requests memory transfer to or from a named peer. Not for recalling a session: use history-recall. Not for store registration: use history-source-registry.

Use when skill or knowledge activation is unreliable, or setup reaches activation reliability. Not for remote, credential, publish, deploy, or irreversible changes.

Use when a non-trivial change lands or is abandoned and its decision, rejected alternatives, and reason must be captured. Not for trivial or corrective changes: those belong in CHANGELOG.

Use when departing knowledge must enter project topic files through a narration-first interview. Not for remote, credential, publish, deploy, or irreversible changes.

Use when contradictions, revisit conditions, or duplicates appear in knowledge entries. Not for remote, credential, publish, deploy, or irreversible changes.

Use when project documentation needs a layout or a knowledge item needs one home. Not for remote, credential, publish, deploy, or irreversible changes.

Use when repo content crosses into working context or synthesized knowledge. Flags injections and blocks derived instructions. Not for tasks requiring source or remote-system changes.

Use when an existing repository needs its unexplained rationale recovered into topic files. Don''t use for remote, credential, publish, deploy, or irreversible changes.

Use when a project context-schema differs from the installed entry format. Not for remote, publish, deploy, or irreversible changes.

Use when a knowledge artifact needs review before sharing or execution. Not for source or remote-system changes.

Use when a human asks to audit memory, find stale or duplicate memories, or needs tidy''s ICM-state audit. Not for writing new memories: use memory-update.

Use when the user asks to sanitize memory for sharing, redact PII, or scan memory for credentials. Not for auditing memory: use memory-clean.

Use when the user explicitly says to save something to memory or scan this session for memories. Not for auditing memory: use memory-clean.

Use when the user and agent may hold different pictures of current state after a gap, sync request, or exposed stale claim. Not for persistence: use memory-update.

Use when asked to recover prior work and current status before resuming. Not for handoff snapshots: use handoff. Not for source or remote-system changes.

Use when the user asks to beam, publish, or share the current local coding session to an authenticated remote receiver. Not for viewing a transcript locally: use session-viewer.

Use when the user asks to view, export, or inspect a session transcript in a browser. Not for sharing a session: use session-share.

Use when asked to find duplication, check consistency, establish or repair SSOT, consolidate facts, or when the user says "consolidate this" or "ssotize this". Not for remote or irreversible changes.

Use when asked to summarize authored work over the last week or a named date range, commit range, or branch. Not for source or remote-system changes.

Use when the user asks for a weekly synthesis, a weekly report, or a "what you need to know this week" digest from team reports. Not for the underlying reports or ad-hoc summaries.

Use when authorized workflow history may contain a repeated process worth extracting and replay-testing. Produces a contradiction-tested workflow mined from authorized history.

Use when a user asks to mine recent chats for workflow preferences. Don''t use for tasks that require source or remote-system changes.

Use when the learner is ready to apply cleared concepts in a real project. Not for exercises or quizzes: use drill.

Use when asked to create a multi-session learning plan. Returns a milestoned plan, practice, and review rubric. Don''t use for tasks that require source or remote-system changes.

Use when a concept needs practising: the user asks for an exercise, quiz, recall, or gap probe. Not for explanations: use explain-concept.

Use when a concept needs making clear rather than practising: explain simply, why does this exist, draw it, or simplify for a beginner. Not for scaffolded practice: use drill.

Use when asked to create an explainer document for a concept, diff, idea, or work recap. Drafts and verifies it in a scratch directory. Not for one-screen explanations: use explain-concept.

Use when a user, especially a new hire, asks for mentoring, guidance, or explanation of infrastructure or engineering practices. Not for code changes.

Use when asked to review learning progress after a milestone. Not for engineering retrospectives, use engineering-retrospective. For agent-environment ones, use agent-environment-retrospective.

Use when the user points to a study-material folder and asks to make it teachable. Not for remote, credential, publish, deploy, or irreversible changes.

Use when the user asks for onboarding, orientation, a repository tour, or where to start. Produces an evidence-backed seven-section map, deep-reads real files, and asks for the next move.

Use when asked to explain or teach a subsystem, module, pattern, or change in progressive layers from purpose to code depth. Not for design rationale: use why. Not for source or remote-system changes.