AI Agent Hub
Back to skills
Manufacturing Data Governance Best Practices icon

Manufacturing Data Governance Best Practices

Data Analysis Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md to install @user_480293a4/shujuzhili-nz into your AI assistant.

About this skill

Problem

Manufacturing material master data often suffers from duplicate items with different codes, causing duplicate purchasing, inconsistent status, and uneven task assignment. Manual duplicate detection misses many cases, while high-volume frontend requests, expensive computed values, async race conditions, and schema changes make governance projects harder to maintain. This skill pack targets Vue 3, Flask, and SQL Server data governance projects by turning common pitfalls into checkable development practices.

How It Works

It breaks material deduplication and governance development into 10 practices: batched Promise.all calls, caching for expensive computed logic, unified display rules, boundary-case checks, requirement confirmation, clear error messages, post-change validation, comments for critical logic, synchronized updates on structure changes, and safe async/await patterns. Use the relevant entry for the current development stage, then work through its problem description, bad example, correct approach, reusable template, and checklist.

Scope

This is best suited to projects with material deduplication, task assignment, or ERP/PDM synchronization needs, especially where frontend performance, code quality, and review discipline matter. It does not replace business matching algorithms, permission design, or data cleansing rules; field semantics, master data standards, and repository-specific constraints still need validation.

Use Cases

  • When batch-calling duplicate-check APIs in a Vue 3 page, use chunked requests to avoid `Promise.all` freezing the browser.
  • When maintaining similarity lists or task assignment views, centralize display rules and add boundary-case checklists.
  • When changing Flask governance APIs or data fields, apply post-change validation and structure-change sync practices.
  • When debugging async status-sync race conditions, follow clear error-message and safe `async/await` templates.

Best For

  • Vue 3 engineers maintaining material duplicate-check pages who need stable batch requests and cached computed logic.
  • Flask backend engineers building data governance APIs who need disciplined field changes, SQL queries, and clear errors.
  • Data governance PMs or QA engineers validating ERP/PDM task synchronization and boundary flows using checklists.
  • Tech leads taking over legacy deduplication systems who need standardized comments, validation, and async race-condition review.