[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M753RWTYDPR3DCVWG80W1S03":3,"skill-same:01M753RWTYDPR3DCVWG80W1S03":130},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M753RWTYDPR3DCVWG80W1S03","visual-explainer",null,"Generate self-contained HTML visual explanations for systems, code changes, plans, data, and technical concepts. Use for diagrams, architecture overviews, diff or plan reviews, project recaps, comparison tables, slide decks, and other visual explanations.","haryelramalho\u002Fskills","haryelramalho","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F38708454?v=4","01M753ESC6XNS6GXGV5X9YMKGA","Haryel Ramalho","01M753ESCSPRNDTEJRVRYY1VJ0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: visual-explainer\ndescription: Generate self-contained HTML visual explanations for systems, code changes, plans, data, and technical concepts. Use for diagrams, architecture overviews, diff or plan reviews, project recaps, comparison tables, slide decks, and other visual explanations.\nlicense: MIT\ncompatibility: Requires a browser to view generated HTML files. Optional surf-cli for AI image generation.\nmetadata:\n  author: nicobailon\n  version: \"0.8.1\"\n---\n\n# Visual Explainer\n\nGenerate self-contained HTML pages that explain systems, code changes, plans, data, and technical concepts visually. Use this skill for diagram requests, architecture overviews, diff\u002Fplan reviews, project recaps, comparison tables, slide decks, and any visual explanation.\n\n## Trigger and delivery rules\n\n- Prefer an HTML page over terminal ASCII when the output is inherently visual.\n- If a table would have 4+ rows or 3+ columns, render it as HTML and give only a short chat summary.\n- Write files to `~\u002F.agent\u002Fdiagrams\u002F` or the explicit eval output path. Use descriptive filenames.\n- Open generated pages in the browser when running normally. In Pi package installs, use `visual_explainer` with `prepare` for planning\u002Fcontext and `render` only after the complete HTML document exists.\n- The final page must be a complete self-contained HTML document, including embedded CSS and any needed JS.\n\n## Reference routing\n\nRead only the references needed for the current output:\n\n| Need | Read |\n|---|---|\n| Text-heavy architecture\u002Fcards | `.\u002Ftemplates\u002Farchitecture.html` |\n| Mermaid flowcharts, sequence, ER, state, class, C4, data flow | `.\u002Ftemplates\u002Fmermaid-flowchart.html`, Mermaid sections in `.\u002Freferences\u002Flibraries.md` |\n| Data tables, comparisons, audits | `.\u002Ftemplates\u002Fdata-table.html` |\n| Slide decks | `.\u002Ftemplates\u002Fslide-deck.html`, `.\u002Freferences\u002Fslide-patterns.md` |\n| CSS layout, overflow, depth, collapsibles, SVG connectors, generated images | `.\u002Freferences\u002Fcss-patterns.md` |\n| Pages with 4+ major sections | `.\u002Freferences\u002Fresponsive-nav.md` |\n| Prose-heavy pages | “Prose Page Elements” in `css-patterns.md`, typography sections in `libraries.md` |\n\n## Choose the representation\n\n| Content | Default representation |\n|---|---|\n| Flowchart, pipeline, state machine, decision tree | Mermaid |\n| Sequence, ER\u002Fschema, class, C4, topology-focused architecture | Mermaid |\n| Text-heavy architecture, module internals, implementation plans | CSS grid cards, optionally with a Mermaid overview |\n| 15+ element architecture | Hybrid: small Mermaid overview + CSS detail cards |\n| Comparison\u002Faudit\u002Fstatus matrix | Semantic HTML `\u003Ctable>` |\n| Timeline\u002Froadmap | CSS timeline |\n| Dashboard\u002Fmetrics | CSS grid + charts\u002FKPIs |\n| Slide deck | `100dvh` slides using slide template patterns |\n\n## Mermaid invariants\n\n- Use `theme: 'base'` with custom `themeVariables` matching the page palette.\n- For complex diagrams use ELK layout when available.\n- Never use bare `\u003Cpre class=\"mermaid\">`.\n- Use the canonical `diagram-shell` pattern from `templates\u002Fmermaid-flowchart.html`: `.diagram-shell` > `.mermaid-wrap` > `.zoom-controls` + `.mermaid-viewport` > `.mermaid-canvas`.\n- Every Mermaid diagram needs zoom in\u002Fout\u002Freset\u002Fexpand controls, Ctrl\u002FCmd+scroll zoom, drag panning, and click-to-expand.\n- Prefer `flowchart TD` for complex diagrams. Use `LR` only for simple 3–4 node linear flows.\n- Use `\u003Cbr\u002F>` in quoted flowchart labels. Do not use escaped `\\n` labels.\n- Never define page-level `.node`; Mermaid uses it internally. Use namespaced page classes such as `.ve-card`.\n- For 15+ elements, do not cram everything into one Mermaid diagram. Use the hybrid overview + cards pattern.\n\n## Layout and style invariants\n\n- Use semantic HTML where it helps accessibility and copy\u002Fpaste: `\u003Ctable>`, headings, lists, `\u003Cdetails>`, captions.\n- Use CSS custom properties for palette: `--bg`, `--surface`, `--border`, `--text`, `--text-dim`, and 3–5 accents.\n- Pick a clear aesthetic direction before writing: blueprint, editorial, paper\u002Fink, terminal, IDE-inspired, or data-dense.\n- Avoid generic defaults: no body font that is only Inter, Roboto, Arial, Helvetica, or system-ui; no violet\u002Ffuchsia Tailwind-default accents as the main palette (`#8b5cf6`, `#7c3aed`, `#a78bfa`, `#d946ef`); no cyan+magenta+purple neon dashboard; no gradient-mesh blobs.\n- Good font pair families: DM Sans + Fira Code; Instrument Serif + JetBrains Mono; IBM Plex Sans + IBM Plex Mono; Bricolage Grotesque + Fragment Mono; Plus Jakarta Sans + Azeret Mono.\n- Good accent directions: terracotta+sage, teal+slate, rose+cranberry, amber+emerald, deep blue+gold.\n- Prevent overflow: `min-width: 0` on grid\u002Fflex children, `overflow-wrap: break-word` for long text, and scroll containers for wide tables\u002Fcode.\n- Do not set `display: flex` directly on `\u003Cli>` when list markers matter.\n- Use depth sparingly: hero\u002Felevated only for primary sections; flat\u002Frecessed for reference material.\n- Use entrance\u002Fhover animation only when it clarifies hierarchy. Respect `prefers-reduced-motion`. Do not use continuous glow, pulse, or breathing effects on static content.\n\n## Slide deck mode\n\nUse slides only when explicitly requested or when a command asks for slides. Slides are a different medium, not a paginated article:\n\n- Each slide is one viewport (`100dvh`) with no page-level scrolling.\n- Use larger type, fewer objects per slide, varied compositions, and visible navigation.\n- Include slide nav chrome from `slide-deck.html`: prev\u002Fnext controls, slide count, keyboard navigation, and carousel dots\u002Findicators.\n- Before writing HTML, inventory the source and map every source item to slides.\n- Do not drop content to fit a fixed slide count. Add slides instead.\n- Use the 10 slide types from `slide-patterns.md`: Title, Section Divider, Content, Split, Diagram, Dashboard, Table, Code, Quote, Full-Bleed.\n\n## Optional generated images\n\nIf `surf` is available, generated images may be embedded as base64 for hero banners, conceptual illustrations, or educational visuals. Skip images for data-heavy, structural, or Mermaid\u002FCSS-suitable content. Pages must stand on CSS, typography, and diagrams without images.\n\n## Final checklist\n\nBefore delivery, verify:\n\n- complete HTML document;\n- output written to the requested path;\n- no console errors when opened;\n- no horizontal overflow at normal desktop width;\n- fonts load with fallbacks;\n- tables preserve rows\u002Fcolumns and wrap long text;\n- Mermaid diagrams use `diagram-shell` with zoom\u002Fpan\u002Fexpand;\n- slides fit one viewport, include carousel dots, and preserve source coverage;\n- visual hierarchy makes the main idea obvious in the first viewport;\n- styling would still be recognizable if compared against a generic dark\u002Fviolet template.\n","# Visual Explainer\n\nGenerate self-contained HTML pages that explain systems, code changes, plans, data, and technical concepts visually. Use this skill for diagram requests, architecture overviews, diff\u002Fplan reviews, project recaps, comparison tables, slide decks, and any visual explanation.\n\n## Trigger and delivery rules\n\n- Prefer an HTML page over terminal ASCII when the output is inherently visual.\n- If a table would have 4+ rows or 3+ columns, render it as HTML and give only a short chat summary.\n- Write files to `~\u002F.agent\u002Fdiagrams\u002F` or the explicit eval output path. Use descriptive filenames.\n- Open generated pages in the browser when running normally. In Pi package installs, use `visual_explainer` with `prepare` for planning\u002Fcontext and `render` only after the complete HTML document exists.\n- The final page must be a complete self-contained HTML document, including embedded CSS and any needed JS.\n\n## Reference routing\n\nRead only the references needed for the current output:\n\n| Need | Read |\n|---|---|\n| Text-heavy architecture\u002Fcards | `.\u002Ftemplates\u002Farchitecture.html` |\n| Mermaid flowcharts, sequence, ER, state, class, C4, data flow | `.\u002Ftemplates\u002Fmermaid-flowchart.html`, Mermaid sections in `.\u002Freferences\u002Flibraries.md` |\n| Data tables, comparisons, audits | `.\u002Ftemplates\u002Fdata-table.html` |\n| Slide decks | `.\u002Ftemplates\u002Fslide-deck.html`, `.\u002Freferences\u002Fslide-patterns.md` |\n| CSS layout, overflow, depth, collapsibles, SVG connectors, generated images | `.\u002Freferences\u002Fcss-patterns.md` |\n| Pages with 4+ major sections | `.\u002Freferences\u002Fresponsive-nav.md` |\n| Prose-heavy pages | “Prose Page Elements” in `css-patterns.md`, typography sections in `libraries.md` |\n\n## Choose the representation\n\n| Content | Default representation |\n|---|---|\n| Flowchart, pipeline, state machine, decision tree | Mermaid |\n| Sequence, ER\u002Fschema, class, C4, topology-focused architecture | Mermaid |\n| Text-heavy architecture, module internals, implementation plans | CSS grid cards, optionally with a Mermaid overview |\n| 15+ element architecture | Hybrid: small Mermaid overview + CSS detail cards |\n| Comparison\u002Faudit\u002Fstatus matrix | Semantic HTML `\u003Ctable>` |\n| Timeline\u002Froadmap | CSS timeline |\n| Dashboard\u002Fmetrics | CSS grid + charts\u002FKPIs |\n| Slide deck | `100dvh` slides using slide template patterns |\n\n## Mermaid invariants\n\n- Use `theme: 'base'` with custom `themeVariables` matching the page palette.\n- For complex diagrams use ELK layout when available.\n- Never use bare `\u003Cpre class=\"mermaid\">`.\n- Use the canonical `diagram-shell` pattern from `templates\u002Fmermaid-flowchart.html`: `.diagram-shell` > `.mermaid-wrap` > `.zoom-controls` + `.mermaid-viewport` > `.mermaid-canvas`.\n- Every Mermaid diagram needs zoom in\u002Fout\u002Freset\u002Fexpand controls, Ctrl\u002FCmd+scroll zoom, drag panning, and click-to-expand.\n- Prefer `flowchart TD` for complex diagrams. Use `LR` only for simple 3–4 node linear flows.\n- Use `\u003Cbr\u002F>` in quoted flowchart labels. Do not use escaped `\\n` labels.\n- Never define page-level `.node`; Mermaid uses it internally. Use namespaced page classes such as `.ve-card`.\n- For 15+ elements, do not cram everything into one Mermaid diagram. Use the hybrid overview + cards pattern.\n\n## Layout and style invariants\n\n- Use semantic HTML where it helps accessibility and copy\u002Fpaste: `\u003Ctable>`, headings, lists, `\u003Cdetails>`, captions.\n- Use CSS custom properties for palette: `--bg`, `--surface`, `--border`, `--text`, `--text-dim`, and 3–5 accents.\n- Pick a clear aesthetic direction before writing: blueprint, editorial, paper\u002Fink, terminal, IDE-inspired, or data-dense.\n- Avoid generic defaults: no body font that is only Inter, Roboto, Arial, Helvetica, or system-ui; no violet\u002Ffuchsia Tailwind-default accents as the main palette (`#8b5cf6`, `#7c3aed`, `#a78bfa`, `#d946ef`); no cyan+magenta+purple neon dashboard; no gradient-mesh blobs.\n- Good font pair families: DM Sans + Fira Code; Instrument Serif + JetBrains Mono; IBM Plex Sans + IBM Plex Mono; Bricolage Grotesque + Fragment Mono; Plus Jakarta Sans + Azeret Mono.\n- Good accent directions: terracotta+sage, teal+slate, rose+cranberry, amber+emerald, deep blue+gold.\n- Prevent overflow: `min-width: 0` on grid\u002Fflex children, `overflow-wrap: break-word` for long text, and scroll containers for wide tables\u002Fcode.\n- Do not set `display: flex` directly on `\u003Cli>` when list markers matter.\n- Use depth sparingly: hero\u002Felevated only for primary sections; flat\u002Frecessed for reference material.\n- Use entrance\u002Fhover animation only when it clarifies hierarchy. Respect `prefers-reduced-motion`. Do not use continuous glow, pulse, or breathing effects on static content.\n\n## Slide deck mode\n\nUse slides only when explicitly requested or when a command asks for slides. Slides are a different medium, not a paginated article:\n\n- Each slide is one viewport (`100dvh`) with no page-level scrolling.\n- Use larger type, fewer objects per slide, varied compositions, and visible navigation.\n- Include slide nav chrome from `slide-deck.html`: prev\u002Fnext controls, slide count, keyboard navigation, and carousel dots\u002Findicators.\n- Before writing HTML, inventory the source and map every source item to slides.\n- Do not drop content to fit a fixed slide count. Add slides instead.\n- Use the 10 slide types from `slide-patterns.md`: Title, Section Divider, Content, Split, Diagram, Dashboard, Table, Code, Quote, Full-Bleed.\n\n## Optional generated images\n\nIf `surf` is available, generated images may be embedded as base64 for hero banners, conceptual illustrations, or educational visuals. Skip images for data-heavy, structural, or Mermaid\u002FCSS-suitable content. Pages must stand on CSS, typography, and diagrams without images.\n\n## Final checklist\n\nBefore delivery, verify:\n\n- complete HTML document;\n- output written to the requested path;\n- no console errors when opened;\n- no horizontal overflow at normal desktop width;\n- fonts load with fallbacks;\n- tables preserve rows\u002Fcolumns and wrap long text;\n- Mermaid diagrams use `diagram-shell` with zoom\u002Fpan\u002Fexpand;\n- slides fit one viewport, include carousel dots, and preserve source coverage;\n- visual hierarchy makes the main idea obvious in the first viewport;\n- styling would still be recognizable if compared against a generic dark\u002Fviolet template.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":27},{"author":25,"version":26},"nicobailon","0.8.1","Requires a browser to view generated HTML files. Optional surf-cli for AI image generation.","main","a5b533be2d244bbf3e5606e851742f0e0ba99423","skills\u002Fcommunity\u002Fvisual-explainer","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills","https:\u002F\u002Fgithub.com\u002Fharyelramalho","linkedin.com\u002Fin\u002Fharyelramalho\u002F","Software Engineer @ SKORR •  Former Vice President of the Junior Computer Association - TecnoJr","2026-07-16 01:34:58",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add haryelramalho\u002Fskills --skill visual-explainer",{"tool":42,"command":43},"bunx","bunx skills add haryelramalho\u002Fskills --skill visual-explainer",{"tool":45,"command":46},"pnpm","pnpm dlx skills add haryelramalho\u002Fskills --skill visual-explainer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002FSKILL.md",true,[50,56,60,64,68,72,76,80,84,88,94,98,102,106,110,114,118,122,126],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},".claude-plugin\u002Fplugin.json","REFERENCE","参考文档",301,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002F.claude-plugin\u002Fplugin.json",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"commands\u002Fdiff-review.md",1941,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Fcommands\u002Fdiff-review.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"commands\u002Ffact-check.md",1129,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Fcommands\u002Ffact-check.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"commands\u002Fgenerate-slides.md",952,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Fcommands\u002Fgenerate-slides.md",{"path":69,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":70,"sourceHtmlUrl":71},"commands\u002Fgenerate-visual-plan.md",1300,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Fcommands\u002Fgenerate-visual-plan.md",{"path":73,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":74,"sourceHtmlUrl":75},"commands\u002Fgenerate-web-diagram.md",699,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Fcommands\u002Fgenerate-web-diagram.md",{"path":77,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":78,"sourceHtmlUrl":79},"commands\u002Fplan-review.md",1682,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Fcommands\u002Fplan-review.md",{"path":81,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":82,"sourceHtmlUrl":83},"commands\u002Fproject-recap.md",1424,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Fcommands\u002Fproject-recap.md",{"path":85,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":86,"sourceHtmlUrl":87},"commands\u002Fshare.md",1412,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Fcommands\u002Fshare.md",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"extension.ts","SCRIPT","脚本",13003,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Fextension.ts",{"path":95,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fcss-patterns.md",45264,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Freferences\u002Fcss-patterns.md",{"path":99,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Flibraries.md",21344,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Freferences\u002Flibraries.md",{"path":103,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fresponsive-nav.md",5817,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Freferences\u002Fresponsive-nav.md",{"path":107,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fslide-patterns.md",45199,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Freferences\u002Fslide-patterns.md",{"path":111,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":112,"sourceHtmlUrl":113},"scripts\u002Fshare.sh",2086,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Fscripts\u002Fshare.sh",{"path":115,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":116,"sourceHtmlUrl":117},"templates\u002Farchitecture.html",17466,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Ftemplates\u002Farchitecture.html",{"path":119,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":120,"sourceHtmlUrl":121},"templates\u002Fdata-table.html",16248,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Ftemplates\u002Fdata-table.html",{"path":123,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":124,"sourceHtmlUrl":125},"templates\u002Fmermaid-flowchart.html",21663,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Ftemplates\u002Fmermaid-flowchart.html",{"path":127,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":128,"sourceHtmlUrl":129},"templates\u002Fslide-deck.html",35558,"https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcommunity\u002Fvisual-explainer\u002Ftemplates\u002Fslide-deck.html",[131,138,145,152,159,166],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":19},"01M753YDMKSDB7320THEQ2CVW5","to-prompt-opus","Use when preparing or rewriting prompts for Claude Opus 4.8, Anthropic API agents, XML-structured prompts, long-context document work, coding agents, research synthesis, frontend\u002Fdesign tasks, or model-specific prompt optimization. Do not use for GPT\u002FOpenAI prompts or raw context packaging without Opus-specific tuning.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fto-prompt-opus\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":19},"01M753YAP95W4K2MCEAEEAV6YA","to-prompt-gpt","Use when preparing or rewriting prompts for GPT-5.5, OpenAI API agents, Responses workflows, coding agents, research synthesis, support assistants, or model-specific prompt optimization. Do not use for Claude\u002FOpus prompts or raw context packaging without GPT-specific tuning.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fto-prompt-gpt\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":19},"01M753Y700AZ0GVJDNW9Q1Q54F","plan-refactor-qa","Plans and runs qa-report before executing Compozy refactor tasks. Use when the user provides a refactor or issue slug and wants Codex to inspect the matching .compozy\u002Ftasks directory, related PRD\u002FTechSpec\u002FADR\u002Ftask artifacts, affected code, and existing tests, then invoke $qa-report with a repository-grounded prompt. Do not use to run tests, execute qa-execution, implement code, or perform post-refactor verification.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fplan-refactor-qa\u002FSKILL.md",[],[],{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":19},"01M753XZENG0Z8S2ET75EM8CGB","multi-tool-branch-review","Orchestrates a multi-tool branch review of the current git branch against a base branch. By default it runs two independent thermo-nuclear maintainability audits, one on Codex GPT-5.5 xhigh and one on Claude Opus xhigh, then consolidates the findings into a single remediation plan via writing-plans. If the user explicitly asks for native reviews, it can add the Claude native review pass, the Codex native review pass, or both. Use when the user wants a deep cross-model review of a branch or PR before merge, or asks to review this branch with multiple tools or models. Encodes known infra failure modes and their fixes (missing Claude ACP adapter, Codex MCP auth hangs, false-positive report files, long jobs orphaned inside subagents). Do not use for reviewing a single uncommitted snippet, for non-git work, for running only one reviewer, or when the user only wants a quick lint or test run.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fmulti-tool-branch-review\u002FSKILL.md",[],[],{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":19},"01M753XQM40XCK55BH5WPA88EW","create-pr-with-template","Create a GitHub Pull Request with gh CLI and prefer repository PR templates automatically. Use this whenever the user asks to open\u002Fcreate a PR, especially when template compliance is needed. If multiple templates exist, ask the user which template to use.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmine\u002Fcreate-pr-with-template\u002FSKILL.md",[],[],{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":19},"01M753XJMBJ8VFPRCDCC1JJ9G4","ui-craft","Provides guardrails for user-facing UI work: usability heuristics, accessibility floors, design-system discipline, component states, microcopy, motion, dark mode, responsive behavior, and human-AI UX. Use when designing, generating, reviewing, or refactoring visible product surfaces such as components, pages, dashboards, forms, dialogs, loading\u002Fempty\u002Ferror states, or AI interfaces. Do not use for backend-only work, infrastructure, CLI\u002FTUI design, or pure documentation editing.","https:\u002F\u002Fgithub.com\u002Fharyelramalho\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated\u002Fui-craft\u002FSKILL.md",[],[]]