cpa

Plugin cpa from marketplace canvas-medical in canvas-medical/coding-agents. Commands read from the repo's manifest — today.

Skills (13)

• canvas-platform

  Canvas native-feature reference. Use whenever an answer depends on what Canvas already does without a plugin — feasibility ("can Canvas do X, and how?"), config-first alternatives (a setting, role, template, or protocol instead of code), out-of-the-box workflows and UI behavior, adjacent native capa

• canvas-sdk

  Canvas SDK reference and documentation. Use whenever a question, claim, or piece of code touches Canvas SDK capabilities, API usage, implementation patterns, or testing — including quick conversational questions ("how do I ingest ADTs?", "what's the import for X?", "how is Y modeled in the SDK?"). F

• companion-app-patterns

  Design, UI, data-access, and packaging conventions for Canvas provider companion applications (scopes `provider_companion_global`, `provider_companion_patient_specific`, `provider_companion_note_specific`). Use when building or reviewing a plugin whose manifest declares one of those scopes, or whose

• custom-data-patterns

  Custom Data anti-patterns and corrections for Canvas plugins - unnecessary compatibility checks, misuse of AttributeHubs vs CustomModels

• data-access-strategy

  Decide how a Canvas plugin reads and writes data - SDK vs FHIR API, and existing Canvas data models vs Custom Data. Use whenever a plugin needs to read or write clinical/operational data, before writing the spec or any data-access code.

• database-performance

  Database performance for Canvas plugins - N+1 detection, over-hydration/memory, write amplification, and Canvas execution limits (effect-batch ceiling, dbid PK)

• fhir-api-client-development

  FHIR API reference and documentation for Canvas plugins that need to read or write data via FHIR endpoints

• fhir-api-client-security

  Security review for plugins acting as FHIR API clients - token management, scope validation, and patient-scoped authorization

• icon-generation

  Generate SVG icons and convert them to 48x48 PNG format for Canvas plugins and applications

• instance-analyze

  Analyze Canvas instance configuration to understand the target environment for plugin development

• plugin-api-server-security

  Security review for plugin API endpoints (SimpleAPI, WebSocket) - authentication and authorization when your plugin is the SERVER

• plugin-patterns

  Canvas plugin architecture patterns, best practices, and implementation templates

• testing

  Unit test authoring and coverage checking for Canvas plugins

Slash commands (11)

• /cpa:analyze-instance

  Analyze a Canvas instance's configuration to understand the target environment.

• /cpa:check-setup

  Verify the development environment has all required tools and configuration before starting plugin development.

• /cpa:coverage

  Run tests with coverage and offer to improve if below 90%.

• /cpa:create-icon

  Generate an SVG icon from a description and automatically convert it to 48x48 PNG format.

• /cpa:database-performance-review

  Review Canvas plugin for database query performance issues, focusing on N+1 queries and ORM optimization.

• /cpa:deploy-lite

  Quick-deploy the current plugin to a Canvas instance — no version bump, no tests, no commit. Just install and monitor logs.

• /cpa:deploy

  Deploy the current plugin to a Canvas instance with log monitoring.

• /cpa:new-plugin

  Start the plugin brainstorming process to transform requirements into a concrete specification, then implement it. Also supports updating an existing plugin with version bumping.

• /cpa:run-evals

  Execute eval cases to verify that security and database performance review commands correctly detect known issues.

• /cpa:security-review

  Comprehensive security audit for Canvas plugins covering both server-side API security and client-side FHIR API security.

• /cpa:wrap-up

  Final checklist before calling a plugin "done" for this version.

Subagents (3)

• deploy-uat

  Deploy Canvas plugins — handles version bump, validation, git commit, and install. Does NOT manage log monitoring (parent command owns that).

• instance-analyzer

  Analyze Canvas instance configuration to understand the target environment for plugin development

• plugin-brainstorm

  Collaborative dialogue to transform vague requirements into concrete Canvas plugin specifications, or update existing plugins with version bumping

MCP servers (1)

• canvas_cmd_line

  runs: uv run --with mcp<2 python ${CLAUDE_PLUGIN_ROOT}/scripts/mcp_canvas_installer.py

Hooks (6)

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/scripts/plugin_gate.py"

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/scripts/plugin_gate.py"

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/scripts/plugin_gate.py"

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/scripts/plugin_gate.py"

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/scripts/plugin_gate.py"

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/scripts/plugin_gate.py"

Similar plugins