| name | go-wails-sql-client-definition |
| description | Canonical skill index and design language for Zentro (Go + Wails + React + TypeScript SQL client). Read this first to pick the right skill and keep implementation decisions aligned.
|
Go Wails SQL Client Definition
Product Direction
- Stack: Go 1.22+, Wails v2, React + TypeScript, database/sql, pgx v5, go-mssqldb.
- Product shape: local-first desktop SQL client for fast and reliable daily querying.
- Priority order: reliability > maintainability > performance > visual polish.
- Design language: explicit, compact, practical; avoid hidden behavior and decorative complexity.
Core Philosophy
- Keep boundaries explicit: frontend, binding facade, application services, adapters, models.
- Keep abstractions earned: add interfaces only for real variation or test seams.
- Keep behavior observable: contextual errors, structured logs, deterministic state transitions.
- Keep changes local: one feature should mostly touch one ownership boundary.
- Keep extension points intentional: modularity where real long-term variability exists.
Dependency Direction
models <- adapters <- services <- wails facade <- frontend
utils can be shared but must not become a god package
Skill Map
| # | Skill | Use When |
|---|
| 01 | Project Architecture | Defining folders, boundaries, import rules |
| 02 | Connection Management | Working with profiles, connect/test/open flows |
| 03 | Async Query Execution | Running/canceling SQL safely with context |
| 04 | Multi-Tab Editor | Managing tab lifecycle and editor state |
| 05 | Result Grid | Rendering, paging, editing, and selection |
| 06 | UI Layout and App State | Shell composition and state ownership |
| 07 | Export and History | CSV export and query history retention |
| 08 | Preferences and Settings | Keys, defaults, migration-safe settings |
| 09 | Logging | Structured observability and error context |
| 10 | Cross-Platform Build | Packaging and release workflows |
| 11 | Framework Builder | Designing extension points and modular growth |
| 12 | Patterns Enforcer | Choosing minimal patterns with clear tradeoffs |
| 13 | Commit Convention | Writing clear conventional commits |
| 14 | Delivery Flow | Planning and shipping in safe increments |
| 15 | Frontend Design | React desktop UI language and interaction design |
| 16 | Maintainability Guardrails | Architecture and change-quality gate |
