[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M787YAVDJ3NTMSK3WSVH1EE5":3,"skill-same:01M787YAVDJ3NTMSK3WSVH1EE5":68},{"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":47,"commitSha":48,"skillDirectory":49,"forksCount":14,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M787YAVDJ3NTMSK3WSVH1EE5","sketch",null,"Throwaway HTML mockups: 2-3 design variants to compare.","abdullibrahim733-pixel\u002FEagle","abdullibrahim733-pixel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230504522?v=4","01M787SK0DQR0H1K326DJT6EBK","ibrahim abdull","01M787SK1HWS9V959THKZM6N70",0,"MIT","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fprofiles\u002Falexender_ceo\u002Fskills\u002Fcreative\u002Fsketch\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sketch\ndescription: \"Throwaway HTML mockups: 2-3 design variants to compare.\"\nversion: 1.0.1\nauthor: Hermes Agent (adapted from gsd-build\u002Fget-shit-done)\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [sketch, mockup, design, ui, prototype, html, variants, exploration, wireframe, comparison]\n    related_skills: [spike, claude-design, popular-web-designs, excalidraw]\n---\n\n# Sketch\n\nUse this skill when the user wants to **see a design direction before committing** to one — exploring a UI\u002FUX idea as disposable HTML mockups. The point is to generate 2-3 interactive variants so the user can compare visual directions side-by-side, not to produce shippable code.\n\nLoad this when the user says things like \"sketch this screen\", \"show me what X could look like\", \"compare layout A vs B\", \"give me 2-3 takes on this UI\", \"let me see some variants\", \"mockup this before I build\".\n\n## When NOT to use this\n\n- User wants a production component — use `claude-design` or build it properly\n- User wants a polished one-off HTML artifact (landing page, deck) — `claude-design`\n- User wants a diagram — `excalidraw`, `architecture-diagram`\n- The design is already locked — just build it\n\n## If the user has the full GSD system installed\n\nIf `gsd-sketch` shows up as a sibling skill (installed via `npx get-shit-done-cc --hermes`), you can use **`gsd-sketch`** for the fuller workflow: persistent `.planning\u002Fsketches\u002F` with MANIFEST, frontier mode analysis, consistency audits across past sketches, and integration with the rest of GSD. This skill is the lightweight standalone version — one-off sketching without the state machinery.\n\n> **Note:** The upstream GSD project ([gsd-build\u002Fget-shit-done](https:\u002F\u002Fgithub.com\u002Fgsd-build\u002Fget-shit-done)) is **archived \u002F no longer maintained** on GitHub. The npm package (`get-shit-done-cc`) still installs, but treat it as an archived community project — this standalone `sketch` skill is the maintained path and needs nothing extra.\n\n## Core method\n\n```\nintake  →  variants  →  head-to-head  →  pick winner (or iterate)\n```\n\n### 1. Intake (skip if the user already gave you enough)\n\nBefore generating variants, get three things — one question at a time, not all at once:\n\n1. **Feel.** \"What should this feel like? Adjectives, emotions, a vibe.\" — *\"calm, editorial, like Linear\"* tells you more than *\"minimal\"*.\n2. **References.** \"What apps, sites, or products capture the feel you're imagining?\" — actual references beat abstract descriptions.\n3. **Core action.** \"What's the single most important thing a user does on this screen?\" — the variants should all serve this well; if they don't, they're just decoration.\n\nReflect each answer briefly before the next question. If the user already gave you all three upfront, skip straight to variants.\n\n### 2. Variants (2-3, never 1, rarely 4+)\n\nProduce **2-3 variants** in one go. Each variant is a complete, standalone HTML file. Don't describe variants — build them. The point is comparison.\n\nEach variant should take a **different design stance**, not different pixel values. Three good variant axes:\n\n- **Density:** compact \u002F airy \u002F ultra-dense (pick two contrasting poles)\n- **Emphasis:** content-first \u002F action-first \u002F tool-first\n- **Aesthetic:** editorial \u002F utilitarian \u002F playful\n- **Layout:** single-column \u002F sidebar \u002F split-pane\n- **Grounding:** card-based \u002F bare-content \u002F document-style\n\nPick one axis and pull apart from it. Two variants that differ only in accent color are wasted effort — the user can't distinguish them.\n\n**Variant naming:** describe the stance, not the number.\n\n```\nsketches\u002F\n├── 001-calm-editorial\u002F\n│   ├── index.html\n│   └── README.md\n├── 001-utilitarian-dense\u002F\n│   ├── index.html\n│   └── README.md\n└── 001-playful-split\u002F\n    ├── index.html\n    └── README.md\n```\n\n### 3. Make them real HTML\n\nEach variant is a **single self-contained HTML file**:\n\n- Inline `\u003Cstyle>` — no build step, no external CSS\n- System fonts or one Google Font via `\u003Clink>`\n- Tailwind via CDN (`\u003Cscript src=\"https:\u002F\u002Fcdn.tailwindcss.com\">\u003C\u002Fscript>`) is fine\n- Realistic fake content — actual sentences, actual names, not \"Lorem ipsum\"\n- **Interactive**: links clickable, hovers real, at least one state transition (open\u002Fclose, filter, toggle). A frozen static image is a worse spike than a sloppy animated one.\n\nOpen it in a browser. If it looks broken, fix it before showing the user.\n\n**Verify variants visually — use Hermes' browser tools.** Don't just write HTML and hope it renders; load each variant and look at it:\n\n```\nbrowser_navigate(url=\"file:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fto\u002Fsketches\u002F001-calm-editorial\u002Findex.html\")\nbrowser_vision(question=\"Does this layout look clean and readable? Any visible bugs (overlapping text, unstyled elements, broken images)?\")\n```\n\n`browser_vision` returns an AI description of what's actually on the page plus a screenshot path — catches layout bugs that pure source inspection misses (e.g. a font import that silently failed, a flex container that collapsed). Fix and re-navigate until each variant looks right.\n\n**Default CSS reset + system font stack** for fast starts:\n\n```html\n\u003Cstyle>\n  * { box-sizing: border-box; margin: 0; padding: 0; }\n  body {\n    font-family: -apple-system, BlinkMacSystemFont, \"Segoe UI\", Roboto,\n                 \"Helvetica Neue\", Arial, sans-serif;\n    -webkit-font-smoothing: antialiased;\n    color: #1a1a1a;\n    background: #fafafa;\n    line-height: 1.5;\n  }\n\u003C\u002Fstyle>\n```\n\n### 4. Variant README\n\nEach variant's `README.md` answers:\n\n```markdown\n## Variant: {stance name}\n\n### Design stance\nOne sentence on the principle driving this variant.\n\n### Key choices\n- Layout: ...\n- Typography: ...\n- Color: ...\n- Interaction: ...\n\n### Trade-offs\n- Strong at: ...\n- Weak at: ...\n\n### Best for\n- The kind of user or use case this variant actually serves\n```\n\n### 5. Head-to-head\n\nAfter all variants are built, present them as a comparison. Don't just list — **opinionate**:\n\n```markdown\n## Three takes on the home screen\n\n| Dimension | Calm editorial | Utilitarian dense | Playful split |\n|-----------|----------------|-------------------|---------------|\n| Density   | Low            | High              | Medium        |\n| Primary action visibility | Low | High | Medium |\n| Scan-ability | High | Medium | Low |\n| Feel | Calm, trusted | Sharp, tool-like | Inviting, energetic |\n\n**My take:** Utilitarian dense for power users, calm editorial for content-forward audiences. Playful split is weakest — tries to do both and commits to neither.\n```\n\nLet the user pick a winner, or combine two into a hybrid, or ask for another round.\n\n## Theming (when the project has a visual identity)\n\nIf the user has an existing theme (colors, fonts, tokens), put shared tokens in `sketches\u002Fthemes\u002Ftokens.css` and `@import` them in each variant. Keep tokens minimal:\n\n```css\n\u002F* sketches\u002Fthemes\u002Ftokens.css *\u002F\n:root {\n  --color-bg: #fafafa;\n  --color-fg: #1a1a1a;\n  --color-accent: #0066ff;\n  --color-muted: #666;\n  --radius: 8px;\n  --font-display: \"Inter\", sans-serif;\n  --font-body: -apple-system, BlinkMacSystemFont, sans-serif;\n}\n```\n\nDon't over-tokenize a throwaway sketch — three colors and one font is usually enough.\n\n## Interactivity bar\n\nA sketch is interactive enough when the user can:\n\n1. **Click a primary action** and something visible happens (state change, modal, toast, navigation feint)\n2. **See one meaningful state transition** (filter a list, toggle a mode, open\u002Fclose a panel)\n3. **Hover recognizable affordances** (buttons, rows, tabs)\n\nMore than that is over-engineering a throwaway. Less than that is a screenshot.\n\n## Frontier mode (picking what to sketch next)\n\nIf sketches already exist and the user says \"what should I sketch next?\":\n\n- **Consistency gaps** — two winning variants from different sketches made independent choices that haven't been composed together yet\n- **Unsketched screens** — referenced but never explored\n- **State coverage** — happy path sketched, but not empty \u002F loading \u002F error \u002F 1000-items\n- **Responsive gaps** — validated at one viewport; does it hold at mobile \u002F ultrawide?\n- **Interaction patterns** — static layouts exist; transitions, drag, scroll behavior don't\n\nPropose 2-4 named candidates. Let the user pick.\n\n## Output\n\n- Create `sketches\u002F` (or `.planning\u002Fsketches\u002F` if the user is using GSD conventions) in the repo root\n- One subdir per variant: `NNN-stance-name\u002Findex.html` + `README.md`\n- Tell the user how to open them: `open sketches\u002F001-calm-editorial\u002Findex.html` on macOS, `xdg-open` on Linux, `start` on Windows\n- Keep variants disposable — a sketch that you felt the need to preserve should be promoted into real project code, not curated as an asset\n\n**Typical tool sequence for one variant:**\n\n```\nterminal(\"mkdir -p sketches\u002F001-calm-editorial\")\nwrite_file(\"sketches\u002F001-calm-editorial\u002Findex.html\", \"\u003C!doctype html>...\")\nwrite_file(\"sketches\u002F001-calm-editorial\u002FREADME.md\", \"## Variant: Calm editorial\\n...\")\nbrowser_navigate(url=\"file:\u002F\u002F$(pwd)\u002Fsketches\u002F001-calm-editorial\u002Findex.html\")\nbrowser_vision(question=\"How does this look? Any obvious layout issues?\")\n```\n\nRepeat for each variant, then present the comparison table.\n\n## Attribution\n\nAdapted from the GSD (Get Shit Done) project's `\u002Fgsd-sketch` workflow — MIT © 2025 Lex Christopherson ([gsd-build\u002Fget-shit-done](https:\u002F\u002Fgithub.com\u002Fgsd-build\u002Fget-shit-done)). The upstream GSD repo is now **archived\u002Funmaintained** on GitHub; the `get-shit-done-cc` npm package still installs (`npx get-shit-done-cc --hermes --global`) and ships persistent sketch state, theme\u002Fvariant pattern references, and consistency-audit workflows, but treat it as an archived community project.\n","# Sketch\n\nUse this skill when the user wants to **see a design direction before committing** to one — exploring a UI\u002FUX idea as disposable HTML mockups. The point is to generate 2-3 interactive variants so the user can compare visual directions side-by-side, not to produce shippable code.\n\nLoad this when the user says things like \"sketch this screen\", \"show me what X could look like\", \"compare layout A vs B\", \"give me 2-3 takes on this UI\", \"let me see some variants\", \"mockup this before I build\".\n\n## When NOT to use this\n\n- User wants a production component — use `claude-design` or build it properly\n- User wants a polished one-off HTML artifact (landing page, deck) — `claude-design`\n- User wants a diagram — `excalidraw`, `architecture-diagram`\n- The design is already locked — just build it\n\n## If the user has the full GSD system installed\n\nIf `gsd-sketch` shows up as a sibling skill (installed via `npx get-shit-done-cc --hermes`), you can use **`gsd-sketch`** for the fuller workflow: persistent `.planning\u002Fsketches\u002F` with MANIFEST, frontier mode analysis, consistency audits across past sketches, and integration with the rest of GSD. This skill is the lightweight standalone version — one-off sketching without the state machinery.\n\n> **Note:** The upstream GSD project ([gsd-build\u002Fget-shit-done](https:\u002F\u002Fgithub.com\u002Fgsd-build\u002Fget-shit-done)) is **archived \u002F no longer maintained** on GitHub. The npm package (`get-shit-done-cc`) still installs, but treat it as an archived community project — this standalone `sketch` skill is the maintained path and needs nothing extra.\n\n## Core method\n\n```\nintake  →  variants  →  head-to-head  →  pick winner (or iterate)\n```\n\n### 1. Intake (skip if the user already gave you enough)\n\nBefore generating variants, get three things — one question at a time, not all at once:\n\n1. **Feel.** \"What should this feel like? Adjectives, emotions, a vibe.\" — *\"calm, editorial, like Linear\"* tells you more than *\"minimal\"*.\n2. **References.** \"What apps, sites, or products capture the feel you're imagining?\" — actual references beat abstract descriptions.\n3. **Core action.** \"What's the single most important thing a user does on this screen?\" — the variants should all serve this well; if they don't, they're just decoration.\n\nReflect each answer briefly before the next question. If the user already gave you all three upfront, skip straight to variants.\n\n### 2. Variants (2-3, never 1, rarely 4+)\n\nProduce **2-3 variants** in one go. Each variant is a complete, standalone HTML file. Don't describe variants — build them. The point is comparison.\n\nEach variant should take a **different design stance**, not different pixel values. Three good variant axes:\n\n- **Density:** compact \u002F airy \u002F ultra-dense (pick two contrasting poles)\n- **Emphasis:** content-first \u002F action-first \u002F tool-first\n- **Aesthetic:** editorial \u002F utilitarian \u002F playful\n- **Layout:** single-column \u002F sidebar \u002F split-pane\n- **Grounding:** card-based \u002F bare-content \u002F document-style\n\nPick one axis and pull apart from it. Two variants that differ only in accent color are wasted effort — the user can't distinguish them.\n\n**Variant naming:** describe the stance, not the number.\n\n```\nsketches\u002F\n├── 001-calm-editorial\u002F\n│   ├── index.html\n│   └── README.md\n├── 001-utilitarian-dense\u002F\n│   ├── index.html\n│   └── README.md\n└── 001-playful-split\u002F\n    ├── index.html\n    └── README.md\n```\n\n### 3. Make them real HTML\n\nEach variant is a **single self-contained HTML file**:\n\n- Inline `\u003Cstyle>` — no build step, no external CSS\n- System fonts or one Google Font via `\u003Clink>`\n- Tailwind via CDN (`\u003Cscript src=\"https:\u002F\u002Fcdn.tailwindcss.com\">\u003C\u002Fscript>`) is fine\n- Realistic fake content — actual sentences, actual names, not \"Lorem ipsum\"\n- **Interactive**: links clickable, hovers real, at least one state transition (open\u002Fclose, filter, toggle). A frozen static image is a worse spike than a sloppy animated one.\n\nOpen it in a browser. If it looks broken, fix it before showing the user.\n\n**Verify variants visually — use Hermes' browser tools.** Don't just write HTML and hope it renders; load each variant and look at it:\n\n```\nbrowser_navigate(url=\"file:\u002F\u002F\u002Fabsolute\u002Fpath\u002Fto\u002Fsketches\u002F001-calm-editorial\u002Findex.html\")\nbrowser_vision(question=\"Does this layout look clean and readable? Any visible bugs (overlapping text, unstyled elements, broken images)?\")\n```\n\n`browser_vision` returns an AI description of what's actually on the page plus a screenshot path — catches layout bugs that pure source inspection misses (e.g. a font import that silently failed, a flex container that collapsed). Fix and re-navigate until each variant looks right.\n\n**Default CSS reset + system font stack** for fast starts:\n\n```html\n\u003Cstyle>\n  * { box-sizing: border-box; margin: 0; padding: 0; }\n  body {\n    font-family: -apple-system, BlinkMacSystemFont, \"Segoe UI\", Roboto,\n                 \"Helvetica Neue\", Arial, sans-serif;\n    -webkit-font-smoothing: antialiased;\n    color: #1a1a1a;\n    background: #fafafa;\n    line-height: 1.5;\n  }\n\u003C\u002Fstyle>\n```\n\n### 4. Variant README\n\nEach variant's `README.md` answers:\n\n```markdown\n## Variant: {stance name}\n\n### Design stance\nOne sentence on the principle driving this variant.\n\n### Key choices\n- Layout: ...\n- Typography: ...\n- Color: ...\n- Interaction: ...\n\n### Trade-offs\n- Strong at: ...\n- Weak at: ...\n\n### Best for\n- The kind of user or use case this variant actually serves\n```\n\n### 5. Head-to-head\n\nAfter all variants are built, present them as a comparison. Don't just list — **opinionate**:\n\n```markdown\n## Three takes on the home screen\n\n| Dimension | Calm editorial | Utilitarian dense | Playful split |\n|-----------|----------------|-------------------|---------------|\n| Density   | Low            | High              | Medium        |\n| Primary action visibility | Low | High | Medium |\n| Scan-ability | High | Medium | Low |\n| Feel | Calm, trusted | Sharp, tool-like | Inviting, energetic |\n\n**My take:** Utilitarian dense for power users, calm editorial for content-forward audiences. Playful split is weakest — tries to do both and commits to neither.\n```\n\nLet the user pick a winner, or combine two into a hybrid, or ask for another round.\n\n## Theming (when the project has a visual identity)\n\nIf the user has an existing theme (colors, fonts, tokens), put shared tokens in `sketches\u002Fthemes\u002Ftokens.css` and `@import` them in each variant. Keep tokens minimal:\n\n```css\n\u002F* sketches\u002Fthemes\u002Ftokens.css *\u002F\n:root {\n  --color-bg: #fafafa;\n  --color-fg: #1a1a1a;\n  --color-accent: #0066ff;\n  --color-muted: #666;\n  --radius: 8px;\n  --font-display: \"Inter\", sans-serif;\n  --font-body: -apple-system, BlinkMacSystemFont, sans-serif;\n}\n```\n\nDon't over-tokenize a throwaway sketch — three colors and one font is usually enough.\n\n## Interactivity bar\n\nA sketch is interactive enough when the user can:\n\n1. **Click a primary action** and something visible happens (state change, modal, toast, navigation feint)\n2. **See one meaningful state transition** (filter a list, toggle a mode, open\u002Fclose a panel)\n3. **Hover recognizable affordances** (buttons, rows, tabs)\n\nMore than that is over-engineering a throwaway. Less than that is a screenshot.\n\n## Frontier mode (picking what to sketch next)\n\nIf sketches already exist and the user says \"what should I sketch next?\":\n\n- **Consistency gaps** — two winning variants from different sketches made independent choices that haven't been composed together yet\n- **Unsketched screens** — referenced but never explored\n- **State coverage** — happy path sketched, but not empty \u002F loading \u002F error \u002F 1000-items\n- **Responsive gaps** — validated at one viewport; does it hold at mobile \u002F ultrawide?\n- **Interaction patterns** — static layouts exist; transitions, drag, scroll behavior don't\n\nPropose 2-4 named candidates. Let the user pick.\n\n## Output\n\n- Create `sketches\u002F` (or `.planning\u002Fsketches\u002F` if the user is using GSD conventions) in the repo root\n- One subdir per variant: `NNN-stance-name\u002Findex.html` + `README.md`\n- Tell the user how to open them: `open sketches\u002F001-calm-editorial\u002Findex.html` on macOS, `xdg-open` on Linux, `start` on Windows\n- Keep variants disposable — a sketch that you felt the need to preserve should be promoted into real project code, not curated as an asset\n\n**Typical tool sequence for one variant:**\n\n```\nterminal(\"mkdir -p sketches\u002F001-calm-editorial\")\nwrite_file(\"sketches\u002F001-calm-editorial\u002Findex.html\", \"\u003C!doctype html>...\")\nwrite_file(\"sketches\u002F001-calm-editorial\u002FREADME.md\", \"## Variant: Calm editorial\\n...\")\nbrowser_navigate(url=\"file:\u002F\u002F$(pwd)\u002Fsketches\u002F001-calm-editorial\u002Findex.html\")\nbrowser_vision(question=\"How does this look? Any obvious layout issues?\")\n```\n\nRepeat for each variant, then present the comparison table.\n\n## Attribution\n\nAdapted from the GSD (Get Shit Done) project's `\u002Fgsd-sketch` workflow — MIT © 2025 Lex Christopherson ([gsd-build\u002Fget-shit-done](https:\u002F\u002Fgithub.com\u002Fgsd-build\u002Fget-shit-done)). The upstream GSD repo is now **archived\u002Funmaintained** on GitHub; the `get-shit-done-cc` npm package still installs (`npx get-shit-done-cc --hermes --global`) and ships persistent sketch state, theme\u002Fvariant pattern references, and consistency-audit workflows, but treat it as an archived community project.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":43,"description":7},"Hermes Agent (adapted from gsd-build\u002Fget-shit-done)","1.0.1",{"hermes":27},{"tags":28,"related_skills":38},[5,29,30,31,32,33,34,35,36,37],"mockup","design","ui","prototype","html","variants","exploration","wireframe","comparison",[39,40,41,42],"spike","claude-design","popular-web-designs","excalidraw",[44,45,46],"linux","macos","windows","main","1f420fcb3f20524e8a830b9d010e0c0ee312d437","hermes-backup\u002Fprofiles\u002Falexender_ceo\u002Fskills\u002Fcreative\u002Fsketch","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel","I am a developer at UMG Africa and i have 2 years of software development also i engage with embedded softwares i am good in rust, cpp, python and kotlin","2026-08-16 18:04:02",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add abdullibrahim733-pixel\u002FEagle --skill sketch",{"tool":60,"command":61},"bunx","bunx skills add abdullibrahim733-pixel\u002FEagle --skill sketch",{"tool":63,"command":64},"pnpm","pnpm dlx skills add abdullibrahim733-pixel\u002FEagle --skill sketch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fprofiles\u002Falexender_ceo\u002Fskills\u002Fcreative\u002Fsketch\u002FSKILL.md",true,[],[69,76,83,90,96,103],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M78BBHAQCSZNG7HYMB97YG3Y","web-ui-verification","Verify web UIs via headless Chrome CDP, no vision needed.","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fsoftware-development\u002Fweb-ui-verification\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M78BB60RHXBY2QV4TA9S917B","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M78BB16QRJZA9P3TXN5SHCQH","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":91,"name":39,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M78BAY69B9JP3SK2NAF3EH2D","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M78BAVDMEBYN49PRDQ8QXTBJ","simplify-code","Parallel 4-agent cleanup of recent code changes.","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fsoftware-development\u002Fsimplify-code\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M78BAE09PQ5RV5MSJN1S788A","scroll-driven-3d-websites","Scroll-scrubbed 3D promo sites (Three.js + GSAP).","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fsoftware-development\u002Fscroll-driven-3d-websites\u002FSKILL.md",[],[]]