AI-powered web development platform

I've been thinking a lot about different mechanics in this direction, and so far using a TypeScript server seems like the most promising approach. Why? Because then we can operate not just with the files themselves and read them individually, but also analyze their dependencies. For example, we tell the agent to examine some component. It can simply use a special tool to get the entities that are there (variables, functions, imports, exports, etc.), as well as easily request the additional dependencies it needs without worrying about where they are located. But if it needs the final code of the required dependency, it can easily find out which file it is in and read it.&#x20;

Along the way, we probably need tools for reading files with a specified line range. After all, a code file can be large, and if TS immediately gives us information not only on where it is located, but also in which line range, we don't necessarily have to read the entire file.

Add code analysis features

It is necessary to provide a minimal project lifecycle:

* Creation from scratch or cloning of repository/repositories
* Launching separate environments (dev/stage/prod)
* Maintaining a single project knowledge base

Add minimal project management functionality

We need the ability to generate both overall layouts and individual elements and components. We also need infographics with text, because text is traditionally problematic for image generation. However, it seems the latest Qwen was boasting about this capability.

Research which models generate layouts and infographics better

Add functionality to run MODX websites

# Problem

Local project modifications are not enough for real-world operations. As a website matures, it develops a working environment, staging/preview, production, and the need to understand where a specific state is located at any given time.

The existing minimal project management task already assumes dev/stage/prod, but this part has not yet been elaborated as a standalone infrastructure problem.

## What to Investigate

We need to understand which environments are actually needed for different classes of projects, how code, data, configuration, and external services are connected between them, and what the safe path for changes to production should be.

We should not assume that three identical environments are mandatory for every website. A small informational site and a production service handling user data may require different levels of strictness.

Related to the [agentic change cycle](/tasks/cmuhtjmas02ocqw0r13pf4kpv), [deploy/rollback](/tasks/cmuhtjmav02oeqw0rtdqqrwaa), and the existing [project management](/tasks/cmqpcbssv001op50usjjkcaqu) task.

Understand the minimal infrastructure model for multiple project environments and the safe promotion of changes between them.

Tasks

Develop environment management for dev, stage, and prod

Add functionality to run MODX websites

Research which models generate layouts and infographics better

Add minimal project management functionality

Add code analysis features