g-sui Go UI Framework

VerifiedSafe

Server-rendered UI framework for Go with server-side HTML generation, state management, and interactivity via server actions and WebSocket. Perfect for building interactive web applications with centralized business logic.

Sby Skills Guide Bot
DevelopmentIntermediate
306/2/2026
Claude Code
#go#server-rendered-ui#web-framework#server-actions

Recommended for

Our review

Server-rendered Go UI framework with server actions and WebSocket.

Strengths

  • Simplified server-side HTML generation
  • Interactivity via server actions and WebSocket patches
  • Reusable Go components

Limitations

  • Requires Go and server-rendering knowledge
  • Smaller ecosystem compared to JS frameworks
  • Documentation scattered across multiple files
When to use it

Use g-sui when building Go web applications that need dynamic UI without heavy JavaScript.

When not to use it

Choose a traditional SPA if you require complex client-side interactivity.

Security analysis

Safe
Quality score80/100

The skill documents a Go UI framework with standard development commands (go run, go test, go build, a deploy script). No destructive, exfiltrating, or obfuscated actions are instructed.

No concerns found

Examples

Create a basic g-sui page
Create a g-sui page with a hello world component using the MakeApp and Page functions.
Implement a form with server action
Show me how to add a form in g-sui with a server action that handles submission.
Set up WebSocket real-time updates
How do I implement WebSocket patches in g-sui for real-time data updates?

name: g-sui description: Server-rendered Go UI framework. Use when building g-sui applications, creating UI components, handling forms with server actions, using data tables, setting up routes, or implementing WebSocket patches. Triggered by "g-sui", "server-rendered UI", "Go UI framework", form handling, or data collation. allowed-tools: Read, Grep, Glob, Bash, Edit, Write

g-sui Framework

Server-rendered UI framework for Go. All HTML generation, business logic, and state management occur on the server. Interactivity achieved through server actions and WebSocket patches.

Quick Start

package main

import "github.com/michalCapo/g-sui/ui"

func main() {
    app := ui.MakeApp("en")

    app.Page("/", func(ctx *ui.Context) string {
        return app.HTML("Home", "bg-gray-100",
            ui.Div("p-8")(
                ui.Div("text-2xl font-bold")("Hello World"),
            ),
        )
    })

    app.Listen(":8080")
}

Documentation Index

| Topic | File | Description | |-------|------|-------------| | Core Concepts | CORE.md | Architecture, Context, Actions, Targets, server rendering | | UI Components | COMPONENTS.md | Buttons, inputs, forms, tables, alerts, cards, tabs, etc. | | Data Management | DATA.md | Data collation, search, sort, filter, pagination, Excel export | | Server Setup | SERVER.md | App initialization, routes, WebSocket, PWA, assets | | Best Practices | PATTERNS.md | Testing, validation, security, state management |

Core Philosophy

  1. Server-Centric Rendering - All HTML generated server-side as strings
  2. String-Based Components - Components are Go functions returning HTML strings
  3. Action-Based Interactivity - User interactions trigger server handlers returning HTML
  4. WebSocket-Enhanced - Real-time updates via /__ws endpoint

Key Types

type Callable = func(*ui.Context) string  // All handlers return HTML
type Attr struct { ID, Class, Value, OnClick, OnSubmit, ... }  // HTML attributes

Common Imports

import "github.com/michalCapo/g-sui/ui"

Development Commands

go run examples/main.go      # Run example app
go test ./...                # Run all tests
go test ./ui/...             # Test UI package
go build                     # Build project
./deploy                     # Create and push new version tag

Releases

To create a new version release:

./deploy

The deploy script automatically:

  • Starts at version v0.100 if no tags exist
  • Increments the minor version by 1 (e.g., v0.100v0.101v0.102)
  • Ensures working tree is clean before tagging
  • Creates an annotated git tag and pushes to remote

Version numbering: v0.XXX format, auto-incremented from v0.100.

Related skills