一键导入
connector-standards
Load all OpenMetadata connector development standards into context. Use before building or reviewing connectors to ensure consistent patterns.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Load all OpenMetadata connector development standards into context. Use before building or reviewing connectors to ensure consistent patterns.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when writing or editing React/TSX in `openmetadata-ui/src/main/resources/ui/src/` or `openmetadata-ui-core-components/`, before reaching for a raw `<div>` + Tailwind utility classes to build layout (flex rows/columns, grids, bordered panels with header/body/footer, separators), and before writing any Tailwind color class (`tw:bg-*`, `tw:text-*`, `tw:border-*`) or hex color value. Applies whenever the change adds or restructures a layout container or touches color/dark-mode styling, not to every div.
Build a new OpenMetadata connector from scratch — scaffold JSON Schema, Python boilerplate, and AI context using schema-first architecture with code generation across Python, Java, TypeScript, and auto-rendered UI forms.
Run `mvn spotless:apply` to fix Java checkstyle / formatting failures and verify the result. Run after authoring or modifying any `.java` files, or when CI reports a "Java checkstyle failed" / "Fix Java checkstyle" issue on a PR.
Run the ESLint + Prettier + organize-imports sequence that CI's `UI Checkstyle` jobs (`lint-src`, `lint-playwright`, `lint-core-components`) run — on just the files the PR changed — and fail if any file ends up with a diff. Run after authoring or modifying any `.ts`/`.tsx`/`.js`/`.jsx`/`.json` under `openmetadata-ui/src/main/resources/ui/src/`, `.../playwright/`, or `openmetadata-ui-core-components/src/main/resources/ui/src/`, or when CI reports a `UI Checkstyle` failure on a PR.
Run `mvn spotless:apply` to fix Java checkstyle / formatting failures and verify the result. Invoke after authoring or modifying any `.java` files, or when CI reports a "Java checkstyle failed" or "Fix Java checkstyle" issue on a PR.
Run the exact ESLint + Prettier + organize-imports sequence that CI's `UI Checkstyle` jobs (`lint-src`, `lint-playwright`, `lint-core-components`) run — on just the files the PR changed — and fail the task if any file ends up with a diff. Invoke after authoring or modifying any `.ts`, `.tsx`, `.js`, `.jsx`, or `.json` file under `openmetadata-ui/src/main/resources/ui/src/`, `.../playwright/`, or `openmetadata-ui-core-components/src/main/resources/ui/src/`, or when CI reports a "UI Checkstyle" job failure on the PR.
| name | connector-standards |
| description | Load all OpenMetadata connector development standards into context. Use before building or reviewing connectors to ensure consistent patterns. |
| user-invocable | true |
| argument-hint | [optional: specific standard name like 'testing' or 'database'] |
| allowed-tools | ["Read","Glob"] |
When a user asks to "load standards", "show connector standards", or before starting any connector development or review work.
If no specific standard is requested, load all standards in this order:
${CLAUDE_SKILL_DIR}/standards/main.md — Architecture overview${CLAUDE_SKILL_DIR}/standards/patterns.md — Error handling, logging, pagination${CLAUDE_SKILL_DIR}/standards/code_style.md — Python and JSON Schema conventions${CLAUDE_SKILL_DIR}/standards/schema.md — Connection schema patterns${CLAUDE_SKILL_DIR}/standards/connection.md — Connection class patterns${CLAUDE_SKILL_DIR}/standards/service_spec.md — ServiceSpec registration${CLAUDE_SKILL_DIR}/standards/testing.md — Unit and integration test patterns${CLAUDE_SKILL_DIR}/standards/registration.md — How to register a connector${CLAUDE_SKILL_DIR}/standards/performance.md — Performance best practices${CLAUDE_SKILL_DIR}/standards/memory.md — Memory management and OOM prevention${CLAUDE_SKILL_DIR}/standards/lineage.md — Lineage extraction methods${CLAUDE_SKILL_DIR}/standards/sql.md — SQLAlchemy patterns and URL buildingThen read all source-type standards:
${CLAUDE_SKILL_DIR}/standards/source_types/*.md
If a specific standard or service type is requested:
| Request | File to Load |
|---|---|
| "testing" | standards/testing.md |
| "patterns" | standards/patterns.md |
| "schema" | standards/schema.md |
| "lineage" | standards/lineage.md |
| "sql" | standards/sql.md |
| "memory" | standards/memory.md |
| "database" | standards/source_types/database.md |
| "sql databases" | standards/source_types/sql_databases.md |
| "data warehouses" | standards/source_types/data_warehouses.md |
| "nosql" | standards/source_types/nosql_databases.md |
| "dashboard" | standards/source_types/dashboard.md |
| "pipeline" | standards/source_types/pipeline.md |
| "messaging" | standards/source_types/messaging.md |
| "mlmodel" | standards/source_types/mlmodel.md |
| "storage" | standards/source_types/storage.md |
| "search" | standards/source_types/search.md |
| "api" | standards/source_types/api.md |
| etc. | standards/source_types/{name}.md |
Confirm to the user which standards were loaded and summarize the key points. Example:
Loaded 12 core standards + 11 source-type standards. Key points:
- Schema-first: one JSON Schema → Python, Java, TypeScript, UI forms
- Use
BaseConnectionfor SQLAlchemy,get_connection()/test_connection()for others- Use pytest with plain
assert, no unittest.TestCase- Always include copyright header, use
ingestion_logger()- Lineage via query logs (database), SQL parsing (dashboard), or task metadata (pipeline)