AI-native scaffolding: grit describe "<feature>" → propose models, handlers, UI
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 10/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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:
- Reads the existing schema + permission catalogue + AGENTS.md conventions
- Calls Claude with a structured prompt + the relevant codebase slice
- Proposes a plan: new models, new endpoints, new permissions, new UI sections, new tests
- User reviews + accepts → `grit generate` is invoked with the parsed plan
- 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"
- Dominant language
- Go
- Stars
- 152
- Forks
- 20
- Avg merge
- 1d 49m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MUKE-coder/grit
-
[Plugin] calendarOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MUKE-coder/grit#228 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
MUKE-coder/grit#227 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 18/100
MUKE-coder/grit#224 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
MUKE-coder/grit#199 · 4 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
MUKE-coder/grit#179 · 4 comments ·
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Chemaclass/agnostic-ai#3681 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
OSS TEST
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
seaweedfs/seaweed-block#268 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day