Introduction

Blueprintor is a VS Code extension that creates files and folders from templates (“blueprints”). It fits when you regularly create the same thing: a React component with a test and styles, a Python module, a Go package, task notes.

How it works

You describe a blueprint in a config: a title, the values to ask for (variables), the file structure and the texts of the files.
In the Explorer you run Run Blueprintor… on the target folder.
You pick a blueprint from the list and enter the values it asks for.
The extension creates the structure, substituting your input into file names, folder names and content.

Features

Nested folders of any depth.
Any number of prompted values per blueprint (variables), each with its own question.
Placeholders in five forms: {name.raw}, {name.pascal}, {name.camel}, {name.kebab}, {name.snake}.
Reusable texts (snippets) or inline content for every file.
Blueprints without questions: just omit variables.
Two configuration sources: global (VS Code settings) and local (blueprintor.config.js). On a title clash, the local one wins.
Everything is validated before writing, so a mistake in a config never leaves a half-created result.
A check for existing files: overwrite, skip existing, or cancel.

Minimal example

module.exports = {
    blueprints: [
        {
            title: "Idea",
            variables: [{ key: "name", prompt: "Idea name" }],
            snippets: {
                idea: `
# {name.pascal}

Notes go here.
`,
            },
            structure: {
                files: [{ name: "{name.kebab}.md", snippet: "idea" }],
            },
        },
    ],
};

Entering my idea creates my-idea.md with the heading # MyIdea.