Cindy Plugin Creator

Build a Cindy plugin from the user's request, or update an existing plugin. This Skill and its references are the authoring documentation shipped with the current Cindy host. Use these contracts instead of guessing APIs from a different release. Keep the user's language for discussion.

Workflow

1. Read the authoring overview, design alignment, structure, and manifest and capabilities. For an existing plugin, inspect its ghost.json and source first. Ask only about decisions the request leaves open; use option cards when available. Summarize the intended behavior, UI, permissions and acceptance criteria before implementation, following the design reference.
2. Before writing code, read the sandbox boundaries and packaging workflow. Read the capability references below as needed; do not load the whole manual at once.
3. For a new plugin, prefer ghost_forge_scaffold with the appropriate plain, agent-action, node-json-rpc or node-mcp template, then edit the generated files. For an existing plugin, preserve its identity, data and compatible behavior. Use schemaVersion: 3 for new manifests and declare the first stable Cindy version actually required.
4. Implement and validate the requested behavior, including Light and Dark modes for any UI. Separate current Agent tool-call operations from autonomous plugin capabilities, as described in the manifest and Agent-call references. Use tool discovery and manuals for authoring the plugin's own discovery and workflow documentation.
5. Call ghost_forge_pack to validate and produce the .cindy artifact. Report what was tested and what remains unverified. Packaging does not install or publish: use ghost_forge_install only when installation is requested, and follow publishing when publication is requested.

Cindy supplies the Forge tools. If they are unavailable in the current environment, explain the missing capability and continue any local source work that is possible; do not claim to have packaged, installed or published. The legacy ghost_forge_guide tool serves these same references by section number or title when needed. It is a compatibility entry point, not a second source of documentation.

Reference index

These references describe Cindy plugin contracts and host APIs available to plugins. Read only the topics needed for the plugin being built. Existing section numbers are preserved for ghost_forge_guide callers and cross-references; files are named by plugin capability rather than reading order.

插件基础与工具设计

Start here to define the plugin's behavior, package and Agent-facing tools.

• 插件创作总览
• 插件需求与交互设计（§0）
• 插件源码与包目录结构（§1）
• 插件身份卡与能力声明 ghost.json（§2）
• 插件工具定义 tools（§3）
• 插件工具发现与两段式目录（§3.5）
• 插件使用手册 manual（§3.6）

插件运行与宿主接口

Use when implementing plugin code, calling host APIs or declaring access to resources.

• 插件后台 main.js 与基础模型调用（§4）
• 插件沙箱边界（§6）
• 插件读取宿主公开上下文（§4.1）
• 插件处理 Agent 在途调用：网络与工作目录（§4.2）
• 插件读取可用 Agent 模型列表（§4.0.3a）
• 插件接入媒体模型与生成结果（§4.0.4）
• 插件联网与凭证代发 network（§4.7）
• 插件文件操作与持久作品库 fs / library（§4.10）
• 插件随包 Node 工作进程、CLI 与 stdio MCP（§4.12）

插件界面与用户交互

Use for the UI surfaces and interactions the plugin actually exposes; mobile pages are optional.

• 插件面板与主题适配（§5）
• 插件一级主视图 mainView（§4.20）
• 插件移动端页面接入与操作来源（§5.1）
• 插件聊天卡片 card（§4.5）
• 插件设置页与自定义参数 settingsHtml / kv（§4.8）
• 插件轻提示与未读角标 notify / badge（§4.9）
• 插件目录选择 pick（§4.14）
• 插件面板预览 preview（§4.15）
• 插件确认弹窗 confirm（§4.18）
• 插件推荐任务（§4.21）

插件事件与任务协作

Use when the plugin listens for events, supplies routine triggers or interacts with Agent tasks.

• 插件提交例行任务事件 routineEvents
• 插件事件订阅 subscribe（§4.6）
• 插件处理 Agent 回复的消息钩子（§4.6.1）
• 插件发起 Agent 任务与请求自动化（§4.11）
• 插件读取当前任务上下文 sessionContext（§4.13）
• 插件创建工作区任务入口 workspace（§4.17）

插件打包、发布与兼容

Read packaging before implementation and delivery. Read publishing only for publication, and bundled Skills only when maintaining an older plugin.

• 插件打包、安装与验证（§7）
• 插件发布签名与审核（§8）
• 插件版本兼容与拒装排查（§9）
• 旧插件捆绑 Skill 的维护与迁移（§4.16）