メニュー
Develop and visually verify changes to the documentation site (VitePress). Use when working on doc pages, Vue components, VitePress config, or validating docs UI with Playwright MCP.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Write or refactor unit tests following the canonical project pattern. Use when adding new unit tests or standardizing existing ones.
Generate a Kotlin SingleModelValidationRule implementation for ONE rule from BPMN_STYLE_GUIDE.md. Use when drafting / iterating on a single rule, or when the user asks to 'generate a rule for <slug>', 'create the element-id-format rule', or 'add just this one rule to the test module'. For all rules at once, use generate-rules-to-enforce-bpmn-styleguide.
Generate Kotlin SingleModelValidationRule implementations for every deterministic (or hybrid) rule in BPMN_STYLE_GUIDE.md, so they can be enforced at test time by the bpmn-to-code-testing module. llm-only rules stay in the style guide for /validate-bpmn-style. Use when the user asks to 'generate validation rules from the style guide', 'enforce BPMN conventions in CI', or 'automate style checks in tests'. For a single rule, use generate-rule-to-enforce-bpmn-styleguide.
Interactively author a BPMN_STYLE_GUIDE.md for your project — a handbook that explains how the team models BPMN processes (naming, allowed elements, IDs, topics, engine-specific special cases). The output is a document humans can read; embedded YAML annotations let downstream skills enforce the rules. Use when the user asks to 'create a BPMN style guide', 'set up BPMN conventions', or 'define BPMN naming rules'.
Create a complete Spring Boot service project from a BPMN file with hexagonal architecture. Bootstraps via Spring Initializr, configures bpmn-to-code, and generates workers, use cases, and services wired to ProcessApi constants — no raw strings anywhere. Use when the user wants to start a new process service from a BPMN model.
Migrate generated API usage from bpmn-to-code v1.1.0 to v2.0.0. Use when the user asks to 'upgrade to v2', 'migrate from v1 to v2', 'fix TaskTypes references', or 'update bpmn-to-code API calls after upgrade'.
| name | docs-dev |
| argument-hint | "<page or component to work on>" |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash(npm *), Bash(cd *), mcp__playwright__* |
| description | Develop and visually verify changes to the documentation site (VitePress). Use when working on doc pages, Vue components, VitePress config, or validating docs UI with Playwright MCP. |
Develop and visually verify changes to the bpmn-to-code documentation site.
.vitepress/theme/. Use Vue 3 Composition API.npm run build to catch broken links or build errors before finishing.The documentation site uses VitePress at docs/.
Key facts:
docs/ (e.g. index.md for landing page)docs/.vitepress/config.mts — site title, navigation, sidebar, footer, social linksdocs/.vitepress/theme/ — custom theme extending DefaultThemeVersionBadge.vue (fetches latest GitHub release, displays in nav bar)docs/.vitepress/theme/style.cssdocs/package.json (do not hardcode)Read the files relevant to $ARGUMENTS. Key files and their purposes:
| File | Purpose |
|---|---|
docs/index.md | Landing page: hero section, feature cards, code comparison |
docs/.vitepress/config.mts | Site config: nav bar, sidebar, footer, social links |
docs/.vitepress/theme/index.ts | Theme setup: extends DefaultTheme, registers components |
docs/.vitepress/theme/style.css | Custom CSS overrides |
docs/.vitepress/theme/components/*.vue | Custom Vue components |
docs/web/index.md | "Try in Browser" page linking to web module |
docs/getting-started/*.md | Gradle and Maven setup guides |
docs/engines/*.md | Engine-specific documentation |
docs/guide/*.md | Configuration and generated API guides |
docs/contributing/*.md | Contributing guide, AI skills, Docker deployment, best practices |
docs/contributing/adr/*.md | Architectural Decision Records |
Follow these conventions:
layout, hero, features). Use ::: containers for tips/warnings.<script setup>). Register in theme/index.ts.config.mts themeConfig.nav and themeConfig.sidebar for new pages.target: _blank.docs/public/ and reference with absolute paths.# Start dev server (with hot reload)
cd docs && npm run dev
# Build for production (catches broken links)
cd docs && npm run build
# Preview production build
cd docs && npm run preview
Do not run visual verification automatically. Use AskUserQuestion to ask the user what should be verified. Only proceed with the steps below if the user or $ARGUMENTS explicitly request visual testing.
Prerequisite: Playwright MCP must be configured in the agent's MCP settings.
cd docs && npm run dev in the background).tmp/ (gitignored). Never check screenshots into git.docs-{page}-{state}.png.tmp/ when the skill terminatesTo attach screenshots to a PR, upload them as draft release assets:
gh release create screenshots-pr-<NUMBER> --draft --title "PR #<NUMBER> Screenshots" --notes "Temporary" .tmp/*.png
gh release view screenshots-pr-<NUMBER> --json assets --jq '.assets[] | .url'
gh pr comment <NUMBER> --body ""
The draft release can be deleted after the PR is merged.
Summarize:
npm run build passed/failed)