[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FD2TX8DST8NEJWH446TKBJ":3,"skill-same:01M7FD2TX8DST8NEJWH446TKBJ":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7FD2TX8DST8NEJWH446TKBJ","android-clean-architecture",null,"Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns. Use when structuring modules, layers, or data flow in an Android or KMP project.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fmobile\u002Fskills\u002Fandroid-clean-architecture\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: android-clean-architecture\ndescription: Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns. Use when structuring modules, layers, or data flow in an Android or KMP project.\nmetadata:\n  origin: ECC\n---\n\n# Android Clean Architecture\n\nClean Architecture patterns for Android and KMP projects. Covers module boundaries, dependency inversion, UseCase\u002FRepository patterns, and data layer design with Room, SQLDelight, and Ktor.\n\n## When to Activate\n\n- Structuring Android or KMP project modules\n- Implementing UseCases, Repositories, or DataSources\n- Designing data flow between layers (domain, data, presentation)\n- Setting up dependency injection with Koin or Hilt\n- Working with Room, SQLDelight, or Ktor in a layered architecture\n\n## Module Structure\n\n### Recommended Layout\n\n```\nproject\u002F\n├── app\u002F                  # Android entry point, DI wiring, Application class\n├── core\u002F                 # Shared utilities, base classes, error types\n├── domain\u002F               # UseCases, domain models, repository interfaces (pure Kotlin)\n├── data\u002F                 # Repository implementations, DataSources, DB, network\n├── presentation\u002F         # Screens, ViewModels, UI models, navigation\n├── design-system\u002F        # Reusable Compose components, theme, typography\n└── feature\u002F              # Feature modules (optional, for larger projects)\n    ├── auth\u002F\n    ├── settings\u002F\n    └── profile\u002F\n```\n\n### Dependency Rules\n\n```\napp → presentation, domain, data, core\npresentation → domain, design-system, core\ndata → domain, core\ndomain → core (or no dependencies)\ncore → (nothing)\n```\n\n**Critical**: `domain` must NEVER depend on `data`, `presentation`, or any framework. It contains pure Kotlin only.\n\n## Domain Layer\n\n### UseCase Pattern\n\nEach UseCase represents one business operation. Use `operator fun invoke` for clean call sites:\n\n```kotlin\nclass GetItemsByCategoryUseCase(\n    private val repository: ItemRepository\n) {\n    suspend operator fun invoke(category: String): Result\u003CList\u003CItem>> {\n        return repository.getItemsByCategory(category)\n    }\n}\n\n\u002F\u002F Flow-based UseCase for reactive streams\nclass ObserveUserProgressUseCase(\n    private val repository: UserRepository\n) {\n    operator fun invoke(userId: String): Flow\u003CUserProgress> {\n        return repository.observeProgress(userId)\n    }\n}\n```\n\n### Domain Models\n\nDomain models are plain Kotlin data classes — no framework annotations:\n\n```kotlin\ndata class Item(\n    val id: String,\n    val title: String,\n    val description: String,\n    val tags: List\u003CString>,\n    val status: Status,\n    val category: String\n)\n\nenum class Status { DRAFT, ACTIVE, ARCHIVED }\n```\n\n### Repository Interfaces\n\nDefined in domain, implemented in data:\n\n```kotlin\ninterface ItemRepository {\n    suspend fun getItemsByCategory(category: String): Result\u003CList\u003CItem>>\n    suspend fun saveItem(item: Item): Result\u003CUnit>\n    fun observeItems(): Flow\u003CList\u003CItem>>\n}\n```\n\n## Data Layer\n\n### Repository Implementation\n\nCoordinates between local and remote data sources:\n\n```kotlin\nclass ItemRepositoryImpl(\n    private val localDataSource: ItemLocalDataSource,\n    private val remoteDataSource: ItemRemoteDataSource\n) : ItemRepository {\n\n    override suspend fun getItemsByCategory(category: String): Result\u003CList\u003CItem>> {\n        return runCatching {\n            val remote = remoteDataSource.fetchItems(category)\n            localDataSource.insertItems(remote.map { it.toEntity() })\n            localDataSource.getItemsByCategory(category).map { it.toDomain() }\n        }\n    }\n\n    override suspend fun saveItem(item: Item): Result\u003CUnit> {\n        return runCatching {\n            localDataSource.insertItems(listOf(item.toEntity()))\n        }\n    }\n\n    override fun observeItems(): Flow\u003CList\u003CItem>> {\n        return localDataSource.observeAll().map { entities ->\n            entities.map { it.toDomain() }\n        }\n    }\n}\n```\n\n### Mapper Pattern\n\nKeep mappers as extension functions near the data models:\n\n```kotlin\n\u002F\u002F In data layer\nfun ItemEntity.toDomain() = Item(\n    id = id,\n    title = title,\n    description = description,\n    tags = tags.split(\"|\"),\n    status = Status.valueOf(status),\n    category = category\n)\n\nfun ItemDto.toEntity() = ItemEntity(\n    id = id,\n    title = title,\n    description = description,\n    tags = tags.joinToString(\"|\"),\n    status = status,\n    category = category\n)\n```\n\n### Room Database (Android)\n\n```kotlin\n@Entity(tableName = \"items\")\ndata class ItemEntity(\n    @PrimaryKey val id: String,\n    val title: String,\n    val description: String,\n    val tags: String,\n    val status: String,\n    val category: String\n)\n\n@Dao\ninterface ItemDao {\n    @Query(\"SELECT * FROM items WHERE category = :category\")\n    suspend fun getByCategory(category: String): List\u003CItemEntity>\n\n    @Upsert\n    suspend fun upsert(items: List\u003CItemEntity>)\n\n    @Query(\"SELECT * FROM items\")\n    fun observeAll(): Flow\u003CList\u003CItemEntity>>\n}\n```\n\n### SQLDelight (KMP)\n\n```sql\n-- Item.sq\nCREATE TABLE ItemEntity (\n    id TEXT NOT NULL PRIMARY KEY,\n    title TEXT NOT NULL,\n    description TEXT NOT NULL,\n    tags TEXT NOT NULL,\n    status TEXT NOT NULL,\n    category TEXT NOT NULL\n);\n\ngetByCategory:\nSELECT * FROM ItemEntity WHERE category = ?;\n\nupsert:\nINSERT OR REPLACE INTO ItemEntity (id, title, description, tags, status, category)\nVALUES (?, ?, ?, ?, ?, ?);\n\nobserveAll:\nSELECT * FROM ItemEntity;\n```\n\n### Ktor Network Client (KMP)\n\n```kotlin\nclass ItemRemoteDataSource(private val client: HttpClient) {\n\n    suspend fun fetchItems(category: String): List\u003CItemDto> {\n        return client.get(\"api\u002Fitems\") {\n            parameter(\"category\", category)\n        }.body()\n    }\n}\n\n\u002F\u002F HttpClient setup with content negotiation\nval httpClient = HttpClient {\n    install(ContentNegotiation) { json(Json { ignoreUnknownKeys = true }) }\n    install(Logging) { level = LogLevel.HEADERS }\n    defaultRequest { url(\"https:\u002F\u002Fapi.example.com\u002F\") }\n}\n```\n\n## Dependency Injection\n\n### Koin (KMP-friendly)\n\n```kotlin\n\u002F\u002F Domain module\nval domainModule = module {\n    factory { GetItemsByCategoryUseCase(get()) }\n    factory { ObserveUserProgressUseCase(get()) }\n}\n\n\u002F\u002F Data module\nval dataModule = module {\n    single\u003CItemRepository> { ItemRepositoryImpl(get(), get()) }\n    single { ItemLocalDataSource(get()) }\n    single { ItemRemoteDataSource(get()) }\n}\n\n\u002F\u002F Presentation module\nval presentationModule = module {\n    viewModelOf(::ItemListViewModel)\n    viewModelOf(::DashboardViewModel)\n}\n```\n\n### Hilt (Android-only)\n\n```kotlin\n@Module\n@InstallIn(SingletonComponent::class)\nabstract class RepositoryModule {\n    @Binds\n    abstract fun bindItemRepository(impl: ItemRepositoryImpl): ItemRepository\n}\n\n@HiltViewModel\nclass ItemListViewModel @Inject constructor(\n    private val getItems: GetItemsByCategoryUseCase\n) : ViewModel()\n```\n\n## Error Handling\n\n### Result\u002FTry Pattern\n\nUse `Result\u003CT>` or a custom sealed type for error propagation:\n\n```kotlin\nsealed interface Try\u003Cout T> {\n    data class Success\u003CT>(val value: T) : Try\u003CT>\n    data class Failure(val error: AppError) : Try\u003CNothing>\n}\n\nsealed interface AppError {\n    data class Network(val message: String) : AppError\n    data class Database(val message: String) : AppError\n    data object Unauthorized : AppError\n}\n\n\u002F\u002F In ViewModel — map to UI state\nviewModelScope.launch {\n    when (val result = getItems(category)) {\n        is Try.Success -> _state.update { it.copy(items = result.value, isLoading = false) }\n        is Try.Failure -> _state.update { it.copy(error = result.error.toMessage(), isLoading = false) }\n    }\n}\n```\n\n## Convention Plugins (Gradle)\n\nFor KMP projects, use convention plugins to reduce build file duplication:\n\n```kotlin\n\u002F\u002F build-logic\u002Fsrc\u002Fmain\u002Fkotlin\u002Fkmp-library.gradle.kts\nplugins {\n    id(\"org.jetbrains.kotlin.multiplatform\")\n}\n\nkotlin {\n    androidTarget()\n    iosX64(); iosArm64(); iosSimulatorArm64()\n    sourceSets {\n        commonMain.dependencies { \u002F* shared deps *\u002F }\n        commonTest.dependencies { implementation(kotlin(\"test\")) }\n    }\n}\n```\n\nApply in modules:\n\n```kotlin\n\u002F\u002F domain\u002Fbuild.gradle.kts\nplugins { id(\"kmp-library\") }\n```\n\n## Anti-Patterns to Avoid\n\n- Importing Android framework classes in `domain` — keep it pure Kotlin\n- Exposing database entities or DTOs to the UI layer — always map to domain models\n- Putting business logic in ViewModels — extract to UseCases\n- Using `GlobalScope` or unstructured coroutines — use `viewModelScope` or structured concurrency\n- Fat repository implementations — split into focused DataSources\n- Circular module dependencies — if A depends on B, B must not depend on A\n\n## References\n\nSee skill: `compose-multiplatform-patterns` for UI patterns.\nSee skill: `kotlin-coroutines-flows` for async patterns.\n","# Android Clean Architecture\n\nClean Architecture patterns for Android and KMP projects. Covers module boundaries, dependency inversion, UseCase\u002FRepository patterns, and data layer design with Room, SQLDelight, and Ktor.\n\n## When to Activate\n\n- Structuring Android or KMP project modules\n- Implementing UseCases, Repositories, or DataSources\n- Designing data flow between layers (domain, data, presentation)\n- Setting up dependency injection with Koin or Hilt\n- Working with Room, SQLDelight, or Ktor in a layered architecture\n\n## Module Structure\n\n### Recommended Layout\n\n```\nproject\u002F\n├── app\u002F                  # Android entry point, DI wiring, Application class\n├── core\u002F                 # Shared utilities, base classes, error types\n├── domain\u002F               # UseCases, domain models, repository interfaces (pure Kotlin)\n├── data\u002F                 # Repository implementations, DataSources, DB, network\n├── presentation\u002F         # Screens, ViewModels, UI models, navigation\n├── design-system\u002F        # Reusable Compose components, theme, typography\n└── feature\u002F              # Feature modules (optional, for larger projects)\n    ├── auth\u002F\n    ├── settings\u002F\n    └── profile\u002F\n```\n\n### Dependency Rules\n\n```\napp → presentation, domain, data, core\npresentation → domain, design-system, core\ndata → domain, core\ndomain → core (or no dependencies)\ncore → (nothing)\n```\n\n**Critical**: `domain` must NEVER depend on `data`, `presentation`, or any framework. It contains pure Kotlin only.\n\n## Domain Layer\n\n### UseCase Pattern\n\nEach UseCase represents one business operation. Use `operator fun invoke` for clean call sites:\n\n```kotlin\nclass GetItemsByCategoryUseCase(\n    private val repository: ItemRepository\n) {\n    suspend operator fun invoke(category: String): Result\u003CList\u003CItem>> {\n        return repository.getItemsByCategory(category)\n    }\n}\n\n\u002F\u002F Flow-based UseCase for reactive streams\nclass ObserveUserProgressUseCase(\n    private val repository: UserRepository\n) {\n    operator fun invoke(userId: String): Flow\u003CUserProgress> {\n        return repository.observeProgress(userId)\n    }\n}\n```\n\n### Domain Models\n\nDomain models are plain Kotlin data classes — no framework annotations:\n\n```kotlin\ndata class Item(\n    val id: String,\n    val title: String,\n    val description: String,\n    val tags: List\u003CString>,\n    val status: Status,\n    val category: String\n)\n\nenum class Status { DRAFT, ACTIVE, ARCHIVED }\n```\n\n### Repository Interfaces\n\nDefined in domain, implemented in data:\n\n```kotlin\ninterface ItemRepository {\n    suspend fun getItemsByCategory(category: String): Result\u003CList\u003CItem>>\n    suspend fun saveItem(item: Item): Result\u003CUnit>\n    fun observeItems(): Flow\u003CList\u003CItem>>\n}\n```\n\n## Data Layer\n\n### Repository Implementation\n\nCoordinates between local and remote data sources:\n\n```kotlin\nclass ItemRepositoryImpl(\n    private val localDataSource: ItemLocalDataSource,\n    private val remoteDataSource: ItemRemoteDataSource\n) : ItemRepository {\n\n    override suspend fun getItemsByCategory(category: String): Result\u003CList\u003CItem>> {\n        return runCatching {\n            val remote = remoteDataSource.fetchItems(category)\n            localDataSource.insertItems(remote.map { it.toEntity() })\n            localDataSource.getItemsByCategory(category).map { it.toDomain() }\n        }\n    }\n\n    override suspend fun saveItem(item: Item): Result\u003CUnit> {\n        return runCatching {\n            localDataSource.insertItems(listOf(item.toEntity()))\n        }\n    }\n\n    override fun observeItems(): Flow\u003CList\u003CItem>> {\n        return localDataSource.observeAll().map { entities ->\n            entities.map { it.toDomain() }\n        }\n    }\n}\n```\n\n### Mapper Pattern\n\nKeep mappers as extension functions near the data models:\n\n```kotlin\n\u002F\u002F In data layer\nfun ItemEntity.toDomain() = Item(\n    id = id,\n    title = title,\n    description = description,\n    tags = tags.split(\"|\"),\n    status = Status.valueOf(status),\n    category = category\n)\n\nfun ItemDto.toEntity() = ItemEntity(\n    id = id,\n    title = title,\n    description = description,\n    tags = tags.joinToString(\"|\"),\n    status = status,\n    category = category\n)\n```\n\n### Room Database (Android)\n\n```kotlin\n@Entity(tableName = \"items\")\ndata class ItemEntity(\n    @PrimaryKey val id: String,\n    val title: String,\n    val description: String,\n    val tags: String,\n    val status: String,\n    val category: String\n)\n\n@Dao\ninterface ItemDao {\n    @Query(\"SELECT * FROM items WHERE category = :category\")\n    suspend fun getByCategory(category: String): List\u003CItemEntity>\n\n    @Upsert\n    suspend fun upsert(items: List\u003CItemEntity>)\n\n    @Query(\"SELECT * FROM items\")\n    fun observeAll(): Flow\u003CList\u003CItemEntity>>\n}\n```\n\n### SQLDelight (KMP)\n\n```sql\n-- Item.sq\nCREATE TABLE ItemEntity (\n    id TEXT NOT NULL PRIMARY KEY,\n    title TEXT NOT NULL,\n    description TEXT NOT NULL,\n    tags TEXT NOT NULL,\n    status TEXT NOT NULL,\n    category TEXT NOT NULL\n);\n\ngetByCategory:\nSELECT * FROM ItemEntity WHERE category = ?;\n\nupsert:\nINSERT OR REPLACE INTO ItemEntity (id, title, description, tags, status, category)\nVALUES (?, ?, ?, ?, ?, ?);\n\nobserveAll:\nSELECT * FROM ItemEntity;\n```\n\n### Ktor Network Client (KMP)\n\n```kotlin\nclass ItemRemoteDataSource(private val client: HttpClient) {\n\n    suspend fun fetchItems(category: String): List\u003CItemDto> {\n        return client.get(\"api\u002Fitems\") {\n            parameter(\"category\", category)\n        }.body()\n    }\n}\n\n\u002F\u002F HttpClient setup with content negotiation\nval httpClient = HttpClient {\n    install(ContentNegotiation) { json(Json { ignoreUnknownKeys = true }) }\n    install(Logging) { level = LogLevel.HEADERS }\n    defaultRequest { url(\"https:\u002F\u002Fapi.example.com\u002F\") }\n}\n```\n\n## Dependency Injection\n\n### Koin (KMP-friendly)\n\n```kotlin\n\u002F\u002F Domain module\nval domainModule = module {\n    factory { GetItemsByCategoryUseCase(get()) }\n    factory { ObserveUserProgressUseCase(get()) }\n}\n\n\u002F\u002F Data module\nval dataModule = module {\n    single\u003CItemRepository> { ItemRepositoryImpl(get(), get()) }\n    single { ItemLocalDataSource(get()) }\n    single { ItemRemoteDataSource(get()) }\n}\n\n\u002F\u002F Presentation module\nval presentationModule = module {\n    viewModelOf(::ItemListViewModel)\n    viewModelOf(::DashboardViewModel)\n}\n```\n\n### Hilt (Android-only)\n\n```kotlin\n@Module\n@InstallIn(SingletonComponent::class)\nabstract class RepositoryModule {\n    @Binds\n    abstract fun bindItemRepository(impl: ItemRepositoryImpl): ItemRepository\n}\n\n@HiltViewModel\nclass ItemListViewModel @Inject constructor(\n    private val getItems: GetItemsByCategoryUseCase\n) : ViewModel()\n```\n\n## Error Handling\n\n### Result\u002FTry Pattern\n\nUse `Result\u003CT>` or a custom sealed type for error propagation:\n\n```kotlin\nsealed interface Try\u003Cout T> {\n    data class Success\u003CT>(val value: T) : Try\u003CT>\n    data class Failure(val error: AppError) : Try\u003CNothing>\n}\n\nsealed interface AppError {\n    data class Network(val message: String) : AppError\n    data class Database(val message: String) : AppError\n    data object Unauthorized : AppError\n}\n\n\u002F\u002F In ViewModel — map to UI state\nviewModelScope.launch {\n    when (val result = getItems(category)) {\n        is Try.Success -> _state.update { it.copy(items = result.value, isLoading = false) }\n        is Try.Failure -> _state.update { it.copy(error = result.error.toMessage(), isLoading = false) }\n    }\n}\n```\n\n## Convention Plugins (Gradle)\n\nFor KMP projects, use convention plugins to reduce build file duplication:\n\n```kotlin\n\u002F\u002F build-logic\u002Fsrc\u002Fmain\u002Fkotlin\u002Fkmp-library.gradle.kts\nplugins {\n    id(\"org.jetbrains.kotlin.multiplatform\")\n}\n\nkotlin {\n    androidTarget()\n    iosX64(); iosArm64(); iosSimulatorArm64()\n    sourceSets {\n        commonMain.dependencies { \u002F* shared deps *\u002F }\n        commonTest.dependencies { implementation(kotlin(\"test\")) }\n    }\n}\n```\n\nApply in modules:\n\n```kotlin\n\u002F\u002F domain\u002Fbuild.gradle.kts\nplugins { id(\"kmp-library\") }\n```\n\n## Anti-Patterns to Avoid\n\n- Importing Android framework classes in `domain` — keep it pure Kotlin\n- Exposing database entities or DTOs to the UI layer — always map to domain models\n- Putting business logic in ViewModels — extract to UseCases\n- Using `GlobalScope` or unstructured coroutines — use `viewModelScope` or structured concurrency\n- Fat repository implementations — split into focused DataSources\n- Circular module dependencies — if A depends on B, B must not depend on A\n\n## References\n\nSee skill: `compose-multiplatform-patterns` for UI patterns.\nSee skill: `kotlin-coroutines-flows` for async patterns.\n",{"name":5,"metadata":24,"description":7},{"origin":25},"ECC","main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fmobile\u002Fskills\u002Fandroid-clean-architecture",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add siddu1004\u002FSFP --skill android-clean-architecture",{"tool":41,"command":42},"bunx","bunx skills add siddu1004\u002FSFP --skill android-clean-architecture",{"tool":44,"command":45},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill android-clean-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fmobile\u002Fskills\u002Fandroid-clean-architecture\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]