[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M733VE86CB9JD8GPX6WJ6ADF":3,"skill-same:01M733VE86CB9JD8GPX6WJ6ADF":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M733VE86CB9JD8GPX6WJ6ADF","technical-wireframe-info-layout",null,"Create a monochrome technical wireframe design system with exploded 3D structure, connector annotations, sparse information labels, and precise dark diagnostic framing.","LiamVisionary\u002Fhivemindos","LiamVisionary","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F102138294?v=4","01M73379NZZ99TT4ZS17XR3Q9D","01M73379PX6AKQNWN05VNSYRXW",13,"MIT","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fpackaged-skills\u002Foptional\u002Fdesign\u002Fmengto\u002Ftechnical-wireframe-info-layout\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fpackaged-skills\u002Foptional\u002Fdesign\u002Fmengto\u002Ftechnical-wireframe-info-layout\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: technical-wireframe-info-layout\ndescription: Create a monochrome technical wireframe design system with exploded 3D structure, connector annotations, sparse information labels, and precise dark diagnostic framing.\nlicense: MIT\n---\n# Technical Wireframe Info Layout Skill\n\n## Use When\n- Create a monochrome technical wireframe design system with exploded 3D structure, connector annotations, sparse information labels, and precise dark diagnostic framing.\n\n## Workflow\n\n## Scope\n- Apply this as a full design-system direction across layout, typography, info labels, widgets, background structure, and the central visualization area.\n- Use it when the interface should feel like a dark technical diagnostic view, product teardown, systems dashboard, or wireframe specification screen.\n- This is not generic sci-fi decoration. The wireframe object, annotations, labels, and supporting UI should all feel like one coherent information layout.\n\n## Visual target\n- Build the page on a near-black monochrome foundation with subtle texture, low-contrast patterning, and very restrained tonal shifts.\n- Use an exploded or layered wireframe object as the main visual anchor, positioned like a structural diagram rather than a decorative hero mesh.\n- Pair that object with floating information labels, dashed or routed connector lines, and sparse metric callouts so the page reads like an annotated system view.\n- Keep the palette almost entirely neutral: black, charcoal, zinc, white, and gray. Emphasis should come from brightness, line weight, and spatial placement instead of strong color.\n- Let typography stay compact and technical, with small labels, utility copy, metric text, and only one or two larger heading moments.\n\n## Implementation guidance\n- Prefer a wide sparse layout with lots of open space around the wireframe object so the annotations and structure remain legible.\n- Use real WebGL, Three.js, SVG, or canvas linework when possible for the wireframe centerpiece instead of flat screenshots or filled 3D renders.\n- Build the object from outlined geometry, edges, torus\u002Fcylinder\u002Fcap layers, or modular parts that can separate slightly to suggest a system exploded into readable components.\n- Add floating info pills or small rounded labels near meaningful object regions, then connect them with thin routed lines or dashed paths.\n- Supporting UI should feel diagnostic and minimal: slim metric widgets, neutral progress bars, legend dots, timeline bars, or memory allocation readouts.\n- Motion should stay subtle and analytical: slow rotation, slight drift, staged label appearance, and gentle connector updates are appropriate.\n\n## Recommended patterns\n- Large right- or center-weighted wireframe object with heading and explanatory copy offset into a quiet corner.\n- Left-side or edge-anchored diagnostic tags with tiny status dots, metadata strings, and smooth connector paths to the main object.\n- Monochrome widget card at the bottom or side showing system allocation, legend rows, or timeline slices with low-contrast bars.\n- Halftone, dither, or faint technical pattern overlay that enriches the dark surface without overpowering the linework.\n- Sparse masked heading reveals and quiet typography that support the analytical mood.\n\n## Tuning knobs\n- Object complexity: add or reduce wireframe layers and exploded parts depending on how technical the model should feel.\n- Annotation density: keep enough labels to explain the structure, but avoid cluttering the composition with too many tags.\n- Contrast: push labels and key edges bright enough to read while preserving the dark subdued background.\n- Motion tempo: keep rotation and reveal timing calm so the interface feels precise rather than flashy.\n- Diagram clarity: use connector paths and spatial separation to make the structure intelligible at a glance.\n\n## Avoid\n- Filled glossy 3D renders that replace the wireframe diagnostic look.\n- Bright accent colors that break the monochrome engineering aesthetic.\n- Dense dashboard cards or marketing sections that compete with the annotated object.\n- Overloading the page with too many labels, lines, or widgets until the diagram becomes noisy.\n- Treating the wireframe centerpiece as unrelated background art instead of the core information structure.\n","# Technical Wireframe Info Layout Skill\n\n## Use When\n- Create a monochrome technical wireframe design system with exploded 3D structure, connector annotations, sparse information labels, and precise dark diagnostic framing.\n\n## Workflow\n\n## Scope\n- Apply this as a full design-system direction across layout, typography, info labels, widgets, background structure, and the central visualization area.\n- Use it when the interface should feel like a dark technical diagnostic view, product teardown, systems dashboard, or wireframe specification screen.\n- This is not generic sci-fi decoration. The wireframe object, annotations, labels, and supporting UI should all feel like one coherent information layout.\n\n## Visual target\n- Build the page on a near-black monochrome foundation with subtle texture, low-contrast patterning, and very restrained tonal shifts.\n- Use an exploded or layered wireframe object as the main visual anchor, positioned like a structural diagram rather than a decorative hero mesh.\n- Pair that object with floating information labels, dashed or routed connector lines, and sparse metric callouts so the page reads like an annotated system view.\n- Keep the palette almost entirely neutral: black, charcoal, zinc, white, and gray. Emphasis should come from brightness, line weight, and spatial placement instead of strong color.\n- Let typography stay compact and technical, with small labels, utility copy, metric text, and only one or two larger heading moments.\n\n## Implementation guidance\n- Prefer a wide sparse layout with lots of open space around the wireframe object so the annotations and structure remain legible.\n- Use real WebGL, Three.js, SVG, or canvas linework when possible for the wireframe centerpiece instead of flat screenshots or filled 3D renders.\n- Build the object from outlined geometry, edges, torus\u002Fcylinder\u002Fcap layers, or modular parts that can separate slightly to suggest a system exploded into readable components.\n- Add floating info pills or small rounded labels near meaningful object regions, then connect them with thin routed lines or dashed paths.\n- Supporting UI should feel diagnostic and minimal: slim metric widgets, neutral progress bars, legend dots, timeline bars, or memory allocation readouts.\n- Motion should stay subtle and analytical: slow rotation, slight drift, staged label appearance, and gentle connector updates are appropriate.\n\n## Recommended patterns\n- Large right- or center-weighted wireframe object with heading and explanatory copy offset into a quiet corner.\n- Left-side or edge-anchored diagnostic tags with tiny status dots, metadata strings, and smooth connector paths to the main object.\n- Monochrome widget card at the bottom or side showing system allocation, legend rows, or timeline slices with low-contrast bars.\n- Halftone, dither, or faint technical pattern overlay that enriches the dark surface without overpowering the linework.\n- Sparse masked heading reveals and quiet typography that support the analytical mood.\n\n## Tuning knobs\n- Object complexity: add or reduce wireframe layers and exploded parts depending on how technical the model should feel.\n- Annotation density: keep enough labels to explain the structure, but avoid cluttering the composition with too many tags.\n- Contrast: push labels and key edges bright enough to read while preserving the dark subdued background.\n- Motion tempo: keep rotation and reveal timing calm so the interface feels precise rather than flashy.\n- Diagram clarity: use connector paths and spatial separation to make the structure intelligible at a glance.\n\n## Avoid\n- Filled glossy 3D renders that replace the wireframe diagnostic look.\n- Bright accent colors that break the monochrome engineering aesthetic.\n- Dense dashboard cards or marketing sections that compete with the annotated object.\n- Overloading the page with too many labels, lines, or widgets until the diagram becomes noisy.\n- Treating the wireframe centerpiece as unrelated background art instead of the core information structure.\n",{"name":5,"license":14,"description":7},"main","f270c4ae4f9d09c4e5da9cfa8adab7e89ae1f53e","packaged-skills\u002Foptional\u002Fdesign\u002Fmengto\u002Ftechnical-wireframe-info-layout",4,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos","https:\u002F\u002Fgithub.com\u002FLiamVisionary","2026-11-10 21:48:41",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add LiamVisionary\u002Fhivemindos --skill technical-wireframe-info-layout",{"tool":37,"command":38},"bunx","bunx skills add LiamVisionary\u002Fhivemindos --skill technical-wireframe-info-layout",{"tool":40,"command":41},"pnpm","pnpm dlx skills add LiamVisionary\u002Fhivemindos --skill technical-wireframe-info-layout","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fpackaged-skills\u002Foptional\u002Fdesign\u002Fmengto\u002Ftechnical-wireframe-info-layout\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},".hivemind-skill-source.json","REFERENCE","参考文档",1175,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fpackaged-skills\u002Foptional\u002Fdesign\u002Fmengto\u002Ftechnical-wireframe-info-layout\u002F.hivemind-skill-source.json",{"path":52,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":15},"LICENSE","许可证",1064,[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M734AA85KQEXDQXQJ3T7769M","tailscale-generation-skill-authoring","This skill should be used when the user asks to \"create a Tailscale generation skill\", \"add a local generation skill\", \"document a generation endpoint\", \"add an image generation provider\", \"add a TTS provider\", \"add video generation\", \"add 3D generation\", or needs guidance on where HivemindOS Tailscale or local generation providers belong in the shared skills shelf.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Ftailscale-generation-skill-authoring\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M734A7VD69PRA0C0EV5EFY9T","localtts","This skill should be used when the user asks to \"generate local TTS\", \"use local text to speech\", \"use remote TTS over Tailscale\", \"make speech audio\", \"add a TTS provider\", \"use Qwen3-TTS\", or needs TTS endpoint setup through local or HivemindOS Tailscale routes.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Flocaltts\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M734A4K2Z0F74QZP7V7WBFRY","karpathy-guidelines","Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Fkarpathy-guidelines\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M734A1HMVYVJX3YJGNQ6KF6C","comfyui-image-generation","This skill should be used when the user asks to \"generate images\", \"generate images with ComfyUI\", \"use local ComfyUI\", \"use remote ComfyUI\", \"use Z-Image\", \"add an image generation provider\", or needs image-generation endpoint setup through local or HivemindOS Tailscale routes.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Fcomfyui-image-generation\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7349Y684Q676DNNHZPSC8W1","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Fcloudflare\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7349V3WCBF835QP74SA9Q8C","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Fcloudflare\u002Fworkers-best-practices\u002FSKILL.md",[],[]]