feat: add advanced software project generator initializer recipe (#4767) #4949

ARYPROGRAMMER · 2025-10-02T13:38:04Z

Summary

Advanced recipe for automated full-stack project initialization supporting multiple framework combinations (React/Vue/Svelte/Next.js + Node.js/Python/Go/Rust), database integrations (PostgreSQL/MongoDB/MySQL/SQLite), Docker, CI/CD, and production-ready configurations with comprehensive testing and documentation.

Key Features:

8 customizable parameters for complete project control
20+ framework/database combinations
Automated setup for ESLint, Prettier, Vitest, Jest, Docker Compose, GitHub Actions
Advanced Jinja2 templating with conditional logic
8-step orchestration workflow (structure → frontend → backend → quality tools → Docker → CI/CD → docs → verification)

Type of Change

Testing

used command:

 goose run --recipe documentation/src/pages/recipes/data/recipes/full-stack-project-initializer.yaml --params project_name=my-test-app --params project_type=fullstack --params frontend_framework=react --params backend_framework=nodejs --params database=postgresql --params include_docker=true --params include_cicd=true --params base_directory=./test-projects

Manual Testing:

Validated YAML structure and syntax
Tested recipe loading with goose CLI
Verified parameter validation and Jinja2 template rendering
Confirmed compatibility with goose recipe format specification

Related Issues

Fixes #4767

Screenshots/Demos (for UX changes)

Before: N/A - New recipe submission

After: N/A - New recipe submission

Email: notaryasingh@gmail.com

Signed-off-by: Arya Pratap Singh <notaryasingh@gmail.com>

github-actions · 2025-10-02T13:39:44Z

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

Our team will review your recipe
If approved, we'll run a security scan
Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

github-actions · 2025-10-02T13:41:29Z

🔍 Recipe Security Scan Results

✅ Status: APPROVED - All recipes passed security scan

📊 Scan Summary:

Total recipes scanned: 1

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (LOW risk)

🔗 View detailed scan results in the workflow artifacts.

iandouglas

Overall, looks great! I'd love to see a setting for "include_testing" where we generate some basic unit/integration testing for the frontend and backend, and including that in the CI/CD step as well.

iandouglas · 2025-10-03T17:23:25Z

documentation/src/pages/recipes/data/recipes/full-stack-project-initializer.yaml

+     {% endif %}
+
+  2. Frontend Setup
+     {% if frontend_framework != "none" %}


I'd move this line above "2. Frontend step", same with backend section

did this for both

iandouglas · 2025-10-03T17:23:56Z

documentation/src/pages/recipes/data/recipes/full-stack-project-initializer.yaml

+  2. Frontend Setup
+     {% if frontend_framework != "none" %}
+     {% if frontend_framework == "react" %}
+     Create React app with Vite and TypeScript in the frontend directory.


i'd love to see these sections indented for each of the if/else clauses, it won't hurt the YAML layout, and would be easier to read

tried my best to make it look good - vscode is bad

my idea here is to indent each section further:

{% if frontend_framework != "none" %} 2. Frontend Setup {% if frontend_framework == "react" %} Create React app with Vite and TypeScript in the frontend directory. ... Create example Welcome component and test. {% elif frontend_framework == "vue" %} Create Vue 3 app with TypeScript, Router, and Pinia. ...

iandouglas · 2025-10-03T17:36:46Z

since this recipe is explicitly called "full-stack", we could probably take out the if conditions for the frontend and backend, since a full stack project would have both anyway ... whether it has a dedicated database would be a different case so that could be an 'if' condition for example.

thoughts?

ARYPROGRAMMER · 2025-10-03T17:41:23Z

ut the if conditions for the frontend and backend, since a full stack project would have both anyway ... whether it has a dedicated database would be a different case so that could be an 'if' condition for example.

oh yes i thought about that, but maybe sometimes you need a frontend only or a backend only - you might use some other custom counterpart. So its like a subset then. "it can full stack" but maybe sometimes you need a particular thing or so. Hence keeping it optional would be best. Just to make it modular. Rest of the issues I will address and fix by morning, i might need to rebase

Signed-off-by: Arya Pratap Singh <notaryasingh@gmail.com>

ARYPROGRAMMER · 2025-10-03T17:59:12Z

most likely i think i addressed everything. let me know further.

thanks for timely guidance @iandouglas

github-actions · 2025-10-03T18:00:01Z

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

Our team will review your recipe
If approved, we'll run a security scan
Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

github-actions · 2025-10-03T18:03:00Z

🔍 Recipe Security Scan Results

✅ Status: APPROVED - All recipes passed security scan

📊 Scan Summary:

Total recipes scanned: 1

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (LOW risk)

🔗 View detailed scan results in the workflow artifacts.

iandouglas

left a few more comments and thoughts for your feedback

iandouglas · 2025-10-03T18:06:54Z

documentation/src/pages/recipes/data/recipes/full-stack-project-initializer.yaml

+    requirement: required
+    description: Name of the project to initialize (alphanumeric and dashes only)
+
+  - key: project_type


do we need this as a parameter if we're always trying to build a full-stack project with this recipe? or should we rename the recipe to something like "software project generator" that doesn't necessarily fall into a frontend/backend/fullstack role?

actually a good idea to rename maybe

iandouglas · 2025-10-03T18:10:48Z

documentation/src/pages/recipes/data/recipes/full-stack-project-initializer.yaml

+    requirement: optional
+    default: "."
+    description: Base directory where the project should be created
+


do we need any awareness of what kind of system we're developing on? eg, mac vs windows may have different tooling or needs (for example, Windows will handle disk paths differently, one common area I had was building paths like c:\src\react-project where the \r in the path gets interpreted as a carriage return character, breaking other workflows.

maybe this doesn't need to be a parameter, it could just be added in the instructions that say something like "detect what kind of operating system I'm on, and if you detect that I'm on Windows, be careful about disk paths where backslash path separators aren't interpreted as escape characters in strings"

iandouglas · 2025-10-03T18:12:10Z

documentation/src/pages/recipes/data/recipes/full-stack-project-initializer.yaml

+  2. Frontend Setup
+     {% if frontend_framework != "none" %}
+     {% if frontend_framework == "react" %}
+     Create React app with Vite and TypeScript in the frontend directory.


my idea here is to indent each section further:

{% if frontend_framework != "none" %} 2. Frontend Setup {% if frontend_framework == "react" %} Create React app with Vite and TypeScript in the frontend directory. ... Create example Welcome component and test. {% elif frontend_framework == "vue" %} Create Vue 3 app with TypeScript, Router, and Pinia. ...

Signed-off-by: Arya Pratap Singh <notaryasingh@gmail.com>

github-actions · 2025-10-03T18:25:56Z

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

Our team will review your recipe
If approved, we'll run a security scan
Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

ARYPROGRAMMER · 2025-10-03T18:26:40Z

added some more things, i think this should not be extended further as it might cross the token limits now. lgtm and actually works. i personally tested on fedora so didnt have any issues

iandouglas

just one last change here for the operating system so people don't get stuck on something that LLMs often get tripped up on for file/disk paths

iandouglas · 2025-10-03T18:34:06Z

documentation/src/pages/recipes/data/recipes/full-stack-project-initializer.yaml

+     Run initial tests to ensure everything works.
+     Display summary of created project structure and next steps.
+
+  Work through these steps systematically. Use shell commands to create files and directories.


I'd just add the note here for goose that adds the following:

Detect the operating system that I'm on, and use appropriate disk path separators, being careful to avoid 'escaping' of slash or backslash characters as appropriate for my operating system when interpreting or using string values for filenames.

github-actions · 2025-10-03T18:34:58Z

🔍 Recipe Security Scan Results

✅ Status: APPROVED - All recipes passed security scan

📊 Scan Summary:

Total recipes scanned: 1

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (LOW risk)

🔗 View detailed scan results in the workflow artifacts.

iandouglas · 2025-10-03T18:35:15Z

great work on the indentation, it's MUCH easier to read through the recipe now. Just one last thing to add to the end and we can get this merged in! Thanks for your contribution!!

Signed-off-by: Arya Pratap Singh <notaryasingh@gmail.com>

ARYPROGRAMMER · 2025-10-03T18:38:12Z

great work on the indentation, it's MUCH easier to read through the recipe now. Just one last thing to add to the end and we can get this merged in! Thanks for your contribution!!

thank you for the guidance, you are really a great maintainer.

you will surely find me in some other pr at goose. thanks

github-actions · 2025-10-03T18:38:58Z

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

Our team will review your recipe
If approved, we'll run a security scan
Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

github-actions · 2025-10-03T18:41:37Z

🔍 Recipe Security Scan Results

✅ Status: APPROVED - All recipes passed security scan

📊 Scan Summary:

Total recipes scanned: 1

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (LOW risk)

🔗 View detailed scan results in the workflow artifacts.

iandouglas · 2025-10-03T18:42:33Z

thanks for your contribution!! we'll get this merged in as soon as the other workflows finish.

ARYPROGRAMMER · 2025-10-03T20:43:50Z

i think the workflows have finished. thanks

taniandjerry · 2025-10-03T22:01:30Z

Amazing work! Thank you for the review @iandouglas, thank you for contributing @ARYPROGRAMMER ! <3

github-actions · 2025-10-03T22:02:17Z

✅ $10 OpenRouter API key sent to notaryasingh@gmail.com. Thanks for your contribution to the goose cookbook!

feat: add advanced full-stack project initializer recipe (block#4767)

a6bc750

Signed-off-by: Arya Pratap Singh <notaryasingh@gmail.com>

ARYPROGRAMMER requested a review from a team as a code owner October 2, 2025 13:38

iandouglas self-requested a review October 3, 2025 17:21

iandouglas self-assigned this Oct 3, 2025

iandouglas suggested changes Oct 3, 2025

View reviewed changes

added testing and indentation fix

9bbe156

Signed-off-by: Arya Pratap Singh <notaryasingh@gmail.com>

iandouglas reviewed Oct 3, 2025

View reviewed changes

ARYPROGRAMMER changed the title ~~feat: add advanced full-stack project initializer recipe (#4767)~~ feat: add advanced software project generator initializer recipe (#4767) Oct 3, 2025

more fixtures

dd83927

Signed-off-by: Arya Pratap Singh <notaryasingh@gmail.com>

iandouglas suggested changes Oct 3, 2025

View reviewed changes

fix: error loop handling at last

1f8b172

Signed-off-by: Arya Pratap Singh <notaryasingh@gmail.com>

iandouglas approved these changes Oct 3, 2025

View reviewed changes

iandouglas removed their assignment Oct 3, 2025

taniandjerry assigned ARYPROGRAMMER Oct 3, 2025

taniandjerry added the hacktoberfest Issues awarding points for Hacktoberfest 2025! label Oct 3, 2025

taniandjerry merged commit 1393783 into block:main Oct 3, 2025
14 checks passed

taniandjerry added the hacktoberfest-accepted label Oct 3, 2025

taniandjerry added the large Weight label for Hacktoberfest 2025 issues label Oct 3, 2025

This was referenced Oct 8, 2025

chore(release): release version 1.10.0 #5060

Closed

release/1.10.0 #5101

Closed

feat: add advanced software project generator initializer recipe (#4767) #4949

feat: add advanced software project generator initializer recipe (#4767) #4949

Uh oh!

Conversation

ARYPROGRAMMER commented Oct 2, 2025

Summary

Type of Change

Testing

Related Issues

Screenshots/Demos (for UX changes)

Uh oh!

github-actions bot commented Oct 2, 2025

Uh oh!

github-actions bot commented Oct 2, 2025

Uh oh!

iandouglas left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

iandouglas commented Oct 3, 2025

Uh oh!

ARYPROGRAMMER commented Oct 3, 2025

Uh oh!

ARYPROGRAMMER commented Oct 3, 2025

Uh oh!

github-actions bot commented Oct 3, 2025

Uh oh!

github-actions bot commented Oct 3, 2025

Uh oh!

iandouglas left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Oct 3, 2025

Uh oh!

ARYPROGRAMMER commented Oct 3, 2025

Uh oh!

iandouglas left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Oct 3, 2025

Uh oh!

iandouglas commented Oct 3, 2025

Uh oh!

ARYPROGRAMMER commented Oct 3, 2025

Uh oh!

github-actions bot commented Oct 3, 2025

Uh oh!

github-actions bot commented Oct 3, 2025

Uh oh!

iandouglas commented Oct 3, 2025

Uh oh!

ARYPROGRAMMER commented Oct 3, 2025

Uh oh!

Uh oh!

taniandjerry commented Oct 3, 2025

Uh oh!

github-actions bot commented Oct 3, 2025

Uh oh!

Reviewers

Assignees

Labels