메뉴
Meta-skill loaded at session start. Directs Claude to check for applicable OpenMetadata skills before starting any task. Ensures structured workflows are followed.
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 | openmetadata-workflow |
| description | Meta-skill loaded at session start. Directs Claude to check for applicable OpenMetadata skills before starting any task. Ensures structured workflows are followed. |
This skill is loaded automatically at session start. It ensures you follow the right workflow for every task.
Check which skills apply to your task and use them. This is not optional — if a skill applies, you must follow it.
| Task type | Required skill(s) |
|---|---|
| New feature (multi-file) | /planning then /tdd then /test-enforcement then /verification |
| Bug fix | /systematic-debugging then /tdd (write regression test) then /verification |
| New API endpoint | /planning then /tdd then /test-enforcement (must include integration test) |
| New connector | /connector-standards then /connector-building then /test-enforcement |
| UI component | /tdd then /test-enforcement (must include Jest + Playwright if user-facing) |
| Code review / PR review | /code-review then /test-enforcement |
| Opening / finalizing a PR | /test-enforcement then /verification then /pr-checklist |
| Connector review | /connector-review |
| E2E test creation | /playwright |
| Finishing implementation | /test-enforcement then /verification |
Note: Connector skills (
/connector-standards,/connector-building,/connector-review) and/playwrightare part of the OpenMetadata Skills plugin and ship together with this workflow skill. They are defined in theskills/directory alongside this file.
Plan before coding. For any non-trivial task, use /planning to design the approach before writing code.
Test-first when possible. Use /tdd to write failing tests before implementation. This applies to Java, Python, and TypeScript equally.
Always enforce test coverage. Before any PR, use /test-enforcement to verify:
Verify with evidence. Use /verification before claiming completion. Show actual test output, not claims.
Review before merging. Use /code-review for two-stage review (spec compliance + code quality).
Fill the PR template completely. Use /pr-checklist before gh pr create to gather every required section: linked issue, high-level design (large PRs), tests + coverage, UI screen recording, and manual test steps.
When your task touches multiple layers, ensure all are synchronized:
openmetadata-spec/ → run make generateyarn parse-schemabootstrap/sql/migrations/locale/languages/en-us.json then run yarn i18nmvn spotless:applymake py_format && make py_format_checkyarn organize-imports:cli && yarn lint:fix && yarn pretty:base --writeyarn license-header-fix)yarn generate:app-docsIf CLAUDE.md instructions conflict with any skill, CLAUDE.md wins. Skills are supplementary workflows, not overrides.