- 📁 assets/
- 📁 references/
- 📄 README.md
- 📄 SKILL.md
Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization. Ensures data integrity, query performance, and maintainable data models.
Add a ThemedDualListInput to a layrz Flutter form or tab. Use when wiring a new list field from any layrz Input class (e.g. LocatorInput, AssetInput) into any widget — a tab, a form view, or any stateful/stateless widget.
Use when analyzing bash-approve hook decisions, finding commands that needed user approval, identifying candidates for auto-approval, or querying the telemetry database
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
This skill should be used when the user is working on open source contributions, responding to maintainer feedback, writing PR descriptions, working on issues, following up on dormant PRs, or needs guidance on open source etiquette and best practices.
Converts the old flat skills.yaml format to the new per-group file format with variants. Use when a PR or branch still has a top-level "skills:" array instead of separate group files.
- 📁 scripts/
- 📄 examples.md
- 📄 patterns.md
- 📄 README.md
Generates git commit messages following conventional commit standards with collaborative attribution. Use when user requests commit message creation, drafting, or help with formatting.
Use this skill whenever working with QuestDB — a high-performance time-series database. Trigger on any mention of QuestDB, time-series SQL with SAMPLE BY, LATEST ON, ASOF JOIN, ILP ingestion, or the questdb Python/Go/Java/Rust/.NET client libraries. Also trigger when writing Grafana queries against QuestDB, creating materialized views for time-series rollups, working with order book or financial market data in QuestDB, or any SQL that involves designated timestamps or time-partitioned tables. QuestDB extends SQL with unique time-series keywords — standard PostgreSQL or MySQL patterns will fail. Always read this skill before writing QuestDB SQL to avoid hallucinating incorrect syntax. --- # QuestDB Skill ## How to Use This Skill **IMPORTANT — MINIMIZE ROUND-TRIPS:** - Do NOT explore library source code (cryptofeed, questdb, etc.) - Do NOT check library versions or verify callback signatures - Do NOT read installed package files to "understand the API" - Do NOT verify infrastructure (Docker containers, Grafana health) is running — trust the user's prompt - Do NOT start `02_ingest.py` separately — `03_dashboard.py` launches it and verifies data automatically - Do NOT read extra reference files for topics already covered in this skill file - DO read reference files when their topic applies (e.g. enterprise.md for auth, grafana-advanced.md for complex panels) - Do NOT use task tracking (TaskCreate/TaskUpdate) for straightforward builds - Do NOT add `sleep` commands to wait for data or check background processes (the deploy script handles this) - Do NOT Ctrl+C, restart, or re-launch the ingestion process once `03_dashboard.py` has started it - Do NOT put VWAP, Bollinger, or RSI in separate timeseries panels — they are refIDs on the OHLC candlestick panel - Do NOT omit or empty `fieldConfig.overrides` — they put RSI on a right Y-axis (0-100%) and spread on a right axis. Without them, different scales crush the chart flat. - Do NOT set dashboard refresh to `"5s"` — the defa
Generate and validate KSeF FA(3) e-invoices — Poland's mandatory structured invoice format (effective from 2026-02-01 for large companies, 2026-04-01 for all). Use this skill whenever the
— before performing any other task — if ANY of these conditions are detected:
Query and manage Banktivity financial data. Use when the user asks about transactions, accounts, spending, categories, tags, or securities in their Banktivity database.
Guides bulk IP range import or update for a single organization from diverse inputs (paste, Word, Excel, CSV). Resolves organization name to Party.partyId in the DB, builds a five-column Excel keyed by party id (not NSTL serial id), runs BulkPartyLoadIPCheck, overlap filter, batch expire, and BulkPartyLoadIPRange. Requires user approval before destructive steps. Use when the user mentions bulk IP upload for one org, single institution IP update, lookup by institution name, paste IP list, doc/spreadsheet IP import, or non-NSTL bulk IP for one party.