[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EM60441B3DX9T415V03HT6":3,"skill-same:01M7EM60441B3DX9T415V03HT6":47},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EM60441B3DX9T415V03HT6","3d-designer",null,"Create 3D visuals with modeling, texturing, lighting, rendering, and optimization for web and product.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-3d-designer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: 3d-designer\ndescription: Create 3D visuals with modeling, texturing, lighting, rendering, and optimization for web and product.\ncategory: creative-design\n---\n\n## Overview\n\n3D design has moved from specialist VFX into everyday product work: marketing renders, product\nvisualizations, AR assets, and web experiences. This skill covers the practical 3D pipeline —\nmodeling, UVs\u002Ftexturing, lighting, rendering — plus the optimization discipline needed for real-time\nand web delivery, where polygon budgets and load times rule.\n\n## When to use\n\n- Creating product renders or marketing visuals\n\n- Building 3D assets for web (WebGL) or AR\n\n- Designing 3D illustrations or abstract brand art\n\n- Preparing models for 3D printing or manufacturing viz\n\n- Optimizing 3D assets for performance\n\n## Core concepts\n\n- - **The pipeline.** Model → UV unwrap → texture\u002Fmaterial → light → render. Each stage builds on\n  the last; skipping UVs or lighting and hoping the render saves you never works.\n- - **Topology matters.** Clean quad-based topology with good edge flow deforms well (for animation)\n  and subdivides cleanly. Triangles and n-gons are fine for static hard-surface work, poison for\n  organic deformation.\n- - **PBR materials.** Physically-based rendering: albedo, roughness, metalness, normal maps.\n  Understand what each map does — 90% of \"why does this look fake\" is wrong roughness\u002Fmetalness\n  values.\n- - **Lighting is everything.** Three-point lighting fundamentals, HDRI environments for realism,\n  and the truth that great lighting saves mediocre models while bad lighting kills great ones. Study\n  real-world light behavior.\n- - **Composition and camera.** 3D scenes follow photographic rules: focal length choices (wide =\n  dramatic, long = compressed), rule of thirds, depth of field for focus. Render like a\n  photographer, not a technician.\n- - **Optimization for delivery.** Web\u002FAR assets need: low poly counts, baked textures, efficient\n  materials, Draco\u002Fmeshopt compression, and LODs. A 50MB model is a failed web asset regardless of\n  beauty.\n\n## Practical workflow\n\n1. 1. **Define the output.** Still render? Turntable? Real-time web? AR? Print? The deliverable\n   determines the entire pipeline (a web asset and a billboard render are different projects).\n2. 2. **Block out first.** Rough primitive shapes establishing proportions and composition. Get the\n   silhouette and camera right before any detail — 80% of a model's read is silhouette.\n3. 3. **Model with intent.** Hard-surface: bevels catch highlights (never leave razor-sharp CG edges\n   — real objects have micro-bevels). Organic: clean topology, reference anatomy. Keep poly counts\n   appropriate to the output.\n4. 4. **UV and texture.** Unwrap with minimal stretching, pack efficiently, paint or source PBR\n   textures. For stylized work: define the material language (flat colors? gradients? toon shading?)\n   and stay consistent.\n5. 5. **Light the scene.** Key light (direction + mood), fill (soften shadows), rim (separation from\n   background), environment (HDRI for reflections\u002Fambient). Iterate lighting before final materials\n   tweaks.\n6. 6. **Render and post.** Appropriate samples (kill noise without wasting hours), render passes if\n   compositing, then color grade: contrast, color balance, vignette. Post-production is where\n   renders get their final 20%.\n7. 7. **Optimize for the target.** Decimate\u002Fretopologize for real-time, bake high-poly detail to\n   normal maps, compress textures (KTX2\u002FBasis for web), test load time and frame rate on target\n   devices.\n\n## Common pitfalls\n\n- - **No bevels.** Razor-sharp edges scream \"CG.\" Real-world edges catch light — micro-bevels are\n  the cheapest realism upgrade.\n- - **Bad lighting.** Flat, single-source, or default lighting. Spend half your time on lighting;\n  it's the highest-leverage stage.\n- - **Texture stretching and seams.** Visible UV seams and stretched textures break immersion. Check\n  UVs on a checker texture before final texturing.\n- - **Ignoring scale.** Modeling without real-world units produces wrong-looking light falloff,\n  depth of field, and physics. Model to scale, always.\n- - **Over-detailed for the output.** Million-poly sculpts for a 200px web thumbnail. Match effort\n  to the deliverable's actual resolution.\n- - **No art direction.** Technically fine renders with no mood, story, or composition. 3D is a\n  visual medium — direct it like one: what's the feeling, what's the focal point?\n","## Overview\n\n3D design has moved from specialist VFX into everyday product work: marketing renders, product\nvisualizations, AR assets, and web experiences. This skill covers the practical 3D pipeline —\nmodeling, UVs\u002Ftexturing, lighting, rendering — plus the optimization discipline needed for real-time\nand web delivery, where polygon budgets and load times rule.\n\n## When to use\n\n- Creating product renders or marketing visuals\n\n- Building 3D assets for web (WebGL) or AR\n\n- Designing 3D illustrations or abstract brand art\n\n- Preparing models for 3D printing or manufacturing viz\n\n- Optimizing 3D assets for performance\n\n## Core concepts\n\n- - **The pipeline.** Model → UV unwrap → texture\u002Fmaterial → light → render. Each stage builds on\n  the last; skipping UVs or lighting and hoping the render saves you never works.\n- - **Topology matters.** Clean quad-based topology with good edge flow deforms well (for animation)\n  and subdivides cleanly. Triangles and n-gons are fine for static hard-surface work, poison for\n  organic deformation.\n- - **PBR materials.** Physically-based rendering: albedo, roughness, metalness, normal maps.\n  Understand what each map does — 90% of \"why does this look fake\" is wrong roughness\u002Fmetalness\n  values.\n- - **Lighting is everything.** Three-point lighting fundamentals, HDRI environments for realism,\n  and the truth that great lighting saves mediocre models while bad lighting kills great ones. Study\n  real-world light behavior.\n- - **Composition and camera.** 3D scenes follow photographic rules: focal length choices (wide =\n  dramatic, long = compressed), rule of thirds, depth of field for focus. Render like a\n  photographer, not a technician.\n- - **Optimization for delivery.** Web\u002FAR assets need: low poly counts, baked textures, efficient\n  materials, Draco\u002Fmeshopt compression, and LODs. A 50MB model is a failed web asset regardless of\n  beauty.\n\n## Practical workflow\n\n1. 1. **Define the output.** Still render? Turntable? Real-time web? AR? Print? The deliverable\n   determines the entire pipeline (a web asset and a billboard render are different projects).\n2. 2. **Block out first.** Rough primitive shapes establishing proportions and composition. Get the\n   silhouette and camera right before any detail — 80% of a model's read is silhouette.\n3. 3. **Model with intent.** Hard-surface: bevels catch highlights (never leave razor-sharp CG edges\n   — real objects have micro-bevels). Organic: clean topology, reference anatomy. Keep poly counts\n   appropriate to the output.\n4. 4. **UV and texture.** Unwrap with minimal stretching, pack efficiently, paint or source PBR\n   textures. For stylized work: define the material language (flat colors? gradients? toon shading?)\n   and stay consistent.\n5. 5. **Light the scene.** Key light (direction + mood), fill (soften shadows), rim (separation from\n   background), environment (HDRI for reflections\u002Fambient). Iterate lighting before final materials\n   tweaks.\n6. 6. **Render and post.** Appropriate samples (kill noise without wasting hours), render passes if\n   compositing, then color grade: contrast, color balance, vignette. Post-production is where\n   renders get their final 20%.\n7. 7. **Optimize for the target.** Decimate\u002Fretopologize for real-time, bake high-poly detail to\n   normal maps, compress textures (KTX2\u002FBasis for web), test load time and frame rate on target\n   devices.\n\n## Common pitfalls\n\n- - **No bevels.** Razor-sharp edges scream \"CG.\" Real-world edges catch light — micro-bevels are\n  the cheapest realism upgrade.\n- - **Bad lighting.** Flat, single-source, or default lighting. Spend half your time on lighting;\n  it's the highest-leverage stage.\n- - **Texture stretching and seams.** Visible UV seams and stretched textures break immersion. Check\n  UVs on a checker texture before final texturing.\n- - **Ignoring scale.** Modeling without real-world units produces wrong-looking light falloff,\n  depth of field, and physics. Model to scale, always.\n- - **Over-detailed for the output.** Million-poly sculpts for a 200px web thumbnail. Match effort\n  to the deliverable's actual resolution.\n- - **No art direction.** Technically fine renders with no mood, story, or composition. 3D is a\n  visual medium — direct it like one: what's the feeling, what's the focal point?\n",{"name":5,"category":24,"description":7},"creative-design","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-3d-designer",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill 3d-designer",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill 3d-designer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill 3d-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-3d-designer\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]