Menu
Architecture guardrails for Go + Wails + React + TypeScript: folder structure, dependency direction, and ownership boundaries.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Guardrails for connection profile lifecycle, secure persistence, and provider-aware connection orchestration in Go + Wails.
Cancellable async SQL execution patterns across backend services, Wails facade, and frontend state updates.
Query tab lifecycle and state-isolation rules for React/TypeScript editor workflows.
Rules for result rendering, type fidelity, paging, and edit workflows in React-based grids.
Shell composition and app-state ownership rules for Wails + React desktop UX.
Guardrails for CSV export and query-history retention with stable schema and low coupling.
| name | zentro-project-architecture |
| description | Architecture guardrails for Go + Wails + React + TypeScript: folder structure, dependency direction, and ownership boundaries. |
Define clear module boundaries so features are easy to change and safe to extend.
cmd/zentro/main.go
internal/models
internal/adapters
internal/services
internal/app (wails-exposed facade)
frontend/src/{features,components,stores,lib}
main.go: composition root and dependency wiring only.models: shared DTO/value types, no Wails/UI imports.adapters: DB/provider/OS integration.services: business workflows using models + adapters.internal/app: thin facade for Wails bindings.frontend: render and interaction; business rules in features/stores, not pure view components.models <- adapters <- services <- app(facade)
frontend -> generated bindings -> app(facade)