[Question]: Trying to figure out create_coding_feature pattern

[mainlyetcetera]

What is your question?

hey all. wanted to check what everyone's doing with the create_coding_feature pattern. i have the code_helper tool installed, and it's able to parse out the root directory of the project. then fabric outputs the JSON list of everything it wants to do. but i'm not sure what to expect at this point. it gives some suggestions, but i thought it would actually generate and edit files. is everyone just following the steps in the suggestions from the pattern, or is it actually supposed to be creating and editing files? thanks!

[ksylvan]

Indeed, its purpose is to edit and generate files.

The way it works is you feed the code_helper output with its instructions into the create_coding_feature pattern.

Of course, it's rudimentary and it doesn't always work (mostly because the LLMs sometimes create incomplete or bad file-change specifications that Fabric can not parse), but for small subtrees of code and using a powerful enough model, it works okay.

For example, I just created an empty directory, and in that directory, I ran this:

code_helper . 'Create a nextjs app scaffolding that connects to a fastapi python server, using both Python and NextJS best practices.' | create_coding_feature -m google/gemini-2.5-pro-preview --search
Applied create operation to README.md
Applied create operation to .gitignore
Applied create operation to backend/main.py
Applied create operation to backend/requirements.txt
Applied create operation to frontend/package.json
Applied create operation to frontend/next.config.mjs
Applied create operation to frontend/pages/index.js
Successfully applied file changes.
You can review the changes with 'git diff' if you're using git.

This response outlines the creation of a monorepo project structure containing a Next.js frontend and a FastAPI backend.

The backend is a simple Python server using FastAPI, providing a sample API endpoint. It includes a `requirements.txt` for dependency management.

The frontend is a Next.js application configured to proxy API requests to the FastAPI backend during development, which is a best practice to avoid CORS issues. The main page includes a React component that fetches data from the backend to demonstrate the connection.

A root-level `README.md` provides comprehensive instructions for setting up and running both services.

And here is what the directory structure looks like.

tree .
.
├── backend
│   ├── main.py
│   └── requirements.txt
├── frontend
│   ├── next.config.mjs
│   ├── package.json
│   └── pages
│       └── index.js
└── README.md

4 directories, 6 files

And I followed the instructions:

I hope that answers your question. Feel free to follow up with me.

[ksylvan]

@mainlyetcetera I don't know if you're still following this, but here is your answer.