使用方法
- 复制安装命令,在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/cesartevisual/threejs-skills --skill threejs-deployment开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Build and Delivery
Use the project's installed versions and existing architecture. These instructions supplement the user's task; they do not authorize unrelated changes or external actions.
Inspect the existing build tool, hosting target, base path, browser requirements, and deployment authorization. Preserve project conventions. Prepare and validate the build even when publishing requires a later authorized step.
Keep Three.js and addons on a compatible revision and deduplicate conflicting instances. Verify peer dependencies before upgrades. Include only required loaders/helpers and lazy-load heavy optional paths when useful. Inspect the output rather than assuming tree-shaking removed unused code.
Resolve model, texture, decoder, worker, and WASM URLs through build-aware paths. Test the actual nested base path and direct navigation to application routes. Serve the right MIME types; verify asset responses are not HTML fallbacks.
Set CORS for legitimately cross-origin assets and CSP directives needed by the chosen worker/decoder setup. Require secure contexts for features that need them. Add cross-origin isolation only when the actual threaded/runtime feature requires it; account for third-party resource implications.
Use immutable caching for content-hashed assets and a coherent update strategy for HTML and manifests. Avoid stale service workers pairing new code with old decoders. Handle offline/error states according to product requirements.
Run a production preview and check representative assets, cache behavior, load failures, fallback devices, and route reloads. Publish only within existing authorization and report the deployed URL only after verifying it.
API reference
Consult the official documentation for exact signatures and revision-specific behavior. If documentation access is unavailable, inspect installed types/source and state any remaining uncertainty.
