Secret-Tool Integration

Adding new API key credentials across the full stack requires coordinating DB schema, backend, frontend, and UI mappings. This skill enforces explicit steps across Prisma schema, migrations, and API definitions to ensure consistent category alignment and safe secret handling.

Wiring a new secret and tool binding in Prisma involves defining new SecretCategory values and applying corresponding schema changes. This skill provides a unified blueprint across DB, API, and UI layers to prevent configuration drift during migration.

Secret-tool integration exposes new tool credentials to the frontend by mapping them consistently through backend API definitions and UI mappings. It enforces explicit steps to ensure safe secret handling and consistent category alignment across the full stack.

You need to create new SecretCategory values when introducing a new tool requiring an API key. This skill guides the necessary mapping and migration steps across DB schema, backend, and frontend definitions to maintain consistent category alignment.

Managing secret-tool bindings piecemeal across stacks is error-prone and causes configuration drift. This skill addresses these limitations by providing an end-to-end blueprint across DB schema, migrations, backend, and frontend definitions for safe secret handling.

Secret-tool integration works without existing dependencies, relying instead on explicit steps across Prisma schema, backend, and frontend definitions. It provides a unified blueprint to ensure consistent category alignment and safe secret handling across the full stack.