[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74J3NEVKYMPX219SCSA0B6T":3,"skill-same:01M74J3NEVKYMPX219SCSA0B6T":73},{"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":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M74J3NEVKYMPX219SCSA0B6T","infocard-creation-preview-standards",null,"Use when creating or revising infocard HTML so preview entrypoints and creation-time responsive constraints stay consistent across themes.","ccwq\u002Finfocard-pub","ccwq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3853416?v=4","01M74HXVGA6GKM3KHHE63QGM4N","Dave C","01M74HXVGWDSB69XNYE41TBQ63",2,"MIT","https:\u002F\u002Fgithub.com\u002Fccwq\u002Finfocard-pub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Finfocard-creation-preview-standards\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: infocard-creation-preview-standards\ndescription: Use when creating or revising infocard HTML so preview entrypoints and creation-time responsive constraints stay consistent across themes.\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [infocard, preview, responsive, live-server]\n    related_skills: [infocard-mobile-verifier, infocard-publish-sop]\n---\n\n# Infocard Creation & Preview Standards\n\n## Overview\n\nThis skill defines the **style-agnostic base rules** for infocard creation and preview.\n\nIt exists to keep four things stable across all infocard themes:\n\n1. the local preview entrypoint\n2. the preview URL shape\n3. responsive authoring constraints that must be handled during writing\u002Fbuilding, not only during QA\n4. the specific rule for wide tables on phone-width layouts\n\nThis skill is not a theme skill. It does not control colors, typography personality, or visual language. It controls the cross-theme creation and preview contract.\n\n## Verification Evidence Discipline\n\n- Treat static validation and visual preview as separate gates: HTML parsing, YAML parsing, forbidden-term checks, and CSS\u002Fviewport inspection do not substitute for a real browser screenshot.\n- Before claiming visual verification, confirm that the preview server actually serves the target file (HTTP status and non-empty response). If a port is occupied, inspect or choose another available port rather than assuming the existing process is healthy.\n- If browser navigation is redirected to an unrelated page or the local server returns an empty response, report visual preview as incomplete; do not present static checks as screenshot evidence.\n- Keep the deliverable usable even when preview infrastructure is unavailable: complete the HTML, run deterministic static checks, and clearly separate verified facts from unverified visual claims.\n\n## When to Use\n\nUse this skill when:\n- creating a new infocard\n- rebuilding an infocard from scratch\n- revising layout, structure, responsive behavior, or table presentation\n- previewing a card before publish\n- checking whether a layout rule belongs to creation-time standards rather than one specific theme\n\n### 重建 vs 补丁（关键区分）\n\n**触发\"重建\"（从零骨架重写）的信号**：\n- 用户明确说\"重建\"\n- 用户说\"样式存在问题\"且非单点小修复\n- HTML 文件已有多次补丁累积，结构出现裂缝（标签错位、重复闭合、空 div 残留）\n- 换主题（如从 main-style 换到 hardblue）\n\n**重建标准操作**：\n1. 读取 `theme\u002F\u003Ctheme-name>.html` 完整 CSS 骨架（不是参考 HTML 片段）\n2. 从零写 HTML，用 theme 的正式 CSS class（`.hero` \u002F `.section` \u002F `.section-no` \u002F `.card` \u002F `.risk` 等）\n3. **禁止**用 inline style 补丁代替结构重建；禁止保留旧卡换色\n4. 写完后用 Python HTMLParser 验证闭合标签\n5. 更新 `meta.yaml` 的 `date` + `updated` 为当前 Asia\u002FShanghai 时间戳\n\n**触发\"补丁\"（精准替换）的信号**：\n- 已知 HTML 结构完好，只需换文案、增删一行内容\n- meta.yaml 时间戳或字段修正\n- 关键词增删\n\n**禁止**：对结构已有裂缝的 HTML 打补丁。裂缝只能通过重建修复。\n\n## Core Standards\n\n### 0) Rule placement discipline\n\n本 skill 只负责创建阶段的通用预览面和响应式约束。真实移动端验收、截图、DOM 诊断与修复统一交给 `infocard-mobile-verifier`；发布级门禁由 `infocard-publish-sop` 和 `visual-verification-gate` 负责。不要在这里复制下游验收或发布 SOP。\n\n\n### 1) Standard local preview surface\n\nAll infocard local preview, including **PC preview and mobile preview**, should use the same LAN surface:\n\n- server: `live-server`\n- host: `0.0.0.0`\n- port: `5588`\n- preferred LAN IP: `10.6.8.14`\n- URL shape: `http:\u002F\u002F10.6.8.14:5588\u002Fdocs\u002F\u003Cslug>.html`\n\nCanonical command:\n\n```bash\nREPO_ROOT=\"$(git rev-parse --show-toplevel)\" || exit 1\ncd \"$REPO_ROOT\"\nlive-server --host=0.0.0.0 --port=5588 --no-browser .\n```\n\nRules:\n- do not switch preview conventions between PC and mobile\n- do not use old 4173\u002F4174 preview habits unless 5588 is unavailable and that exception is stated explicitly\n- do not substitute `python http.server` for the standard infocard preview workflow\n\n### 2) Preview is not mobile-only\n\nThe same preview surface is used for:\n- PC layout review\n- mobile layout review\n- screenshot verification\n- visual debugging before publish\n\nThis avoids split-brain workflows where desktop is checked in one environment and mobile in another.\n\n### 3) Responsive constraints belong in creation, not only acceptance\n\nIf a layout problem is predictable during authoring, it must be handled **while creating the card**, not postponed until the final mobile QA pass.\n\nThis especially applies to:\n- wide tables\n- multi-column blocks\n- code blocks\n- image galleries\n- dense stat grids\n\nDo not rely on final QA to discover a structural issue that should have been designed out earlier.\n\n### 3.1) Author-stage trigger declaration\n\nBefore authoring, the release bundle declares `visual_review.required` and its triggers. The Author must preserve that declaration and design the responsive behavior for every listed trigger; it cannot downgrade the card to static-only review. If the card introduces a new trigger-bearing element not listed in the bundle, report it to the main thread before handoff so the bundle\u002Fevidence plan can be updated. The handoff must identify the responsive treatment for each trigger (for example: multi-column → stack, table\u002Fcode → dedicated local horizontal scrolling, fixed control → normal flow or safe area on mobile).\n\n## Wide Table Rule\n\n### 4) Wide tables are a creation-time constraint\n\nIf a table is likely to exceed phone width, design it from the beginning with a dedicated horizontal scrolling container.\n\nThe correct strategy is:\n- keep readable column widths\n- preserve the rightmost columns\n- allow horizontal scrolling inside the table region\n\nThe wrong strategies are:\n- shrinking the entire page to force the table to fit\n- scaling\u002Fzooming the viewport to fake a pass\n- compressing columns until the text becomes unreadable\n- clipping the rightmost columns\n- replacing a structurally needed table with a broken pseudo-stack that loses comparison value\n\n### 5) Wide-table acceptance condition on mobile\n\nOn a phone-width viewport, the table passes only if:\n- the user can horizontally reach the rightmost column\n- the text remains readable\n- the table does not force the whole page into unusable overflow\n- the rest of the page layout remains stable\n\nThis rule is **style-agnostic**. It applies across infocard themes.\n\n### 6) Desktop readability rule for manual tables\n\nDo not treat horizontal scrolling as the default desktop outcome for a core reference table.\n\nIf the desktop page width can reasonably accommodate the table, prefer:\n- giving the table a full-width section\n- moving auxiliary explanation below or above the table\n- reserving split-column layouts for supporting notes rather than the main parameter matrix\n\nAvoid putting the primary parameter\u002Foptions table inside a left-right split that makes desktop users scroll sideways for information that should fit in one reading pass.\n\nMobile may still use an independent horizontal-scroll container when needed, but desktop should first try to preserve one-screen legibility for the main manual table.\n\n## Creation-stage checklist\n\n1. 在主 checkout 的 `.docs\u002F\u003Crun-id>\u002F\u003Cslug>\u002F` 创建或修订候选稿。\n2. 使用统一的 `live-server` 预览面检查桌面布局。\n3. 对宽表、代码块、多列块、图片和固定控件预先设计窄屏处理，并在交给 `infocard-mobile-verifier` 前记录处理意图。\n4. 需要移动端证据时，转交 `infocard-mobile-verifier`；本 skill 不执行移动截图或发布门禁。\n\n## Common Pitfalls\n\n1. **Treating preview as a mobile-only rule.**\n   Wrong. The live-server + LAN URL rule is for both PC and mobile preview.\n\n2. **Putting wide-table logic only into QA skills.**\n   Wrong. Wide tables are an authoring-time responsibility first, QA responsibility second.\n\n3. **Passing by shrinking the whole page.**\n   Wrong. A readable table with local horizontal scroll beats a globally shrunken page.\n\n4. **Theme leakage.**\n   Wrong. These rules belong to cross-theme creation\u002Fpreview standards, not one specific style skill.\n\n5. **Using a different local server ad hoc.**\n   Wrong. Standard infocard preview should converge on `live-server` at `10.6.8.14:5588` unless an explicit exception is documented.\n\n## References\n\n- `references\u002Fmanual-table-desktop-vs-mobile.md` — when a manual\u002Fparameter table should become full-width on desktop while preserving local horizontal scroll on mobile.\n- `references\u002Frule-placement-and-table-scope-2026-06-18.md` — why cross-theme preview rules and style-agnostic wide-table constraints belong in this umbrella skill first.\n- `references\u002Fdarkblue-theme-classes.md` — darkblue 主题 CSS class 速查（调色板、hero、card、pill、grid 布局、SVG 简图规范），含完整参考源文件路径。\n\n## Handoff checklist\n\n- [ ] Local preview uses `live-server`\n- [ ] Preview URL uses `http:\u002F\u002F10.6.8.14:5588\u002Fdocs\u002F\u003Cslug>.html`\n- [ ] 桌面预览已在统一 preview surface 完成\n- [ ] Responsive constraints were handled during creation, not deferred blindly to final QA\n- [ ] 宽表使用局部滚动容器或已设计移动 card\u002Flist 表达\n- [ ] Rule application is theme-agnostic\n\n## Deprecated compatibility entry\n\n此旧入口仅作兼容转发，替代入口为 `infocard-quality-gate`。它不得再独立宣布视觉通过或重复启动完整浏览器验收。\n","# Infocard Creation & Preview Standards\n\n## Overview\n\nThis skill defines the **style-agnostic base rules** for infocard creation and preview.\n\nIt exists to keep four things stable across all infocard themes:\n\n1. the local preview entrypoint\n2. the preview URL shape\n3. responsive authoring constraints that must be handled during writing\u002Fbuilding, not only during QA\n4. the specific rule for wide tables on phone-width layouts\n\nThis skill is not a theme skill. It does not control colors, typography personality, or visual language. It controls the cross-theme creation and preview contract.\n\n## Verification Evidence Discipline\n\n- Treat static validation and visual preview as separate gates: HTML parsing, YAML parsing, forbidden-term checks, and CSS\u002Fviewport inspection do not substitute for a real browser screenshot.\n- Before claiming visual verification, confirm that the preview server actually serves the target file (HTTP status and non-empty response). If a port is occupied, inspect or choose another available port rather than assuming the existing process is healthy.\n- If browser navigation is redirected to an unrelated page or the local server returns an empty response, report visual preview as incomplete; do not present static checks as screenshot evidence.\n- Keep the deliverable usable even when preview infrastructure is unavailable: complete the HTML, run deterministic static checks, and clearly separate verified facts from unverified visual claims.\n\n## When to Use\n\nUse this skill when:\n- creating a new infocard\n- rebuilding an infocard from scratch\n- revising layout, structure, responsive behavior, or table presentation\n- previewing a card before publish\n- checking whether a layout rule belongs to creation-time standards rather than one specific theme\n\n### 重建 vs 补丁（关键区分）\n\n**触发\"重建\"（从零骨架重写）的信号**：\n- 用户明确说\"重建\"\n- 用户说\"样式存在问题\"且非单点小修复\n- HTML 文件已有多次补丁累积，结构出现裂缝（标签错位、重复闭合、空 div 残留）\n- 换主题（如从 main-style 换到 hardblue）\n\n**重建标准操作**：\n1. 读取 `theme\u002F\u003Ctheme-name>.html` 完整 CSS 骨架（不是参考 HTML 片段）\n2. 从零写 HTML，用 theme 的正式 CSS class（`.hero` \u002F `.section` \u002F `.section-no` \u002F `.card` \u002F `.risk` 等）\n3. **禁止**用 inline style 补丁代替结构重建；禁止保留旧卡换色\n4. 写完后用 Python HTMLParser 验证闭合标签\n5. 更新 `meta.yaml` 的 `date` + `updated` 为当前 Asia\u002FShanghai 时间戳\n\n**触发\"补丁\"（精准替换）的信号**：\n- 已知 HTML 结构完好，只需换文案、增删一行内容\n- meta.yaml 时间戳或字段修正\n- 关键词增删\n\n**禁止**：对结构已有裂缝的 HTML 打补丁。裂缝只能通过重建修复。\n\n## Core Standards\n\n### 0) Rule placement discipline\n\n本 skill 只负责创建阶段的通用预览面和响应式约束。真实移动端验收、截图、DOM 诊断与修复统一交给 `infocard-mobile-verifier`；发布级门禁由 `infocard-publish-sop` 和 `visual-verification-gate` 负责。不要在这里复制下游验收或发布 SOP。\n\n\n### 1) Standard local preview surface\n\nAll infocard local preview, including **PC preview and mobile preview**, should use the same LAN surface:\n\n- server: `live-server`\n- host: `0.0.0.0`\n- port: `5588`\n- preferred LAN IP: `10.6.8.14`\n- URL shape: `http:\u002F\u002F10.6.8.14:5588\u002Fdocs\u002F\u003Cslug>.html`\n\nCanonical command:\n\n```bash\nREPO_ROOT=\"$(git rev-parse --show-toplevel)\" || exit 1\ncd \"$REPO_ROOT\"\nlive-server --host=0.0.0.0 --port=5588 --no-browser .\n```\n\nRules:\n- do not switch preview conventions between PC and mobile\n- do not use old 4173\u002F4174 preview habits unless 5588 is unavailable and that exception is stated explicitly\n- do not substitute `python http.server` for the standard infocard preview workflow\n\n### 2) Preview is not mobile-only\n\nThe same preview surface is used for:\n- PC layout review\n- mobile layout review\n- screenshot verification\n- visual debugging before publish\n\nThis avoids split-brain workflows where desktop is checked in one environment and mobile in another.\n\n### 3) Responsive constraints belong in creation, not only acceptance\n\nIf a layout problem is predictable during authoring, it must be handled **while creating the card**, not postponed until the final mobile QA pass.\n\nThis especially applies to:\n- wide tables\n- multi-column blocks\n- code blocks\n- image galleries\n- dense stat grids\n\nDo not rely on final QA to discover a structural issue that should have been designed out earlier.\n\n### 3.1) Author-stage trigger declaration\n\nBefore authoring, the release bundle declares `visual_review.required` and its triggers. The Author must preserve that declaration and design the responsive behavior for every listed trigger; it cannot downgrade the card to static-only review. If the card introduces a new trigger-bearing element not listed in the bundle, report it to the main thread before handoff so the bundle\u002Fevidence plan can be updated. The handoff must identify the responsive treatment for each trigger (for example: multi-column → stack, table\u002Fcode → dedicated local horizontal scrolling, fixed control → normal flow or safe area on mobile).\n\n## Wide Table Rule\n\n### 4) Wide tables are a creation-time constraint\n\nIf a table is likely to exceed phone width, design it from the beginning with a dedicated horizontal scrolling container.\n\nThe correct strategy is:\n- keep readable column widths\n- preserve the rightmost columns\n- allow horizontal scrolling inside the table region\n\nThe wrong strategies are:\n- shrinking the entire page to force the table to fit\n- scaling\u002Fzooming the viewport to fake a pass\n- compressing columns until the text becomes unreadable\n- clipping the rightmost columns\n- replacing a structurally needed table with a broken pseudo-stack that loses comparison value\n\n### 5) Wide-table acceptance condition on mobile\n\nOn a phone-width viewport, the table passes only if:\n- the user can horizontally reach the rightmost column\n- the text remains readable\n- the table does not force the whole page into unusable overflow\n- the rest of the page layout remains stable\n\nThis rule is **style-agnostic**. It applies across infocard themes.\n\n### 6) Desktop readability rule for manual tables\n\nDo not treat horizontal scrolling as the default desktop outcome for a core reference table.\n\nIf the desktop page width can reasonably accommodate the table, prefer:\n- giving the table a full-width section\n- moving auxiliary explanation below or above the table\n- reserving split-column layouts for supporting notes rather than the main parameter matrix\n\nAvoid putting the primary parameter\u002Foptions table inside a left-right split that makes desktop users scroll sideways for information that should fit in one reading pass.\n\nMobile may still use an independent horizontal-scroll container when needed, but desktop should first try to preserve one-screen legibility for the main manual table.\n\n## Creation-stage checklist\n\n1. 在主 checkout 的 `.docs\u002F\u003Crun-id>\u002F\u003Cslug>\u002F` 创建或修订候选稿。\n2. 使用统一的 `live-server` 预览面检查桌面布局。\n3. 对宽表、代码块、多列块、图片和固定控件预先设计窄屏处理，并在交给 `infocard-mobile-verifier` 前记录处理意图。\n4. 需要移动端证据时，转交 `infocard-mobile-verifier`；本 skill 不执行移动截图或发布门禁。\n\n## Common Pitfalls\n\n1. **Treating preview as a mobile-only rule.**\n   Wrong. The live-server + LAN URL rule is for both PC and mobile preview.\n\n2. **Putting wide-table logic only into QA skills.**\n   Wrong. Wide tables are an authoring-time responsibility first, QA responsibility second.\n\n3. **Passing by shrinking the whole page.**\n   Wrong. A readable table with local horizontal scroll beats a globally shrunken page.\n\n4. **Theme leakage.**\n   Wrong. These rules belong to cross-theme creation\u002Fpreview standards, not one specific style skill.\n\n5. **Using a different local server ad hoc.**\n   Wrong. Standard infocard preview should converge on `live-server` at `10.6.8.14:5588` unless an explicit exception is documented.\n\n## References\n\n- `references\u002Fmanual-table-desktop-vs-mobile.md` — when a manual\u002Fparameter table should become full-width on desktop while preserving local horizontal scroll on mobile.\n- `references\u002Frule-placement-and-table-scope-2026-06-18.md` — why cross-theme preview rules and style-agnostic wide-table constraints belong in this umbrella skill first.\n- `references\u002Fdarkblue-theme-classes.md` — darkblue 主题 CSS class 速查（调色板、hero、card、pill、grid 布局、SVG 简图规范），含完整参考源文件路径。\n\n## Handoff checklist\n\n- [ ] Local preview uses `live-server`\n- [ ] Preview URL uses `http:\u002F\u002F10.6.8.14:5588\u002Fdocs\u002F\u003Cslug>.html`\n- [ ] 桌面预览已在统一 preview surface 完成\n- [ ] Responsive constraints were handled during creation, not deferred blindly to final QA\n- [ ] 宽表使用局部滚动容器或已设计移动 card\u002Flist 表达\n- [ ] Rule application is theme-agnostic\n\n## Deprecated compatibility entry\n\n此旧入口仅作兼容转发，替代入口为 `infocard-quality-gate`。它不得再独立宣布视觉通过或重复启动完整浏览器验收。\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"description":7},"Hermes Agent","1.0.0",{"hermes":27},{"tags":28,"related_skills":33},[29,30,31,32],"infocard","preview","responsive","live-server",[34,35],"infocard-mobile-verifier","infocard-publish-sop","main","4ea40456a3623e494105429a3ae13c3ff61f17f5",".agents\u002Fskills\u002Fproductivity\u002Finfocard-creation-preview-standards",1,"https:\u002F\u002Fgithub.com\u002Fccwq\u002Finfocard-pub","https:\u002F\u002Fccwq.github.io\u002Finfocard-pub\u002F","https:\u002F\u002Fgithub.com\u002Fccwq","丐帮37代iphone","2026-11-12 20:21:30",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add ccwq\u002Finfocard-pub --skill infocard-creation-preview-standards",{"tool":51,"command":52},"bunx","bunx skills add ccwq\u002Finfocard-pub --skill infocard-creation-preview-standards",{"tool":54,"command":55},"pnpm","pnpm dlx skills add ccwq\u002Finfocard-pub --skill infocard-creation-preview-standards","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fccwq\u002Finfocard-pub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Finfocard-creation-preview-standards\u002FSKILL.md",true,[59,65,69],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fdarkblue-theme-classes.md","REFERENCE","参考文档",4071,"https:\u002F\u002Fgithub.com\u002Fccwq\u002Finfocard-pub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Finfocard-creation-preview-standards\u002Freferences\u002Fdarkblue-theme-classes.md",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fmanual-table-desktop-vs-mobile.md",1629,"https:\u002F\u002Fgithub.com\u002Fccwq\u002Finfocard-pub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Finfocard-creation-preview-standards\u002Freferences\u002Fmanual-table-desktop-vs-mobile.md",{"path":70,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Frule-placement-and-table-scope-2026-06-18.md",1258,"https:\u002F\u002Fgithub.com\u002Fccwq\u002Finfocard-pub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Finfocard-creation-preview-standards\u002Freferences\u002Frule-placement-and-table-scope-2026-06-18.md",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M74J5D6V3BJYVJXMMXVJ8H30","authorized-infocard-execution","Use for authorized infocard runs after tool failures.","https:\u002F\u002Fgithub.com\u002Fccwq\u002Finfocard-pub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpublishing\u002Fauthorized-infocard-execution\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M74J5A599BH65TWJZDMTF07S","web-capture","Use when a web page needs screenshots or device simulation. Capture desktop, mobile, and tablet screenshots via agent-browser and return auditable image paths.","https:\u002F\u002Fgithub.com\u002Fccwq\u002Finfocard-pub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Fweb-capture\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M74J50DVMHVKYQHC112CYR4K","infocard-x-content-tracing","X content to upstream project\u002Fauthor tracing.","https:\u002F\u002Fgithub.com\u002Fccwq\u002Finfocard-pub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Finfocard-x-content-tracing\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M74J4WVB5QEJ23QKXKHWT6DK","infocard-visual-pass-loop","Screenshot-and-fix loop when 200 passes but theme is broken.","https:\u002F\u002Fgithub.com\u002Fccwq\u002Finfocard-pub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Finfocard-visual-pass-loop\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M74J4SF3YN9G53QCRXNNE4CV","infocard-topic-selection","Use when selecting or evaluating information-card topics from the user's profile or explicitly supplied themes; judge value and visual expression potential without choosing a concrete infocard theme or publishing.","https:\u002F\u002Fgithub.com\u002Fccwq\u002Finfocard-pub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Finfocard-topic-selection\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M74J4KRQYFGM4ZJRRGRV90VE","infocard-theme-validation","Use when changing infocard theme CSS or pushing docs.","https:\u002F\u002Fgithub.com\u002Fccwq\u002Finfocard-pub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Finfocard-theme-validation\u002FSKILL.md",[],[]]