AI-native scaffolding: grit describe "<feature>" → propose models, handlers, UI

Aperta
#53 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
10/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
go
Ambito
ai, cli, tooling

Direzione di ricerca

Start by reading the existing grit CLI entry point and the grit generate implementation to see how generators, schema, permissions and AGENTS.md conventions are wired. The issue describes a new grit describe command that calls Claude and produces a plan, but it names no files or tests, so first map the command dispatch, generator and permission catalogue. Done means a reviewed implementation plan for the command, not generated code.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement help wanted

Vision

This is the killer feature. The next generation of frameworks (v0, Convex, base44) blur the line between "describe" and "build". Grit has a unique advantage: the codebase has strong conventions (TwoPane, drawer forms, RBAC, generators) that an AI can reliably extend.

Proposal

```
grit describe "tenants need a vacation hold feature — they pause their booking
for N days without paying, can extend by 7 days max, requires manager approval"
```

The CLI:

  1. Reads the existing schema + permission catalogue + AGENTS.md conventions
  2. Calls Claude with a structured prompt + the relevant codebase slice
  3. Proposes a plan: new models, new endpoints, new permissions, new UI sections, new tests
  4. User reviews + accepts → `grit generate` is invoked with the parsed plan
  5. Output is committed to a `grit/` branch with a generated PR description

Critically: the framework's strict conventions (issues #18-#36) make AI output high-quality. Most AI scaffolders produce bespoke code; Grit's would produce code indistinguishable from hand-written framework code because the framework constrains it.

Why this is differentiating

Encore and Convex talk about AI-native infra. Nobody has nailed it for self-hosted Go. "Describe a feature in English, get a working PR" is the kind of demo that goes viral.

Acceptance

  • The vacation-hold example produces compiling, type-checked code with appropriate permission gates
  • Generated code passes the framework's lint rules (issue #5 / #18)
  • A senior engineer reviewing the PR sees "this looks like our team wrote it"
Lingua principale
Go
Stelle
152
Fork
20
Merge medio
1g 49m
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di MUKE-coder/grit

Tutte le issue di MUKE-coder/grit

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.