[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D4XFSQJ78FD86RC930437D":3,"skill-same:01M7D4XFSQJ78FD86RC930437D":48},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7D4XFSQJ78FD86RC930437D","kotlin-backend-jpa-entity-mapping",null,"Model Kotlin persistence code correctly for Spring Data JPA and Hibernate. Covers entity design, identity and equality, uniqueness constraints, relationships, fetch plans, and common ORM (Object-Relational Mapping) traps  specific to Kotlin. Use when creating or reviewing JPA (Java Persistence API)  entities, diagnosing N+1 or LazyInitializationException, placing indexes and  uniqueness rules, or preventing Kotlin-specific bugs such as data class  entities and broken equals\u002FhashCode.","Darshan8610\u002FDynamic-Island","Darshan8610","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F280662176?v=4","01M7D3NS7B63B86XTVEHZWQRM2","01M7D3NS8HT3SPCDXKS1VFAB0X",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F06-Kotlin-kotlin-agent-skills\u002Fskills\u002Fkotlin-backend-jpa-entity-mapping\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: kotlin-backend-jpa-entity-mapping\ndescription: >\n  Model Kotlin persistence code correctly for Spring Data JPA and Hibernate.\n  Covers entity design, identity and equality, uniqueness constraints,\n  relationships, fetch plans, and common ORM (Object-Relational Mapping) traps \n  specific to Kotlin. Use when creating or reviewing JPA (Java Persistence API) \n  entities, diagnosing N+1 or LazyInitializationException, placing indexes and \n  uniqueness rules, or preventing Kotlin-specific bugs such as data class \n  entities and broken equals\u002FhashCode.\nlicense: Apache-2.0\nmetadata:\n  author: JetBrains\n  version: \"1.0.0\"\n---\n\n# JPA Entity Mapping for Kotlin\n\nKotlin's `data class` is natural for DTOs but dangerous for JPA entities. Hibernate relies on\nidentity semantics that `data class` breaks: `equals`\u002F`hashCode` over all fields corrupts\n`Set`\u002F`Map` membership after state changes, and auto-generated `copy()` creates detached\nduplicates of managed entities.\n\nThis skill teaches correct entity design, identity strategies, and uniqueness constraints\nfor Kotlin + Spring Data JPA projects.\n\n## Entity Design Rules\n\n- **Never use `data class` for JPA entities.** Use a regular `class`. Keep `data class` for DTOs.\n- Keep transport DTOs and persistence entities separate unless the project clearly uses a shared model.\n- Model required columns as non-null only when object construction and persistence lifecycle make it safe.\n- Use `lateinit` only when the project already accepts that tradeoff and the lifecycle is safe.\n- Verify `kotlin(\"plugin.jpa\")` or equivalent no-arg support when JPA entities exist.\n- Verify classes and members are compatible with proxying where needed.\n\n## Identity and Equality\n\n- Never accept all-field `equals`\u002F`hashCode` generated by `data class` on an entity.\n- Follow project conventions when they already define an identity strategy.\n- If no convention exists, use ID-based equality with a stable `hashCode`.\n- For DB-generated IDs, model the unsaved state with nullable `var id: Long? = null`\n  and a `protected set`; do not use `0L` as a sentinel value.\n- Be explicit about mutable fields and lazy associations when discussing equality.\n\n### Broken: `data class` Entity\n\n```kotlin\n\u002F\u002F WRONG: data class generates equals\u002FhashCode from ALL fields,\n\u002F\u002F and the generated ID uses a 0 sentinel instead of null\ndata class Order(\n    @Id @GeneratedValue val id: Long = 0,\n    var status: String,\n    var total: BigDecimal\n)\n\u002F\u002F BUG: order.status = \"SHIPPED\"; set.contains(order) → false (hash changed)\n\u002F\u002F BUG: Hibernate proxy.equals(entity) → false (proxy has lazy fields uninitialized)\n```\n\n### Correct: Regular Class with ID-Based Identity\n\n```kotlin\n@Entity\n@Table(name = \"orders\")\nclass Order(\n    @Column(nullable = false)\n    var status: String,\n\n    @Column(nullable = false)\n    var total: BigDecimal\n) {\n    @Id\n    @GeneratedValue(strategy = GenerationType.IDENTITY)\n    var id: Long? = null\n        protected set\n\n    override fun equals(other: Any?): Boolean {\n        if (this === other) return true\n        if (other !is Order) return false\n        return id != null && id == other.id\n    }\n\n    override fun hashCode(): Int = javaClass.hashCode()\n\n    \u002F\u002F toString must NOT reference lazy collections\n    override fun toString(): String = \"Order(id=$id, status=$status)\"\n}\n```\n\n**Key rules:**\n- `equals` compares by ID only — stable under dirty tracking and proxy unwrapping\n- `hashCode` returns class-based constant — avoids `Set`\u002F`Map` corruption after persist\n- `toString` excludes lazy-loaded relations — prevents `LazyInitializationException`\n- Constructor params are mutable entity fields; DB-generated `id` is nullable with a protected setter\n\n## Uniqueness Constraints\n\nWhen an API must be idempotent (e.g., \"reserve stock for order X\"), enforce uniqueness\nat both layers: database constraint for correctness, application check for clean errors.\n\n### Broken: No Duplicate Guard\n\n```kotlin\n@Service\nclass ReservationService(private val repo: ReservationRepository) {\n    @Transactional\n    fun createReservation(variantId: Long, orderId: String, qty: Int): Reservation {\n        \u002F\u002F BUG: no check — duplicates silently accumulate\n        return repo.save(Reservation(variantId = variantId, orderId = orderId, quantity = qty))\n    }\n}\n```\n\n### Correct: Database Constraint + Application Guard\n\n```kotlin\n@Entity\n@Table(\n    name = \"reservations\",\n    uniqueConstraints = [\n        UniqueConstraint(columnNames = [\"variant_id\", \"order_id\"])\n    ]\n)\nclass Reservation(\n    @Column(name = \"variant_id\", nullable = false)\n    val variantId: Long,\n\n    @Column(name = \"order_id\", nullable = false)\n    val orderId: String,\n\n    @Column(nullable = false)\n    var quantity: Int\n) {\n    @Id @GeneratedValue(strategy = GenerationType.IDENTITY)\n    var id: Long? = null\n        protected set\n}\n\ninterface ReservationRepository : JpaRepository\u003CReservation, Long> {\n    fun findByVariantIdAndOrderId(variantId: Long, orderId: String): Reservation?\n}\n\n@Service\nclass ReservationService(private val repo: ReservationRepository) {\n    @Transactional\n    fun createReservation(variantId: Long, orderId: String, qty: Int): Reservation {\n        repo.findByVariantIdAndOrderId(variantId, orderId)?.let {\n            throw IllegalStateException(\n                \"Reservation already exists for variant=$variantId, order=$orderId\"\n            )\n        }\n        return repo.save(Reservation(variantId = variantId, orderId = orderId, quantity = qty))\n    }\n}\n```\n\n**Key rules:**\n- Database constraint is mandatory — application checks alone have race conditions\n- Application check provides clean error messages — without it, users get raw `DataIntegrityViolationException`\n- Both layers together: application catches the common case, database catches the race\n- Spring Data derives `findByXAndY` queries automatically\n\n## Query and Fetch Rules\n\n- Diagnose N+1 by looking at actual query count or SQL logs, not by guessing from annotations.\n- Prefer targeted fetch solutions: `@EntityGraph`, `JOIN FETCH`, batch fetching, or DTO projection.\n- Be careful with collection fetch joins plus pagination — call out the tradeoff.\n- Use indexes and uniqueness constraints to support real query patterns.\n\n## Common ORM Traps\n\n- **Bidirectional associations:** maintain both sides in domain methods. Half-updated graphs cause subtle bugs.\n- **`orphanRemoval` vs cascade remove:** not interchangeable. Explain lifecycle semantics before choosing.\n- **Lazy load triggers:** `toString`, debug logging, JSON serialization, and IDE inspection can all trigger lazy loads.\n- **Bulk updates\u002Fdeletes:** bypass persistence context and lifecycle callbacks. Subsequent reads may be stale.\n- **Multiple bag fetches:** can cause Cartesian explosion. Verify the ORM can execute collection-heavy fetch plans safely.\n- **`Set` + mutable equality:** collection membership can break after entity state changes.\n- **`@Version`:** the clearest optimistic concurrency mechanism when concurrent updates matter.\n- **`open-in-view` disabled:** DTO mapping touching lazy fields must happen inside a transaction boundary.\n\n## Guardrails\n\n- Do not use `data class` for JPA entities.\n- Do not recommend `FetchType.EAGER` everywhere to silence lazy loading symptoms.\n- Do not expose entities directly through API responses by default.\n- Do not claim an N+1 fix without explaining how the fetch plan changes query behavior.\n","# JPA Entity Mapping for Kotlin\n\nKotlin's `data class` is natural for DTOs but dangerous for JPA entities. Hibernate relies on\nidentity semantics that `data class` breaks: `equals`\u002F`hashCode` over all fields corrupts\n`Set`\u002F`Map` membership after state changes, and auto-generated `copy()` creates detached\nduplicates of managed entities.\n\nThis skill teaches correct entity design, identity strategies, and uniqueness constraints\nfor Kotlin + Spring Data JPA projects.\n\n## Entity Design Rules\n\n- **Never use `data class` for JPA entities.** Use a regular `class`. Keep `data class` for DTOs.\n- Keep transport DTOs and persistence entities separate unless the project clearly uses a shared model.\n- Model required columns as non-null only when object construction and persistence lifecycle make it safe.\n- Use `lateinit` only when the project already accepts that tradeoff and the lifecycle is safe.\n- Verify `kotlin(\"plugin.jpa\")` or equivalent no-arg support when JPA entities exist.\n- Verify classes and members are compatible with proxying where needed.\n\n## Identity and Equality\n\n- Never accept all-field `equals`\u002F`hashCode` generated by `data class` on an entity.\n- Follow project conventions when they already define an identity strategy.\n- If no convention exists, use ID-based equality with a stable `hashCode`.\n- For DB-generated IDs, model the unsaved state with nullable `var id: Long? = null`\n  and a `protected set`; do not use `0L` as a sentinel value.\n- Be explicit about mutable fields and lazy associations when discussing equality.\n\n### Broken: `data class` Entity\n\n```kotlin\n\u002F\u002F WRONG: data class generates equals\u002FhashCode from ALL fields,\n\u002F\u002F and the generated ID uses a 0 sentinel instead of null\ndata class Order(\n    @Id @GeneratedValue val id: Long = 0,\n    var status: String,\n    var total: BigDecimal\n)\n\u002F\u002F BUG: order.status = \"SHIPPED\"; set.contains(order) → false (hash changed)\n\u002F\u002F BUG: Hibernate proxy.equals(entity) → false (proxy has lazy fields uninitialized)\n```\n\n### Correct: Regular Class with ID-Based Identity\n\n```kotlin\n@Entity\n@Table(name = \"orders\")\nclass Order(\n    @Column(nullable = false)\n    var status: String,\n\n    @Column(nullable = false)\n    var total: BigDecimal\n) {\n    @Id\n    @GeneratedValue(strategy = GenerationType.IDENTITY)\n    var id: Long? = null\n        protected set\n\n    override fun equals(other: Any?): Boolean {\n        if (this === other) return true\n        if (other !is Order) return false\n        return id != null && id == other.id\n    }\n\n    override fun hashCode(): Int = javaClass.hashCode()\n\n    \u002F\u002F toString must NOT reference lazy collections\n    override fun toString(): String = \"Order(id=$id, status=$status)\"\n}\n```\n\n**Key rules:**\n- `equals` compares by ID only — stable under dirty tracking and proxy unwrapping\n- `hashCode` returns class-based constant — avoids `Set`\u002F`Map` corruption after persist\n- `toString` excludes lazy-loaded relations — prevents `LazyInitializationException`\n- Constructor params are mutable entity fields; DB-generated `id` is nullable with a protected setter\n\n## Uniqueness Constraints\n\nWhen an API must be idempotent (e.g., \"reserve stock for order X\"), enforce uniqueness\nat both layers: database constraint for correctness, application check for clean errors.\n\n### Broken: No Duplicate Guard\n\n```kotlin\n@Service\nclass ReservationService(private val repo: ReservationRepository) {\n    @Transactional\n    fun createReservation(variantId: Long, orderId: String, qty: Int): Reservation {\n        \u002F\u002F BUG: no check — duplicates silently accumulate\n        return repo.save(Reservation(variantId = variantId, orderId = orderId, quantity = qty))\n    }\n}\n```\n\n### Correct: Database Constraint + Application Guard\n\n```kotlin\n@Entity\n@Table(\n    name = \"reservations\",\n    uniqueConstraints = [\n        UniqueConstraint(columnNames = [\"variant_id\", \"order_id\"])\n    ]\n)\nclass Reservation(\n    @Column(name = \"variant_id\", nullable = false)\n    val variantId: Long,\n\n    @Column(name = \"order_id\", nullable = false)\n    val orderId: String,\n\n    @Column(nullable = false)\n    var quantity: Int\n) {\n    @Id @GeneratedValue(strategy = GenerationType.IDENTITY)\n    var id: Long? = null\n        protected set\n}\n\ninterface ReservationRepository : JpaRepository\u003CReservation, Long> {\n    fun findByVariantIdAndOrderId(variantId: Long, orderId: String): Reservation?\n}\n\n@Service\nclass ReservationService(private val repo: ReservationRepository) {\n    @Transactional\n    fun createReservation(variantId: Long, orderId: String, qty: Int): Reservation {\n        repo.findByVariantIdAndOrderId(variantId, orderId)?.let {\n            throw IllegalStateException(\n                \"Reservation already exists for variant=$variantId, order=$orderId\"\n            )\n        }\n        return repo.save(Reservation(variantId = variantId, orderId = orderId, quantity = qty))\n    }\n}\n```\n\n**Key rules:**\n- Database constraint is mandatory — application checks alone have race conditions\n- Application check provides clean error messages — without it, users get raw `DataIntegrityViolationException`\n- Both layers together: application catches the common case, database catches the race\n- Spring Data derives `findByXAndY` queries automatically\n\n## Query and Fetch Rules\n\n- Diagnose N+1 by looking at actual query count or SQL logs, not by guessing from annotations.\n- Prefer targeted fetch solutions: `@EntityGraph`, `JOIN FETCH`, batch fetching, or DTO projection.\n- Be careful with collection fetch joins plus pagination — call out the tradeoff.\n- Use indexes and uniqueness constraints to support real query patterns.\n\n## Common ORM Traps\n\n- **Bidirectional associations:** maintain both sides in domain methods. Half-updated graphs cause subtle bugs.\n- **`orphanRemoval` vs cascade remove:** not interchangeable. Explain lifecycle semantics before choosing.\n- **Lazy load triggers:** `toString`, debug logging, JSON serialization, and IDE inspection can all trigger lazy loads.\n- **Bulk updates\u002Fdeletes:** bypass persistence context and lifecycle callbacks. Subsequent reads may be stale.\n- **Multiple bag fetches:** can cause Cartesian explosion. Verify the ORM can execute collection-heavy fetch plans safely.\n- **`Set` + mutable equality:** collection membership can break after entity state changes.\n- **`@Version`:** the clearest optimistic concurrency mechanism when concurrent updates matter.\n- **`open-in-view` disabled:** DTO mapping touching lazy fields must happen inside a transaction boundary.\n\n## Guardrails\n\n- Do not use `data class` for JPA entities.\n- Do not recommend `FetchType.EAGER` everywhere to silence lazy loading symptoms.\n- Do not expose entities directly through API responses by default.\n- Do not claim an N+1 fix without explaining how the fetch plan changes query behavior.\n",{"name":5,"license":14,"metadata":23,"description":26},{"author":24,"version":25},"JetBrains","1.0.0","Model Kotlin persistence code correctly for Spring Data JPA and Hibernate. Covers entity design, identity and equality, uniqueness constraints, relationships, fetch plans, and common ORM (Object-Relational Mapping) traps  specific to Kotlin. Use when creating or reviewing JPA (Java Persistence API)  entities, diagnosing N+1 or LazyInitializationException, placing indexes and  uniqueness rules, or preventing Kotlin-specific bugs such as data class  entities and broken equals\u002FhashCode.\n","main","a22dccb577b5d59b83ac12e9e784b16d919df95d","used skills\u002F06-Kotlin-kotlin-agent-skills\u002Fskills\u002Fkotlin-backend-jpa-entity-mapping",1,"https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island","https:\u002F\u002Fgithub.com\u002FDarshan8610","2026-10-31 11:29:16",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Darshan8610\u002FDynamic-Island --skill kotlin-backend-jpa-entity-mapping",{"tool":40,"command":41},"bunx","bunx skills add Darshan8610\u002FDynamic-Island --skill kotlin-backend-jpa-entity-mapping",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Darshan8610\u002FDynamic-Island --skill kotlin-backend-jpa-entity-mapping","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F06-Kotlin-kotlin-agent-skills\u002Fskills\u002Fkotlin-backend-jpa-entity-mapping\u002FSKILL.md",true,[],[49,58,65,74,81,89],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":53,"licenseFileUrl":54,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7D6EQ4V97KQAAJDX03NH1PK","security-review","Security code review for vulnerabilities. Use when asked to \"security review\", \"find vulnerabilities\", \"check for security issues\", \"audit security\", \"OWASP review\", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.","CC-BY-SA-4.0","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F25-getsentry-skills\u002Fskills\u002Fsecurity-review\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F25-getsentry-skills\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7D6EFH7JA3N91H85BMF90X5","security-model","Define, review, or update SECURITY_MODEL.md files that tell security review tools a repository's threat model, trust boundaries, invariants, reportable finding classes, and exclusions. Use when asked to \"write a security model\", \"threat model this repo for scanners\", \"define security review scope\", \"what counts as a vulnerability here\", \"update SECURITY_MODEL.md\", \"why did the scanner flag or miss this\", or to check whether existing security guidance still matches the code. Not for running a security review or editing the SECURITY.md disclosure policy.","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F25-getsentry-skills\u002Fskills\u002Fsecurity-model\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":69,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7D69FRBB22BSGEJBFH71JA4","mobile-harness","Portable Android and iOS device-control harness for agents. Use when an agent needs to control or automate Android\u002FiOS devices — tap, swipe, screenshot, app control — locally (ADB\u002FPortal\u002FSimulator) or on Mobilerun cloud devices.","MIT","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F23-droidrun-mobile-harness\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F23-droidrun-mobile-harness\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7D5Z37XC1K629HJP6DMA2CF","compose-agent","Helps AI coding assistants write modern Jetpack Compose: correct state, side effects, performance-aware modifiers, Navigation 3, Paging 3 in Compose, coroutines on lifecycle, animations, UI tests, focus\u002Fkeyboard navigation, Compose Multiplatform boundaries, idiomatic Kotlin, and well-shaped composable APIs. Targets the mistakes LLMs actually make in Compose code. Use when reading, writing, or reviewing Compose projects.","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F20-hamen-compose_skill\u002Fskills\u002Fcompose-agent\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":69,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7D5ABYRS59CE3SVC8DHC35F","material-design-3-ui","Design, redesign, review, or implement user interfaces using Google Material Design 3 (M3), Material You, and optional Material 3 Expressive principles. Use for UI\u002FUX screens, app flows, design systems, component selection, theming, responsive\u002Fadaptive layouts, accessibility audits, Figma-ready specifications, or developer handoff where Material Design 3 is required.","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F18-skydashnet-material-design-3-ui-skill\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7D5A2RS4MAX9H0CGT60NQ1B","web-design-guidelines","Web platform design and accessibility guidelines. Use when building web interfaces, auditing accessibility, implementing responsive layouts, or reviewing web UI code. Triggers on tasks involving HTML, CSS, web components, WCAG compliance, responsive design, or web performance.","https:\u002F\u002Fgithub.com\u002FDarshan8610\u002FDynamic-Island\u002Fblob\u002Fmain\u002Fused skills\u002F17-ehmo-platform-design-skills\u002Fskills\u002Fweb\u002FSKILL.md",[],[]]