[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BSG3TM80SVC3E6MHYA2CH4":3,"skill-same:01M7BSG3TM80SVC3E6MHYA2CH4":55},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7BSG3TM80SVC3E6MHYA2CH4","clean-code-principles",null,"SOLID principles, design patterns, DRY, KISS, and clean code fundamentals. Use when reviewing architecture, checking code quality, refactoring, or discussing design decisions. Triggers on \"review architecture\", \"check code quality\", \"SOLID principles\", \"design patterns\", or \"clean code\".","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fasyrafhussin-agent-skills\u002Fclean-code-principles\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: clean-code-principles\ndescription: SOLID principles, design patterns, DRY, KISS, and clean code fundamentals. Use when reviewing architecture, checking code quality, refactoring, or discussing design decisions. Triggers on \"review architecture\", \"check code quality\", \"SOLID principles\", \"design patterns\", or \"clean code\".\nlicense: MIT\nmetadata:\n  author: AsyrafHussin\n  version: \"1.0.2\"\n---\n\n# Clean Code Principles\n\nFundamental software design principles, SOLID, design patterns, and clean code practices. Language-agnostic guidelines for writing maintainable, scalable software.\n\n## When to Apply\n\nReference these guidelines when:\n- Designing new features or systems\n- Reviewing code architecture\n- Refactoring existing code\n- Discussing design decisions\n- Improving code quality\n\n## Rule Categories by Priority\n\n| Priority | Category | Impact | Prefix |\n|----------|----------|--------|--------|\n| 1 | SOLID Principles | CRITICAL | `solid-` |\n| 2 | Core Principles | CRITICAL | `core-` |\n| 3 | Design Patterns | HIGH | `pattern-` |\n| 4 | Code Organization | HIGH | `org-` |\n| 5 | Naming & Readability | MEDIUM | `name-` |\n| 6 | Functions & Methods | MEDIUM | `func-` |\n| 7 | Comments & Documentation | LOW | `doc-` |\n\n## Quick Reference\n\n### 1. SOLID Principles (CRITICAL)\n\n- `solid-srp` - Single Responsibility Principle\n- `solid-ocp` - Open\u002FClosed Principle\n- `solid-lsp` - Liskov Substitution Principle\n- `solid-isp` - Interface Segregation Principle\n- `solid-dip` - Dependency Inversion Principle\n\n### 2. Core Principles (CRITICAL)\n\n- `core-dry` - Don't Repeat Yourself\n- `core-kiss` - Keep It Simple, Stupid\n- `core-yagni` - You Aren't Gonna Need It\n- `core-separation-of-concerns` - Separate different responsibilities\n- `core-composition-over-inheritance` - Favor composition\n- `core-law-of-demeter` - Principle of least knowledge\n- `core-fail-fast` - Detect and report errors early\n- `core-encapsulation` - Hide implementation details\n\n### 3. Design Patterns (HIGH)\n\n- `pattern-factory` - Factory pattern for object creation\n- `pattern-strategy` - Strategy pattern for algorithms\n- `pattern-repository` - Repository pattern for data access\n- `pattern-decorator` - Decorator pattern for behavior extension\n- `pattern-observer` - Observer pattern for event handling\n- `pattern-adapter` - Adapter pattern for interface conversion\n- `pattern-facade` - Facade pattern for simplified interfaces\n- `pattern-dependency-injection` - DI for loose coupling\n\n### 4. Code Organization (HIGH) — planned\n\n- `org-feature-folders` - Organize by feature, not layer\n- `org-module-boundaries` - Clear module boundaries\n- `org-layered-architecture` - Proper layer separation\n- `org-package-cohesion` - Related code together\n- `org-circular-dependencies` - Avoid circular imports\n\n### 5. Naming & Readability (MEDIUM) — planned\n\n- `name-meaningful` - Use intention-revealing names\n- `name-consistent` - Consistent naming conventions\n- `name-searchable` - Avoid magic numbers\u002Fstrings\n- `name-avoid-encodings` - No Hungarian notation\n- `name-domain-language` - Use domain terminology\n\n### 6. Functions & Methods (MEDIUM) — planned\n\n- `func-small` - Keep functions small\n- `func-single-purpose` - Do one thing\n- `func-few-arguments` - Limit parameters\n- `func-no-side-effects` - Minimize side effects\n- `func-command-query` - Separate commands and queries\n\n### 7. Comments & Documentation (LOW) — planned\n\n- `doc-self-documenting` - Code should explain itself\n- `doc-why-not-what` - Explain why, not what\n- `doc-avoid-noise` - No redundant comments\n- `doc-api-docs` - Document public APIs\n\n## Essential Guidelines\n\nFor detailed examples and explanations, see the rule files:\n\n- [core-dry.md](rules\u002Fcore-dry.md) - Don't Repeat Yourself principle\n- [pattern-repository.md](rules\u002Fpattern-repository.md) - Repository pattern for data access\n\n### SOLID Principles (Summary)\n\n| Principle | Definition |\n|-----------|------------|\n| **S**ingle Responsibility | A class should have only one reason to change |\n| **O**pen\u002FClosed | Open for extension, closed for modification |\n| **L**iskov Substitution | Subtypes must be substitutable for base types |\n| **I**nterface Segregation | Don't force clients to depend on unused interfaces |\n| **D**ependency Inversion | Depend on abstractions, not concretions |\n\n### Core Principles (Summary)\n\n| Principle | Definition |\n|-----------|------------|\n| **DRY** | Don't Repeat Yourself - single source of truth |\n| **KISS** | Keep It Simple - avoid over-engineering |\n| **YAGNI** | You Aren't Gonna Need It - build only what's needed |\n\n### Quick Examples\n\n```typescript\n\u002F\u002F Single Responsibility - one class, one job\nclass UserService {\n  constructor(\n    private validator: UserValidator,\n    private repository: UserRepository,\n  ) {}\n\n  createUser(data) {\n    this.validator.validate(data);\n    return this.repository.create(data);\n  }\n}\n\n\u002F\u002F Dependency Inversion - depend on abstractions\ninterface Repository\u003CT> {\n  find(id: string): Promise\u003CT | null>;\n  save(entity: T): Promise\u003CT>;\n}\n\nclass OrderService {\n  constructor(private repository: Repository\u003COrder>) {}\n}\n\n\u002F\u002F DRY - single source of truth\nconst EMAIL_REGEX = \u002F^[^\\s@]+@[^\\s@]+\\.[^\\s@]+$\u002F;\nconst isValidEmail = (email: string) => EMAIL_REGEX.test(email);\n\n\u002F\u002F Meaningful names over magic numbers\nconst MINIMUM_AGE = 18;\nif (user.age >= MINIMUM_AGE) { }\n```\n\n## Output Format\n\nWhen auditing code, output findings in this format:\n\n```\nfile:line - [principle] Description of issue\n```\n\nExample:\n```\nsrc\u002Fservices\u002FUserService.ts:15 - [solid-srp] Class handles validation, persistence, and notifications\nsrc\u002Futils\u002Fhelpers.ts:42 - [core-dry] Email validation duplicated from validators\u002Femail.ts\nsrc\u002Fmodels\u002FOrder.ts:28 - [name-meaningful] Variable 'x' should describe its purpose\n```\n\n## How to Use\n\nRead individual rule files for detailed explanations:\n\n```\nrules\u002Fsolid-srp-class.md\nrules\u002Fcore-dry.md\nrules\u002Fpattern-repository.md\n```\n\n## References\n\nThis skill is built on established software engineering principles:\n\n### Core Books\n- **Clean Code** by Robert C. Martin - Foundation for clean code practices\n- **Design Patterns** by Gang of Four - Classic design pattern catalog\n- **Refactoring** by Martin Fowler - Improving code structure\n- **The Pragmatic Programmer** by Hunt & Thomas - Practical wisdom\n\n### Online Resources\n- [Refactoring Guru](https:\u002F\u002Frefactoring.guru\u002F) - Design patterns and code smells\n- [Martin Fowler's Refactoring Catalog](https:\u002F\u002Frefactoring.com\u002Fcatalog\u002F) - Comprehensive refactoring techniques\n- [Uncle Bob's Clean Coder Blog](https:\u002F\u002Fblog.cleancoder.com\u002F) - Software craftsmanship articles\n\n### Pattern Catalogs\n- [Refactoring Guru - Design Patterns](https:\u002F\u002Frefactoring.guru\u002Fdesign-patterns)\n- [Martin Fowler - Enterprise Patterns](https:\u002F\u002Fmartinfowler.com\u002FeaaCatalog\u002F)\n\n## Metadata\n\n**Version:** 1.0.2\n**Status:** Active\n**Coverage:** 23 rules across 3 implemented categories (SOLID, Core Principles, Design Patterns); 4 planned\n**Last Updated:** 2026-03-07\n\n### Rule Statistics\n- SOLID Principles: 10 rules\n- Core Principles: 12 rules\n- Design Patterns: 1 rule\n\n","# Clean Code Principles\n\nFundamental software design principles, SOLID, design patterns, and clean code practices. Language-agnostic guidelines for writing maintainable, scalable software.\n\n## When to Apply\n\nReference these guidelines when:\n- Designing new features or systems\n- Reviewing code architecture\n- Refactoring existing code\n- Discussing design decisions\n- Improving code quality\n\n## Rule Categories by Priority\n\n| Priority | Category | Impact | Prefix |\n|----------|----------|--------|--------|\n| 1 | SOLID Principles | CRITICAL | `solid-` |\n| 2 | Core Principles | CRITICAL | `core-` |\n| 3 | Design Patterns | HIGH | `pattern-` |\n| 4 | Code Organization | HIGH | `org-` |\n| 5 | Naming & Readability | MEDIUM | `name-` |\n| 6 | Functions & Methods | MEDIUM | `func-` |\n| 7 | Comments & Documentation | LOW | `doc-` |\n\n## Quick Reference\n\n### 1. SOLID Principles (CRITICAL)\n\n- `solid-srp` - Single Responsibility Principle\n- `solid-ocp` - Open\u002FClosed Principle\n- `solid-lsp` - Liskov Substitution Principle\n- `solid-isp` - Interface Segregation Principle\n- `solid-dip` - Dependency Inversion Principle\n\n### 2. Core Principles (CRITICAL)\n\n- `core-dry` - Don't Repeat Yourself\n- `core-kiss` - Keep It Simple, Stupid\n- `core-yagni` - You Aren't Gonna Need It\n- `core-separation-of-concerns` - Separate different responsibilities\n- `core-composition-over-inheritance` - Favor composition\n- `core-law-of-demeter` - Principle of least knowledge\n- `core-fail-fast` - Detect and report errors early\n- `core-encapsulation` - Hide implementation details\n\n### 3. Design Patterns (HIGH)\n\n- `pattern-factory` - Factory pattern for object creation\n- `pattern-strategy` - Strategy pattern for algorithms\n- `pattern-repository` - Repository pattern for data access\n- `pattern-decorator` - Decorator pattern for behavior extension\n- `pattern-observer` - Observer pattern for event handling\n- `pattern-adapter` - Adapter pattern for interface conversion\n- `pattern-facade` - Facade pattern for simplified interfaces\n- `pattern-dependency-injection` - DI for loose coupling\n\n### 4. Code Organization (HIGH) — planned\n\n- `org-feature-folders` - Organize by feature, not layer\n- `org-module-boundaries` - Clear module boundaries\n- `org-layered-architecture` - Proper layer separation\n- `org-package-cohesion` - Related code together\n- `org-circular-dependencies` - Avoid circular imports\n\n### 5. Naming & Readability (MEDIUM) — planned\n\n- `name-meaningful` - Use intention-revealing names\n- `name-consistent` - Consistent naming conventions\n- `name-searchable` - Avoid magic numbers\u002Fstrings\n- `name-avoid-encodings` - No Hungarian notation\n- `name-domain-language` - Use domain terminology\n\n### 6. Functions & Methods (MEDIUM) — planned\n\n- `func-small` - Keep functions small\n- `func-single-purpose` - Do one thing\n- `func-few-arguments` - Limit parameters\n- `func-no-side-effects` - Minimize side effects\n- `func-command-query` - Separate commands and queries\n\n### 7. Comments & Documentation (LOW) — planned\n\n- `doc-self-documenting` - Code should explain itself\n- `doc-why-not-what` - Explain why, not what\n- `doc-avoid-noise` - No redundant comments\n- `doc-api-docs` - Document public APIs\n\n## Essential Guidelines\n\nFor detailed examples and explanations, see the rule files:\n\n- [core-dry.md](rules\u002Fcore-dry.md) - Don't Repeat Yourself principle\n- [pattern-repository.md](rules\u002Fpattern-repository.md) - Repository pattern for data access\n\n### SOLID Principles (Summary)\n\n| Principle | Definition |\n|-----------|------------|\n| **S**ingle Responsibility | A class should have only one reason to change |\n| **O**pen\u002FClosed | Open for extension, closed for modification |\n| **L**iskov Substitution | Subtypes must be substitutable for base types |\n| **I**nterface Segregation | Don't force clients to depend on unused interfaces |\n| **D**ependency Inversion | Depend on abstractions, not concretions |\n\n### Core Principles (Summary)\n\n| Principle | Definition |\n|-----------|------------|\n| **DRY** | Don't Repeat Yourself - single source of truth |\n| **KISS** | Keep It Simple - avoid over-engineering |\n| **YAGNI** | You Aren't Gonna Need It - build only what's needed |\n\n### Quick Examples\n\n```typescript\n\u002F\u002F Single Responsibility - one class, one job\nclass UserService {\n  constructor(\n    private validator: UserValidator,\n    private repository: UserRepository,\n  ) {}\n\n  createUser(data) {\n    this.validator.validate(data);\n    return this.repository.create(data);\n  }\n}\n\n\u002F\u002F Dependency Inversion - depend on abstractions\ninterface Repository\u003CT> {\n  find(id: string): Promise\u003CT | null>;\n  save(entity: T): Promise\u003CT>;\n}\n\nclass OrderService {\n  constructor(private repository: Repository\u003COrder>) {}\n}\n\n\u002F\u002F DRY - single source of truth\nconst EMAIL_REGEX = \u002F^[^\\s@]+@[^\\s@]+\\.[^\\s@]+$\u002F;\nconst isValidEmail = (email: string) => EMAIL_REGEX.test(email);\n\n\u002F\u002F Meaningful names over magic numbers\nconst MINIMUM_AGE = 18;\nif (user.age >= MINIMUM_AGE) { }\n```\n\n## Output Format\n\nWhen auditing code, output findings in this format:\n\n```\nfile:line - [principle] Description of issue\n```\n\nExample:\n```\nsrc\u002Fservices\u002FUserService.ts:15 - [solid-srp] Class handles validation, persistence, and notifications\nsrc\u002Futils\u002Fhelpers.ts:42 - [core-dry] Email validation duplicated from validators\u002Femail.ts\nsrc\u002Fmodels\u002FOrder.ts:28 - [name-meaningful] Variable 'x' should describe its purpose\n```\n\n## How to Use\n\nRead individual rule files for detailed explanations:\n\n```\nrules\u002Fsolid-srp-class.md\nrules\u002Fcore-dry.md\nrules\u002Fpattern-repository.md\n```\n\n## References\n\nThis skill is built on established software engineering principles:\n\n### Core Books\n- **Clean Code** by Robert C. Martin - Foundation for clean code practices\n- **Design Patterns** by Gang of Four - Classic design pattern catalog\n- **Refactoring** by Martin Fowler - Improving code structure\n- **The Pragmatic Programmer** by Hunt & Thomas - Practical wisdom\n\n### Online Resources\n- [Refactoring Guru](https:\u002F\u002Frefactoring.guru\u002F) - Design patterns and code smells\n- [Martin Fowler's Refactoring Catalog](https:\u002F\u002Frefactoring.com\u002Fcatalog\u002F) - Comprehensive refactoring techniques\n- [Uncle Bob's Clean Coder Blog](https:\u002F\u002Fblog.cleancoder.com\u002F) - Software craftsmanship articles\n\n### Pattern Catalogs\n- [Refactoring Guru - Design Patterns](https:\u002F\u002Frefactoring.guru\u002Fdesign-patterns)\n- [Martin Fowler - Enterprise Patterns](https:\u002F\u002Fmartinfowler.com\u002FeaaCatalog\u002F)\n\n## Metadata\n\n**Version:** 1.0.2\n**Status:** Active\n**Coverage:** 23 rules across 3 implemented categories (SOLID, Core Principles, Design Patterns); 4 planned\n**Last Updated:** 2026-03-07\n\n### Rule Statistics\n- SOLID Principles: 10 rules\n- Core Principles: 12 rules\n- Design Patterns: 1 rule\n\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"AsyrafHussin","1.0.2","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fasyrafhussin-agent-skills\u002Fclean-code-principles",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill clean-code-principles",{"tool":41,"command":42},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill clean-code-principles",{"tool":44,"command":45},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill clean-code-principles","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fasyrafhussin-agent-skills\u002Fclean-code-principles\u002FSkill.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"metadata.json","REFERENCE","参考文档",493,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fasyrafhussin-agent-skills\u002Fclean-code-principles\u002Fmetadata.json",[56,63,68,75,80,87],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":64,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":76,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":88,"name":82,"nameZh":6,"description":83,"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},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]