Skip to content

astroville/sprout / .claude/skills/greenfield-scaffolding

greenfield-scaffolding

Verified

Bootstrap 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 init on a new project
  • When /scan detects a stack but no conventions exist yet
  • When the user says "set up hero for this project" or "onboard this codebase"

Steps

  1. Run hero scan to detect the tech stack (languages, frameworks, build tools)

  2. 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
  3. Run hero index to make everything searchable

  4. Run hero install project . --target <detected-tool> to wire up MCP

Stack-specific templates

StackConventions generated
Goerror wrapping, table-driven tests, package naming
TypeScript/NodeESM imports, async/await patterns, type strictness
Pythonvirtual env, type hints, pytest conventions
Java/Kotlinpackage structure, dependency injection, Gradle/Maven
Rusterror handling (thiserror/anyhow), module structure
Reactcomponent 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
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall