[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EX495RSHTTCEJVX7C83FA3":3,"skill-same:01M7EX495RSHTTCEJVX7C83FA3":114},{"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":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7EX495RSHTTCEJVX7C83FA3","design-dna",null,"Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure\u002Fschema, (2) a user provides images, screenshots, or URLs of reference designs and wants them analyzed into a structured JSON profile covering all three dimensions, (3) a user has a Design DNA JSON and content and wants a design generated from it, or (4) any combination of these phases. Triggers on \"design DNA\", \"extract design style\", \"analyze design\", \"design tokens from reference\", \"generate design from JSON\", \"design system from screenshot\", \"design profile\", \"style guide JSON\", \"visual effects analysis\", \"design with effects\", \"3d design analysis\".","mhyahya854\u002FAI-Second-Brain_Universal-Rules","mhyahya854","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F194078115?v=4","01M7EGSP2M9T858SDHJMXQ257Y","01M7EGSP3N6HN6879SVDPMD4DZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: design-dna\ndescription: >-\n  Extract, define, and apply design DNA across three dimensions: design system\n  (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL,\n  3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user\n  wants to see the full 3-dimension design structure\u002Fschema, (2) a user provides\n  images, screenshots, or URLs of reference designs and wants them analyzed into\n  a structured JSON profile covering all three dimensions, (3) a user has a\n  Design DNA JSON and content and wants a design generated from it, or (4) any\n  combination of these phases. Triggers on \"design DNA\", \"extract design style\",\n  \"analyze design\", \"design tokens from reference\", \"generate design from JSON\",\n  \"design system from screenshot\", \"design profile\", \"style guide JSON\",\n  \"visual effects analysis\", \"design with effects\", \"3d design analysis\".\n---\n\n# Design DNA\n\nA 3-phase workflow for extracting, structuring, and applying design identity across three dimensions:\n\n1. **Design System** — measurable tokens (color, typography, spacing, layout, shape, elevation, motion, components)\n2. **Design Style** — qualitative perception (mood, visual language, composition, imagery, interaction feel, brand voice)\n3. **Visual Effects** — special rendering (Canvas, WebGL, 3D, particles, shaders, scroll effects, cursor effects, SVG animations, glassmorphism, etc.)\n\n## Phases\n\n### Phase 1: Structure — Output the Schema\n\nWhen the user asks for the structural dimensions or schema:\n\n1. Read [references\u002Fschema.md](references\u002Fschema.md)\n2. Present the full schema with field descriptions\n3. Explain the three dimensions and their roles:\n   - **design_system**: What you can measure — exact hex values, pixel sizes, rem scales\n   - **design_style**: What you can feel — mood, personality, composition strategy\n   - **visual_effects**: What you can see but can't express in CSS alone — WebGL scenes, particle systems, shader distortions, scroll-driven animations\n4. Ask if the user wants to customize or extend any dimensions\n\n### Phase 2: Analyze — Extract DNA from References\n\nWhen the user provides images, screenshots, or links representing a target design style:\n\n1. Read [references\u002Fschema.md](references\u002Fschema.md) for the full field list\n2. For each reference provided:\n   - If image\u002Fscreenshot: **first run the deterministic color measurement** (see below), then analyze the remaining visual properties directly\n   - If URL: fetch and analyze the page's visual design\n3. For every field in the schema, extract or infer a value from the references\n4. When multiple references conflict, note the dominant pattern and mention variants\n5. Output a complete Design DNA JSON — every field populated, no empty strings\n6. After output, ask: \"Want to adjust any values before using this for generation?\"\n\n**Analysis approach per dimension:**\n\n#### Dimension 1: design_system\n- **color**: Do not estimate hex values by eye — perceived colors drift toward familiar palette defaults (often by a ΔE of 10+). When the reference is an image file, measure instead. Resolve `SKILL_ROOT` to the absolute directory containing this `SKILL.md`; never assume the current project directory contains the skill's `scripts\u002F` folder. Use absolute paths for the reference and output, and keep one uniquely named measurement file per reference:\n  ```bash\n  npm install --prefix \"$SKILL_ROOT\u002Fscripts\" --silent\n  node \"$SKILL_ROOT\u002Fscripts\u002Fmeasure-colors.mjs\" \"$REFERENCE_IMAGE\" > \"$MEASUREMENT_JSON\"\n  ```\n  Use the measured hexes verbatim in the DNA JSON: map the `background` role to `surface.background`; map `text` to the end of `neutral.scale` that contrasts with the measured background and document that foreground use in `neutral.usage`; and map `accent` to `accent.hex`. Keep both the measured palette and its `measurement` configuration in `design_system.color.measured_palette` and `design_system.color.measurement` so verification can reuse the same clustering configuration. Coverage values are fractions from `0` to `1`. Only fall back to visual sampling when measurement is impossible (for example, a URL-only reference that cannot be screenshotted). Choose primary and secondary colors by semantic role, use accent for CTA emphasis, and order the neutral scale from lightest to darkest regardless of theme.\n- **typography**: Identify font families by visual characteristics (geometric, humanist, serif class). Estimate scale ratios from heading\u002Fbody size relationships.\n- **spacing**: Assess density by element proximity. Measure rhythm by section gap consistency.\n- **layout**: Identify grid by content alignment patterns. Note max-width, column count, asymmetry.\n- **shape**: Measure border-radius by comparing to element height. Note border and divider presence.\n- **elevation**: Classify shadow softness, spread, and layering approach.\n- **motion**: If observable (video\u002Finteractive), note easing curves and duration feel.\n\n#### Dimension 2: design_style\n- Synthesize holistic impressions — mood, personality, composition strategy\n- Compare against genre archetypes (SaaS, editorial, brutalist, etc.)\n- Note ornamentation level and whitespace philosophy\n\n#### Dimension 3: visual_effects\n- **From code**: Scan for `\u003Ccanvas>`, WebGL contexts, Three.js\u002FPixi.js imports, GSAP\u002FLottie usage, custom shaders, IntersectionObserver scroll triggers, SVG `\u003Canimate>` elements\n- **From screenshots**: Describe visible effects that go beyond standard CSS — glowing particles, 3D object renders, noise textures, gradient animations, parallax depth, cursor trails, text distortions, glassmorphic surfaces. Note these in `composite_notes` when exact implementation can't be determined.\n- **From video\u002Finteraction demos**: Note scroll behaviors, hover distortions, transition choreography, loading sequences\n- Set `enabled: false` for any effect category not present in the reference\n- Rate `overview.effect_intensity` and `overview.performance_tier` based on what's observed\n\n### Phase 3: Generate — Apply DNA to Content\n\nWhen the user provides DNA JSON + content to design:\n\n1. Read [references\u002Fgeneration-guide.md](references\u002Fgeneration-guide.md)\n2. Parse the DNA JSON and extract all tokens across three dimensions\n3. Build CSS custom properties from `design_system` values\n4. Apply `design_style` qualitative fields to guide subjective design decisions\n5. When the design needs assets or source materials, fetch them from the original source whenever possible. If the user provided a URL, retrieve the real asset from that URL instead of recreating, approximating, or substituting it.\n6. Implement `visual_effects` using appropriate technologies:\n   - Lightweight effects → CSS animations, SVG, vanilla JS\n   - Medium effects → Canvas 2D, GSAP, Lottie\n   - Heavy effects → Three.js, custom GLSL shaders, Pixi.js\n7. Generate the design output (default: self-contained HTML with inline CSS\u002FJS)\n8. Run quality checks from the generation guide\n9. **Verify (when the DNA contains a measured palette)**: save the current Design DNA JSON if it is not already a file, screenshot the generated output, then score it against that DNA file. Resolve `SKILL_ROOT` from this `SKILL.md` and use absolute paths; do not assume a temporary file named `measured-colors.json` exists:\n   ```bash\n   node \"$SKILL_ROOT\u002Fscripts\u002Fverify.mjs\" \"$IMPLEMENTATION_SCREENSHOT\" \"$DESIGN_DNA_JSON\"\n   ```\n   A standalone measurement JSON may be used instead of the DNA file when that is the only persisted artifact. For multiple image references, verify against each reference's measurement separately. The report gives per-color ΔE and coverage drift with PASS\u002FFAIL thresholds. If it fails, fix the offending colors and re-verify instead of asking the user to judge fidelity by eye.\n\n**If the user provides only content without DNA JSON**, ask whether to:\n- Analyze a reference first (go to Phase 2)\n- Use a described style (extract DNA from description, then generate)\n\n## Phase Combinations\n\nUsers may invoke any combination:\n- **Phase 1 only**: \"Show me the design structure\u002Fschema\"\n- **Phase 2 only**: \"Analyze this design\" (with images\u002Flinks)\n- **Phase 2 → 3**: \"Analyze this design and build me a landing page in the same style\"\n- **Phase 1 → 2 → 3**: Full pipeline\n- **Phase 3 only**: User already has DNA JSON\n\nDetect which phase(s) are needed from context and execute accordingly.\n","# Design DNA\n\nA 3-phase workflow for extracting, structuring, and applying design identity across three dimensions:\n\n1. **Design System** — measurable tokens (color, typography, spacing, layout, shape, elevation, motion, components)\n2. **Design Style** — qualitative perception (mood, visual language, composition, imagery, interaction feel, brand voice)\n3. **Visual Effects** — special rendering (Canvas, WebGL, 3D, particles, shaders, scroll effects, cursor effects, SVG animations, glassmorphism, etc.)\n\n## Phases\n\n### Phase 1: Structure — Output the Schema\n\nWhen the user asks for the structural dimensions or schema:\n\n1. Read [references\u002Fschema.md](references\u002Fschema.md)\n2. Present the full schema with field descriptions\n3. Explain the three dimensions and their roles:\n   - **design_system**: What you can measure — exact hex values, pixel sizes, rem scales\n   - **design_style**: What you can feel — mood, personality, composition strategy\n   - **visual_effects**: What you can see but can't express in CSS alone — WebGL scenes, particle systems, shader distortions, scroll-driven animations\n4. Ask if the user wants to customize or extend any dimensions\n\n### Phase 2: Analyze — Extract DNA from References\n\nWhen the user provides images, screenshots, or links representing a target design style:\n\n1. Read [references\u002Fschema.md](references\u002Fschema.md) for the full field list\n2. For each reference provided:\n   - If image\u002Fscreenshot: **first run the deterministic color measurement** (see below), then analyze the remaining visual properties directly\n   - If URL: fetch and analyze the page's visual design\n3. For every field in the schema, extract or infer a value from the references\n4. When multiple references conflict, note the dominant pattern and mention variants\n5. Output a complete Design DNA JSON — every field populated, no empty strings\n6. After output, ask: \"Want to adjust any values before using this for generation?\"\n\n**Analysis approach per dimension:**\n\n#### Dimension 1: design_system\n- **color**: Do not estimate hex values by eye — perceived colors drift toward familiar palette defaults (often by a ΔE of 10+). When the reference is an image file, measure instead. Resolve `SKILL_ROOT` to the absolute directory containing this `SKILL.md`; never assume the current project directory contains the skill's `scripts\u002F` folder. Use absolute paths for the reference and output, and keep one uniquely named measurement file per reference:\n  ```bash\n  npm install --prefix \"$SKILL_ROOT\u002Fscripts\" --silent\n  node \"$SKILL_ROOT\u002Fscripts\u002Fmeasure-colors.mjs\" \"$REFERENCE_IMAGE\" > \"$MEASUREMENT_JSON\"\n  ```\n  Use the measured hexes verbatim in the DNA JSON: map the `background` role to `surface.background`; map `text` to the end of `neutral.scale` that contrasts with the measured background and document that foreground use in `neutral.usage`; and map `accent` to `accent.hex`. Keep both the measured palette and its `measurement` configuration in `design_system.color.measured_palette` and `design_system.color.measurement` so verification can reuse the same clustering configuration. Coverage values are fractions from `0` to `1`. Only fall back to visual sampling when measurement is impossible (for example, a URL-only reference that cannot be screenshotted). Choose primary and secondary colors by semantic role, use accent for CTA emphasis, and order the neutral scale from lightest to darkest regardless of theme.\n- **typography**: Identify font families by visual characteristics (geometric, humanist, serif class). Estimate scale ratios from heading\u002Fbody size relationships.\n- **spacing**: Assess density by element proximity. Measure rhythm by section gap consistency.\n- **layout**: Identify grid by content alignment patterns. Note max-width, column count, asymmetry.\n- **shape**: Measure border-radius by comparing to element height. Note border and divider presence.\n- **elevation**: Classify shadow softness, spread, and layering approach.\n- **motion**: If observable (video\u002Finteractive), note easing curves and duration feel.\n\n#### Dimension 2: design_style\n- Synthesize holistic impressions — mood, personality, composition strategy\n- Compare against genre archetypes (SaaS, editorial, brutalist, etc.)\n- Note ornamentation level and whitespace philosophy\n\n#### Dimension 3: visual_effects\n- **From code**: Scan for `\u003Ccanvas>`, WebGL contexts, Three.js\u002FPixi.js imports, GSAP\u002FLottie usage, custom shaders, IntersectionObserver scroll triggers, SVG `\u003Canimate>` elements\n- **From screenshots**: Describe visible effects that go beyond standard CSS — glowing particles, 3D object renders, noise textures, gradient animations, parallax depth, cursor trails, text distortions, glassmorphic surfaces. Note these in `composite_notes` when exact implementation can't be determined.\n- **From video\u002Finteraction demos**: Note scroll behaviors, hover distortions, transition choreography, loading sequences\n- Set `enabled: false` for any effect category not present in the reference\n- Rate `overview.effect_intensity` and `overview.performance_tier` based on what's observed\n\n### Phase 3: Generate — Apply DNA to Content\n\nWhen the user provides DNA JSON + content to design:\n\n1. Read [references\u002Fgeneration-guide.md](references\u002Fgeneration-guide.md)\n2. Parse the DNA JSON and extract all tokens across three dimensions\n3. Build CSS custom properties from `design_system` values\n4. Apply `design_style` qualitative fields to guide subjective design decisions\n5. When the design needs assets or source materials, fetch them from the original source whenever possible. If the user provided a URL, retrieve the real asset from that URL instead of recreating, approximating, or substituting it.\n6. Implement `visual_effects` using appropriate technologies:\n   - Lightweight effects → CSS animations, SVG, vanilla JS\n   - Medium effects → Canvas 2D, GSAP, Lottie\n   - Heavy effects → Three.js, custom GLSL shaders, Pixi.js\n7. Generate the design output (default: self-contained HTML with inline CSS\u002FJS)\n8. Run quality checks from the generation guide\n9. **Verify (when the DNA contains a measured palette)**: save the current Design DNA JSON if it is not already a file, screenshot the generated output, then score it against that DNA file. Resolve `SKILL_ROOT` from this `SKILL.md` and use absolute paths; do not assume a temporary file named `measured-colors.json` exists:\n   ```bash\n   node \"$SKILL_ROOT\u002Fscripts\u002Fverify.mjs\" \"$IMPLEMENTATION_SCREENSHOT\" \"$DESIGN_DNA_JSON\"\n   ```\n   A standalone measurement JSON may be used instead of the DNA file when that is the only persisted artifact. For multiple image references, verify against each reference's measurement separately. The report gives per-color ΔE and coverage drift with PASS\u002FFAIL thresholds. If it fails, fix the offending colors and re-verify instead of asking the user to judge fidelity by eye.\n\n**If the user provides only content without DNA JSON**, ask whether to:\n- Analyze a reference first (go to Phase 2)\n- Use a described style (extract DNA from description, then generate)\n\n## Phase Combinations\n\nUsers may invoke any combination:\n- **Phase 1 only**: \"Show me the design structure\u002Fschema\"\n- **Phase 2 only**: \"Analyze this design\" (with images\u002Flinks)\n- **Phase 2 → 3**: \"Analyze this design and build me a landing page in the same style\"\n- **Phase 1 → 2 → 3**: Full pipeline\n- **Phase 3 only**: User already has DNA JSON\n\nDetect which phase(s) are needed from context and execute accordingly.\n",{"name":5,"description":7},"main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules","https:\u002F\u002Fgithub.com\u002Fmhyahya854","2026-11-06 02:03:37",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill design-dna",{"tool":36,"command":37},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill design-dna",{"tool":39,"command":40},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill design-dna","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FSKILL.md",true,[44,50,54,58,64,68,72,76,80,84,88,92,98,102,106,110],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"docs\u002Fexample-deterministic-measurement.png","ASSET","资产文件",567836,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002Fdocs\u002Fexample-deterministic-measurement.png",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"docs\u002Fexample-style-transfer.png",55016,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002Fdocs\u002Fexample-style-transfer.png",{"path":55,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":15},"LICENSE","许可证",1079,{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"README.es.md","REFERENCE","参考文档",7775,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FREADME.es.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"README.ja.md",9254,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FREADME.ja.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"README.ko.md",7934,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FREADME.ko.md",{"path":73,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":74,"sourceHtmlUrl":75},"README.md",7134,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FREADME.md",{"path":77,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":78,"sourceHtmlUrl":79},"README.zh-CN.md",6702,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FREADME.zh-CN.md",{"path":81,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":82,"sourceHtmlUrl":83},"README.zh-TW.md",6715,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FREADME.zh-TW.md",{"path":85,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fgeneration-guide.md",8567,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002Freferences\u002Fgeneration-guide.md",{"path":89,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fschema.md",11989,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002Freferences\u002Fschema.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fcolor-math.mjs","SCRIPT","脚本",1542,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002Fscripts\u002Fcolor-math.mjs",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fmeasure-colors.mjs",9132,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002Fscripts\u002Fmeasure-colors.mjs",{"path":103,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fpackage.json",330,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002Fscripts\u002Fpackage.json",{"path":107,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":108,"sourceHtmlUrl":109},"scripts\u002Ftest\u002Fcolor-measurement.test.mjs",10306,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002Fscripts\u002Ftest\u002Fcolor-measurement.test.mjs",{"path":111,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":112,"sourceHtmlUrl":113},"scripts\u002Fverify.mjs",6132,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002Fscripts\u002Fverify.mjs",[115,123,131,138,145,152],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M7EX4T721AAH60R0239P8WBZ","frontend-slides","Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT\u002FPPTX to web, or create slides for a talk\u002Fpitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":19},"01M7EX45RF2XZKRC3KDJDTT1PH","wireframe","Generate JSON wireframe with HTML preview","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":19},"01M7EWZEM3MHD48AYSYFR2C9JP","social-publishing","Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API. Use when the user wants to publish, schedule, or manage social media content programmatically. Requires SOCIALCLAW_API_KEY.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fsocial-publishing\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":19},"01M7EWKDEK9840C728VXT78EQ9","hermes-tweet","Install and operate Hermes Tweet, a Hermes Agent plugin for X\u002FTwitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X\u002FTwitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X\u002FTwitter context. Requires XQUIK_API_KEY for read and action tools.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fhermes-tweet\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":19},"01M7EWASXP3NZWW95CJPT2CRWN","refactoring-ui","Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions \"my UI looks off\" (or amateur\u002Funprofessional), \"fix the design\", \"Tailwind styling\", \"color palette\", \"visual hierarchy\", \"design system\", \"spacing scale\", or \"component styling\". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwondelai\u002Fskills\u002Frefactoring-ui\u002FSKILL.md",[],[],{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":19},"01M7EWAHYM6JZCB1NXA72PVKDH","microinteractions","Design the small details -- triggers, rules, feedback, loops and modes -- that separate good products from great ones. Use when the user mentions \"microinteraction\", \"button feedback\", \"loading state\", \"toggle design\", \"animation detail\", \"state transitions\", \"input feedback\", \"the interface feels dead\", \"make the UI feel responsive\", or \"add polish to interactions\". Also trigger when designing form-validation responses, progress indicators, confirmation dialogs, or any element where the user expects immediate feedback. Covers trigger design, state rules, feedback mechanisms, and progressive loops. For overall UI polish, see refactoring-ui. For affordance design, see design-everyday-things.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwondelai\u002Fskills\u002Fmicrointeractions\u002FSKILL.md",[],[]]