[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76RXT0CS6NB03JTNGSZXN0E":3,"skill-same:01M76RXT0CS6NB03JTNGSZXN0E":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},"01M76RXT0CS6NB03JTNGSZXN0E","compose-multiplatform-patterns",null,"Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.","AlexanderNarbaev\u002Fagi","AlexanderNarbaev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F33544956?v=4","01M755ZKB1JJ26ZBNZSDJ4C0TV","01M755ZKBX072HZMHVQBWK7MK7",1,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fcompose-multiplatform-patterns\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: compose-multiplatform-patterns\ndescription: Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.\nused-by:\n  - \"Code\"\n  - \"General\"\nschemaVersion: \"v0.1\"\n---\n\n# Compose Multiplatform Patterns\n\nPatterns for building shared UI across Android, iOS, Desktop, and Web using Compose Multiplatform and Jetpack Compose. Covers state management, navigation, theming, and performance.\n\n## When to Activate\n\n- Building Compose UI (Jetpack Compose or Compose Multiplatform)\n- Managing UI state with ViewModels and Compose state\n- Implementing navigation in KMP or Android projects\n- Designing reusable composables and design systems\n- Optimizing recomposition and rendering performance\n\n## State Management\n\n### ViewModel + Single State Object\n\nUse a single data class for screen state. Expose it as `StateFlow` and collect in Compose:\n\n```kotlin\ndata class ItemListState(\n    val items: List\u003CItem> = emptyList(),\n    val isLoading: Boolean = false,\n    val error: String? = null,\n    val searchQuery: String = \"\"\n)\n\nclass ItemListViewModel(\n    private val getItems: GetItemsUseCase\n) : ViewModel() {\n    private val _state = MutableStateFlow(ItemListState())\n    val state: StateFlow\u003CItemListState> = _state.asStateFlow()\n\n    fun onSearch(query: String) {\n        _state.update { it.copy(searchQuery = query) }\n        loadItems(query)\n    }\n\n    private fun loadItems(query: String) {\n        viewModelScope.launch {\n            _state.update { it.copy(isLoading = true) }\n            getItems(query).fold(\n                onSuccess = { items -> _state.update { it.copy(items = items, isLoading = false) } },\n                onFailure = { e -> _state.update { it.copy(error = e.message, isLoading = false) } }\n            )\n        }\n    }\n}\n```\n\n### Collecting State in Compose\n\n```kotlin\n@Composable\nfun ItemListScreen(viewModel: ItemListViewModel = koinViewModel()) {\n    val state by viewModel.state.collectAsStateWithLifecycle()\n\n    ItemListContent(\n        state = state,\n        onSearch = viewModel::onSearch\n    )\n}\n\n@Composable\nprivate fun ItemListContent(\n    state: ItemListState,\n    onSearch: (String) -> Unit\n) {\n    \u002F\u002F Stateless composable — easy to preview and test\n}\n```\n\n### Event Sink Pattern\n\nFor complex screens, use a sealed interface for events instead of multiple callback lambdas:\n\n```kotlin\nsealed interface ItemListEvent {\n    data class Search(val query: String) : ItemListEvent\n    data class Delete(val itemId: String) : ItemListEvent\n    data object Refresh : ItemListEvent\n}\n\n\u002F\u002F In ViewModel\nfun onEvent(event: ItemListEvent) {\n    when (event) {\n        is ItemListEvent.Search -> onSearch(event.query)\n        is ItemListEvent.Delete -> deleteItem(event.itemId)\n        is ItemListEvent.Refresh -> loadItems(_state.value.searchQuery)\n    }\n}\n\n\u002F\u002F In Composable — single lambda instead of many\nItemListContent(\n    state = state,\n    onEvent = viewModel::onEvent\n)\n```\n\n## Navigation\n\n### Type-Safe Navigation (Compose Navigation 2.8+)\n\nDefine routes as `@Serializable` objects:\n\n```kotlin\n@Serializable data object HomeRoute\n@Serializable data class DetailRoute(val id: String)\n@Serializable data object SettingsRoute\n\n@Composable\nfun AppNavHost(navController: NavHostController = rememberNavController()) {\n    NavHost(navController, startDestination = HomeRoute) {\n        composable\u003CHomeRoute> {\n            HomeScreen(onNavigateToDetail = { id -> navController.navigate(DetailRoute(id)) })\n        }\n        composable\u003CDetailRoute> { backStackEntry ->\n            val route = backStackEntry.toRoute\u003CDetailRoute>()\n            DetailScreen(id = route.id)\n        }\n        composable\u003CSettingsRoute> { SettingsScreen() }\n    }\n}\n```\n\n### Dialog and Bottom Sheet Navigation\n\nUse `dialog()` and overlay patterns instead of imperative show\u002Fhide:\n\n```kotlin\nNavHost(navController, startDestination = HomeRoute) {\n    composable\u003CHomeRoute> { \u002F* ... *\u002F }\n    dialog\u003CConfirmDeleteRoute> { backStackEntry ->\n        val route = backStackEntry.toRoute\u003CConfirmDeleteRoute>()\n        ConfirmDeleteDialog(\n            itemId = route.itemId,\n            onConfirm = { navController.popBackStack() },\n            onDismiss = { navController.popBackStack() }\n        )\n    }\n}\n```\n\n## Composable Design\n\n### Slot-Based APIs\n\nDesign composables with slot parameters for flexibility:\n\n```kotlin\n@Composable\nfun AppCard(\n    modifier: Modifier = Modifier,\n    header: @Composable () -> Unit = {},\n    content: @Composable ColumnScope.() -> Unit,\n    actions: @Composable RowScope.() -> Unit = {}\n) {\n    Card(modifier = modifier) {\n        Column {\n            header()\n            Column(content = content)\n            Row(horizontalArrangement = Arrangement.End, content = actions)\n        }\n    }\n}\n```\n\n### Modifier Ordering\n\nModifier order matters — apply in this sequence:\n\n```kotlin\nText(\n    text = \"Hello\",\n    modifier = Modifier\n        .padding(16.dp)          \u002F\u002F 1. Layout (padding, size)\n        .clip(RoundedCornerShape(8.dp))  \u002F\u002F 2. Shape\n        .background(Color.White) \u002F\u002F 3. Drawing (background, border)\n        .clickable { }           \u002F\u002F 4. Interaction\n)\n```\n\n## KMP Platform-Specific UI\n\n### expect\u002Factual for Platform Composables\n\n```kotlin\n\u002F\u002F commonMain\n@Composable\nexpect fun PlatformStatusBar(darkIcons: Boolean)\n\n\u002F\u002F androidMain\n@Composable\nactual fun PlatformStatusBar(darkIcons: Boolean) {\n    val systemUiController = rememberSystemUiController()\n    SideEffect { systemUiController.setStatusBarColor(Color.Transparent, darkIcons) }\n}\n\n\u002F\u002F iosMain\n@Composable\nactual fun PlatformStatusBar(darkIcons: Boolean) {\n    \u002F\u002F iOS handles this via UIKit interop or Info.plist\n}\n```\n\n## Performance\n\n### Stable Types for Skippable Recomposition\n\nMark classes as `@Stable` or `@Immutable` when all properties are stable:\n\n```kotlin\n@Immutable\ndata class ItemUiModel(\n    val id: String,\n    val title: String,\n    val description: String,\n    val progress: Float\n)\n```\n\n### Use `key()` and Lazy Lists Correctly\n\n```kotlin\nLazyColumn {\n    items(\n        items = items,\n        key = { it.id }  \u002F\u002F Stable keys enable item reuse and animations\n    ) { item ->\n        ItemRow(item = item)\n    }\n}\n```\n\n### Defer Reads with `derivedStateOf`\n\n```kotlin\nval listState = rememberLazyListState()\nval showScrollToTop by remember {\n    derivedStateOf { listState.firstVisibleItemIndex > 5 }\n}\n```\n\n### Avoid Allocations in Recomposition\n\n```kotlin\n\u002F\u002F BAD — new lambda and list every recomposition\nitems.filter { it.isActive }.forEach { ActiveItem(it, onClick = { handle(it) }) }\n\n\u002F\u002F GOOD — key each item so callbacks stay attached to the right row\nval activeItems = remember(items) { items.filter { it.isActive } }\nactiveItems.forEach { item ->\n    key(item.id) {\n        ActiveItem(item, onClick = { handle(item) })\n    }\n}\n```\n\n## Theming\n\n### Material 3 Dynamic Theming\n\n```kotlin\n@Composable\nfun AppTheme(\n    darkTheme: Boolean = isSystemInDarkTheme(),\n    dynamicColor: Boolean = true,\n    content: @Composable () -> Unit\n) {\n    val colorScheme = when {\n        dynamicColor && Build.VERSION.SDK_INT >= Build.VERSION_CODES.S -> {\n            if (darkTheme) dynamicDarkColorScheme(LocalContext.current)\n            else dynamicLightColorScheme(LocalContext.current)\n        }\n        darkTheme -> darkColorScheme()\n        else -> lightColorScheme()\n    }\n\n    MaterialTheme(colorScheme = colorScheme, content = content)\n}\n```\n\n## Anti-Patterns to Avoid\n\n- Using `mutableStateOf` in ViewModels when `MutableStateFlow` with `collectAsStateWithLifecycle` is safer for lifecycle\n- Passing `NavController` deep into composables — pass lambda callbacks instead\n- Heavy computation inside `@Composable` functions — move to ViewModel or `remember {}`\n- Using `LaunchedEffect(Unit)` as a substitute for ViewModel init — it re-runs on configuration change in some setups\n- Creating new object instances in composable parameters — causes unnecessary recomposition\n\n## References\n\nSee skill: `android-clean-architecture` for module structure and layering.\nSee skill: `kotlin-coroutines-flows` for coroutine and Flow patterns.\n","# Compose Multiplatform Patterns\n\nPatterns for building shared UI across Android, iOS, Desktop, and Web using Compose Multiplatform and Jetpack Compose. Covers state management, navigation, theming, and performance.\n\n## When to Activate\n\n- Building Compose UI (Jetpack Compose or Compose Multiplatform)\n- Managing UI state with ViewModels and Compose state\n- Implementing navigation in KMP or Android projects\n- Designing reusable composables and design systems\n- Optimizing recomposition and rendering performance\n\n## State Management\n\n### ViewModel + Single State Object\n\nUse a single data class for screen state. Expose it as `StateFlow` and collect in Compose:\n\n```kotlin\ndata class ItemListState(\n    val items: List\u003CItem> = emptyList(),\n    val isLoading: Boolean = false,\n    val error: String? = null,\n    val searchQuery: String = \"\"\n)\n\nclass ItemListViewModel(\n    private val getItems: GetItemsUseCase\n) : ViewModel() {\n    private val _state = MutableStateFlow(ItemListState())\n    val state: StateFlow\u003CItemListState> = _state.asStateFlow()\n\n    fun onSearch(query: String) {\n        _state.update { it.copy(searchQuery = query) }\n        loadItems(query)\n    }\n\n    private fun loadItems(query: String) {\n        viewModelScope.launch {\n            _state.update { it.copy(isLoading = true) }\n            getItems(query).fold(\n                onSuccess = { items -> _state.update { it.copy(items = items, isLoading = false) } },\n                onFailure = { e -> _state.update { it.copy(error = e.message, isLoading = false) } }\n            )\n        }\n    }\n}\n```\n\n### Collecting State in Compose\n\n```kotlin\n@Composable\nfun ItemListScreen(viewModel: ItemListViewModel = koinViewModel()) {\n    val state by viewModel.state.collectAsStateWithLifecycle()\n\n    ItemListContent(\n        state = state,\n        onSearch = viewModel::onSearch\n    )\n}\n\n@Composable\nprivate fun ItemListContent(\n    state: ItemListState,\n    onSearch: (String) -> Unit\n) {\n    \u002F\u002F Stateless composable — easy to preview and test\n}\n```\n\n### Event Sink Pattern\n\nFor complex screens, use a sealed interface for events instead of multiple callback lambdas:\n\n```kotlin\nsealed interface ItemListEvent {\n    data class Search(val query: String) : ItemListEvent\n    data class Delete(val itemId: String) : ItemListEvent\n    data object Refresh : ItemListEvent\n}\n\n\u002F\u002F In ViewModel\nfun onEvent(event: ItemListEvent) {\n    when (event) {\n        is ItemListEvent.Search -> onSearch(event.query)\n        is ItemListEvent.Delete -> deleteItem(event.itemId)\n        is ItemListEvent.Refresh -> loadItems(_state.value.searchQuery)\n    }\n}\n\n\u002F\u002F In Composable — single lambda instead of many\nItemListContent(\n    state = state,\n    onEvent = viewModel::onEvent\n)\n```\n\n## Navigation\n\n### Type-Safe Navigation (Compose Navigation 2.8+)\n\nDefine routes as `@Serializable` objects:\n\n```kotlin\n@Serializable data object HomeRoute\n@Serializable data class DetailRoute(val id: String)\n@Serializable data object SettingsRoute\n\n@Composable\nfun AppNavHost(navController: NavHostController = rememberNavController()) {\n    NavHost(navController, startDestination = HomeRoute) {\n        composable\u003CHomeRoute> {\n            HomeScreen(onNavigateToDetail = { id -> navController.navigate(DetailRoute(id)) })\n        }\n        composable\u003CDetailRoute> { backStackEntry ->\n            val route = backStackEntry.toRoute\u003CDetailRoute>()\n            DetailScreen(id = route.id)\n        }\n        composable\u003CSettingsRoute> { SettingsScreen() }\n    }\n}\n```\n\n### Dialog and Bottom Sheet Navigation\n\nUse `dialog()` and overlay patterns instead of imperative show\u002Fhide:\n\n```kotlin\nNavHost(navController, startDestination = HomeRoute) {\n    composable\u003CHomeRoute> { \u002F* ... *\u002F }\n    dialog\u003CConfirmDeleteRoute> { backStackEntry ->\n        val route = backStackEntry.toRoute\u003CConfirmDeleteRoute>()\n        ConfirmDeleteDialog(\n            itemId = route.itemId,\n            onConfirm = { navController.popBackStack() },\n            onDismiss = { navController.popBackStack() }\n        )\n    }\n}\n```\n\n## Composable Design\n\n### Slot-Based APIs\n\nDesign composables with slot parameters for flexibility:\n\n```kotlin\n@Composable\nfun AppCard(\n    modifier: Modifier = Modifier,\n    header: @Composable () -> Unit = {},\n    content: @Composable ColumnScope.() -> Unit,\n    actions: @Composable RowScope.() -> Unit = {}\n) {\n    Card(modifier = modifier) {\n        Column {\n            header()\n            Column(content = content)\n            Row(horizontalArrangement = Arrangement.End, content = actions)\n        }\n    }\n}\n```\n\n### Modifier Ordering\n\nModifier order matters — apply in this sequence:\n\n```kotlin\nText(\n    text = \"Hello\",\n    modifier = Modifier\n        .padding(16.dp)          \u002F\u002F 1. Layout (padding, size)\n        .clip(RoundedCornerShape(8.dp))  \u002F\u002F 2. Shape\n        .background(Color.White) \u002F\u002F 3. Drawing (background, border)\n        .clickable { }           \u002F\u002F 4. Interaction\n)\n```\n\n## KMP Platform-Specific UI\n\n### expect\u002Factual for Platform Composables\n\n```kotlin\n\u002F\u002F commonMain\n@Composable\nexpect fun PlatformStatusBar(darkIcons: Boolean)\n\n\u002F\u002F androidMain\n@Composable\nactual fun PlatformStatusBar(darkIcons: Boolean) {\n    val systemUiController = rememberSystemUiController()\n    SideEffect { systemUiController.setStatusBarColor(Color.Transparent, darkIcons) }\n}\n\n\u002F\u002F iosMain\n@Composable\nactual fun PlatformStatusBar(darkIcons: Boolean) {\n    \u002F\u002F iOS handles this via UIKit interop or Info.plist\n}\n```\n\n## Performance\n\n### Stable Types for Skippable Recomposition\n\nMark classes as `@Stable` or `@Immutable` when all properties are stable:\n\n```kotlin\n@Immutable\ndata class ItemUiModel(\n    val id: String,\n    val title: String,\n    val description: String,\n    val progress: Float\n)\n```\n\n### Use `key()` and Lazy Lists Correctly\n\n```kotlin\nLazyColumn {\n    items(\n        items = items,\n        key = { it.id }  \u002F\u002F Stable keys enable item reuse and animations\n    ) { item ->\n        ItemRow(item = item)\n    }\n}\n```\n\n### Defer Reads with `derivedStateOf`\n\n```kotlin\nval listState = rememberLazyListState()\nval showScrollToTop by remember {\n    derivedStateOf { listState.firstVisibleItemIndex > 5 }\n}\n```\n\n### Avoid Allocations in Recomposition\n\n```kotlin\n\u002F\u002F BAD — new lambda and list every recomposition\nitems.filter { it.isActive }.forEach { ActiveItem(it, onClick = { handle(it) }) }\n\n\u002F\u002F GOOD — key each item so callbacks stay attached to the right row\nval activeItems = remember(items) { items.filter { it.isActive } }\nactiveItems.forEach { item ->\n    key(item.id) {\n        ActiveItem(item, onClick = { handle(item) })\n    }\n}\n```\n\n## Theming\n\n### Material 3 Dynamic Theming\n\n```kotlin\n@Composable\nfun AppTheme(\n    darkTheme: Boolean = isSystemInDarkTheme(),\n    dynamicColor: Boolean = true,\n    content: @Composable () -> Unit\n) {\n    val colorScheme = when {\n        dynamicColor && Build.VERSION.SDK_INT >= Build.VERSION_CODES.S -> {\n            if (darkTheme) dynamicDarkColorScheme(LocalContext.current)\n            else dynamicLightColorScheme(LocalContext.current)\n        }\n        darkTheme -> darkColorScheme()\n        else -> lightColorScheme()\n    }\n\n    MaterialTheme(colorScheme = colorScheme, content = content)\n}\n```\n\n## Anti-Patterns to Avoid\n\n- Using `mutableStateOf` in ViewModels when `MutableStateFlow` with `collectAsStateWithLifecycle` is safer for lifecycle\n- Passing `NavController` deep into composables — pass lambda callbacks instead\n- Heavy computation inside `@Composable` functions — move to ViewModel or `remember {}`\n- Using `LaunchedEffect(Unit)` as a substitute for ViewModel init — it re-runs on configuration change in some setups\n- Creating new object instances in composable parameters — causes unnecessary recomposition\n\n## References\n\nSee skill: `android-clean-architecture` for module structure and layering.\nSee skill: `kotlin-coroutines-flows` for coroutine and Flow patterns.\n",{"name":5,"used-by":23,"description":7,"schemaVersion":26},[24,25],"Code","General","v0.1","main","7709dc9e5ebd3bd641124ad2a3f6bb053ac2dab6",".veai\u002Fskills\u002Fcompose-multiplatform-patterns",0,"https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev","2026-11-15 04:35:36",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add AlexanderNarbaev\u002Fagi --skill compose-multiplatform-patterns",{"tool":40,"command":41},"bunx","bunx skills add AlexanderNarbaev\u002Fagi --skill compose-multiplatform-patterns",{"tool":43,"command":44},"pnpm","pnpm dlx skills add AlexanderNarbaev\u002Fagi --skill compose-multiplatform-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fcompose-multiplatform-patterns\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"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":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M76RZHYHMGE1WP9JBCMNA801","springboot-patterns","Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fspringboot-patterns\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M76RZE6JNZH5HV7Q8JM7R0PN","search-first","Research-before-coding workflow. Search for existing tools, libraries, and patterns before writing custom code. Invokes the researcher agent.","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fsearch-first\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M76RZBV42EMQV77H7GMFY4AJ","scholar-evaluation","Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fscholar-evaluation\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M76RZ97GC3XAY48H126C30PM","redis-patterns","Redis data structure patterns, caching strategies, distributed locks, rate limiting, pub\u002Fsub, and connection management for production applications.","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fredis-patterns\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M76RZ528FANTKX7Q9XR0CXM7","react-patterns","React 18\u002F19 patterns including hooks discipline, server\u002Fclient component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Freact-patterns\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M76RZ1244PZQRQV5HBQ4PVYQ","query-patterns","SQL patterns, relational database design, query optimization, transactions, analytics, and dialect-aware best practices.","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fquery-patterns\u002FSKILL.md",[],[]]