essentials

Plugin essentials from marketplace ccconfigs in dhruvbaldawa/ccconfigs. Commands read from the repo's manifest — 6 days ago.

Skills (15)

• codebase-design

  Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

• conveyor

  Milestone execution loop with subagents — essentials:implementer commits each slice through the pre-commit hook, senior-engineer-reviewer + test-reviewer gate it, essentials:fixer answers findings, the orchestrator watches and records. Use when the user says "conveyor" or hands over a plan milestone

• debugging

  Systematic debugging that identifies root causes rather than treating symptoms. Use when a bug, failing test, or unexpected behavior has no obvious cause, or a first fix attempt didn't hold. Uses structured multi-hypothesis reasoning for complex analysis, web search for research, and structured inve

• explainer-artifact

  Turns a debugging/design session into a polished, concept-first Artifact that explains a technical problem and its fix to an engineer who wasn't there. Use when the user asks for an "explainer", to "explain this visually", to make something "easy to understand", to "create an artifact explaining X",

• grill-me

  Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

• handoff

  Compact the current conversation into a handoff document for another agent to pick up. Use when context is running out, when switching machines or sessions, or when delegating in-progress work.

• improve-codebase-architecture

  Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. Use when the user wants an architecture review, asks where the codebase is getting hard to change, or wants to find refactoring candidates.

• pr

  Template and guidance for writing a pull request body — summary visual, before/after evidence, and merge-danger assessment. Use when writing or updating a PR description.

• project-setup

  Bootstrap new projects with strong typing, linting, formatting, and testing. Supports Python, TypeScript, and other languages with research fallback. Use when starting a new project or adding typing, linting, formatting, or test tooling to one that lacks it.

• prototype

  Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

• retro

  Conduct a retrospective on a coding session and suggest improvements to the agent's environment. Use when the user asks for a retro, or wants to know what would make future agent runs go better.

• teach

  Teach the user a new skill or concept, within this workspace. Use when the user wants to learn a topic over multiple sessions rather than get a one-off explanation.

• technical-planning

  Plans technical projects with risk-first development, milestone structuring, and managed deferral. Use when planning software projects, defining milestones, structuring development phases, or breaking down complex tasks into manageable iterations.

• wait-what

  Stop. That last message did not land — re-pitch it. Use when the user says "wait, what", "you lost me", "I don't follow", or otherwise signals the previous explanation failed.

• writing-documentation

  Produces concise, clear documentation by applying Elements of Style principles. Use when writing or improving any technical documentation (READMEs, guides, API docs, architecture docs). Not for code comments.

Slash commands (2)

• /essentials:catchup

  Review all changes between current branch and main

• /essentials:optimize-doc

  Optimize documentation for conciseness and clarity by strengthening vague instructions and removing redundancy

Subagents (4)

• fixer

  Fixes exactly the blocking review findings on a conveyor slice as new commits through the pre-commit hook

• implementer

  Implements one conveyor slice as planned commits through the pre-commit hook; asks before building when the design is in doubt

• senior-engineer-reviewer

  Brutally reviews code like a senior engineer with no patience for architectural sins, premature abstractions, or code that will become tech debt

• test-reviewer

  Brutally reviews test code for useless tests, flaky patterns, missing assertions, and tests that would pass even if the code was broken