[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XC6FFY5RF1S4C6B2KVFW26":3,"skill-same:01M6XC6FFY5RF1S4C6B2KVFW26":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":25,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":13,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6XC6FFY5RF1S4C6B2KVFW26","css-append-selector-verify",null,"Safely append CSS styles from one file to another, with per-selector grep verification after every append to catch silent truncation that tail or wc-l alone would miss","UF-gzj\u002Fopenspace-claude-evolution","UF-gzj","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272393507?v=4","01M6XBCZB755P01VVYGQWPYZY3","01M6XBCZFJA5AREA17WGETA3FW",0,"MIT","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fcss-append-selector-verify\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[26,27,28,29,30,31,32,33,34,35,36,37,38],"css","verify","append","selector","css append selector verify","verification","file","grep","styles","with","tail","wc","catch","2026-11-10 10:12:30",false,"---\nname: css-append-selector-verify\ndescription: Safely append CSS styles from one file to another, with per-selector grep verification after every append to catch silent truncation that tail or wc-l alone would miss\n---\n\n# Safe CSS Append Workflow (with Per-Selector Verification)\n\nThis skill provides a systematic approach for safely appending CSS styles from a source file to a destination file. The workflow ensures no content is overwritten, CSS variables are properly adapted, and **every appended selector is individually confirmed present** — so silent heredoc truncation of long lines is caught immediately rather than being masked by a passing line-count check.\n\n## When to Use This Skill\n\n- Migrating styles between projects\n- Copying component styles while preserving existing rules\n- Adding new CSS rules without duplicating or conflicting with existing styles\n- Adapting styles to use a different set of CSS variables\n\n## Workflow Steps\n\n### 1. Read and Analyze Source CSS\n\nFirst, examine the source CSS file to identify the selectors and rules you want to transfer:\n\n```bash\n# Read the source CSS file\ncat \u002Fpath\u002Fto\u002Fsource\u002Fstyles.css\n\n# Identify specific selectors if needed\ngrep \"selector-pattern\" \u002Fpath\u002Fto\u002Fsource\u002Fstyles.css\n```\n\n**Document:**\n- Target selectors (e.g., `.panel-tab`, `.header-nav`)\n- CSS variables used (e.g., `--primary-color`, `--spacing-unit`)\n- Complete rule sets for each selector\n\n### 2. Read and Check Destination CSS\n\nExamine the destination file to understand existing rules and avoid duplication:\n\n```bash\n# Read the destination CSS file\ncat \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css\n\n# Check if specific selectors already exist\ngrep \"selector-name\" \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css\n\n# Check for existing CSS variables\ngrep \"^[[:space:]]*--\" \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css | head -20\n```\n\n**Identify:**\n- Existing selectors that might conflict\n- CSS variable naming conventions in the destination\n- Any existing rules for the target selectors\n\n### 3. Identify Missing Styles and Required Adaptations\n\nCompare source and destination to determine:\n- Which selectors are completely missing\n- Which properties are missing from existing selectors\n- How CSS variables need to be mapped (source → destination)\n\n**Example variable mapping:**\n```\nSource: --panel-bg → Destination: --background-secondary\nSource: --text-primary → Destination: --color-text-primary\nSource: --border-radius → Keep as-is (if already defined in destination)\n```\n\n### 4. Prepare Adapted CSS Content\n\nCreate the CSS content to append, adapting variables as needed:\n\n```css\n\u002F* Example adapted CSS *\u002F\n.new-selector {\n    background-color: var(--background-secondary);  \u002F* was --panel-bg *\u002F\n    color: var(--color-text-primary);               \u002F* was --text-primary *\u002F\n    border-radius: var(--border-radius);            \u002F* unchanged *\u002F\n    padding: 8px 16px;\n}\n\n.existing-selector {\n    \u002F* Only add missing properties, not the entire rule *\u002F\n    new-property: value;\n}\n```\n\n### 5. Safely Append to Destination\n\nUse append operations (never overwrite) to add the new styles.\n\n**Record the line count BEFORE appending** (use this in step 6):\n\n```bash\nBEFORE=$(wc -l \u003C \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css)\n```\n\nThen append:\n\n```bash\ncat >> \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css \u003C\u003C 'EOF'\n\n\u002F* Added styles from source project *\u002F\n.selector-name {\n    property: value;\n    variable-property: var(--adapted-variable);\n}\nEOF\n```\n\n**Best practices:**\n- Add a comment indicating the source or purpose\n- Include a blank line before the new content for readability\n- Use `>>` (append) never `>` (overwrite)\n\n### 6. Verify the Changes (Per-Selector Grep + Tail)\n\nConfirm that the styles were added correctly. **Do not rely on `tail` or `wc -l` alone** — a heredoc can silently truncate an overly long line, leaving a selector block incomplete while the line count still increases. The required approach is to grep for *every* selector that was just appended.\n\n#### 6a. Line-count delta\n\n```bash\nAFTER=$(wc -l \u003C \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css)\necho \"Lines added: $((AFTER - BEFORE))\"\n```\n\n#### 6b. Per-selector grep — one grep per appended selector\n\n```bash\n# Repeat for every selector appended in step 5\ngrep -n \"\\.selector-name\"      \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css || echo \"MISSING: .selector-name\"\ngrep -n \"\\.another-selector\"   \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css || echo \"MISSING: .another-selector\"\n```\n\nIf any grep prints \"MISSING\", the append was incomplete — re-run step 5.\n\n#### 6c. Automation helper for many selectors\n\nIf many selectors were appended, use a loop:\n\n```bash\nDEST=\u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css\nMISSING=0\nfor selector in \\\n    \".selector-name\" \\\n    \".another-selector\" \\\n    \".yet-another\"; do\n  if ! grep -q \"$selector\" \"$DEST\"; then\n    echo \"MISSING SELECTOR: $selector\"\n    MISSING=$((MISSING + 1))\n  fi\ndone\n\nif [ \"$MISSING\" -gt 0 ]; then\n  echo \"ERROR: $MISSING selector(s) not found — append may have been truncated.\"\n  exit 1\nelse\n  echo \"All selectors verified present.\"\nfi\n```\n\n#### 6d. Visual spot-check\n\n```bash\ntail -n 30 \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css\n```\n\n**Why per-selector grep is required:**\n- `wc -l` increments even when a line is truncated — the count passes but content is lost.\n- `tail` shows recent lines but only reveals truncation if you happen to notice a cut-off line visually.\n- A `grep` for each selector name fails with a non-zero exit code if the selector is absent, making the failure explicit and automatable.\n\n## Complete Example\n\nHere's a full example workflow:\n\n```bash\n# 1. Read source CSS and identify target\ncat project-a\u002Fcomponents.css | grep -A 10 \".button-primary\"\n\n# 2. Check destination for conflicts\ngrep \".button-primary\" project-b\u002Fmain.css\ngrep \"^[[:space:]]*--btn-\" project-b\u002Fmain.css\n\n# 3. Identify that .button-primary is missing, and variables need mapping:\n#    --btn-color → --primary-color (exists in destination)\n#    --btn-padding → create inline value\n\n# 4. Record line count before append\nBEFORE=$(wc -l \u003C project-b\u002Fmain.css)\n\n# 5. Append adapted styles\ncat >> project-b\u002Fmain.css \u003C\u003C 'EOF'\n\n\u002F* Button styles from project-a *\u002F\n.button-primary {\n    background-color: var(--primary-color);\n    padding: 10px 20px;\n    border-radius: 4px;\n    font-weight: 600;\n}\nEOF\n\n# 6a. Line-count delta\nAFTER=$(wc -l \u003C project-b\u002Fmain.css)\necho \"Lines before: $BEFORE  |  Lines after: $AFTER  |  Added: $((AFTER - BEFORE))\"\n\n# 6b. Per-selector grep — catches truncation that wc -l and tail miss\ngrep -n \"\\.button-primary\" project-b\u002Fmain.css \\\n  && echo \"OK: .button-primary\" \\\n  || echo \"MISSING: .button-primary — possible truncation!\"\n\n# 6c. Visual spot-check\ntail -n 10 project-b\u002Fmain.css\n```\n\n## Safety Checklist\n\n- [ ] Source file read and analyzed\n- [ ] Destination file checked for existing rules\n- [ ] Missing styles identified\n- [ ] CSS variables mapped correctly\n- [ ] Append operation used (not overwrite)\n- [ ] Every appended selector individually confirmed with grep (not just tail\u002Fwc -l)\n- [ ] Automation loop (or per-selector greps) returned zero missing selectors\n- [ ] No duplicate selectors created\n- [ ] All variable references exist in destination\n\n## Common Pitfalls\n\n1. **Overwriting instead of appending**: Always use `>>`, never `>`\n2. **Variable mismatch**: Ensure all CSS variables exist in the destination or are properly defined\n3. **Duplicate selectors**: Check for existing rules before adding complete selector blocks\n4. **Incomplete verification**: Always grep for every appended selector by name — `tail` and `wc -l` do not detect mid-block truncation\n5. **Heredoc line-length truncation**: Very long CSS property values or data URIs inside a heredoc can be silently cut. If a line is extremely long, use a temporary file approach instead (see Tips)\n\n## Tips\n\n- Use `wc -l` before and after as a *supplementary* sanity check, but never as the sole verification\n- Collect all selector names appended in a shell array at write time, then loop over them in the verification step — this eliminates the risk of forgetting to check a selector\n- Keep a mapping document for complex variable transformations\n- For very long lines (e.g., embedded SVGs or data URIs), write the CSS to a temp file first and use `cat tmpfile >> dest.css` rather than a heredoc; then grep-verify as normal\n- Group related selectors together when appending multiple rules\n","# Safe CSS Append Workflow (with Per-Selector Verification)\n\nThis skill provides a systematic approach for safely appending CSS styles from a source file to a destination file. The workflow ensures no content is overwritten, CSS variables are properly adapted, and **every appended selector is individually confirmed present** — so silent heredoc truncation of long lines is caught immediately rather than being masked by a passing line-count check.\n\n## When to Use This Skill\n\n- Migrating styles between projects\n- Copying component styles while preserving existing rules\n- Adding new CSS rules without duplicating or conflicting with existing styles\n- Adapting styles to use a different set of CSS variables\n\n## Workflow Steps\n\n### 1. Read and Analyze Source CSS\n\nFirst, examine the source CSS file to identify the selectors and rules you want to transfer:\n\n```bash\n# Read the source CSS file\ncat \u002Fpath\u002Fto\u002Fsource\u002Fstyles.css\n\n# Identify specific selectors if needed\ngrep \"selector-pattern\" \u002Fpath\u002Fto\u002Fsource\u002Fstyles.css\n```\n\n**Document:**\n- Target selectors (e.g., `.panel-tab`, `.header-nav`)\n- CSS variables used (e.g., `--primary-color`, `--spacing-unit`)\n- Complete rule sets for each selector\n\n### 2. Read and Check Destination CSS\n\nExamine the destination file to understand existing rules and avoid duplication:\n\n```bash\n# Read the destination CSS file\ncat \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css\n\n# Check if specific selectors already exist\ngrep \"selector-name\" \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css\n\n# Check for existing CSS variables\ngrep \"^[[:space:]]*--\" \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css | head -20\n```\n\n**Identify:**\n- Existing selectors that might conflict\n- CSS variable naming conventions in the destination\n- Any existing rules for the target selectors\n\n### 3. Identify Missing Styles and Required Adaptations\n\nCompare source and destination to determine:\n- Which selectors are completely missing\n- Which properties are missing from existing selectors\n- How CSS variables need to be mapped (source → destination)\n\n**Example variable mapping:**\n```\nSource: --panel-bg → Destination: --background-secondary\nSource: --text-primary → Destination: --color-text-primary\nSource: --border-radius → Keep as-is (if already defined in destination)\n```\n\n### 4. Prepare Adapted CSS Content\n\nCreate the CSS content to append, adapting variables as needed:\n\n```css\n\u002F* Example adapted CSS *\u002F\n.new-selector {\n    background-color: var(--background-secondary);  \u002F* was --panel-bg *\u002F\n    color: var(--color-text-primary);               \u002F* was --text-primary *\u002F\n    border-radius: var(--border-radius);            \u002F* unchanged *\u002F\n    padding: 8px 16px;\n}\n\n.existing-selector {\n    \u002F* Only add missing properties, not the entire rule *\u002F\n    new-property: value;\n}\n```\n\n### 5. Safely Append to Destination\n\nUse append operations (never overwrite) to add the new styles.\n\n**Record the line count BEFORE appending** (use this in step 6):\n\n```bash\nBEFORE=$(wc -l \u003C \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css)\n```\n\nThen append:\n\n```bash\ncat >> \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css \u003C\u003C 'EOF'\n\n\u002F* Added styles from source project *\u002F\n.selector-name {\n    property: value;\n    variable-property: var(--adapted-variable);\n}\nEOF\n```\n\n**Best practices:**\n- Add a comment indicating the source or purpose\n- Include a blank line before the new content for readability\n- Use `>>` (append) never `>` (overwrite)\n\n### 6. Verify the Changes (Per-Selector Grep + Tail)\n\nConfirm that the styles were added correctly. **Do not rely on `tail` or `wc -l` alone** — a heredoc can silently truncate an overly long line, leaving a selector block incomplete while the line count still increases. The required approach is to grep for *every* selector that was just appended.\n\n#### 6a. Line-count delta\n\n```bash\nAFTER=$(wc -l \u003C \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css)\necho \"Lines added: $((AFTER - BEFORE))\"\n```\n\n#### 6b. Per-selector grep — one grep per appended selector\n\n```bash\n# Repeat for every selector appended in step 5\ngrep -n \"\\.selector-name\"      \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css || echo \"MISSING: .selector-name\"\ngrep -n \"\\.another-selector\"   \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css || echo \"MISSING: .another-selector\"\n```\n\nIf any grep prints \"MISSING\", the append was incomplete — re-run step 5.\n\n#### 6c. Automation helper for many selectors\n\nIf many selectors were appended, use a loop:\n\n```bash\nDEST=\u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css\nMISSING=0\nfor selector in \\\n    \".selector-name\" \\\n    \".another-selector\" \\\n    \".yet-another\"; do\n  if ! grep -q \"$selector\" \"$DEST\"; then\n    echo \"MISSING SELECTOR: $selector\"\n    MISSING=$((MISSING + 1))\n  fi\ndone\n\nif [ \"$MISSING\" -gt 0 ]; then\n  echo \"ERROR: $MISSING selector(s) not found — append may have been truncated.\"\n  exit 1\nelse\n  echo \"All selectors verified present.\"\nfi\n```\n\n#### 6d. Visual spot-check\n\n```bash\ntail -n 30 \u002Fpath\u002Fto\u002Fdestination\u002Fstyles.css\n```\n\n**Why per-selector grep is required:**\n- `wc -l` increments even when a line is truncated — the count passes but content is lost.\n- `tail` shows recent lines but only reveals truncation if you happen to notice a cut-off line visually.\n- A `grep` for each selector name fails with a non-zero exit code if the selector is absent, making the failure explicit and automatable.\n\n## Complete Example\n\nHere's a full example workflow:\n\n```bash\n# 1. Read source CSS and identify target\ncat project-a\u002Fcomponents.css | grep -A 10 \".button-primary\"\n\n# 2. Check destination for conflicts\ngrep \".button-primary\" project-b\u002Fmain.css\ngrep \"^[[:space:]]*--btn-\" project-b\u002Fmain.css\n\n# 3. Identify that .button-primary is missing, and variables need mapping:\n#    --btn-color → --primary-color (exists in destination)\n#    --btn-padding → create inline value\n\n# 4. Record line count before append\nBEFORE=$(wc -l \u003C project-b\u002Fmain.css)\n\n# 5. Append adapted styles\ncat >> project-b\u002Fmain.css \u003C\u003C 'EOF'\n\n\u002F* Button styles from project-a *\u002F\n.button-primary {\n    background-color: var(--primary-color);\n    padding: 10px 20px;\n    border-radius: 4px;\n    font-weight: 600;\n}\nEOF\n\n# 6a. Line-count delta\nAFTER=$(wc -l \u003C project-b\u002Fmain.css)\necho \"Lines before: $BEFORE  |  Lines after: $AFTER  |  Added: $((AFTER - BEFORE))\"\n\n# 6b. Per-selector grep — catches truncation that wc -l and tail miss\ngrep -n \"\\.button-primary\" project-b\u002Fmain.css \\\n  && echo \"OK: .button-primary\" \\\n  || echo \"MISSING: .button-primary — possible truncation!\"\n\n# 6c. Visual spot-check\ntail -n 10 project-b\u002Fmain.css\n```\n\n## Safety Checklist\n\n- [ ] Source file read and analyzed\n- [ ] Destination file checked for existing rules\n- [ ] Missing styles identified\n- [ ] CSS variables mapped correctly\n- [ ] Append operation used (not overwrite)\n- [ ] Every appended selector individually confirmed with grep (not just tail\u002Fwc -l)\n- [ ] Automation loop (or per-selector greps) returned zero missing selectors\n- [ ] No duplicate selectors created\n- [ ] All variable references exist in destination\n\n## Common Pitfalls\n\n1. **Overwriting instead of appending**: Always use `>>`, never `>`\n2. **Variable mismatch**: Ensure all CSS variables exist in the destination or are properly defined\n3. **Duplicate selectors**: Check for existing rules before adding complete selector blocks\n4. **Incomplete verification**: Always grep for every appended selector by name — `tail` and `wc -l` do not detect mid-block truncation\n5. **Heredoc line-length truncation**: Very long CSS property values or data URIs inside a heredoc can be silently cut. If a line is extremely long, use a temporary file approach instead (see Tips)\n\n## Tips\n\n- Use `wc -l` before and after as a *supplementary* sanity check, but never as the sole verification\n- Collect all selector names appended in a shell array at write time, then loop over them in the verification step — this eliminates the risk of forgetting to check a selector\n- Keep a mapping document for complex variable transformations\n- For very long lines (e.g., embedded SVGs or data URIs), write the CSS to a temp file first and use `cat tmpfile >> dest.css` rather than a heredoc; then grep-verify as normal\n- Group related selectors together when appending multiple rules\n",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","showcase\u002Fskills\u002Fcss-append-selector-verify","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution","https:\u002F\u002Fgithub.com\u002FUF-gzj","2026-04-16 09:31:03",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill css-append-selector-verify",{"tool":56,"command":57},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill css-append-selector-verify",{"tool":59,"command":60},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill css-append-selector-verify","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fcss-append-selector-verify\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},".skill_id","OTHER","其他",38,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fcss-append-selector-verify\u002F.skill_id",[71,95,110,119,148,164],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":39},"01M6XCCXD3NCM2YKR3WNGBASPC","write-special-chars-ts-check","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,32,94],"check","write","write special chars ts check","typescript","filters","characters","Existing","type-checking","for","errors","script","output","type","files","only","template","python",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":39},"01M6XCCT7E3J922Q345PBGSHPN","write-special-chars-readback","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of \u002Ftmp helper scripts.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[102,103,79,32,104,94,105,106,107,108,109,93,31,35,83,86,88],"readback","write special chars readback","helper","post","via","scripts","cleanup","read",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":39},"01M6XCCMQX1R8B6FECWB3P63T7","write-special-chars-heredoc","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) by using a Python heredoc script executed via shell.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[117,79,83,118,88,106,93,32,94,86],"write special chars heredoc","shell",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":130,"publishedAt":39},"01M6XCCG41M994JJEX6VN52PEP","worldmonitor-reference","Curated architecture index of the WorldMonitor open-source dashboard. Reference for extracting patterns — vanilla TypeScript, Panel class hierarchy, service layer, CSS grid, API edge functions, refresh scheduler, and 60+ data source integrations.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[125],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[131,132,133,134,135,81,26,136,137,138,139,86,140,141,142,143,144,145,146,147],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","scheduler","layer","hierarchy","source","extracting","panel","patterns","edge functions","integrations","open","api","data",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":39},"01M6XCCCHWNKG2W4VH9E6A10HF","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[155,156,157,158,86,159,35,160,161,162,163],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":39},"01M6XCC7X8PKMR2DEW91XGHYSV","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[171,172,173,27,174,175,32,176,177,178],"directory","verify directory structure","structure","access","first","issues","diagnose","file access"]