{"id":53917,"plugin_id":"plugins_6ac8b869e5308191bb06de77c7389543","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:55:19.823Z","digest":"11da2b8fb034ad07e2ea5b463d605796577c30fc82712bcf4a5bacc854431c73","against":null,"payload":{"description":"Plan a maintainable web architecture for persistent 3D scenes, page content, assets, and graceful rendering fallbacks.","included_files":[],"name":"3d-scene-architecture","skill_md_contents":"---\nname: 3d-scene-architecture\ndescription: Plan a maintainable web architecture for persistent 3D scenes, page content, assets, and graceful rendering fallbacks.\n---\n\n# 3D Scene Architecture\n\nUse when designing the technical structure for a 3D website or turning a visual brief into an implementation-ready architecture.\n\n## Process\n\n1. Inspect the existing repository and preserve its framework, package manager, routing, styling, deployment runtime, and test conventions unless the user asks for a migration.\n2. Separate semantic routes and content from the renderer, scene registry, camera/animation state, assets, and any server-side preview services. Keep text and essential controls in accessible DOM layers.\n3. Recommend a persistent renderer and coordinated camera across sections when the experience benefits from a continuous journey. Use independently loaded scene groups or route-specific scenes where they reduce complexity. Do not require one canvas if the current stack or page behavior makes that unsuitable.\n4. Select technologies based on project fit. React Three Fiber/Three.js, a server-rendered React framework, an animation library, and typed state can be useful options, not mandatory requirements. Avoid adding multiple overlapping animation or state systems without a clear need.\n5. Define asset loading, compression, texture sizes, material reuse, level of detail, instancing, disposal, visibility pausing, and device-aware rendering. Make loading progress truthful and errors recoverable.\n6. Keep public data distinct from secrets. Put service credentials server-side, validate user-supplied URLs, and do not expose tokens or private project data in client bundles.\n7. Include route-level rendering behavior, direct deep links, refresh behavior, error boundaries, and a complete semantic 2D fallback for unsupported WebGL, failed assets, or constrained devices.\n\n## Output\n\nReturn the project fit and stack rationale, component/scene boundaries, state/data flow, asset strategy, loading/error behavior, and testing requirements. Label unverified runtime or provider assumptions.\n\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}