Project agent (Gemini CLI). Describes what the project is, what phase it's in, and what to do (and not do) right now. Read before diving into code.
A reusable "global quick-filter flow" library that the user (solo dev) will use across all of their React Native apps.
Inspiration: the highly-praised quick-filter structures of e-commerce apps in Turkey (Trendyol, Hepsiburada, Çiçeksepeti, n11, Trendyol GO, Getir, Amazon TR, etc.) — horizontal chip/pill rows, bottom-sheet filter panels, "sort" menus, quick-filter badges, active-filter summaries.
Goal: consolidate these UX patterns into a single library and plug them into the user's apps as a drop-in.
Library code will NOT be written yet. The repo is currently in the reference-gathering phase.
- The user will first share the filter structures they like (screenshot, video, app name, description).
- These references go into the
references/folder. - Do not write any component/library code until enough references have accumulated and the UX + technical contract are clear.
- If the design, public API surface, package name, or the filter types to be covered are unclear → stop and ask the user, don't proceed on assumptions.
Expected filter primitives (finalized once the user approves):
- Horizontally scrollable quick-filter chip/pill row
- Bottom-sheet filter panel (multi-select, category, price range, size/color, brand, etc.)
- Sort picker
- Active filter counter + "clear filters"
- Summary badges for selected filters
- React Native library, TypeScript (strict).
- Reusable across multiple apps; aims for a headless core + styleable default UI separation.
- Package name:
react-native-quick-filter(temporary — pending user approval). - Localization-first: all user-facing strings must be i18n-ready.
- The theme/design system is not decided silently — references and user approval are authoritative.
references/— filter examples the user liked and shared (image/video/note)docs/— UX contract, API design, decisions- (library source code will be added later)
- Don't write library code before references arrive.
- Don't decide the design system/theme by assumption — the user's examples are authoritative.
- Don't finalize the package name/
package.jsonwithout user approval.