[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70JC66NH5ZFCPGTNDWB6V7J":3,"skill-same:01M70JC66NH5ZFCPGTNDWB6V7J":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M70JC66NH5ZFCPGTNDWB6V7J","threejs-world-generation",null,"Build deterministic, editable, free-viewpoint Three.js worlds from text or structured briefs. Use for cinematic 3D terrain, semantic regions, procedural biomes, explicit landmarks, environmental scattering, camera fly-throughs, world diagnostics, or requests for a real 3D environment rather than generated 2D footage. Integrates OpenMontage's threejs_world tool with HyperFrames; do not use for a single isolated 3D object or a flat parallax scene.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fthreejs-world\u002Fthreejs-world-generation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"threejs world generation","world","generation","threejs","threejs world","environment","for","three","do","deterministic","camera","diagnostics","briefs","parallax","fly","procedural","text","free","generated","3D","2026-11-10 10:12:30",false,"---\nname: threejs-world-generation\ndescription: Build deterministic, editable, free-viewpoint Three.js worlds from text or structured briefs. Use for cinematic 3D terrain, semantic regions, procedural biomes, explicit landmarks, environmental scattering, camera fly-throughs, world diagnostics, or requests for a real 3D environment rather than generated 2D footage. Integrates OpenMontage's threejs_world tool with HyperFrames; do not use for a single isolated 3D object or a flat parallax scene.\n---\n\n# Three.js World Generation\n\nFor production meshes and Blender assembly, also read `3d-asset-generation`.\nThree.js remains the semantic interactive\u002Fblockout renderer; Blender is the\nproduction renderer when the brief calls for dense reference-grade scenery.\n\nThe production handoff must include target dimensions for imported assets,\nsemantic scatter exclusion zones, terrain-following water\u002Fpath geometry,\nlandmark visibility policy, camera clearance, and global\u002Fregional\u002Fwalk review\nframes. These are world-spec contracts, not manual Blender cleanup notes.\n\nCreate a persistent scene graph, not a sequence of unrelated 2D shots. Preserve the user's explicit constraints, infer missing construction details separately, establish the global terrain first, and refine selected regions without disturbing the world-wide spatial contract.\n\n## Choose the fidelity tier explicitly\n\n- `blockout`: procedural primitives, vertex colors, semantic\u002Flayout validation, fast iteration. Never call this production-quality, reference-grade, or visually equivalent to WorldClaw.\n- `production`: licensed local GLTF\u002FGLB catalogs, a minimum eight-model palette across four semantic categories, three PBR terrain layers, asset provenance, walk-level repetition review, and no primitive landmark fallback.\n\nFor a hero video or any reference showing populated textured environments, use `production`. If its catalog\u002Fmaterial\u002Fprovider requirements cannot be met, stop at preflight or the asset gate. Do not render a blockout as the final deliverable.\n\n## Read first\n\n- Read [references\u002Fworldclaw-principles.md](references\u002Fworldclaw-principles.md) when planning or explaining the coarse-to-fine method.\n- Read [references\u002Fworld-spec.md](references\u002Fworld-spec.md) before authoring a `world_spec` or calling `threejs_world`.\n- Read `hyperframes-core`, `hyperframes-animation`, and `hyperframes-animation\u002Fadapters\u002Fthree.md` before editing the emitted workspace.\n- Read `threejs-loaders`, `threejs-materials`, `threejs-textures`, `threejs-lighting`, and `threejs-postprocessing` for production-tier work.\n\n## Route the request\n\n- Use the `animation` pipeline for design-led, explanatory, abstract, or music-led world films.\n- Use the `cinematic` pipeline for trailer-like mood, dramatic reveals, or source-plus-world edits.\n- Choose HyperFrames when the deliverable is the code-native Three.js world. Choose Blender for reference-grade hero rendering and FFmpeg only to package Blender's numbered frames and approved audio. Record that choice at proposal; do not silently switch after approval.\n- Keep this as a capability inside existing pipelines. Do not create a new pipeline merely because a scene is 3D.\n\n## Workflow\n\n### 1. Separate intent from completion\n\nRecord two lists before planning:\n\n- `explicit_constraints`: only facts the user supplied.\n- `inferred_details`: scale, region coverage, terrain operators, densities, palette refinements, and camera details added to make the world executable.\n\nNever smuggle an inferred landmark, biome, or story beat into the explicit list.\n\n### 2. Plan globally\n\nAuthor one shared `world_spec` containing:\n\n- world scale, terrain resolution, elevation range, and seed;\n- semantic regions with normalized centers, radii, landform operators, palette, and scatter recipes;\n- atmosphere and lighting shared across all regions;\n- explicit landmarks with stable IDs and world-space placement;\n- a complete camera path with time, position, target, and field of view.\n\nPrefer 3-7 regions. Each region must contribute a distinct silhouette, surface read, or functional role.\n\n### 3. Build the terrain foundation\n\nFor production, first call `threejs_asset_catalog` to install rights-safe catalogs under `projects\u002F\u003Cid>\u002Fassets\u002F3d\u002Fcatalogs\u002F\u003Ccatalog-id>\u002F`. Record source, license, archive hash, model inventory, and every selected model in the asset manifest. Then call `threejs_world` with `quality_tier: \"production\"` and the installed catalog paths.\n\n```python\nfrom tools.graphics.threejs_world import ThreeJSWorld\n\nresult = ThreeJSWorld().execute({\n    \"operation\": \"build\",\n    \"world_spec\": world_spec,\n    \"output_path\": \"projects\u002F\u003Cid>\u002Fhyperframes\",\n    \"duration_seconds\": 60,\n    \"render_mode\": \"cinematic\",\n    \"quality_tier\": \"production\",\n    \"asset_catalog_paths\": [\"projects\u002F\u003Cid>\u002Fassets\u002F3d\u002Fcatalogs\u002Fkenney-nature-kit\"],\n})\n```\n\nTreat `world.json`, `world-spec.js`, `world-runtime.js`, and `world-report.json` as editable assets. Do not flatten them into a video until the assets gate is approved.\n\n### 4. Inspect regionally\n\nBuild a second pass with `render_mode: \"semantic\"` or `\"wireframe\"` when spatial problems are hard to see in the cinematic material pass. Inspect snapshots from global, regional, and walk-level viewpoints.\n\nMaintain an issue queue with stable subjects:\n\n- terrain transition or silhouette;\n- landmark scale, pose, or contact;\n- scatter density, slope rejection, or repetition;\n- material contrast and atmosphere;\n- camera clearance, clipping, or weak framing.\n\nFix only the affected region or object when possible. Preserve the seed, region IDs, camera times, and unrelated parameters.\n\n### 5. Refine with bounded loops\n\nRun at most three render-guided refinement rounds:\n\n1. build the workspace;\n2. run the unified HyperFrames `check` gate and snapshot representative times;\n3. inspect frames and update the issue queue;\n4. change the narrowest relevant spec fields;\n5. rebuild with the same seed and compare.\n\nStop when no substantial issue remains or the iteration budget is reached. Report residual limitations rather than disguising them with overlays.\n\n### 6. Compose without overwriting\n\nFor browser-native delivery, set `render_runtime: \"hyperframes\"` and `composition_mode: \"atelier\"`; `video_compose` must preserve the authored workspace. For reference-grade video, render a Blender PNG sequence with `resume: true`, then set `render_runtime: \"ffmpeg\"` for packaging. Preserve the world spec and `.blend` as the editable source of truth.\n\n## Quality gates\n\n- Terrain is continuous and region boundaries blend without obvious seams.\n- Every landmark touches its support surface and remains inside world bounds.\n- Scatter respects region affinity, slope limits, and deterministic seed behavior.\n- Global, regional, and walk-level frames all read as the same continuous world.\n- Camera paths remain above terrain, avoid clipping, and provide at least one scale-establishing reveal.\n- World source remains editable after render: regions, landmarks, camera keys, and palette have stable IDs or fields.\n- HyperFrames `check` and post-render review pass before delivery. Use the legacy `validate` or `inspect` operations only when supporting an older runtime.\n- Production beauty frames contain textured assets at foreground, midground, and background depths; no dominant object may read as an untextured box, cone, octahedron, or dodecahedron.\n- Production requires at least four semantic asset categories, eight distinct models, three PBR terrain layers, one regional composition review per camera-critical region, and explicit repetition\u002Fcontact findings.\n\n## Boundaries\n\n- The production catalog path materially improves geometry and surface richness, but it still does not reproduce WorldClaw's GPT-Image-2, SAM3, SAM3D, Hunyuan3D, BlenderMCP, or four-H20 implementation.\n- Do not claim articulated assets, game physics, navigation meshes, or interaction logic unless another tool explicitly adds them.\n- Do not use unseeded randomness, wall-clock animation, remote models, or render-time asset fetches.\n- Do not delete the lower-level `threejs-*` skills. They are the subsystem references used when extending this runtime.\n","# Three.js World Generation\n\nFor production meshes and Blender assembly, also read `3d-asset-generation`.\nThree.js remains the semantic interactive\u002Fblockout renderer; Blender is the\nproduction renderer when the brief calls for dense reference-grade scenery.\n\nThe production handoff must include target dimensions for imported assets,\nsemantic scatter exclusion zones, terrain-following water\u002Fpath geometry,\nlandmark visibility policy, camera clearance, and global\u002Fregional\u002Fwalk review\nframes. These are world-spec contracts, not manual Blender cleanup notes.\n\nCreate a persistent scene graph, not a sequence of unrelated 2D shots. Preserve the user's explicit constraints, infer missing construction details separately, establish the global terrain first, and refine selected regions without disturbing the world-wide spatial contract.\n\n## Choose the fidelity tier explicitly\n\n- `blockout`: procedural primitives, vertex colors, semantic\u002Flayout validation, fast iteration. Never call this production-quality, reference-grade, or visually equivalent to WorldClaw.\n- `production`: licensed local GLTF\u002FGLB catalogs, a minimum eight-model palette across four semantic categories, three PBR terrain layers, asset provenance, walk-level repetition review, and no primitive landmark fallback.\n\nFor a hero video or any reference showing populated textured environments, use `production`. If its catalog\u002Fmaterial\u002Fprovider requirements cannot be met, stop at preflight or the asset gate. Do not render a blockout as the final deliverable.\n\n## Read first\n\n- Read [references\u002Fworldclaw-principles.md](references\u002Fworldclaw-principles.md) when planning or explaining the coarse-to-fine method.\n- Read [references\u002Fworld-spec.md](references\u002Fworld-spec.md) before authoring a `world_spec` or calling `threejs_world`.\n- Read `hyperframes-core`, `hyperframes-animation`, and `hyperframes-animation\u002Fadapters\u002Fthree.md` before editing the emitted workspace.\n- Read `threejs-loaders`, `threejs-materials`, `threejs-textures`, `threejs-lighting`, and `threejs-postprocessing` for production-tier work.\n\n## Route the request\n\n- Use the `animation` pipeline for design-led, explanatory, abstract, or music-led world films.\n- Use the `cinematic` pipeline for trailer-like mood, dramatic reveals, or source-plus-world edits.\n- Choose HyperFrames when the deliverable is the code-native Three.js world. Choose Blender for reference-grade hero rendering and FFmpeg only to package Blender's numbered frames and approved audio. Record that choice at proposal; do not silently switch after approval.\n- Keep this as a capability inside existing pipelines. Do not create a new pipeline merely because a scene is 3D.\n\n## Workflow\n\n### 1. Separate intent from completion\n\nRecord two lists before planning:\n\n- `explicit_constraints`: only facts the user supplied.\n- `inferred_details`: scale, region coverage, terrain operators, densities, palette refinements, and camera details added to make the world executable.\n\nNever smuggle an inferred landmark, biome, or story beat into the explicit list.\n\n### 2. Plan globally\n\nAuthor one shared `world_spec` containing:\n\n- world scale, terrain resolution, elevation range, and seed;\n- semantic regions with normalized centers, radii, landform operators, palette, and scatter recipes;\n- atmosphere and lighting shared across all regions;\n- explicit landmarks with stable IDs and world-space placement;\n- a complete camera path with time, position, target, and field of view.\n\nPrefer 3-7 regions. Each region must contribute a distinct silhouette, surface read, or functional role.\n\n### 3. Build the terrain foundation\n\nFor production, first call `threejs_asset_catalog` to install rights-safe catalogs under `projects\u002F\u003Cid>\u002Fassets\u002F3d\u002Fcatalogs\u002F\u003Ccatalog-id>\u002F`. Record source, license, archive hash, model inventory, and every selected model in the asset manifest. Then call `threejs_world` with `quality_tier: \"production\"` and the installed catalog paths.\n\n```python\nfrom tools.graphics.threejs_world import ThreeJSWorld\n\nresult = ThreeJSWorld().execute({\n    \"operation\": \"build\",\n    \"world_spec\": world_spec,\n    \"output_path\": \"projects\u002F\u003Cid>\u002Fhyperframes\",\n    \"duration_seconds\": 60,\n    \"render_mode\": \"cinematic\",\n    \"quality_tier\": \"production\",\n    \"asset_catalog_paths\": [\"projects\u002F\u003Cid>\u002Fassets\u002F3d\u002Fcatalogs\u002Fkenney-nature-kit\"],\n})\n```\n\nTreat `world.json`, `world-spec.js`, `world-runtime.js`, and `world-report.json` as editable assets. Do not flatten them into a video until the assets gate is approved.\n\n### 4. Inspect regionally\n\nBuild a second pass with `render_mode: \"semantic\"` or `\"wireframe\"` when spatial problems are hard to see in the cinematic material pass. Inspect snapshots from global, regional, and walk-level viewpoints.\n\nMaintain an issue queue with stable subjects:\n\n- terrain transition or silhouette;\n- landmark scale, pose, or contact;\n- scatter density, slope rejection, or repetition;\n- material contrast and atmosphere;\n- camera clearance, clipping, or weak framing.\n\nFix only the affected region or object when possible. Preserve the seed, region IDs, camera times, and unrelated parameters.\n\n### 5. Refine with bounded loops\n\nRun at most three render-guided refinement rounds:\n\n1. build the workspace;\n2. run the unified HyperFrames `check` gate and snapshot representative times;\n3. inspect frames and update the issue queue;\n4. change the narrowest relevant spec fields;\n5. rebuild with the same seed and compare.\n\nStop when no substantial issue remains or the iteration budget is reached. Report residual limitations rather than disguising them with overlays.\n\n### 6. Compose without overwriting\n\nFor browser-native delivery, set `render_runtime: \"hyperframes\"` and `composition_mode: \"atelier\"`; `video_compose` must preserve the authored workspace. For reference-grade video, render a Blender PNG sequence with `resume: true`, then set `render_runtime: \"ffmpeg\"` for packaging. Preserve the world spec and `.blend` as the editable source of truth.\n\n## Quality gates\n\n- Terrain is continuous and region boundaries blend without obvious seams.\n- Every landmark touches its support surface and remains inside world bounds.\n- Scatter respects region affinity, slope limits, and deterministic seed behavior.\n- Global, regional, and walk-level frames all read as the same continuous world.\n- Camera paths remain above terrain, avoid clipping, and provide at least one scale-establishing reveal.\n- World source remains editable after render: regions, landmarks, camera keys, and palette have stable IDs or fields.\n- HyperFrames `check` and post-render review pass before delivery. Use the legacy `validate` or `inspect` operations only when supporting an older runtime.\n- Production beauty frames contain textured assets at foreground, midground, and background depths; no dominant object may read as an untextured box, cone, octahedron, or dodecahedron.\n- Production requires at least four semantic asset categories, eight distinct models, three PBR terrain layers, one regional composition review per camera-critical region, and explicit repetition\u002Fcontact findings.\n\n## Boundaries\n\n- The production catalog path materially improves geometry and surface richness, but it still does not reproduce WorldClaw's GPT-Image-2, SAM3, SAM3D, Hunyuan3D, BlenderMCP, or four-H20 implementation.\n- Do not claim articulated assets, game physics, navigation meshes, or interaction logic unless another tool explicitly adds them.\n- Do not use unseeded randomness, wall-clock animation, remote models, or render-time asset fetches.\n- Do not delete the lower-level `threejs-*` skills. They are the subsystem references used when extending this runtime.\n",{"name":5,"description":7},"main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Fmy_skills\u002Fthreejs-world\u002Fthreejs-world-generation",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill threejs-world-generation",{"tool":63,"command":64},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill threejs-world-generation",{"tool":66,"command":67},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill threejs-world-generation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fthreejs-world\u002Fthreejs-world-generation\u002FSKILL.md",true,[71,77],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fworld-spec.md","REFERENCE","参考文档",4599,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fthreejs-world\u002Fthreejs-world-generation\u002Freferences\u002Fworld-spec.md",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fworldclaw-principles.md",3029,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fthreejs-world\u002Fthreejs-world-generation\u002Freferences\u002Fworldclaw-principles.md",[82,90,98,105,112,119],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":97},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":97},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":97},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":97},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":97},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]