Compose and Compose Multiplatform expert skill for UI development across Android, Desktop, iOS, and Web. Guides state management, view composition, animations, navigation, performance, design-to-code workflows, and production crash patterns. Backed by actual source code analysis from both androidx/androidx and JetBrains/compose-multiplatform-core. Use this skill whenever the user mentions Compose, @Composable, remember, LaunchedEffect, Scaffold, NavHost, MaterialTheme, LazyColumn, Modifier, recomposition, Style, styleable, MutableStyleState, Compose Multiplatform, CMP, KMP, commonMain, expect, actual, ComposeUIViewController, Window composable, UIKitView, ComposeViewport, Res.drawable, Res.string, or any Compose API. Also trigger when the user says "Android UI", "Kotlin UI", "compose layout", "compose navigation", "compose animation", "material3", "compose styles", "compose multiplatform", "desktop compose", "iOS compose", "compose web", "design to compose", "build this UI", "implement this design", or asks about modern Kotlin UI development patterns. Even casual mentions like "my compose screen is slow" or "how do I pass data between screens" should trigger this skill. --- # Compose Expert Skill Non-opinionated, practical guidance for writing correct, performant Compose code — across Android, Desktop, iOS, and Web. Covers Jetpack Compose and Compose Multiplatform. Backed by analysis of actual source code from `androidx/androidx` and `JetBrains/compose-multiplatform-core`. ## Workflow When helping with Compose code, follow this checklist: ### 1. Understand the request - What Compose layer is involved? (Runtime, UI, Foundation, Material3, Navigation) - Is this a state problem, layout problem, performance problem, or architecture question? - Is this Android-only or Compose Multiplatform (CMP)? ### 2. Analyze the design (if visual reference provided) - If the user shares a Figma frame, screenshot, or design spec, consult `references/design-to-compose.md` - Decompose th
Attach a DuckDB database file for use with /duckdb-skills:query. Explores the schema (tables, columns, row counts) and writes a SQL state file so subsequent queries can restore this session automatically via duckdb -init.
Research a topic deeply, plan a blog step by step, and write a long-form article with structured Markdown outputs in the current working directory. Supports multilingual writing, source tracking, metadata generation, and optional image insertion via available image tools.
Use when ACP schema is necessary to clarify the work or when the user asks for ACP data, rules, events, or documentation --- # ACP documentation and schema
- 📁 reference/
- 📁 scripts/
- 📄 SKILL.md
High-performance data analysis using Polars - load, transform, aggregate, visualize and export tabular data. Use for CSV/JSON/Parquet processing, statistical analysis, time series, and creating charts.
- 📄 cloudperf_api.py
- 📄 SKILL.md
CloudPerf network performance testing tool. Query cloud network quality data including citysets, countries, cities, ASNs, and performance metrics between source and destination nodes. Use when the user asks about network performance, latency, cloud region comparison, or CloudPerf data.
- 📁 references/
- 📁 templates/
- 📄 SKILL.md
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
Internal logic and data flow philosophy (The 5 Laws of Elegant Defense). Understand deeply to ensure code guides data naturally and prevents errors.
Content Analyzer — any content (URL, text, transcript) into structured analysis report with actionable insights. Use when user asks to analyze, summarize, or extract key takeaways from content.
- 📁 .claude/
- 📁 .claude-plugin/
- 📁 .github/
- 📄 .cursorrules
- 📄 .gitignore
- 📄 API.md
Live affiliate program data from list.affitor.com. Search programs, compare commissions, check cookie days, find top performers. Use when researching affiliate programs, comparing options, or checking program details. Persistent daemon with cache — first call starts server (~2s), subsequent calls ~100ms.
- 📁 assets/
- 📁 hooks/
- 📁 references/
- 📄 .gitignore
- 📄 CREDITS.md
- 📄 LICENSE
Agentforce session tracing extraction and analysis.
