菜单
Scaffold a new Tailor content extension - content element (ce), content container (cc), meta input (mi), or plugin (pl) - and wire it into the registry. Use when adding a new ce/cc/mi/pl extension to the platform.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Draft a high-quality GitHub bug report from a QA observation - dedup, fill the bug_report form fields. DRAFT ONLY: it never files the issue; it hands you a ready `gh issue create` command to run yourself. Use when QA finds a defect to report.
Draft a GitHub proposal (feature / enhancement / task) - dedup, classify the type, fill the proposal form fields. DRAFT ONLY: it never files the issue; it hands you a ready `gh issue create` command to run yourself. Use when proposing new capability, an improvement, or a unit of work (not a defect - that's /report-bug).
Draft a clear, reviewer-ready pull request description for the current branch (or an existing PR) - feature-first summary, motivation, test plan, linked issues - verified against the real diff. DRAFT ONLY: it never creates, edits, or pushes; it hands you a ready `gh pr create`/`gh pr edit` command to run yourself. Use when writing up a PR.
Scaffold a new backend HTTP endpoint / vertical slice in apps/backend (Zod schema + defineAction + service + mounter) following the slice conventions. Use when adding a backend endpoint, action, or resource.
Scaffold a Playwright Page Object plus a functional spec in tests/, following the POM conventions. Use when adding an end-to-end test for a feature or flow.
Turn a bug (GitHub issue number or description) into a failing Playwright spec that reproduces it - POM-based, tagged @bug, linked to the issue, and marked test.fail() so CI stays green until a fix flips it red. Use to capture a known bug as a regression-first test.
| name | scaffold-extension |
| description | Scaffold a new Tailor content extension - content element (ce), content container (cc), meta input (mi), or plugin (pl) - and wire it into the registry. Use when adding a new ce/cc/mi/pl extension to the platform. |
Tailor has four extension types. Packages live in
packages/core-extensions/<type>/<name>/ and are aggregated into the app
by the registries in extensions/<type>/{client,server}.js.
Pick the type and read the matching guide in
docs/dev/extensions/ (content-elements, content-containers,
meta-inputs, plugins).
Create the package source. There is no source generator - mirror an
existing sibling package under packages/core-extensions/<type>/<name>/
(each ships an edit/client side and a server side). The CLI in step 4
only registers and installs a package that already exists; it does not
write its source.
Respect naming. Packages are prefixed @tailor-cms/ce-* (elements),
@tailor-cms/tcc-* (containers), @tailor-cms/tp-* (plugins). Each
ships an edit/client side and a server side.
Register + wire it via the CLI - do NOT hand-edit the registry.
extensions/<type>/{client,server}.js, types.js, and enum.ts are
GENERATED from extensions/<type>/registry.json; hand-edits get
overwritten. The installer is interactive (inquirer), so ask the user to
run it via the ! prefix:
pnpm ce addpnpm cc addpnpm mi addpnpm pl add
add (aliases i/install) appends the entry to registry.json, runs
pnpm add for the client (and server) package, then regenerates those
export modules. If you edit registry.json directly, run
pnpm <type> rebuild to regenerate.Follow FE conventions (see apps/frontend/CLAUDE.md): dumb
components + composables, is/has boolean props, ns:action events,
decompose into focused subcomponents.
Verify. pnpm build, then pnpm dev and confirm the extension
appears and persists. For library/API questions use the context7 MCP.