Structured dialogue framework for truth-seeking roundtable discussions. A rational moderator invites representative figures with different thinking styles to engage in high-intensity, instant-response deep conversation, generating ASCII visualization frameworks each round and building a structured knowledge network.
Adaptive reading companion for non-technical books (philosophy, humanities, history, economics, finance, literature). Assesses books, generates reading guides, supports ongoing discussion, and proposes structured Obsidian notes. Use when starting a new book, discussing a book in progress, or generating book notes.
Structured planning workflow for any coding task. Use at the start of every new feature, bug fix, refactor, or implementation request. Analyzes the project, asks up to 5 clarifying questions, creates a TODO.md, gets user approval, then executes task by task. Never writes code before a plan is approved.
Use when the project contains sfdx-project.json, .forceignore, or a force-app/ directory, or when working with .cls, .trigger, or Lightning Web Component files. Use when the user asks to "deploy to org", "push to org", "retrieve from org", "pull from org", "run apex tests", "run tests", "create apex class", "create lwc", "create trigger", "create aura component", "delete metadata", "open org", "set target org", "list orgs", "diff against org", "compare with org", "check what changed in org", "pull metadata from org", "browse org metadata", "fix this apex class", "why is my test failing", or any task involving Salesforce, Apex, SFDX, LWC, Lightning Web Components, metadata deployment, or the sf CLI.
Socratic book-learning tutor for any book or course. Teaches chapter-by-chapter using guided questioning, ~200-word explanations, and comprehension checks. Tracks progress and writes durable concept notes to a vault. Reads book config from project CLAUDE.md. Use when the user says "chapter N", "let's study", "teach me X", or when a project CLAUDE.md declares a learning context.
Clean-code focused Apex guidance for readability, naming conventions, 3-tier architecture (entry-point, static service, OO), error handling, and unit vs integration testing. Use when reviewing or generating Apex for clarity and maintainable structure, excluding security/performance scoring.