claude-tooling

Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.

Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.

Cross-repo visibility for agent loops. Lists running, completed, and crashed loops. Reads the registry and per-repo tracking logs. Shows tmux attach commands. Use when checking what loops are active, what ran recently, or loop details.

Capture feedback about wf, util, or vault plugins and file it as a GitHub issue for improvement. Use after any session where the tooling fell short — wrong agent behavior, missing skill coverage, misleading prompts, workflow friction, or convention gaps. Only for generic plugin improvements that would help ANY project, not repo-specific config. Files to JSai23/claude-tooling with the plugin-feedback label.

Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.

Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.

Cross-repo visibility for agent loops. Lists running, completed, and crashed loops. Reads the registry and per-repo tracking logs. Shows tmux attach commands. Use when checking what loops are active, what ran recently, or loop details.

Logging auditor focused on signal over noise. Use for /logging.

Add, fix, or update logging in project code

Add, fix, or update logging in project code

Use this agent for processing inbox, filing notes, organizing the vault, updating living docs, maintaining backlinks and tags, and running audit passes. The organizer that turns raw captures into structured knowledge.

This skill should be used when the user asks to "process inbox", "auto process", "file this note", "triage inbox", "route this to the right place", or needs to automatically move notes from 0-Inbox to their correct PARA destination.

Use this agent for thinking through problems, exploring what your notes say, discussing where projects stand, and synthesizing across areas. A research partner that reads your vault and thinks with you. Writes synthesis to inbox.

Use this agent for interactive writing sessions. Drafts notes from conversation, encodes filing intent for the librarian, writes to inbox only. A transcription partner that captures your thinking well.

This skill should be used when the user asks to "check tags", "update tags", "audit tags", "change tag", "list tags", "tag this note", "fix frontmatter tags", or needs to manage tags across notes.

This skill should be used when the user asks to "file a note", "organize vault", "PARA structure", "vault rules", "add frontmatter", "tag a note", "archive a note", "naming convention", or when working with Obsidian vault files.

Implementation session — execute milestones from a plan, write production code and tests, follow codebase patterns, surface deviations, maintain living docs. Launched via: claude --agent wf:builder

Maintenance session — continuous cleanup of LLM-generated technical debt in code and documentation. Keeps docs current, prunes stale plans, fixes drift. Launched via: claude --agent wf:gardener

Log decisions, progress, deviations, and discoveries during any workflow phase

Planning and design session — everything before code. Use when starting a feature, designing a system change, or breaking down complex work into an execution plan. Launched via: claude --agent wf:planner

Verification session — end-of-cycle quality review covering design, integrity, cleanliness, and production readiness. Delegates to specialized agents via Task tool. Launched via: claude --agent wf:verifier

Implementation practices — deviation protocol, progress tracking, code standards, codebase reflection

ALWAYS USE if you are the builder. Use after every implementation pass — update living docs, maintain diagrams (Mermaid for formal, ASCII for loose), reconcile plan with reality, update ARCHITECTURE.md when system shape changes. Documentation is a core output, not an afterthought.

The agent documentation system — doc types, folder structure, frontmatter conventions, agent roles, lifecycle

Log decisions, progress, deviations, and discoveries during any workflow phase

How to write implementation plans — code structure, module layout, component connections, with execution blocks at the end

ALWAYS USE if you are the verifier or gardener. Use after any build cycle to audit documentation accuracy — check diagram drift, living doc freshness, ARCHITECTURE.md currency, cross-link integrity, and plan status. Gardener uses broadly across the full doc tree; verifier uses post-build to confirm the builder did its doc duty.

Documentation writer focused on brevity. Use for /doc.

Capture feedback about wf, util, or vault plugins and file it as a GitHub issue for improvement. Use after any session where the tooling fell short — wrong agent behavior, missing skill coverage, misleading prompts, workflow friction, or convention gaps. Only for generic plugin improvements that would help ANY project, not repo-specific config. Files to JSai23/claude-tooling with the plugin-feedback label.

How to think about design — product outcomes, system architecture, code structure, tradeoffs

Ask questions about design, architecture, or how code fits together

Answers design and architecture questions from plans and docs. Use for /ask.

Create session handoff document for transferring work to another session

Generate or update project documentation

Resume work from a previous handoff document

Rust code quality audit based on Apollo best practices

Token-efficient code analysis reference. Use when analyzing large codebases or needing structured code intelligence.

This skill should be used when the user asks to "search notes",

Generate or update standard code documentation — docstrings, rustdoc, API references, READMEs

This skill should be used when the user asks to "add backlinks", "find related notes", "what should this link to", "update backlinks", "suggest connections", or needs to find appropriate wikilinks for a note.