Avinava

Apply Salesforce knowledge and best practices for SOAP API Developer Guide

Apply Salesforce knowledge and best practices for Communications, Media, Energy and Utilities (CME) Developer Guide

How to develop, extend, and maintain the SF Documentation Knowledge System

Apply Salesforce knowledge and best practices for Marketing Cloud API

Apply Salesforce knowledge and best practices for Marketing Cloud Package Development

Apply Salesforce knowledge and best practices for Get Started, Marketing Cloud Developers

Apply Salesforce knowledge and best practices for Programmatic Marketing Content

Apply Salesforce knowledge and best practices for Marketing Cloud SDKs

Audit and install a self-correcting guardrail stack in any TypeScript project. Four-phase workflow: understand the guardrail system from this repo, inventory the target project, generate a gap analysis, then apply changes — creating missing configs and merging missing sections into existing ones.

Extend an existing guardrail installation with LLM discipline rules: complexity limits, cognitive complexity, naming conventions, ESM idioms, documentation coverage, and test coverage thresholds. Run after setup-guardrails.

Use when adding imports, creating packages, or reviewing code to ensure tiered dependency rules are followed. Read this to understand the tier system.

Use on every commit. The pre-commit hooks run 8 checks in parallel. If any fail, read ALL errors, fix them in one pass, and retry.

Use when creating a new workspace package in a monorepo. Covers package creation, tier assignment, and all config updates required.

Use when adding a new full-stack CRUD resource (e.g. "add a Comments resource"). Walks through Prisma model, Zod schema, tRPC router, and React page in order. Mirrors the patterns already used by Contact/Task/Project.

Use before pushing to a deployed environment (staging or prod). Walks through env vars, migrations, secrets, build, and rollback prep.

Use the first time an agent (or human) opens this repo. Installs deps, prepares the env, validates that the dev environment works, and points the agent at the right files.

Use when starting a real project from this template. Removes the CRM demo (Contact/Task/Project) cleanly so the repo is a blank slate without breaking guardrails.

Use on every commit. The pre-commit hooks run checks in parallel. If any fail, read ALL errors, fix them in one pass, and retry. NEVER use --no-verify.

Systematic code review and refactoring of a TypeScript/JavaScript codebase. Use when asked to audit, review, refactor, or improve code quality.