菜单
Scaffold a new plugin in the toolchest marketplace. Creates plugins/<name>/ with .claude-plugin/plugin.json, README.md, and skills/<skill>/SKILL.md, then patches the root marketplace.json and the root README plugin table. Use when the user asks to add, scaffold, or create a new plugin.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Documentation router for Dioxus, the Rust framework for cross-platform (web/desktop/mobile) apps in one codebase. Use whenever the user works with Dioxus — writing `rsx!` markup, components (`#[component]`), signals and hooks (`use_signal`, `use_resource`, `use_memo`, `use_context`, `use_effect`), the router, fullstack / server functions (`#[server]`), assets (the `asset!` macro), or the `dx` CLI (`dx new`, `dx serve`, `dx bundle`, `dx doctor`). Also trigger on Dioxus setup, styling, or deployment questions, a `Cargo.toml` with a `dioxus` dependency, `.rs` files importing `dioxus::prelude::*`, migrating to 0.7, or any "how do I <X> in Dioxus" question. This skill does not bundle the docs — it routes to the smallest fetchable source (per-page markdown, a section `llms.txt`, or docs.rs) and carries an inline Dioxus 0.7 gotchas cheat-sheet.
Create or update the BRAND.md the writer's room writes to — by discovering an existing brand identity in the project (voice docs, published content, site copy), by importing a brand/voice document the user maintains elsewhere, by interviewing the user, or by refreshing the current file. Covers voice, audience, tone-by-context, vocabulary, no-go topics, on/off-voice example pairs, mechanics, and SEO/channels. Invoked on its own or by /writers-room:convene when no BRAND.md is found.
Convene the writer's room — hand off a topic and get back a finished, on-brand piece (article, blog post, or site copy). Runs a short upfront clarification interview, then hands the topic and answers to the showrunner agent, which spawns the room and writes the piece. Checks for a BRAND.md first and helps create one if it's missing. The room does the writing — this skill only interviews and hands off.
Verify that plugins/, .claude-plugin/marketplace.json, and the root README plugin table are all in sync. Reports any plugin that appears in one or two of those places but not all three. Use when the user asks to check, audit, or verify the marketplace state.
DESIGN.md format specification from Google Labs — a self-contained plain-text representation of a design system that keeps visual identity consistent across design sessions and between AI agents and tools. A DESIGN.md file has two parts: YAML frontmatter holding typed design tokens (colors, typography, spacing, rounded scale, components) plus a markdown body with design rationale and guidance. Tokens follow the Design Token JSON spec with {path.to.token} cross-references and convert cleanly to/from tokens.json, Figma variables, and Tailwind CSS — primary target is Tailwind v4 @theme CSS directives, with legacy v3 tailwind.config.js as fallback. Use when working with DESIGN.md files, defining or editing design tokens, generating a DESIGN.md from scratch, converting tokens to/from tokens.json / Figma / Tailwind v4 @theme / Tailwind v3 config, interpreting another agent's DESIGN.md, or answering questions about the DESIGN.md format.
Use when an agent needs to run sudo or another privileged Linux command from a non-interactive shell, especially after errors like "sudo: a terminal is required", "sudo: no askpass program specified", "sudo: no password was provided", or when sudo prompts cannot appear in the current harness. Helps detect installed askpass helpers, configure SUDO_ASKPASS, use sudo -A safely, avoid authentication lockouts, and ask the user for minimal manual setup when needed.
| name | scaffold-plugin |
| description | Scaffold a new plugin in the toolchest marketplace. Creates plugins/<name>/ with .claude-plugin/plugin.json, README.md, and skills/<skill>/SKILL.md, then patches the root marketplace.json and the root README plugin table. Use when the user asks to add, scaffold, or create a new plugin. |
| argument-hint | <plugin-name> [first-skill-name] |
| disable-model-invocation | true |
| allowed-tools | Read, Write, Edit, Bash, AskUserQuestion |
Add a new plugin to this marketplace, keeping the three sources of truth in sync.
$1 — plugin name (kebab-case, required). Becomes the directory name and the name field everywhere.$2 — first skill name (optional, kebab-case). Defaults to the plugin name.If $1 is missing, ask the user. Do not invent a name.
Gather these from the user in a single AskUserQuestion call (don't echo back the plugin name — ask only what you don't have):
plugin.json, marketplace.json, and the root README row.Then propose the full file plan in chat before writing — list every file you'll create and every file you'll modify with a one-line summary. Wait for approval.
This template scaffolds a skill-based plugin. Two other shapes exist; the three-place sync and metadata conventions below apply unchanged to all of them.
ty-lsp): skip skills/<skill>/SKILL.md and the first-skill questions entirely, and instead create .lsp.json at the plugin root (server-name → {command, args, extensionToLanguage}); the root README table's Skill column gets —.writers-room): add agents/<agent>.md files at the plugin root, one per agent — frontmatter needs name and description; tools is optional (note: agents use tools, skills use allowed-tools). Agents are auto-discovered (no plugin.json field) and register as <plugin>:<agent>. If one agent spawns siblings, its Agent(...) allowlist must use the namespaced form — Agent(<plugin>:<agent>, …); bare names break delegation silently. Adding or renaming an agent means updating every sibling allowlist that names it. A skill that needs the user (interview, confirmation gates) stays main-thread — subagents have no AskUserQuestion.Create:
plugins/<plugin>/.claude-plugin/plugin.jsonplugins/<plugin>/README.mdplugins/<plugin>/skills/<skill>/SKILL.mdModify:
.claude-plugin/marketplace.json — append plugin entry to plugins[]README.md — append row to "Available Plugins" tableBase every field on existing files. The owner string is arimxyer and the license is Apache-2.0 — do not substitute the local git user.
plugins/<plugin>/.claude-plugin/plugin.json{
"name": "<plugin>",
"description": "<one-line description>",
"version": "1.0.0",
"author": {
"name": "arimxyer"
},
"repository": "https://github.com/arimxyer/toolchest",
"license": "Apache-2.0"
}
plugins/<plugin>/README.mdMinimal — mirror the structure of plugins/sudo-askpass/README.md:
# <Title-Case Plugin Name>
<One-paragraph description of what the plugin does.>
## What It Does
- <bullet>
- <bullet>
## Usage
It can also be invoked directly:
```text
/<plugin>:<skill> <args>
### `plugins/<plugin>/skills/<skill>/SKILL.md`
```markdown
---
name: <skill>
description: <one-line skill description>
---
# <skill>
<Body of the skill — what it does and when to use it.>
Leave optional frontmatter (argument-hint, allowed-tools, metadata) off the starter SKILL.md. Frontmatter style varies across this repo's plugins; the user can add fields when the skill's shape is clear.
If a skill ships supporting files (templates, examples), put them in skills/<skill>/references/ next to that skill — not at the plugin root (see writers-room's MEMO.template.md / BRAND.template.md).
.claude-plugin/marketplace.jsonAppend to the plugins array, matching the existing object shape exactly:
{
"name": "<plugin>",
"source": "./plugins/<plugin>",
"description": "<one-line description>",
"version": "1.0.0",
"author": {
"name": "arimxyer"
},
"license": "Apache-2.0"
}
Use the Edit tool with a unique anchor (e.g., the closing ] of plugins[] plus the preceding }) to insert. After editing, verify by reading the file back. The prettier hook will reformat it on save — that's expected.
README.mdAppend a row to the "Available Plugins" table. Match the existing column order: | <plugin> | /<plugin>:<skill> | <description> |.
After writing all files, run:
jq -e . .claude-plugin/marketplace.json > /dev/null
jq -e . plugins/<plugin>/.claude-plugin/plugin.json > /dev/null
Both should exit 0. Then list what was created and ask the user to review.
/check-marketplace-sync automatically; offer it as a follow-up if useful.