Menu
When changing DB schema or permission dimensions, consider predefined roles and bucket_role / role-related code.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | roles-schema-sync |
| description | When changing DB schema or permission dimensions, consider predefined roles and bucket_role / role-related code. |
When changing DB schema (especially permission-related columns or new resource types), or when adding/removing CRUD dimensions for bucket admins.
Predefined roles are defined in code (packages/helpers/src/bucketRoles/constants.ts) and may need:
bucketCrud, bucketMessagesCrud, bucketAdminsCrud) if CRUD semantics change.roles.full, roles.noUpdate) and in management-web/originals.Use parent-prefixed names for nested resources (e.g. bucketMessagesCrud); see nested-resource-prefix-naming.
Custom roles live in schema tables (bucket_role, management_admin_role). Adding columns or changing CRUD semantics may require:
infra/database/migrations/*.sql + infra/k8s/base/stack/postgres-init/0003_app_schema.sql (generated)infra/management-database/migrations/*.sql + infra/k8s/base/stack/postgres-init/0005_management_schema.sql.frag (generated)BucketRoleService updates.UI that lists or applies roles (dropdowns, Roles tab, role create/edit forms) may need to:
packages/helpers/src/bucketRoles/constants.tsinfra/k8s/base/stack/postgres-init/0003_app_schema.sql, infra/database/migrations/*.sqlinfra/k8s/base/stack/postgres-init/0005_management_schema.sql.frag, infra/management-database/migrations/*.sqlpackages/orm (BucketRole entity, BucketRoleService)apps/management-api (bucket roles routes, controller, schemas)packages/helpers-requests (bucket roles), packages/ui (BucketAdminsView, EditBucketAdminForm, BucketSettingsTabs)When changing API routes, auth, or env-dependent behavior, add or update the corresponding integration tests and keep the test file layout consistent.
When adding or changing files under infra/k8s/ or sync targets for k8s, know what Argo CD syncs and remind the user to push to Git so the cluster can sync.
Keeps tools/generate-data seeders and docs in sync when main or management DB schema or ORM entities change. Use when adding or changing tables/entities in packages/orm, packages/management-orm, or infra database migrations.
Use when adding or changing environment variables, infra/env/classification YAML, scripts/env-classification, K8s env render, or local env generation.
Common patterns for the Boilerplate HTTP API (Express)
When adding or changing preconditions, cleanup steps, or env usage for local Docker Compose or local k3d, keep both in sync where they share resources (e.g. infra/config/local/*.env).