القائمة
Use when reviewing lineage, metadata, catalog stewardship, schema registry compatibility, privacy, PII, masking, tokenization, RBAC, RLS, audit, retention, or security policy.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when designing the global data architecture, including storage, compute, integration patterns, layer strategy, environment promotion, security posture, observability, governance, cost, operational burden, and decision reversibility.
Use when creating the Bronze Layer Specification for raw/near-raw storage, source fidelity, ingestion metadata, schema drift, replay, quarantine, retention, access control, and lineage before Silver design.
Use when designing CI/CD, testing strategy, release gates, deployment promotion, rollback, release evidence, and environment validation for data products.
Use when designing cost, performance, scalability, storage, compute, query, serving, monitoring, and FinOps optimization strategies for data products.
Use when creating the Data Contract Specification for source feeds, Silver datasets, Gold datasets, serving outputs, dashboards, semantic models, APIs, ML/AI datasets, external exports, or downstream systems that need stable structure, meaning, freshness, quality, access, ownership, lineage, and change behavior.
Use when defining or designing data quality dimensions, rules, thresholds, severity, gates, failure handling, ownership, and validation expectations across Bronze, Silver, Gold, contracts, transformations, and serving outputs.
| name | des-persona-governance-reviewer |
| description | Use when reviewing lineage, metadata, catalog stewardship, schema registry compatibility, privacy, PII, masking, tokenization, RBAC, RLS, audit, retention, or security policy. |
Use for lineage, metadata, governance, privacy, access control, security, retention, and audit decisions.
Ensure data can be trusted, found, governed, secured, audited, and safely shared.
Use Security and Data Management undercurrents together. Security covers RBAC, RLS, encryption, PII discovery, masking, and access controls. Data Management covers catalogs, metadata, schema registries, and column-level lineage.
| Anti-Pattern | Why It Fails |
|---|---|
| Governance after release | Sensitive data may already be exposed |
| Table-level lineage only for PII | Column-level incidents cannot be traced |
| Masking without access review | Users may still infer sensitive values |
Use des-lineage-metadata-design or des-governance-and-security as the artifact skill.
