[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D3JDC3RMSXJS1811HJ7AJ0":3,"skill-same:01M7D3JDC3RMSXJS1811HJ7AJ0":53},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7D3JDC3RMSXJS1811HJ7AJ0","clean-code",null,"Pragmatic Clean Code engineering, domain-expressive naming, function single-responsibility, cohesion & coupling metrics, language-specific idiomatic design, and elimination of premature abstraction.","poppyTM\u002Faipo-lang","poppyTM","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F339400917?v=4","01M78F6YNKFR5S5JQR27X9F09Z","Poppy Team","01M7D3H3PCFF0AZSRPP5GTS76P",0,"MIT","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Fclean-code\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: clean-code\ndescription: Pragmatic Clean Code engineering, domain-expressive naming, function single-responsibility, cohesion & coupling metrics, language-specific idiomatic design, and elimination of premature abstraction.\n---\n\n# Pragmatic Clean Code & Design Ergonomics\n\n## 1. Title and Description\n**Pragmatic Clean Code & Design Ergonomics (`clean-code`)**\nEnforces the Prumo canonical clean code discipline: explicit responsibilities, low coupling, high cohesion, domain-driven naming, small cohesive functions, composition over inheritance, deterministic error returns, and zero speculative abstractions.\n\n## 2. Purpose\nMaintain a codebase that is immediately understandable, easily testable, and cheap to modify, while strictly guarding against both \"spaghetti code\" and its opposite hazard: \"enterprise astronautics\" (premature interfaces, excessive wrapper layers, and over-engineering).\n\n## 3. Prerequisites\n- Target source code in any language supported by Prumo (Go, Rust, TypeScript, Python, C++, Zig).\n- Formatting and static analysis tools for the target stack.\n\n## 4. Inputs\n- Existing source files, pull request diffs, or newly authored modules.\n- Domain models and architectural boundary definitions.\n\n## 5. Outputs\n- Clean, readable, idiomatic code adhering to language-specific conventions.\n- Explicit refactoring diffs removing code smells and dead code.\n- Clean code review findings conforming to `templates\u002Fclean-code-review.md`.\n\n## 6. Execution Steps\n\n### Step 1: Domain-Expressive Naming\n1. **Intention-Revealing Names**: Names must state why an entity exists, what it does, and how it is used. Avoid noise words (`Data`, `Info`, `Manager`, `Processor`, `Object`) unless formally defined in the domain glossary.\n2. **Grammar Conventions**:\n   - Variables\u002FTypes: Nouns or noun phrases (`Invoice`, `TransactionBatch`, `TokenEnvelope`).\n   - Functions\u002FMethods: Action verbs or predicates (`calculateTax()`, `isAuthorized()`, `parsePayload()`).\n   - Booleans: Formulate as yes\u002Fno predicates (`is_valid`, `has_children`, `can_retry`). Never use negative names (`is_not_empty`).\n3. **Searchability and Pronounceability**: Forbid single-letter variables except for standard loop indices (`i`, `j`), coordinate mathematics (`x`, `y`), or standard idiom conventions (Go receiver `s *Server`).\n\n### Step 2: Function Responsibility & Granularity\n1. **Single Level of Abstraction Principle (SLAP)**: Statements within a function should belong to the same level of conceptual abstraction. High-level orchestrators should not mix with low-level bitwise masking or string manipulation.\n2. **Small & Cohesive**: Limit function size to what comfortably fits on a single viewport (typically \u003C= 35 lines). If a function requires comments dividing it into logical \"phases\", extract each phase into a private helper function.\n3. **Minimize Argument Arity**:\n   - 0–2 arguments: Ideal.\n   - 3 arguments: Acceptable when strictly related.\n   - 4+ arguments: Code smell. Bundle parameters into a cohesive configuration struct or options object.\n\n### Step 3: Anti-Premature-Abstraction Rule (Pragmatic Discipline)\n1. **The Rule of Three**: Do not extract a shared abstraction upon the second occurrence of code. Wait until the pattern appears a third time with demonstrably identical *behavioral* intent (not just coincidental structural similarity).\n2. **No Single-Implementation Interfaces**: In Go, Rust, and TypeScript, never declare an interface if there is only one concrete implementation, unless explicitly required for external mock boundaries in unit tests.\n3. **Composition Over Inheritance**: Avoid deep class inheritance hierarchies. Favor composing flat structs containing discrete capability traits or delegates.\n\n### Step 4: Cohesion & Coupling Optimization\n1. **High Cohesion**: Every method in a struct\u002Fclass should access or modify a significant portion of its fields. If a subset of methods only touches a subset of fields, split the struct into two distinct types (Lack of Cohesion of Methods - LCOM).\n2. **Low Coupling**: Depend on abstract, stable capabilities rather than volatile concrete modules. Dependencies must point inwards toward domain logic.\n3. **No Hidden Temporal Coupling**: If method `B()` must strictly be called after method `A()`, enforce this through the type system (e.g., `A()` returns a `ConfiguredState` token required as a parameter by `B()`).\n\n### Step 5: Side Effects & State Mutation\n1. **Pure Core, Imperative Shell**: Isolate pure calculation functions (no I\u002FO, no mutation, deterministic output from input) from the imperative edges that handle filesystem, database, and network I\u002FO.\n2. **Command-Query Separation (CQS)**: A function should either perform an action (mutation) or answer a query (return data), but never both, unless returning state transition receipts (e.g. `Pop()`).\n3. **Immutability by Default**: Mark variables, parameters, and fields immutable wherever the language supports it (`const`, `readonly`, `let` without `mut`).\n\n### Step 6: Code Smell Audit & Elimination\nAudit the codebase systematically for classic Martin Fowler code smells:\n- **Long Method \u002F Large Class**: Extract Class \u002F Extract Method.\n- **Primitive Obsession**: Replace raw primitives with typed Value Objects (e.g. `UserId`, `Money`, `EmailAddress`).\n- **Feature Envy**: Method frequently accesses data of another class; move the method to the data owner.\n- **Dead Code**: Delete commented-out code and unreferenced functions immediately. Version control preserves history.\n\n## 7. Verification\n```bash\n# 1. Complexity & Cohesion Analysis\n.\u002Fscripts\u002Fanalyze_complexity.sh .\n\n# 2. Linter & Static Analysis (Language-specific)\n# Go: golangci-lint run\n# Rust: cargo clippy -- -D clippy::pedantic\n# TypeScript: eslint .\n```\n\n## 8. Fallbacks & Failure Recovery\n| Code Smell \u002F Hazard | Root Cause | Deterministic Remediation |\n|---|---|---|\n| Cyclomatic Complexity > 15 | Nested conditionals, large switch statements | Apply \"Replace Conditional with Polymorphism\" or early-return guards (`guard clauses`). |\n| Shotgun Surgery | Single feature change forces edits across 6+ distinct files | Group related responsibilities into a single cohesive domain module. |\n| Divergent Change | One class is repeatedly changed for multiple unrelated reasons | Apply Single Responsibility Principle: separate concerns into dedicated structs. |\n| Premature Generic Boilerplate | Interfaces with only 1 implementation, deep factories | Inline factories and replace interface with concrete struct until polymorphism is proven necessary. |\n\n## 9. Constraints\n- **Preserve behavior**: Refactoring must never alter external observable behavior. All unit tests must pass before and after changes.\n- **Do not invent abstractions**: Never create generic plugins, base classes, or factories \"just in case\" future requirements need them.\n- **No commented-out code**: Dead code must be removed, not commented out.\n\n## 10. Examples\n\n### Anti-Pattern: Primitive Obsession & Premature Complexity\n```typescript\n\u002F\u002F BAD: Primitives, temporal coupling, side effects, cryptic naming\nclass OrderProc {\n    private db: any;\n    public o: any;\n\n    \u002F\u002F Temporal coupling: must call init() before calc()!\n    init(orderId: string) {\n        this.o = this.db.fetch(orderId);\n    }\n\n    calc(d: number, t: string) {\n        \u002F\u002F Deep nested logic, magic numbers, side-effect inside query\n        if (this.o != null) {\n            if (t === \"US\") {\n                this.o.total = this.o.subtotal * 1.08 - d;\n                this.db.save(this.o); \u002F\u002F Unexpected side-effect in calculate!\n                return this.o.total;\n            }\n        }\n        return -1; \u002F\u002F Magic error code!\n    }\n}\n```\n\n### Idiomatic Pattern: Domain Types, Immutability & CQS\n```typescript\n\u002F\u002F GOOD: Value objects, pure calculations, explicit errors, clear naming\nexport class CurrencyAmount {\n    constructor(public readonly cents: number, public readonly currency: \"USD\" | \"EUR\") {\n        if (!Number.isInteger(cents) || cents \u003C 0) {\n            throw new Error(`Invalid monetary amount: ${cents}`);\n        }\n    }\n}\n\nexport interface TaxPolicy {\n    calculateTax(subtotal: CurrencyAmount): CurrencyAmount;\n}\n\nexport class OrderBillingService {\n    \u002F\u002F Pure calculation function: zero I\u002FO, deterministic, easily testable\n    public calculateFinalTotal(\n        subtotal: CurrencyAmount,\n        discount: CurrencyAmount,\n        taxPolicy: TaxPolicy\n    ): CurrencyAmount {\n        if (discount.cents > subtotal.cents) {\n            throw new Error(\"Discount cannot exceed order subtotal\");\n        }\n\n        const discountedSubtotal = new CurrencyAmount(subtotal.cents - discount.cents, subtotal.currency);\n        const tax = taxPolicy.calculateTax(discountedSubtotal);\n\n        return new CurrencyAmount(discountedSubtotal.cents + tax.cents, subtotal.currency);\n    }\n}\n```\n","# Pragmatic Clean Code & Design Ergonomics\n\n## 1. Title and Description\n**Pragmatic Clean Code & Design Ergonomics (`clean-code`)**\nEnforces the Prumo canonical clean code discipline: explicit responsibilities, low coupling, high cohesion, domain-driven naming, small cohesive functions, composition over inheritance, deterministic error returns, and zero speculative abstractions.\n\n## 2. Purpose\nMaintain a codebase that is immediately understandable, easily testable, and cheap to modify, while strictly guarding against both \"spaghetti code\" and its opposite hazard: \"enterprise astronautics\" (premature interfaces, excessive wrapper layers, and over-engineering).\n\n## 3. Prerequisites\n- Target source code in any language supported by Prumo (Go, Rust, TypeScript, Python, C++, Zig).\n- Formatting and static analysis tools for the target stack.\n\n## 4. Inputs\n- Existing source files, pull request diffs, or newly authored modules.\n- Domain models and architectural boundary definitions.\n\n## 5. Outputs\n- Clean, readable, idiomatic code adhering to language-specific conventions.\n- Explicit refactoring diffs removing code smells and dead code.\n- Clean code review findings conforming to `templates\u002Fclean-code-review.md`.\n\n## 6. Execution Steps\n\n### Step 1: Domain-Expressive Naming\n1. **Intention-Revealing Names**: Names must state why an entity exists, what it does, and how it is used. Avoid noise words (`Data`, `Info`, `Manager`, `Processor`, `Object`) unless formally defined in the domain glossary.\n2. **Grammar Conventions**:\n   - Variables\u002FTypes: Nouns or noun phrases (`Invoice`, `TransactionBatch`, `TokenEnvelope`).\n   - Functions\u002FMethods: Action verbs or predicates (`calculateTax()`, `isAuthorized()`, `parsePayload()`).\n   - Booleans: Formulate as yes\u002Fno predicates (`is_valid`, `has_children`, `can_retry`). Never use negative names (`is_not_empty`).\n3. **Searchability and Pronounceability**: Forbid single-letter variables except for standard loop indices (`i`, `j`), coordinate mathematics (`x`, `y`), or standard idiom conventions (Go receiver `s *Server`).\n\n### Step 2: Function Responsibility & Granularity\n1. **Single Level of Abstraction Principle (SLAP)**: Statements within a function should belong to the same level of conceptual abstraction. High-level orchestrators should not mix with low-level bitwise masking or string manipulation.\n2. **Small & Cohesive**: Limit function size to what comfortably fits on a single viewport (typically \u003C= 35 lines). If a function requires comments dividing it into logical \"phases\", extract each phase into a private helper function.\n3. **Minimize Argument Arity**:\n   - 0–2 arguments: Ideal.\n   - 3 arguments: Acceptable when strictly related.\n   - 4+ arguments: Code smell. Bundle parameters into a cohesive configuration struct or options object.\n\n### Step 3: Anti-Premature-Abstraction Rule (Pragmatic Discipline)\n1. **The Rule of Three**: Do not extract a shared abstraction upon the second occurrence of code. Wait until the pattern appears a third time with demonstrably identical *behavioral* intent (not just coincidental structural similarity).\n2. **No Single-Implementation Interfaces**: In Go, Rust, and TypeScript, never declare an interface if there is only one concrete implementation, unless explicitly required for external mock boundaries in unit tests.\n3. **Composition Over Inheritance**: Avoid deep class inheritance hierarchies. Favor composing flat structs containing discrete capability traits or delegates.\n\n### Step 4: Cohesion & Coupling Optimization\n1. **High Cohesion**: Every method in a struct\u002Fclass should access or modify a significant portion of its fields. If a subset of methods only touches a subset of fields, split the struct into two distinct types (Lack of Cohesion of Methods - LCOM).\n2. **Low Coupling**: Depend on abstract, stable capabilities rather than volatile concrete modules. Dependencies must point inwards toward domain logic.\n3. **No Hidden Temporal Coupling**: If method `B()` must strictly be called after method `A()`, enforce this through the type system (e.g., `A()` returns a `ConfiguredState` token required as a parameter by `B()`).\n\n### Step 5: Side Effects & State Mutation\n1. **Pure Core, Imperative Shell**: Isolate pure calculation functions (no I\u002FO, no mutation, deterministic output from input) from the imperative edges that handle filesystem, database, and network I\u002FO.\n2. **Command-Query Separation (CQS)**: A function should either perform an action (mutation) or answer a query (return data), but never both, unless returning state transition receipts (e.g. `Pop()`).\n3. **Immutability by Default**: Mark variables, parameters, and fields immutable wherever the language supports it (`const`, `readonly`, `let` without `mut`).\n\n### Step 6: Code Smell Audit & Elimination\nAudit the codebase systematically for classic Martin Fowler code smells:\n- **Long Method \u002F Large Class**: Extract Class \u002F Extract Method.\n- **Primitive Obsession**: Replace raw primitives with typed Value Objects (e.g. `UserId`, `Money`, `EmailAddress`).\n- **Feature Envy**: Method frequently accesses data of another class; move the method to the data owner.\n- **Dead Code**: Delete commented-out code and unreferenced functions immediately. Version control preserves history.\n\n## 7. Verification\n```bash\n# 1. Complexity & Cohesion Analysis\n.\u002Fscripts\u002Fanalyze_complexity.sh .\n\n# 2. Linter & Static Analysis (Language-specific)\n# Go: golangci-lint run\n# Rust: cargo clippy -- -D clippy::pedantic\n# TypeScript: eslint .\n```\n\n## 8. Fallbacks & Failure Recovery\n| Code Smell \u002F Hazard | Root Cause | Deterministic Remediation |\n|---|---|---|\n| Cyclomatic Complexity > 15 | Nested conditionals, large switch statements | Apply \"Replace Conditional with Polymorphism\" or early-return guards (`guard clauses`). |\n| Shotgun Surgery | Single feature change forces edits across 6+ distinct files | Group related responsibilities into a single cohesive domain module. |\n| Divergent Change | One class is repeatedly changed for multiple unrelated reasons | Apply Single Responsibility Principle: separate concerns into dedicated structs. |\n| Premature Generic Boilerplate | Interfaces with only 1 implementation, deep factories | Inline factories and replace interface with concrete struct until polymorphism is proven necessary. |\n\n## 9. Constraints\n- **Preserve behavior**: Refactoring must never alter external observable behavior. All unit tests must pass before and after changes.\n- **Do not invent abstractions**: Never create generic plugins, base classes, or factories \"just in case\" future requirements need them.\n- **No commented-out code**: Dead code must be removed, not commented out.\n\n## 10. Examples\n\n### Anti-Pattern: Primitive Obsession & Premature Complexity\n```typescript\n\u002F\u002F BAD: Primitives, temporal coupling, side effects, cryptic naming\nclass OrderProc {\n    private db: any;\n    public o: any;\n\n    \u002F\u002F Temporal coupling: must call init() before calc()!\n    init(orderId: string) {\n        this.o = this.db.fetch(orderId);\n    }\n\n    calc(d: number, t: string) {\n        \u002F\u002F Deep nested logic, magic numbers, side-effect inside query\n        if (this.o != null) {\n            if (t === \"US\") {\n                this.o.total = this.o.subtotal * 1.08 - d;\n                this.db.save(this.o); \u002F\u002F Unexpected side-effect in calculate!\n                return this.o.total;\n            }\n        }\n        return -1; \u002F\u002F Magic error code!\n    }\n}\n```\n\n### Idiomatic Pattern: Domain Types, Immutability & CQS\n```typescript\n\u002F\u002F GOOD: Value objects, pure calculations, explicit errors, clear naming\nexport class CurrencyAmount {\n    constructor(public readonly cents: number, public readonly currency: \"USD\" | \"EUR\") {\n        if (!Number.isInteger(cents) || cents \u003C 0) {\n            throw new Error(`Invalid monetary amount: ${cents}`);\n        }\n    }\n}\n\nexport interface TaxPolicy {\n    calculateTax(subtotal: CurrencyAmount): CurrencyAmount;\n}\n\nexport class OrderBillingService {\n    \u002F\u002F Pure calculation function: zero I\u002FO, deterministic, easily testable\n    public calculateFinalTotal(\n        subtotal: CurrencyAmount,\n        discount: CurrencyAmount,\n        taxPolicy: TaxPolicy\n    ): CurrencyAmount {\n        if (discount.cents > subtotal.cents) {\n            throw new Error(\"Discount cannot exceed order subtotal\");\n        }\n\n        const discountedSubtotal = new CurrencyAmount(subtotal.cents - discount.cents, subtotal.currency);\n        const tax = taxPolicy.calculateTax(discountedSubtotal);\n\n        return new CurrencyAmount(discountedSubtotal.cents + tax.cents, subtotal.currency);\n    }\n}\n```\n",{"name":5,"description":7},"main","b2b8635798b0fab7a7c037608a616985cc1da742",".ai\u002Fskills\u002Fclean-code","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang","https:\u002F\u002Fwww.poppy.lat\u002Faipo\u002Fdocs\u002F","https:\u002F\u002Fgithub.com\u002FpoppyTM","https:\u002F\u002Fpoppy.lat","Construímos linguagens de programação e ferramentas para quem lê código com o mesmo cuidado com que escreve.","2026-11-02 17:30:11",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add poppyTM\u002Faipo-lang --skill clean-code",{"tool":39,"command":40},"bunx","bunx skills add poppyTM\u002Faipo-lang --skill clean-code",{"tool":42,"command":43},"pnpm","pnpm dlx skills add poppyTM\u002Faipo-lang --skill clean-code","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Fclean-code\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"manifest.json","REFERENCE","参考文档",2207,"https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Fclean-code\u002Fmanifest.json",[54,61,67,73,79,86],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7D3JYBW82B2Q8XH75TKWBT7","lang-aipo","Aipo V1 canonical engineering, ADR-001 syntax conformance, braces blocks, Tipo:nome method bindings, structural interfaces, transactional failure handling, and anti-hallucination guardrails for LLMs.","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002Fskills\u002Flang-aipo\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7D3JWY6HS47F1TRVX14SZ5F","goal-management","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fgoal-management\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7D3JV6D1SPD1WNS14634CGV","evidence-collection","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fevidence-collection\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7D3JSSDVRNC7W42KAFA65MH","code-review","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fcode-review\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7D3JPEZSE144W9T31QKB9XP","testing-quality","Testing pyramid, deterministic tests, regression tests, behavior assertions, test isolation, flaky detection, representative fixtures","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Ftesting-quality\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7D3JJES8J9K0HXG45H27BRF","cognitive-clarity","Unambiguous communication, single-decision focus, visual structuring, and rationale-first explanation tailored for neurodivergent collaboration","https:\u002F\u002Fgithub.com\u002FpoppyTM\u002Faipo-lang\u002Fblob\u002Fmain\u002F.ai\u002Fskills\u002Fcognitive-clarity\u002FSKILL.md",[],[]]