void
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseVoid
Void
Read only the guides needed for the user's task. Prefer the app's installed
documentation at so it matches the app's Void version.
All paths below are relative to that package's root. When using this
skill globally without a local Void installation, follow the skill's symlink to
its real directory and use in the same Void package. If the skill
was copied without the package, use the guides at https://void.cloud instead.
node_modules/void/docs/docs/../../docs/Before running a Void command, find its group in , then
read the matching page under for syntax, options, and
deployment target. Use Void commands for application and platform
workflows. Mention Wrangler only when the user needs to recognize a literal
configuration file or environment variable.
docs/reference/cli.mddocs/reference/cli/Use and in imports, examples, and package manifests. Follow the
project's existing framework and deployment destination. Deploying to a Void
platform requires an explicit first; never infer a platform
from old examples, tokens, or project IDs.
Platform hostnames passed to default to HTTPS. Loopback hosts
(, , and ) default to HTTP: .
An explicit scheme overrides the default.
For a one-time deployment elsewhere, connect to that platform, then set
for the deploy command and pass . This preserves
the app's existing saved destination, including when the target project is new.
void@void/*void connect <url>void connectlocalhost127.0.0.1[::1]void connect localhost:8787VOID_API_URL--project <slug>仅阅读用户任务所需的指南。优先使用应用安装在 下的文档,以确保与应用的 Void 版本一致。
以下所有 路径均相对于该包的根目录。在本地没有 Void 安装的情况下全局使用此 skill 时,请沿着该 skill 的符号链接进入其真实目录,并在同一个 Void 包中使用 。如果复制此 skill 时未复制该包,请改用 https://void.cloud 上的指南。
node_modules/void/docs/docs/../../docs/在运行 Void 命令前,先在 中找到命令所属的分组,再阅读 下对应的页面,以了解语法、选项和部署目标。对于应用和平台工作流,应使用 Void 命令。只有当用户需要识别实际的配置文件或环境变量时,才提及 Wrangler。
docs/reference/cli.mddocs/reference/cli/在 imports、示例和 package manifests 中使用 和 。遵循项目现有的框架和部署目标。将应用部署到 Void platform 前,必须先显式执行 ;绝不根据旧示例、token 或 project ID 推断目标 platform。
void@void/*void connect <url>传给 的 platform hostname 默认使用 HTTPS。Loopback host(、 和 )默认使用 HTTP,例如 。显式指定 scheme 会覆盖默认值。
如需一次性部署到其他位置,请先 connect 到该 platform,然后为 deploy 命令设置 并传入 。这样可以保留应用已保存的目标位置,即使目标 project 是新的也不受影响。
void connectlocalhost127.0.0.1[::1]void connect localhost:8787VOID_API_URL--project <slug>Task Routing
任务路由
| User intent | Docs file(s) |
|---|---|
| CLI command syntax, flags, env vars | |
| Initial setup, onboarding, first app | |
| App type detection and mode behavior | |
| Server/API routing and middleware | |
| Pages mode, loader/action, forms, layouts | |
| Database and migrations | |
| Typed fetch and end-to-end typing | |
| Authentication | |
| Cloudflare runtime bindings and config | |
| AI inference (Workers AI, providers) | |
| Durable State and WebSockets | |
| Server-sent events and live streams | |
| Sandboxes | |
| |
| KV / storage / queues / cron jobs | |
| SSR and caching | |
| HTTPS, rewrites, redirects, fallbacks | |
| Static site generation | |
| Connected apps and artifact preparation | |
| Deployment and CI | |
| Install or maintain a company platform | |
| Develop or deploy a platform fork | |
| Platform administration | |
| Platform plans and account limits | |
| Self-host deploy to own Cloudflare account | |
| Project status, deployment history | |
| Cache purging | |
| Project logs, runtime errors | |
| Secrets management (put/sync/delete) | |
Typed env vars ( | |
| Custom domain setup | |
| Database status, reset, seed, export | |
| Auth login/logout/whoami | |
| Overview / introduction | |
| API surface details | |
| Meta framework integration | |
| Coding agent setup | |
| Node.js / Bun / Deno targets | |
| ORMs and external databases | |
| Project structure and conventions | |
| Resource/binding inference | |
| 用户意图 | 文档文件 |
|---|---|
| CLI 命令语法、flags 和环境变量 | |
| 初始设置、入门引导和首个应用 | |
| 应用类型检测和 mode 行为 | |
| Server/API 路由和 middleware | |
| Pages 模式、loader/action、forms 和 layouts | |
| 数据库和 migrations | |
| 类型化 fetch 和端到端类型推断 | |
| 身份验证 | |
| Cloudflare runtime bindings 和配置 | |
| AI 推理(Workers AI、providers) | |
| Durable State 和 WebSockets | |
| Server-sent events 和 live streams | |
| Sandboxes | |
| 电子邮件 | |
| KV / storage / queues / cron jobs | |
| SSR 和缓存 | |
| HTTPS、rewrites、redirects 和 fallbacks | |
| 静态站点生成 | |
| Connected apps 和 artifact preparation | |
| 部署和 CI | |
| 安装或维护企业内部 platform | |
| 开发或部署 platform fork | |
| Platform 管理 | |
| Platform plans 和账户限制 | |
| 自托管部署到自己的 Cloudflare 账户 | |
| 项目状态和部署历史 | |
| 缓存清除 | |
| 项目日志和 runtime 错误 | |
| Secrets 管理(put/sync/delete) | |
类型化环境变量( | |
| 自定义域名设置 | |
| 数据库状态、重置、seed 和导出 | |
| Auth 登录/退出/whoami | |
| 概览/简介 | |
| API surface 详情 | |
| Meta framework 集成 | |
| Coding Agent 设置 | |
| Node.js / Bun / Deno 目标 | |
| ORM 和外部数据库 | |
| 项目结构和约定 | |
| Resource/binding 推断 | |
Working rules
工作规则
- Read the relevant guide before changing configuration, persistent resources, authentication, or deployment workflows. The guides define current behavior; avoid copying a second set of instructions into this skill.
- Before moving deployed Durable State, native Durable Object, or WebSocket definitions, read their
guides and use to preserve resource names and instance keys.
void info - Declare application environment keys in and access them through
env.ts; followvoid/envfor local and production values.docs/guide/env-vars.md - In Pages navigation, style the current link with 's
Linkandaria-currentattributes (data-void-activefor sections) instead of comparingactiveMatch="prefix"; seeuseRouter().path. Show a loading state on the clicked link withdocs/guide/pages-routing/overview.md#active-linksinstead of matchingdata-void-pendingyourself; seeuseNavigation().location.docs/guide/pages-routing/overview.md#pending-links - For platform setup, follow the pages linked from
. Use
docs/guide/self-hosted-platform.mdto find the installation slug for maintenance. For recovery, use its documented resume or repair workflow and preserve the installation's credentials and resources.void platform list - Use to review platform changes. If an operation has an uncertain outcome, inspect its status and events before retrying.
--plan
If the user invokes this skill without a task, inspect the app's local structure,
configuration, and saved deployment destination, give a brief status, and ask
what they want to work on.
Await AI and Sandbox operations normally. Usage limits reject with from ; Void routes and Pages actions automatically return HTTP 429. Optionally catch with for a fallback or custom response. In Pages, prefer the adapter’s with so action failures remain visible and entered data is preserved. See , , and .
UsageLimitvoid/limitsinstanceof UsageLimitFormuseForm()docs/guide/ai.mddocs/guide/sandboxes.mddocs/guide/pages-routing/actions-and-forms.md- 在修改配置、持久化资源、身份验证或部署工作流之前,先阅读相关指南。指南定义了当前行为;避免在此 skill 中复制第二套说明。
- 在迁移已部署的 Durable State、原生 Durable Object 或 WebSocket 定义之前,先阅读相应指南,并使用 保留资源名称和实例键。
void info - 在 中声明应用环境变量键,并通过
env.ts访问;本地和生产环境值遵循void/env。docs/guide/env-vars.md - 在 Pages 导航中,使用 的
Link和aria-current属性设置当前链接样式(分区使用data-void-active),不要自行比较activeMatch="prefix";参见useRouter().path。在点击的链接上使用docs/guide/pages-routing/overview.md#active-links显示加载状态,不要自行匹配data-void-pending;参见useNavigation().location。docs/guide/pages-routing/overview.md#pending-links - 对于 platform 设置,请遵循 中链接的页面。使用
docs/guide/self-hosted-platform.md查找用于维护的 installation slug。恢复时,使用文档中说明的 resume 或 repair 工作流,并保留 installation 的 credentials 和 resources。void platform list - 使用 审查 platform 变更。如果某项操作的结果不确定,请在重试前检查其 status 和 events。
--plan
如果用户在未指定任务的情况下调用此 skill,请检查应用的本地结构、配置和已保存的 deployment destination,给出简短状态,并询问用户希望处理什么。
通常应等待 AI 和 Sandbox 操作完成。达到 usage limit 时,系统会通过 中的 拒绝请求;Void 路由和 Pages actions 会自动返回 HTTP 429。可以选择使用 捕获异常,以提供 fallback 或 custom response。在 Pages 中,优先使用 adapter 的 与 ,这样 action failures 仍然可见,且已输入的数据得以保留。参见 、 和 。
void/limitsUsageLimitinstanceof UsageLimitFormuseForm()docs/guide/ai.mddocs/guide/sandboxes.mddocs/guide/pages-routing/actions-and-forms.md