メニュー
Configure Cursor with the /build command from rpw-published. Use when setting up Cursor to use the build workflow, or when the user asks to add/configure the build command in Cursor.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | configure-cursor-build |
| description | Configure Cursor with the /build command from rpw-published. Use when setting up Cursor to use the build workflow, or when the user asks to add/configure the build command in Cursor. |
Helps configure Cursor so the /build command is available. The build command lives in plugins/rpw-published/commands/ and provides the full lifecycle development orchestrator workflow.
build.md supports two request patterns:
/build <request> -> full planning workflow with explicit approvals./build without planning: <request> (or /build --without-planning <request>) -> condensed planning + single go/no-go approval before implementation.Cursor keeps a safety confirmation step even for "without planning" requests.
Cursor does not yet natively support the same plugin command hooks as Claude Code. Configuration requires manual steps.
Locate the build command source
plugins/rpw-published/commands/build.md (unified command)Create or update Cursor commands
~/.cursor/commands/build.md so Cursor can find itmake link-cursor links build.md into ~/.cursor/commands/Verify
make check-links to confirm the symlink status/build in CursorIf user has existing build from elsewhere
make unlink first to remove old linksmake link-cursor| Command | Purpose |
|---|---|
make link-cursor | Link build.md into ~/.cursor/commands |
make unlink | Remove links from ~/.cursor/commands |
make check-links | Verify symlink status |
make check | Run project gate (alias for make verify) |
make adopt-cursor | Backup existing files, then link |
Ideally Cursor will directly support the same plugin/hook mechanism the build command uses. When that happens, this skill can be simplified to: "Install the rpw-published plugin; Cursor will load the build command automatically."
/build from the rpw-published plugin when the marketplace is installed. No symlink needed.Use when drafting release notes or a changelog for this marketplace — "draft the release notes", "what changed since the last release", "write the changelog", "generate the release-log entry". Mines squash-merged PR titles/bodies + linked issues between the last v-tag and HEAD and renders the docs/release-log.md entry plus a PR/release description, shaped to this repo's calendar-first release flow (ADR-001).
House conventions for reviewing a diff/PR and preparing a PR for merge in this repo. Use when the user says "prep this PR", "review this diff", "review this PR", "ready to merge?", "is this mergeable?", or before opening/landing a PR. Carries the repo-specific review checklist and PR-body shape; defers review *mechanics* to the built-in /code-review, /review, and /security-review commands.
Build and deploy Databricks Apps using the bash-over-REST starter template. Use when scaffolding, configuring, deploying, or iterating on Databricks Apps with Lakebase connectivity.
Define, deploy, run, and debug Databricks Jobs the house way — DABs-defined (never UI-created), profile-based auth only (no PATs), with CLI log reading for the local-repro debugging loop. Use when creating or editing a Databricks job, wiring a job into a Databricks Asset Bundle (`databricks.yml`), scheduling a notebook/Python/dbt task, running a job from the CLI, or debugging a failed job run (reading run output, task logs, or `run-now` results).
Create, configure, and query Databricks Model Serving endpoints, and route every in-code LLM call through Model Serving (the `ChatDatabricks` / Model-Serving-first convention) instead of a provider SDK. Use when creating or configuring a serving endpoint, querying an endpoint, choosing how Python code should call an LLM, wiring auth passthrough for a deployed agent, or debugging the ambiguous-host-profile crash (`Use --profile to specify which profile to use` / `401 Credential was not sent`).
Classify Databricks Unity Catalog (UC) connections as MCP-native vs HTTP-proxy and pick the right one for a given MCP server. Use when wiring a UC connection into an MCP server, creating a new MCP server that needs Databricks auth, troubleshooting "Session terminated" or 32600 errors from `uc-mcp-proxy`, or deciding which UC connection name to point at on a workspace where multiple connections target the same upstream service.