cesartevisual/threejs-skills

threejs-deployment

Prepare and verify Three.js web builds, asset hosting, decoder paths, caching, and deployment compatibility.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/cesartevisual/threejs-skills --skill threejs-deployment

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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.

같은 저장소의 Skills

더 많은 Skills

모든 Skills