Generated File Map

One command, the whole stack

From a single field spec, Grit fans out a working, end-to-end feature. Here are the four files at the heart of it — switch tabs to see the same resource across Go and TypeScript:

type Product struct {
    ID         string         `gorm:"primaryKey;size:36" json:"id"`
    Name       string         `gorm:"size:255;not null" json:"name" binding:"required"`
    Price      float64        `gorm:"not null" json:"price"`
    CategoryID string         `gorm:"size:36;not null;index" json:"category_id"`
    Category   Category       `gorm:"foreignKey:CategoryID" json:"category,omitempty"`
    CreatedAt  time.Time      `json:"created_at"`
    UpdatedAt  time.Time      `json:"updated_at"`
    DeletedAt  gorm.DeletedAt `gorm:"index" json:"-"`
}

func (p *Product) BeforeCreate(tx *gorm.DB) error {
    if p.ID == "" {
        p.ID = uuid.New().String()
    }
    return nil
}

Excerpts, abbreviated for clarity — the real files are complete and runnable.

Backend + shared (always)

These are written for every architecture that has an API and a shared package.

Web app (if present)

Admin panel (if present)

Mobile — Expo (if present)

Desktop — Wails (if present)

Files it edits (marker injection)

Rather than overwrite shared files, Grit injects at // grit:* markers. Keep the markers in place — they're how generation and seeding stay idempotent.

Routes are the exception, and used to be the worst case: four edits per resource, hundreds of lines apart, in a routes.go that passed a thousand lines with a handful of resources. Each resource now gets its own internal/routes/<resource>_routes.go holding the handler and every path that reaches it, and routes.go no longer changes when you add or remove one.