Best Practices for Creating Skeleton Projects with Spec Kit

[iorgadas-cloud]

Hi, we are looking to create several similar projects that involve fetching data from source X, processing it, and persisting it to a database. We would like to understand the best approach to use Spec Kit for creating a skeleton project that serves as a base for these projects, with its own specifications (primarily focused on the data source type).

Additionally, is it possible to include a Git repository as part of the specification step? We believe this could provide Spec Kit with a reference or hint on how to implement the project.

[abvstudio-net]

I'm also interested in providing an existing repository as an "inspiration" as a part of my spec. It would allow us to go from [example code] -> [spec] -> [our code]

[educostadev]

How about building a customized MCP server that expose few-shots tools ? and also guidance on how to implement the code.
You could create Markdown documentation with your project’s patterns and definitions, reference it in your constitution file, and then expose the MCP tools with few-shot examples.