[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DZ0CH3JRG58CGDN97RWRP":3,"skill-same:01M79DZ0CH3JRG58CGDN97RWRP":99},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79DZ0CH3JRG58CGDN97RWRP","diagram-animator",null,"Turn a static diagram into an animated, step-through walkthrough — a self-contained HTML file where each numbered step draws its arrow, highlights the components involved, dims everything else, and narrates what is happening, with play\u002Fpause and step navigation. Also exports GIF, MP4, and per-step PNG stills. Use this whenever the user wants a diagram animated, brought to life, made interactive, walked through, or explained step by step; whenever they share an architecture, flow, sequence, network, pipeline, or process diagram (SVG, Mermaid, Graphviz\u002FDOT, or PNG) and want to show how it works rather than just how it looks; and whenever they ask for an animated version of a diagram for a deck, demo, doc, README, or Slack. Trigger on \"animate this diagram\", \"can you make this move\", \"step through this architecture\", \"animated version of this flow\", \"show the request path\", or a diagram plus any mention of walkthrough, explainer, or narration.","sharepointoscar\u002Fagent-workflow-skills","sharepointoscar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1544014?v=4","01M79DYNNSWKW6C81A3C9QF0FQ","Oscar Medina","01M79DYNPDXTKQ5RFX4071RBM8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: diagram-animator\ndescription: Turn a static diagram into an animated, step-through walkthrough — a self-contained HTML file where each numbered step draws its arrow, highlights the components involved, dims everything else, and narrates what is happening, with play\u002Fpause and step navigation. Also exports GIF, MP4, and per-step PNG stills. Use this whenever the user wants a diagram animated, brought to life, made interactive, walked through, or explained step by step; whenever they share an architecture, flow, sequence, network, pipeline, or process diagram (SVG, Mermaid, Graphviz\u002FDOT, or PNG) and want to show how it works rather than just how it looks; and whenever they ask for an animated version of a diagram for a deck, demo, doc, README, or Slack. Trigger on \"animate this diagram\", \"can you make this move\", \"step through this architecture\", \"animated version of this flow\", \"show the request path\", or a diagram plus any mention of walkthrough, explainer, or narration.\n---\n\n# Diagram Animator\n\nStatic architecture diagrams show *what exists*. They are bad at showing *what\nhappens*, because every arrow is drawn simultaneously and the reader has no idea\nwhere to start. This skill converts a diagram into a sequenced walkthrough: one\nstep at a time, the relevant arrow draws itself, the components involved light\nup, everything else recedes, and a caption explains the mechanism.\n\nThe output is a single self-contained HTML file. No build step for the viewer, no\nexternal requests, works offline, survives being emailed. Optional GIF \u002F MP4 \u002F\nPNG exports come from the same source.\n\n## The pipeline\n\n```\nsource diagram ──▶ layered SVG ──▶ steps.json ──▶ build.py ──▶ flow.html\n                       │                                          │\n                  (the real work)                        export_frames.js\n                                                                  │\n                                                     gif · mp4 · per-step stills\n```\n\nThe engine (`assets\u002Fengine.js`) is already written and general. Do not rewrite\nit per diagram — the per-diagram work is grouping the SVG and authoring the\nsteps. That split is what keeps this cheap to run repeatedly.\n\n## Workflow\n\n### 1. Get a vector source\n\nAsk for the SVG before settling for a raster. Most diagrams that arrive as a PNG\nwere exported from something, and the quality gap is large enough that one\nround-trip is worth it. If the chat uploader rejects a `.svg` attachment as an\nunprocessable image, suggest renaming it to `.svg.txt`, connecting the containing\nfolder, or pasting the source inline.\n\nFor Mermaid, Graphviz, or a raster fallback, read `references\u002Finputs.md` — it\ncovers rendering to SVG and mapping the generated ids onto the scheme below.\n\n### 2. Restructure the SVG into layers\n\nRead `references\u002Fgrouping.md` before doing this. The essential rule: every\nindependently dimmable unit becomes its own `\u003Cg class=\"layer\" id=\"...\">`, and\nthose groups are **flat siblings**, never nested — nesting multiplies opacity, so\na highlighted box inside a dimmed panel can never brighten.\n\nFlows get `id=\"f1\"..\"fN\"` on the group and `id=\"p1\"..\"pN\"` on the geometry inside.\nThe number circle and its digit go in a `\u003Cg class=\"badge\">`.\n\nGeometry is never modified. The animation is purely additive, so the static\ndiagram still renders identically.\n\nVerify before moving on:\n\n```bash\npython scripts\u002Fcheck_layers.py diagram.svg\n```\n\nIt catches nested layers, ungrouped elements that will never dim, duplicate ids,\nand flows missing their geometry — all of which are invisible until you watch the\nresult and something looks broken.\n\n### 3. Author the steps\n\nWrite `steps.json` per `references\u002Fsteps-schema.md`. Each step names the flow,\nthe layers to keep bright, an accent color matching that arrow, a short tag, a\ntitle, and a caption.\n\nThe captions are the deliverable. The animation is a delivery mechanism for an\nexplanation — if the caption only restates the arrow's own label, the whole thing\nis decoration. Read the diagram closely enough to say what actually happens at\neach hop: the protocol, the claim being checked, the component doing the work,\nwhat would break without it. Where the diagram states a design property\n(\"no standing privileges\", \"unchanged from reference arch\"), work out which step\nearns it and say so there.\n\nTwo things to get right, because they are the most common mistakes:\n\n- **Focus the containing panel alongside an inner box.** Highlighting `g-oauth`\n  without `g-vault-shell` leaves a bright box floating on an invisible panel.\n- **Match each step's `color` to its arrow's stroke.** The engine paints five\n  things from that one value; a mismatch shows up everywhere at once.\n\n### 4. Build\n\n```bash\npython scripts\u002Fbuild.py \\\n  --svg diagram.svg --steps steps.json --out flow.html \\\n  --title \"...\" --footer \"...\"\n```\n\nOptions: `--theme light`, `--theme-file brand.css`, `--no-chrome` (autoplay-only,\nfor screen recording or embedding), `--scrub` (timeline slider), `--strict`.\nSee `references\u002Ftheming.md`.\n\n### 5. Verify in a browser — always\n\nAn animation that throws on step 4 looks fine in step 1. Load it headless, check\nfor console errors, and screenshot a few steps to confirm the dimming and\nhighlighting land where intended:\n\n```bash\nnode scripts\u002Fexport_frames.js flow.html out\u002F --stills\n```\n\nThen actually look at the stills. Check that focused regions read clearly against\nthe dimmed background, that no element stayed bright because it was left out of a\nlayer, and that captions fit their box without overflowing.\n\n### 6. Deliver\n\nSend `flow.html` with `SendUserFile`. A step-through diagram is something people\nreopen and share, so also persist it with `create_artifact` when a desktop is\nconnected.\n\nIf the user wants stills, a GIF, or an MP4 — for a deck, a README, or Slack,\nwhere HTML will not embed — see **Exports** below.\n\n## Exports\n\n`scripts\u002Fexport_frames.js` drives the built HTML through its own timeline and\nscreenshots deterministically. This works because `engine.js` models the entire\nanimation as a pure function of a scalar time value, so seeking to *t* always\nproduces the identical frame regardless of machine speed.\n\n```bash\n# per-step PNGs (overview, one per step, complete)\nnode scripts\u002Fexport_frames.js flow.html out\u002F --stills --scale 2\n\n# looping GIF — Slack, README, chat\nnode scripts\u002Fexport_frames.js flow.html out\u002F --gif --fps 18 --gif-width 1100\n\n# video — much smaller and sharper than GIF, and it has a scrub bar\nnode scripts\u002Fexport_frames.js flow.html out\u002F --mp4 --fps 30   # web, Slack, PowerPoint\nnode scripts\u002Fexport_frames.js flow.html out\u002F --mov --fps 30   # QuickTime, Keynote, Final Cut\n\n# everything\nnode scripts\u002Fexport_frames.js flow.html out\u002F --stills --gif --mp4 --mov\n```\n\nRequires `playwright` (node) and, for GIF\u002Fvideo, `ffmpeg`. Without ffmpeg the raw\nframes are still written and can be encoded later.\n\n### Picking a format\n\n| Want | Use |\n|---|---|\n| Someone can click through at their own pace | the HTML — always ship this |\n| Plays inline in Slack, GitHub, chat | `--gif` |\n| Deck, email, DM, anywhere with a player | `--mp4` |\n| macOS-native — QuickTime, Keynote, Final Cut | `--mov` |\n| Will be re-edited or re-encoded downstream | `--prores` (large; ProRes 422 HQ) |\n| Slides, print, a doc | `--stills --scale 2` |\n\n`--mov` and `--mp4` are the same H.264 encode in different containers. The MOV\nwrapper matters because some macOS apps refuse to preview an `.mp4` inline, and\nKeynote handles `.mov` more predictably.\n\nNotes that save a re-run:\n\n- GIFs of a full 7-step sequence get large. Keep `--fps` at 15–20 and\n  `--gif-width` at ~1100, or send a video instead where the destination allows it.\n- Video wants `--fps 30`; GIF does not benefit past ~20 and just gets heavier.\n- `--no-chrome` at build time gives cleaner exports — playback controls are not\n  useful in a video. `export_frames.js` hides them anyway, but building without\n  them also reclaims the vertical space.\n- Even dimensions and `yuv420p` are non-negotiable for H.264 that opens in\n  QuickTime and Preview; the script enforces both. An odd width produces a file\n  that plays in VLC and nowhere else, which is a miserable thing to debug.\n- Stills at `--scale 2` are the right choice for slides and print.\n\n## Files\n\n```\nassets\u002F\n  engine.js        timeline engine — seekable, deterministic; do not rewrite per diagram\n  engine.css       chrome + dim\u002Fhighlight\u002Fglow states, all themable via CSS vars\n  template.html    placeholder shell that build.py fills\nscripts\u002F\n  build.py         inline SVG + steps + engine → one self-contained HTML\n  check_layers.py  pre-flight the restructured SVG (run before building)\n  export_frames.js deterministic stills \u002F GIF \u002F MP4 capture\nreferences\u002F\n  grouping.md      how to restructure an SVG into layers — read before step 2\n  steps-schema.md  the steps.json format, field by field\n  inputs.md        Mermaid, Graphviz, and PNG-fallback paths\n  theming.md       themes, CSS variable knobs, no-chrome and scrub variants\n  themes\u002Flight.css light theme\nexamples\u002F\n  steps.example.json  a complete 7-step config from a real architecture diagram\n```\n\n## Scaling the effort\n\nA 3-step process diagram is a fifteen-minute job: group, write three captions,\nbuild, check. A 12-step architecture diagram with nested panels needs real care\nin the grouping pass, and the captions become genuine technical writing.\n\nWhere the diagram covers a domain with established mechanics — an auth flow, a\ndeployment pipeline, a consensus protocol — the captions are much better when\nthey name the actual mechanism rather than paraphrasing the boxes. If something\nin the diagram is unfamiliar or the terminology is ambiguous, ask rather than\nguess: a confidently wrong caption is worse than a plain one, because the\nanimation lends it authority.\n","# Diagram Animator\n\nStatic architecture diagrams show *what exists*. They are bad at showing *what\nhappens*, because every arrow is drawn simultaneously and the reader has no idea\nwhere to start. This skill converts a diagram into a sequenced walkthrough: one\nstep at a time, the relevant arrow draws itself, the components involved light\nup, everything else recedes, and a caption explains the mechanism.\n\nThe output is a single self-contained HTML file. No build step for the viewer, no\nexternal requests, works offline, survives being emailed. Optional GIF \u002F MP4 \u002F\nPNG exports come from the same source.\n\n## The pipeline\n\n```\nsource diagram ──▶ layered SVG ──▶ steps.json ──▶ build.py ──▶ flow.html\n                       │                                          │\n                  (the real work)                        export_frames.js\n                                                                  │\n                                                     gif · mp4 · per-step stills\n```\n\nThe engine (`assets\u002Fengine.js`) is already written and general. Do not rewrite\nit per diagram — the per-diagram work is grouping the SVG and authoring the\nsteps. That split is what keeps this cheap to run repeatedly.\n\n## Workflow\n\n### 1. Get a vector source\n\nAsk for the SVG before settling for a raster. Most diagrams that arrive as a PNG\nwere exported from something, and the quality gap is large enough that one\nround-trip is worth it. If the chat uploader rejects a `.svg` attachment as an\nunprocessable image, suggest renaming it to `.svg.txt`, connecting the containing\nfolder, or pasting the source inline.\n\nFor Mermaid, Graphviz, or a raster fallback, read `references\u002Finputs.md` — it\ncovers rendering to SVG and mapping the generated ids onto the scheme below.\n\n### 2. Restructure the SVG into layers\n\nRead `references\u002Fgrouping.md` before doing this. The essential rule: every\nindependently dimmable unit becomes its own `\u003Cg class=\"layer\" id=\"...\">`, and\nthose groups are **flat siblings**, never nested — nesting multiplies opacity, so\na highlighted box inside a dimmed panel can never brighten.\n\nFlows get `id=\"f1\"..\"fN\"` on the group and `id=\"p1\"..\"pN\"` on the geometry inside.\nThe number circle and its digit go in a `\u003Cg class=\"badge\">`.\n\nGeometry is never modified. The animation is purely additive, so the static\ndiagram still renders identically.\n\nVerify before moving on:\n\n```bash\npython scripts\u002Fcheck_layers.py diagram.svg\n```\n\nIt catches nested layers, ungrouped elements that will never dim, duplicate ids,\nand flows missing their geometry — all of which are invisible until you watch the\nresult and something looks broken.\n\n### 3. Author the steps\n\nWrite `steps.json` per `references\u002Fsteps-schema.md`. Each step names the flow,\nthe layers to keep bright, an accent color matching that arrow, a short tag, a\ntitle, and a caption.\n\nThe captions are the deliverable. The animation is a delivery mechanism for an\nexplanation — if the caption only restates the arrow's own label, the whole thing\nis decoration. Read the diagram closely enough to say what actually happens at\neach hop: the protocol, the claim being checked, the component doing the work,\nwhat would break without it. Where the diagram states a design property\n(\"no standing privileges\", \"unchanged from reference arch\"), work out which step\nearns it and say so there.\n\nTwo things to get right, because they are the most common mistakes:\n\n- **Focus the containing panel alongside an inner box.** Highlighting `g-oauth`\n  without `g-vault-shell` leaves a bright box floating on an invisible panel.\n- **Match each step's `color` to its arrow's stroke.** The engine paints five\n  things from that one value; a mismatch shows up everywhere at once.\n\n### 4. Build\n\n```bash\npython scripts\u002Fbuild.py \\\n  --svg diagram.svg --steps steps.json --out flow.html \\\n  --title \"...\" --footer \"...\"\n```\n\nOptions: `--theme light`, `--theme-file brand.css`, `--no-chrome` (autoplay-only,\nfor screen recording or embedding), `--scrub` (timeline slider), `--strict`.\nSee `references\u002Ftheming.md`.\n\n### 5. Verify in a browser — always\n\nAn animation that throws on step 4 looks fine in step 1. Load it headless, check\nfor console errors, and screenshot a few steps to confirm the dimming and\nhighlighting land where intended:\n\n```bash\nnode scripts\u002Fexport_frames.js flow.html out\u002F --stills\n```\n\nThen actually look at the stills. Check that focused regions read clearly against\nthe dimmed background, that no element stayed bright because it was left out of a\nlayer, and that captions fit their box without overflowing.\n\n### 6. Deliver\n\nSend `flow.html` with `SendUserFile`. A step-through diagram is something people\nreopen and share, so also persist it with `create_artifact` when a desktop is\nconnected.\n\nIf the user wants stills, a GIF, or an MP4 — for a deck, a README, or Slack,\nwhere HTML will not embed — see **Exports** below.\n\n## Exports\n\n`scripts\u002Fexport_frames.js` drives the built HTML through its own timeline and\nscreenshots deterministically. This works because `engine.js` models the entire\nanimation as a pure function of a scalar time value, so seeking to *t* always\nproduces the identical frame regardless of machine speed.\n\n```bash\n# per-step PNGs (overview, one per step, complete)\nnode scripts\u002Fexport_frames.js flow.html out\u002F --stills --scale 2\n\n# looping GIF — Slack, README, chat\nnode scripts\u002Fexport_frames.js flow.html out\u002F --gif --fps 18 --gif-width 1100\n\n# video — much smaller and sharper than GIF, and it has a scrub bar\nnode scripts\u002Fexport_frames.js flow.html out\u002F --mp4 --fps 30   # web, Slack, PowerPoint\nnode scripts\u002Fexport_frames.js flow.html out\u002F --mov --fps 30   # QuickTime, Keynote, Final Cut\n\n# everything\nnode scripts\u002Fexport_frames.js flow.html out\u002F --stills --gif --mp4 --mov\n```\n\nRequires `playwright` (node) and, for GIF\u002Fvideo, `ffmpeg`. Without ffmpeg the raw\nframes are still written and can be encoded later.\n\n### Picking a format\n\n| Want | Use |\n|---|---|\n| Someone can click through at their own pace | the HTML — always ship this |\n| Plays inline in Slack, GitHub, chat | `--gif` |\n| Deck, email, DM, anywhere with a player | `--mp4` |\n| macOS-native — QuickTime, Keynote, Final Cut | `--mov` |\n| Will be re-edited or re-encoded downstream | `--prores` (large; ProRes 422 HQ) |\n| Slides, print, a doc | `--stills --scale 2` |\n\n`--mov` and `--mp4` are the same H.264 encode in different containers. The MOV\nwrapper matters because some macOS apps refuse to preview an `.mp4` inline, and\nKeynote handles `.mov` more predictably.\n\nNotes that save a re-run:\n\n- GIFs of a full 7-step sequence get large. Keep `--fps` at 15–20 and\n  `--gif-width` at ~1100, or send a video instead where the destination allows it.\n- Video wants `--fps 30`; GIF does not benefit past ~20 and just gets heavier.\n- `--no-chrome` at build time gives cleaner exports — playback controls are not\n  useful in a video. `export_frames.js` hides them anyway, but building without\n  them also reclaims the vertical space.\n- Even dimensions and `yuv420p` are non-negotiable for H.264 that opens in\n  QuickTime and Preview; the script enforces both. An odd width produces a file\n  that plays in VLC and nowhere else, which is a miserable thing to debug.\n- Stills at `--scale 2` are the right choice for slides and print.\n\n## Files\n\n```\nassets\u002F\n  engine.js        timeline engine — seekable, deterministic; do not rewrite per diagram\n  engine.css       chrome + dim\u002Fhighlight\u002Fglow states, all themable via CSS vars\n  template.html    placeholder shell that build.py fills\nscripts\u002F\n  build.py         inline SVG + steps + engine → one self-contained HTML\n  check_layers.py  pre-flight the restructured SVG (run before building)\n  export_frames.js deterministic stills \u002F GIF \u002F MP4 capture\nreferences\u002F\n  grouping.md      how to restructure an SVG into layers — read before step 2\n  steps-schema.md  the steps.json format, field by field\n  inputs.md        Mermaid, Graphviz, and PNG-fallback paths\n  theming.md       themes, CSS variable knobs, no-chrome and scrub variants\n  themes\u002Flight.css light theme\nexamples\u002F\n  steps.example.json  a complete 7-step config from a real architecture diagram\n```\n\n## Scaling the effort\n\nA 3-step process diagram is a fifteen-minute job: group, write three captions,\nbuild, check. A 12-step architecture diagram with nested panels needs real care\nin the grouping pass, and the captions become genuine technical writing.\n\nWhere the diagram covers a domain with established mechanics — an auth flow, a\ndeployment pipeline, a consensus protocol — the captions are much better when\nthey name the actual mechanism rather than paraphrasing the boxes. If something\nin the diagram is unfamiliar or the terminology is ambiguous, ask rather than\nguess: a confidently wrong caption is worse than a plain one, because the\nanimation lends it authority.\n",{"name":5,"description":7},"main","f27dd0e6c87efa56cfdea304aa3e89e63c02711b","plugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills","https:\u002F\u002Fgithub.com\u002Fsharepointoscar","Author | DevOps Practitioner | Docker | Terraform | Kubernetes | Jenkins X  | AWS | GCP | Azure and SP Veteran (since code-name Tahoe)","2026-11-11 12:44:52",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add sharepointoscar\u002Fagent-workflow-skills --skill diagram-animator",{"tool":37,"command":38},"bunx","bunx skills add sharepointoscar\u002Fagent-workflow-skills --skill diagram-animator",{"tool":40,"command":41},"pnpm","pnpm dlx skills add sharepointoscar\u002Fagent-workflow-skills --skill diagram-animator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002FSKILL.md",true,[45,51,57,61,67,71,75,79,83,87,91,95],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"assets\u002Fengine.css","ASSET","资产文件",5089,"https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002Fassets\u002Fengine.css",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"assets\u002Fengine.js","SCRIPT","脚本",14072,"https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002Fassets\u002Fengine.js",{"path":58,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":59,"sourceHtmlUrl":60},"assets\u002Ftemplate.html",1201,"https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002Fassets\u002Ftemplate.html",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"examples\u002Fsteps.example.json","REFERENCE","参考文档",4765,"https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002Fexamples\u002Fsteps.example.json",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fgrouping.md",4794,"https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002Freferences\u002Fgrouping.md",{"path":72,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Finputs.md",4149,"https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002Freferences\u002Finputs.md",{"path":76,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fsteps-schema.md",3514,"https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002Freferences\u002Fsteps-schema.md",{"path":80,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fthemes\u002Flight.css",653,"https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002Freferences\u002Fthemes\u002Flight.css",{"path":84,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Ftheming.md",3101,"https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002Freferences\u002Ftheming.md",{"path":88,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fbuild.py",6347,"https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002Fscripts\u002Fbuild.py",{"path":92,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fcheck_layers.py",5963,"https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002Fscripts\u002Fcheck_layers.py",{"path":96,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fexport_frames.js",9694,"https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdevopsoscar\u002Fskills\u002Fdiagram-animator\u002Fscripts\u002Fexport_frames.js",[100,107,114,121,128,135],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M79FQNYDNR7TYQAM5061GVKR","web-performance-optimization","Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fweb-performance-optimization\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M79FQK396EEGX40QA7B9S404","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M79FQFK4GJCG8HVRG8JQF4QH","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fwcag-audit-patterns\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M79FQ7WRQXC4D20Q2HTBMDG7","ui-ux-pro-max","UI\u002FUX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn\u002Fui MCP for component search and examples.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fui-ux-pro-max\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":19},"01M79FPZC11BPBWDCVK2TER0RC","stitch-ui-design","Expert guide for creating effective prompts for Google Stitch AI UI design tool. Use when user wants to design UI\u002FUX in Stitch, create app interfaces, generate mobile\u002Fweb designs, or needs help crafting Stitch prompts. Covers prompt structure, specificity techniques, iteration strategies, and design-to-code workflows for Stitch by Google.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fstitch-ui-design\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":19},"01M79FPTMMM3C57JN25RTRX2HR","scroll-experience","Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fscroll-experience\u002FSKILL.md",[],[]]