القائمة
Prefer reusable components and keep globals minimal. Use when adding layout, form, or UI that could be reused, or when adding styles to globals.scss.
التثبيت باستخدام 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 | reusable-components |
| description | Prefer reusable components and keep globals minimal. Use when adding layout, form, or UI that could be reused, or when adding styles to globals.scss. |
| version | 1.0.0 |
When to use: Any time you are adding layout, form, or UI that could be reused, or when you are about to add styles to globals.scss (or app-level global CSS).
globals.scss only for true app-wide basics (e.g. html/body, root layout wrappers like .app-view). Page- or feature-specific layout and styling belong in component module SCSS or layout components.ComponentName.module.scss) for component-specific styles so they are scoped and easy to find.AuthFormLayout (or similar) component with its own .module.scss instead of auth-specific classes in globals.scss.children and owns the structure and styles.globals.scss? → Consider a reusable component + module SCSS instead.