[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M739YMBE5ZPXY5R9CWATD6B8":3,"skill-same:01M739YMBE5ZPXY5R9CWATD6B8":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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M739YMBE5ZPXY5R9CWATD6B8","compose-multiplatform-patterns",null,"Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fcompose-multiplatform-patterns\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: compose-multiplatform-patterns\ndescription: Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.\norigin: ECC\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,"origin":24,"description":7},"ECC","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fcompose-multiplatform-patterns",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill compose-multiplatform-patterns",{"tool":41,"command":42},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill compose-multiplatform-patterns",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill compose-multiplatform-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fcompose-multiplatform-patterns\u002FSKILL.md",true,[],[50,58,65,73,81,89],{"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":54,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"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":92,"categories":93,"keywords":94,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]