Model end-to-end search data flow from user input to UI.
npx skills add https://github.com/mrndstvndv/Search --skill search-dataflow
Please help me install this Agent Skill. Skill: search-dataflow Source: https://github.com/mrndstvndv/Search/tree/main/.opencode/skill/search-dataflow Command: npx skills add https://github.com/mrndstvndv/Search --skill search-dataflow
This guide demonstrates how to model and reason about the complete data flow of a search UI, from user input to live results, including debouncing, alias resolution, provider coordination, aggregation, and ranking.
Provide a sample search query in the UI and observe how input debounces, aliases are resolved, providers are dispatched, results are aggregated and ranked, and the UI updates.
High-intent search queries and answers about installing and using this skill.
You orchestrate search data flow by modeling query creation, applying debounce, resolving aliases, dispatching to providers, aggregating results, and ranking them for reactive state-driven UI updates. This approach uses Kotlin state management constructs like StateFlow and SharedFlow.
Managing multiple search providers involves dispatching asynchronous queries to each provider and aggregating the responses. The data flow architecture handles provider coordination and aggregates results before applying ranking and triggering reactive state updates.
Debounce works with StateFlow and SharedFlow by delaying query processing during rapid input changes. This filters out intermediate keystrokes, ensuring the search architecture only dispatches asynchronous provider queries when user input stabilizes under varying load conditions.
Yes, you can use SharedPreferences to persist search settings and remember user preferences across sessions. The search data flow architecture integrates this persistence mechanism alongside reactive state management to maintain configuration continuity.
Yes, the search data flow architecture supports reactive UI updates using mutableStateOf and mutableStateListOf. These Kotlin state management patterns drive live results rendering after query aggregation, alias resolution, and ranking complete.
You should not use a centralized search data flow if your application only queries a single static data source without needing alias resolution, debounce, or multi-provider aggregation. The architecture targets interactive search experiences combining multiple asynchronous providers.
thinhtt264Manage Android UI state with ViewModel, StateFlow, and SharedFlow.
PatternsDevSwitch Vue components dynamically using the is binding and KeepAlive.
luongldptitImplement structured concurrency and Flow patterns for Kotlin Android and Multiplatform projects.
XiaoPuOuOImplement structured concurrency and Flow-based streams in Kotlin apps.
