astroville/sprout / .claude/skills/greenfield-scaffolding
greenfield-scaffolding
VerifiedBootstrap a new project's Hero workspace with stack-appropriate conventions, decisions, and initial specs.
What I do
After hero init on a new project, generate starter knowledge entries
tailored to the detected tech stack. This gives a fresh workspace immediate
value instead of being an empty folder.
When to use me
- After
hero initon a new project - When
/scandetects a stack but no conventions exist yet - When the user says "set up hero for this project" or "onboard this codebase"
Steps
-
Run
hero scanto detect the tech stack (languages, frameworks, build tools) -
Based on the detected stack, generate:
Conventions (write to
.hero/knowledge/conventions/):- Error handling patterns for the detected language
- Testing conventions (test location, naming, runner)
- API design patterns (if web framework detected)
- Git workflow (branch naming, commit message format)
Decisions (write to
.hero/knowledge/decisions/):- Why this tech stack was chosen (ask the user or note "pre-existing")
- Package manager choice
- Build tool rationale
Initial specs (write to
.hero/planning/features/):- A "project health" spec covering CI, linting, test coverage targets
- A "documentation" spec if README is thin
-
Run
hero indexto make everything searchable -
Run
hero install project . --target <detected-tool>to wire up MCP
Stack-specific templates
| Stack | Conventions generated |
|---|---|
| Go | error wrapping, table-driven tests, package naming |
| TypeScript/Node | ESM imports, async/await patterns, type strictness |
| Python | virtual env, type hints, pytest conventions |
| Java/Kotlin | package structure, dependency injection, Gradle/Maven |
| Rust | error handling (thiserror/anyhow), module structure |
| React | component patterns, state management, testing-library |
What not to do
- Don't generate conventions that contradict existing code patterns
- Don't assume a framework — detect it first
- Don't overwrite existing conventions or decisions
- Keep generated content concise — starter quality, not comprehensive
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |