[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74HZ1Z90KEBHT277H77TGDM":3,"skill-same:01M74HZ1Z90KEBHT277H77TGDM":63},{"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":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M74HZ1Z90KEBHT277H77TGDM","infocard-layout-debugging",null,"Fix misplaced infocard grid elements.","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\u002Fcontent\u002Finfocard-layout-debugging\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: infocard-layout-debugging\ndescription: Fix misplaced infocard grid elements.\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [infocard, css, grid, responsive, visual-debugging, publishing]\n    related_skills: [infocard-style-man-skill, infocard-crayon-style, web-visual-acceptance, infocard-mobile-verifier]\n---\n\n# infocard-layout-debugging\n\n信息卡主题布局调试与视觉验收技能。用于处理编号、时间轴、正文列、装饰线、响应式布局与线上缓存之间的错位问题。\n\n## 触发条件\n\n- 用户指出编号跑到右侧、正文被挤窄、时间轴错位或移动端布局异常。\n- CSS 已声明 `grid-column`，但截图仍显示元素位置错误。\n- 本地、CDN 与用户截图的视觉结果不一致。\n- 主题改造涉及 poster-shell、timeline、编号列或移动端断点。\n\n## 核心原则\n\n1. **先查 DOM 层级，再改 CSS。** `grid-column` 只对当前 grid 容器的直接 grid item 生效；嵌套元素不能跨越父子层级参与祖先 grid。\n2. **结构优先于视觉补丁。** 不要先用 `position:absolute` 把错误嵌套的元素“拉回”目标位置；应优先修复组件骨架。\n3. **线上事实优先于截图猜测。** 先抓取线上 HTML\u002FCSS，确认部署版本和 DOM 顺序，再使用截图或视觉模型分析。\n4. **桌面与移动端必须成对验证。** 编号列宽度、编号宽度、时间轴 left 偏移和正文 padding 必须同步更新。\n5. **主题必须保持泛化。** 修复应落在组件骨架、token 和响应式规则，不得绑定某一张卡片的固定内容。\n6. **视觉完成 ≠ 几何数据完成。** 用户已明确指出：仅靠 DOM rect、CSS computed style、`getBoundingClientRect` 一致等几何证据，不能算\"视觉验收通过\"。修复后必须用 Playwright 抓桌面 + 移动端双视口截图，再用 `vision_analyze` 给出每张图的 issues \u002F score。任何修复只要缺截图复审，就不允许在交付报告里宣称\"完成\"。\n\n## 标准组件骨架\n\n```html\n\u003Cdiv class=\"skill-card\">\n  \u003Cdiv class=\"card-stripe blue\">\u003C\u002Fdiv>\n  \u003Cdiv class=\"card-num blue\">01\u003C\u002Fdiv>\n  \u003Cdiv class=\"card-body\">\n    \u003Cdiv class=\"card-icon\" aria-hidden=\"true\">🧬\u003C\u002Fdiv>\n    \u003Ch3 class=\"card-title\">标题\u003C\u002Fh3>\n    \u003Cp class=\"card-desc\">正文\u003C\u002Fp>\n    \u003Cdiv class=\"card-tags\">标签\u003C\u002Fdiv>\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\n`.card-num` 与 `.card-stripe` 必须是 `.skill-card` 的直接子级；`.card-body` 必须显式声明 `grid-column:2`。\n\n```css\n.skill-card {\n  position: relative;\n  display: grid;\n  grid-template-columns: 76px 1fr;\n}\n.card-num { grid-column: 1; grid-row: 1; }\n.card-body { grid-column: 2; grid-row: 1; min-width: 0; }\n.card-stripe { position: absolute; left: 72px; }\n```\n\n## 调试流程\n\n### 白色空隙与浅色边缘\n\n先确认实际预览\u002F发布的文件路径，尤其要区分 `theme\u002F`、`dist\u002F` 与同名旧模板；不要把截图中的浅色边缘直接归因于浏览器默认 margin。检查 `html, body, main, .poster-shell` 的 margin、padding、background 和宽度，并用最小、可回滚的覆盖消除外部样式造成的尺寸差异：\n\n```css\nhtml, body, main, .poster-shell { box-sizing: border-box; }\nhtml, body, main { margin: 0; padding: 0; background: var(--crayon-bg); }\n```\n\n不要为了消除空隙直接改 `min-height:100vh` 或重构 DOM；先验证是否实际加载了旧版 `.page { width: calc(100% - 20px) }`。\n\n### 编号列与时间轴几何对齐\n\n时间轴 `left` 应和编号列边界使用同一基准。\n\n- **R6 桌面端**（crayon poster-shell 已升级）：`grid-template-columns: 100px 1fr`，时间轴 `left:96px`，编号 `padding-right:32px`。100 \u002F 96 \u002F 32 三值必须成套调整。\n- **R6 移动端**：`grid-template-columns: 72px 1fr`，时间轴 `left:68px`，编号 `padding-right:24px`。\n- **R5 旧档位**（不推荐，仅用于历史卡）：`grid-template-columns:68px 1fr`，时间轴 `left:68px`，编号 `padding-right:10px`；移动端 `48px 1fr` + `left:48px` + `padding-right:8px`。\n\n编号 `padding-right` 只提供视觉留白，不应承担列定位。如果数字与时间轴看上去贴线，先检查 padding 是否足够（≥24px），再判断是否要扩列宽：\n\n```css\n.poster-shell .card-stripe { left: 96px; }\n.poster-shell .card-num    { padding-right: 32px; align-self: center; }\n@media (max-width:720px) {\n  .poster-shell .card-stripe { left: 68px; }\n  .poster-shell .card-num    { padding-right: 24px; }\n}\n```\n\n若色彩类只写了 `background-color`，不能覆盖时间轴已有的 `background-image` 渐变；按条目换色时应替换对应的渐变 `background-image`。\n\n\n### 1. 检查线上版本\n\n```bash\ncurl -s --max-time 12 'https:\u002F\u002Fexample.com\u002Fcard.html' > \u002Ftmp\u002Fcard.html\n```\n\n检查预期版本标记、`.skill-card` 内 DOM 顺序 `stripe → num → body`、线上 CSS 修复值。不要只根据浏览器旧截图判断部署状态。\n\n### 2. 检查 DOM 结构\n\n```python\nimport re\nhtml = open('\u002Ftmp\u002Fcard.html').read()\nfirst = re.search(r'\u003Cdiv class=\"skill-card\">(.*?)\u003C\u002Fdiv>\\s*\u003Cdiv class=\"skill-card\">', html, re.S)\nchunk = first.group(1)\nassert chunk.index('card-stripe') \u003C chunk.index('card-num') \u003C chunk.index('card-body')\n```\n\n若 `card-num` 出现在 `card-body` 之后，先修 HTML，不要只改 CSS。\n\n### 3. 检查 computed layout\n\n```js\nconst card = document.querySelector('.skill-card');\nconst num = card.querySelector(':scope > .card-num');\nconst body = card.querySelector(':scope > .card-body');\nconst stripe = card.querySelector(':scope > .card-stripe');\nconsole.table({\n  card: card.getBoundingClientRect().toJSON(),\n  num: num?.getBoundingClientRect().toJSON(),\n  body: body?.getBoundingClientRect().toJSON(),\n  stripe: stripe?.getBoundingClientRect().toJSON(),\n  bodyGridColumn: getComputedStyle(body).gridColumn,\n});\n```\n\n预期：`num.left` 接近 `card.left`；`body.left` 约为 `card.left + 编号列宽度`；`body.width` 占据剩余宽度；`stripe.left` 位于编号列右边缘附近；`bodyGridColumn` 为 `2`。\n\n### 4. 移动端同步检查\n\n在 `max-width:720px` 下，四个值必须成套调整：\n\n```css\n.skill-card { grid-template-columns: 52px 1fr; }\n.card-num { width: 52px; font-size: 44px; }\n.card-stripe { left: 48px; }\n.card-body { padding-left: 14px; padding-right: 10px; }\n```\n\n不要只修改 `grid-template-columns`，否则编号或时间轴会漂移。\n\n### 5. 视觉验收\n\n先做 DOM\u002FCSS 确定性检查，再做截图。截图只用于确认：编号位于左侧、时间轴线与圆点在编号列右缘、标题正文标签从正文列开始、移动端无横向溢出或裁切。\n\n视觉模型误读平台外壳、浏览器缓存或旧 CDN 时，以线上 HTML\u002FCSS token 和 DOM 顺序为 ground truth。\n\n## 常见失败模式\n\n| 症状 | 根因 | 正确处理 |\n|---|---|---|\n| 编号跑到右侧 | `.card-num` 嵌套在 `.card-body`，无法参与祖先 grid | 把编号移到 `.skill-card` 直接子级 |\n| `grid-column:1` 看似存在但无效 | 元素不是该 grid 的直接 item | 修 DOM 层级，不是继续堆 CSS |\n| 时间轴偏移到正文内部 | `.card-stripe` 定位基准被错误嵌套层级改变 | 移为 `.skill-card` 直接子级并相对 card 定位 |\n| 移动端编号贴边或线错位 | 只调列宽，没有同步 num width\u002Fstripe left\u002Fpadding | 按移动端四值成套调整 |\n| 用户截图仍是旧版本 | CDN、浏览器或平台缓存 | curl 核验线上 HTML，再说明缓存可能性 |\n| 本地主题正确、具体卡片错误 | 主题模板与卡片内联 CSS 隔离 | 检查具体卡片 HTML；需要显式同步内联组件 CSS |\n\n## 交付要求\n\n完成修复后报告根因、修改范围、桌面与移动端确定性检查、build\u002Fverify\u002Fleak 结果、公网 URL 与线上 DOM\u002FCSS 验证结果。\n\n若现有主题技能已记录旧版列宽或旧骨架，应在其 references 中补充本类修复；若该技能受保护不可编辑，则保留本技能作为布局调试补充，并在交付中说明存在主题技能重叠。\n","# infocard-layout-debugging\n\n信息卡主题布局调试与视觉验收技能。用于处理编号、时间轴、正文列、装饰线、响应式布局与线上缓存之间的错位问题。\n\n## 触发条件\n\n- 用户指出编号跑到右侧、正文被挤窄、时间轴错位或移动端布局异常。\n- CSS 已声明 `grid-column`，但截图仍显示元素位置错误。\n- 本地、CDN 与用户截图的视觉结果不一致。\n- 主题改造涉及 poster-shell、timeline、编号列或移动端断点。\n\n## 核心原则\n\n1. **先查 DOM 层级，再改 CSS。** `grid-column` 只对当前 grid 容器的直接 grid item 生效；嵌套元素不能跨越父子层级参与祖先 grid。\n2. **结构优先于视觉补丁。** 不要先用 `position:absolute` 把错误嵌套的元素“拉回”目标位置；应优先修复组件骨架。\n3. **线上事实优先于截图猜测。** 先抓取线上 HTML\u002FCSS，确认部署版本和 DOM 顺序，再使用截图或视觉模型分析。\n4. **桌面与移动端必须成对验证。** 编号列宽度、编号宽度、时间轴 left 偏移和正文 padding 必须同步更新。\n5. **主题必须保持泛化。** 修复应落在组件骨架、token 和响应式规则，不得绑定某一张卡片的固定内容。\n6. **视觉完成 ≠ 几何数据完成。** 用户已明确指出：仅靠 DOM rect、CSS computed style、`getBoundingClientRect` 一致等几何证据，不能算\"视觉验收通过\"。修复后必须用 Playwright 抓桌面 + 移动端双视口截图，再用 `vision_analyze` 给出每张图的 issues \u002F score。任何修复只要缺截图复审，就不允许在交付报告里宣称\"完成\"。\n\n## 标准组件骨架\n\n```html\n\u003Cdiv class=\"skill-card\">\n  \u003Cdiv class=\"card-stripe blue\">\u003C\u002Fdiv>\n  \u003Cdiv class=\"card-num blue\">01\u003C\u002Fdiv>\n  \u003Cdiv class=\"card-body\">\n    \u003Cdiv class=\"card-icon\" aria-hidden=\"true\">🧬\u003C\u002Fdiv>\n    \u003Ch3 class=\"card-title\">标题\u003C\u002Fh3>\n    \u003Cp class=\"card-desc\">正文\u003C\u002Fp>\n    \u003Cdiv class=\"card-tags\">标签\u003C\u002Fdiv>\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\n`.card-num` 与 `.card-stripe` 必须是 `.skill-card` 的直接子级；`.card-body` 必须显式声明 `grid-column:2`。\n\n```css\n.skill-card {\n  position: relative;\n  display: grid;\n  grid-template-columns: 76px 1fr;\n}\n.card-num { grid-column: 1; grid-row: 1; }\n.card-body { grid-column: 2; grid-row: 1; min-width: 0; }\n.card-stripe { position: absolute; left: 72px; }\n```\n\n## 调试流程\n\n### 白色空隙与浅色边缘\n\n先确认实际预览\u002F发布的文件路径，尤其要区分 `theme\u002F`、`dist\u002F` 与同名旧模板；不要把截图中的浅色边缘直接归因于浏览器默认 margin。检查 `html, body, main, .poster-shell` 的 margin、padding、background 和宽度，并用最小、可回滚的覆盖消除外部样式造成的尺寸差异：\n\n```css\nhtml, body, main, .poster-shell { box-sizing: border-box; }\nhtml, body, main { margin: 0; padding: 0; background: var(--crayon-bg); }\n```\n\n不要为了消除空隙直接改 `min-height:100vh` 或重构 DOM；先验证是否实际加载了旧版 `.page { width: calc(100% - 20px) }`。\n\n### 编号列与时间轴几何对齐\n\n时间轴 `left` 应和编号列边界使用同一基准。\n\n- **R6 桌面端**（crayon poster-shell 已升级）：`grid-template-columns: 100px 1fr`，时间轴 `left:96px`，编号 `padding-right:32px`。100 \u002F 96 \u002F 32 三值必须成套调整。\n- **R6 移动端**：`grid-template-columns: 72px 1fr`，时间轴 `left:68px`，编号 `padding-right:24px`。\n- **R5 旧档位**（不推荐，仅用于历史卡）：`grid-template-columns:68px 1fr`，时间轴 `left:68px`，编号 `padding-right:10px`；移动端 `48px 1fr` + `left:48px` + `padding-right:8px`。\n\n编号 `padding-right` 只提供视觉留白，不应承担列定位。如果数字与时间轴看上去贴线，先检查 padding 是否足够（≥24px），再判断是否要扩列宽：\n\n```css\n.poster-shell .card-stripe { left: 96px; }\n.poster-shell .card-num    { padding-right: 32px; align-self: center; }\n@media (max-width:720px) {\n  .poster-shell .card-stripe { left: 68px; }\n  .poster-shell .card-num    { padding-right: 24px; }\n}\n```\n\n若色彩类只写了 `background-color`，不能覆盖时间轴已有的 `background-image` 渐变；按条目换色时应替换对应的渐变 `background-image`。\n\n\n### 1. 检查线上版本\n\n```bash\ncurl -s --max-time 12 'https:\u002F\u002Fexample.com\u002Fcard.html' > \u002Ftmp\u002Fcard.html\n```\n\n检查预期版本标记、`.skill-card` 内 DOM 顺序 `stripe → num → body`、线上 CSS 修复值。不要只根据浏览器旧截图判断部署状态。\n\n### 2. 检查 DOM 结构\n\n```python\nimport re\nhtml = open('\u002Ftmp\u002Fcard.html').read()\nfirst = re.search(r'\u003Cdiv class=\"skill-card\">(.*?)\u003C\u002Fdiv>\\s*\u003Cdiv class=\"skill-card\">', html, re.S)\nchunk = first.group(1)\nassert chunk.index('card-stripe') \u003C chunk.index('card-num') \u003C chunk.index('card-body')\n```\n\n若 `card-num` 出现在 `card-body` 之后，先修 HTML，不要只改 CSS。\n\n### 3. 检查 computed layout\n\n```js\nconst card = document.querySelector('.skill-card');\nconst num = card.querySelector(':scope > .card-num');\nconst body = card.querySelector(':scope > .card-body');\nconst stripe = card.querySelector(':scope > .card-stripe');\nconsole.table({\n  card: card.getBoundingClientRect().toJSON(),\n  num: num?.getBoundingClientRect().toJSON(),\n  body: body?.getBoundingClientRect().toJSON(),\n  stripe: stripe?.getBoundingClientRect().toJSON(),\n  bodyGridColumn: getComputedStyle(body).gridColumn,\n});\n```\n\n预期：`num.left` 接近 `card.left`；`body.left` 约为 `card.left + 编号列宽度`；`body.width` 占据剩余宽度；`stripe.left` 位于编号列右边缘附近；`bodyGridColumn` 为 `2`。\n\n### 4. 移动端同步检查\n\n在 `max-width:720px` 下，四个值必须成套调整：\n\n```css\n.skill-card { grid-template-columns: 52px 1fr; }\n.card-num { width: 52px; font-size: 44px; }\n.card-stripe { left: 48px; }\n.card-body { padding-left: 14px; padding-right: 10px; }\n```\n\n不要只修改 `grid-template-columns`，否则编号或时间轴会漂移。\n\n### 5. 视觉验收\n\n先做 DOM\u002FCSS 确定性检查，再做截图。截图只用于确认：编号位于左侧、时间轴线与圆点在编号列右缘、标题正文标签从正文列开始、移动端无横向溢出或裁切。\n\n视觉模型误读平台外壳、浏览器缓存或旧 CDN 时，以线上 HTML\u002FCSS token 和 DOM 顺序为 ground truth。\n\n## 常见失败模式\n\n| 症状 | 根因 | 正确处理 |\n|---|---|---|\n| 编号跑到右侧 | `.card-num` 嵌套在 `.card-body`，无法参与祖先 grid | 把编号移到 `.skill-card` 直接子级 |\n| `grid-column:1` 看似存在但无效 | 元素不是该 grid 的直接 item | 修 DOM 层级，不是继续堆 CSS |\n| 时间轴偏移到正文内部 | `.card-stripe` 定位基准被错误嵌套层级改变 | 移为 `.skill-card` 直接子级并相对 card 定位 |\n| 移动端编号贴边或线错位 | 只调列宽，没有同步 num width\u002Fstripe left\u002Fpadding | 按移动端四值成套调整 |\n| 用户截图仍是旧版本 | CDN、浏览器或平台缓存 | curl 核验线上 HTML，再说明缓存可能性 |\n| 本地主题正确、具体卡片错误 | 主题模板与卡片内联 CSS 隔离 | 检查具体卡片 HTML；需要显式同步内联组件 CSS |\n\n## 交付要求\n\n完成修复后报告根因、修改范围、桌面与移动端确定性检查、build\u002Fverify\u002Fleak 结果、公网 URL 与线上 DOM\u002FCSS 验证结果。\n\n若现有主题技能已记录旧版列宽或旧骨架，应在其 references 中补充本类修复；若该技能受保护不可编辑，则保留本技能作为布局调试补充，并在交付中说明存在主题技能重叠。\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"description":7},"Hermes Agent","1.0.0",{"hermes":27},{"tags":28,"related_skills":35},[29,30,31,32,33,34],"infocard","css","grid","responsive","visual-debugging","publishing",[36,37,38,39],"infocard-style-man-skill","infocard-crayon-style","web-visual-acceptance","infocard-mobile-verifier","main","4ea40456a3623e494105429a3ae13c3ff61f17f5",".agents\u002Fskills\u002Fcontent\u002Finfocard-layout-debugging",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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add ccwq\u002Finfocard-pub --skill infocard-layout-debugging",{"tool":55,"command":56},"bunx","bunx skills add ccwq\u002Finfocard-pub --skill infocard-layout-debugging",{"tool":58,"command":59},"pnpm","pnpm dlx skills add ccwq\u002Finfocard-pub --skill infocard-layout-debugging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fccwq\u002Finfocard-pub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcontent\u002Finfocard-layout-debugging\u002FSKILL.md",true,[],[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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",[],[]]