Vault-Toolbox

Implementation patterns for the Vault Toolbox Browser Extension (Manifest V3).

Specialized design challenges for the Vault Toolbox Browser Extension, focusing on VQL prototyping.

Specialized audit for the Vault Toolbox Browser Extension, focusing on Island Architecture and UI visibility.

Specialized data grid implementation for the Vault Toolbox Browser Extension using TanStack Table/Virtual.

Specialized design requirements for the Vault Toolbox Browser Extension, focusing on UI visibility.

Specialized testing and dev-server protocol for the Vault Toolbox Browser Extension.

Specialized scaffolding and shell integration for the Vault Toolbox Browser Extension.

Specialized tutorial cheat sheet for the Vault Toolbox Browser Extension.

UI standards for the Vault Toolbox Browser Extension focusing on Chakra UI and the Nested Pillar layout.

Specialized testing requirements for the Vault Toolbox Browser Extension, focusing on Vitest and Chrome context.

Universal methodology for Vault API interaction. Includes Evidence-First mandate and Vault API CLI guide.

Guides the Brainstorming and Socratic Design phase. Use this at the start of any new feature to explore architectural paths.

Performs an automated self-audit of code and metadata. Use this at the end of every task to ensure compliance with standards.

Retrieve, create, update, alter, drop, or describe Veeva Vault configuration via the Metadata Definition Language (MDL) REST API. Use whenever the user asks about MDL, executing MDL scripts, Vault component metadata, RECREATE/ALTER/CREATE/DROP/RENAME of components like Picklist, Object, Aitooltype, Aitool, Aicontexttype, Recordtrigger, Doclifecycle, Objectlifecycle, etc., listing components in a vault, exporting an existing component as an MDL script, or describing a component type's schema. Trigger on phrases like "MDL", "execute MDL", "RECREATE Aitool", "ALTER Object", "CREATE Picklist", "DROP component", "retrieve MDL component", "vault metadata", "component schema", "configuration metadata", "list MDL components", or "deploy this picklist to my vault". In THIS project all MDL/metadata calls go through the authenticated `vault_api.js` gateway — never raw curl, never collect username/password.

Universal best practices for data orchestration and display in Vault grids and tables.

Fast-prototyping lane that defers (never skips) the heavy lifecycle phases, preserving the safety rails, with a gated graduation path back to full rigor.

Guides the technical design phase (Phase 2). Use this to create comprehensive design documents after brainstorming.

Guidance for surgically transplanting features from a fork into the main project.

Specialized guidance for implementing Vault Java SDK components for Custom Pages.

Synchronizes project documentation, the codebase knowledge graph, and the skills manifest. Use after implementing features or refactoring.

Toggles token-efficient communication modes (rocky, eridani, signal, caveman).

Universal methodology for scaffolding new features using Toolbox Designer.

Provides a guided, step-by-step tutorial for the Toolbox Designer lifecycle.

Universal UI philosophy and verification criteria for Vault Designer applications.

Enforces the TDD (Red-Green-Refactor) mandate. Use during implementation to ensure logic is verified by tests.

Packages Custom Pages into deployable Vault Packages (VPKs) via the vpk CLI.

Guarantees 100% correct, verified VQL queries. Use whenever creating, modifying, or troubleshooting any Vault Query Language (VQL) statement.

Packages and deploys Veeva Vault custom code — auto-detects whether a feature has client (Custom Page) and/or server (Java SDK) code and packages it as one all-in-one VPK, then deploys via the project's authenticated vault_api gateway. Also offers Java single-file hot-deploy and Custom Page client direct-deploy. Use whenever the user asks to build a VPK, deploy SDK code, push code to a Vault sandbox, hot-patch a single Java class, build/upload a custom page client distribution, run a Page MDL, or run a full feature deploy. Triggers — "build a VPK", "deploy my code", "push to my vault", "hot patch", "PUT /code", "deploy my custom page", "upload distribution", "uicode/distributions", "execute MDL", "full deploy", "deploy everything". Deployment is gated on whether vault_api is authenticated; if not, the skill offers to authenticate, and if declined, packages the VPK and stops so the user can deploy manually later.