I Built a Local VS Code Environment That Saves Me Hours on Every Project

As my projects became larger, I realized I was repeating the same maintenance tasks over and over again.

Creating folders.

Cleaning unnecessary spaces.

Reindenting files.

Converting CRLF to LF.

Keeping backups.

Generating a project tree for documentation.

None of these tasks are difficult, but together they constantly interrupt the development workflow.

Instead of installing more and more extensions, I decided to build a fully local VS Code environment based on Python scripts and explicit VS Code tasks.

The objective wasn't to automate everything.

The objective was to automate repetitive work while keeping every action predictable and under my control.

Saving Time Before Writing Code

One of the biggest improvements comes before development even begins.

Instead of manually creating every folder and file, I simply describe the project structure inside a structure.txt file.

Running one command generates the entire project hierarchy automatically.

my_project

    README.md

    app

        app.py

    static

        css

            style.css

The opposite workflow is just as useful.

When a project already exists, another script scans every folder and generates a complete PROJECT_TREE.txt file.

It has become one of my favorite tools for documenting projects, sharing their architecture and quickly understanding existing codebases.

I also use a dedicated reindentation shortcut that instantly reformats HTML, CSS, JavaScript and JSON files.

Operations that previously required several minutes now take only a few seconds.

Small Tools With One Responsibility

Instead of building one large script that tries to do everything, every tool has a single responsibility.

• Generate a project structure
• Generate a project directory tree
• Detect unnecessary spaces
• Clean whitespace
• Convert CRLF to LF
• Format Python with autopep8
• Create timestamped backups

Each script remains simple, readable and easy to maintain.

Explicit Instead of Automatic

One design choice was particularly important.

Nothing modifies my code without my decision.

Every operation is launched manually through a dedicated VS Code task.

I always know what will run, when it will run and which files will be affected.

That makes the entire environment much easier to trust.

Entirely Local

Everything works locally.

No cloud services.

No subscriptions.

No hidden background processes.

No mandatory VS Code extensions.

The scripts are plain Python files that anyone can read, modify and adapt to their own workflow.

If you'd like to see the tools in action, I've recorded a complete demonstration playlist covering every script, task and workflow:

YouTube playlist:
https://www.youtube.com/watch?v=NZgXd_sHEy4&list=PLR1GDrpaWT2k

You can also explore the complete presentation, documentation and feature overview on the project website:

Website:
https://palks-studio.com/en/vscode-environment-pack

If you're interested in the implementation details, the full source code is available on GitHub:

GitHub:
https://github.com/Palks-Studio/vs-code-environment-pack

Why I Built It

This project started with a simple whitespace cleaner.

Little by little, I kept adding the tools I wished I had every day.

Today it has become the environment I use for every new project.

It isn't meant to replace existing tools.

It simply removes repetitive work while allowing me to keep complete control over my code.

If you enjoy lightweight local workflows instead of depending on large toolchains, you might find this approach useful.

https://palks-studio.com