apex plugins

by tonone-ai

Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

by tonone-ai

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

by tonone-ai

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

by tonone-ai

CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

by tonone-ai

System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".

by tonone-ai

Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

by tonone-ai

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

by tonone-ai

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

by tonone-ai

CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

by tonone-ai

System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".

by Matt Corbett

Salesforce practitioner team — agents (apex-engineer, flow-automation-architect, agentforce-architect, salesforce-platform-architect, salesforce-reviewer) covering governor-safe bulkified Apex (triggers/async/services), declarative automation by density (Flow vs Apex, order-of-execution), Agentforce design (topics/actions, Atlas determinism, Trust Layer), org architecture (data model, OWD→sharing→Apex security, 2GP packaging/DevOps, LDV), and a forked review rubric (the house opinions as pass/fail). Citation-grounded knowledge bank (Mermaid decision trees incl. automation-density), a scenarios bank (field notes), best-practices, skills, commands, templates, an advisory hook + a runnable SOQL/DML-in-loop scanner (scripts/apex_governor_smell.py), and an .lsp.json (Apex + LWC LSP). MCP recommend-not-bundle (org-credentialed @salesforce/mcp). Seams: integration→azure-cloud, analytics→data-platform, LWC styling→web-design, security-review→ravenclaude-core. Requires ravenclaude-core@>=0.7.0.

by grzmol

Salesforce delivery harness for Claude Code: parallel multi-agent workflow, documentation-grounded Salesforce and fflib skills, deterministic hooks, and local plus post-deploy verification gates.