grit new: mark a recommended choice for first-time users
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- go
- Domain
- cli, documentation
Research direction
Start in internal/prompt/ and find where the architecture, frontend, style and theme questions are defined, noting how each option's label and default are rendered. Check that pressing Enter returns the default for every prompt, then add the "(recommended)" label to the defaults matching --triple --next and print the newcomer line before the first prompt. Finally mirror that line in the Quick Start on /docs/start; done when accepting every default reproduces the documented recommended command.
Written by the indexing model from the issue text.
Description
The interactive grit new asks for an architecture (five modes), a frontend (two), a style and a theme. Nothing in internal/prompt/ marks a recommended option, so a beginner stops at the first question. /docs/start already recommends --triple --next; the CLI should agree.
Proposal
- Label the defaults "(recommended)" and print one line above the first prompt: "New to Grit? Press Enter to accept every default."
- Make Enter accept the default on every prompt, if it doesn't already.
- Mirror the same line in the Quick Start.
Done when pressing Enter through the prompt produces the same project as the documented recommended command.
Filed from a docs and developer-experience review of gritframework.dev and this repository (November 2026).
Generated by Claude Code
- 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
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 72/100
MUKE-coder/grit#243 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
MUKE-coder/grit#242 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
MUKE-coder/grit#237 ·
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MUKE-coder/grit#236 ·
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
MUKE-coder/grit#235 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tencentyun/cos-go-sdk-v5#364 ·
-
area: agents-mcp priority: normal
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
timwhitez/agent-sdk-golang#318 ·
Maintainers usually reply within 1 day