القائمة
Use a consistent tabbed layout on management-web edit pages when there are multiple distinct forms (e.g. profile vs password).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
When changing DB schema or permission dimensions, consider predefined roles and bucket_role / role-related code.
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)
| name | management-edit-page-tabs |
| description | Use a consistent tabbed layout on management-web edit pages when there are multiple distinct forms (e.g. profile vs password). |
When to use: When adding or changing edit pages in management-web that have multiple distinct forms (e.g. profile vs change password, or multiple logical sections that could be separate forms).
Use a tabbed layout with one tab per form (or logical group):
Tabs from @boilerplate/ui with LinkComponent={Link} and exactMatch.activeHref behavior.?tab=... in the URL and a route helper (e.g. userEditRoute(id, tab)) so the active tab matches with and without query params.apps/management-web/src/app/(main)/user/[id]/edit/, EditUserPageContent.tsx, userEditRoute(id, tab)).apps/management-web/src/app/(main)/settings/SettingsContent.tsx, accountSettingsRoute(tab)).Edit pages with a single form (e.g. admin edit, bucket admin edit, role edit, message edit) do not need tabs. If a future edit page gains a second form, apply this pattern.