How to use ProFolderAI’s developer tools

Overview

All six tools live in one place: your dashboard, under the Tools section below the main generator. Each one opens the same kind of panel — a stack/framework field, a description field, and a Generate button — and returns real files you can copy directly into your project.

They all draw from the same monthly usage allowance as your plan, and three of them are available for free on Starter: Starter Templates, API Routes, and Project Configs. The other three — Code Scaffolder, Database Schemas, and Components — are included with Pro and Team.

Code Scaffolder

What it does: turns a plain-language project description into a small, runnable starter — an entry point, one real route or page, the dependency manifest, and a short README. Not empty folders — actual working code.

How to use it:

1. Open Code Scaffolder from the Tools section.
2. In Stack / framework, name your framework — e.g. Next.js or FastAPI.
3. In Describe what you need, add one key detail — e.g. Next.js app with user authentication.
4. Click Generate and copy each file into your project.

Example: stack Node.js, Express, description a small REST API for managing todo items returns a working server.js, one route file, package.json, and a README explaining how to run it.

Starter Templates

What it does: the same scaffolding engine as Code Scaffolder, pre-loaded with four ready-made stacks so you don’t have to describe anything yourself.

How to use it:

1. Open Starter Templates.
2. Tap a preset: Next.js + Stripe SaaS, Express + Postgres API, React + Vite SPA, or Python FastAPI service.
3. Optionally add a note in the description field to steer the result.
4. Click Generate.

Example: tapping Express + Postgres API with no description returns a working Express server wired to PostgreSQL with JWT auth and one sample route.

API Routes

What it does: generates one real endpoint file — with validation and error handling, not a TODO — matching your framework’s conventions.

How to use it:

1. Open API Routes.
2. Name the framework — e.g. Express, FastAPI, Next.js API routes.
3. Describe the endpoint, including the method — e.g. POST endpoint to create a user.
4. Click Generate.

Example: stack Express, description POST endpoint to create a user with email and password returns a route file with input validation and a matching test file.

Database Schemas

What it does: generates a real schema — and a migration file where the ORM supports one — using correct syntax for the ORM you name.

How to use it:

1. Open Database Schemas.
2. Name your ORM or database — e.g. Prisma, SQLAlchemy, Mongoose.
3. Describe your entities and key fields — e.g. User with email, password, and orders relation.
4. Click Generate.

Example: ORM Prisma, description User with email, password, and a one-to-many relation to Order returns a correct schema.prisma model with the relation defined.

Components

What it does: generates one UI component — plus its stylesheet and a basic test, where the framework conventionally separates them — in your framework’s idiomatic style.

How to use it:

1. Open Components.
2. Name the framework — e.g. React, Vue.
3. Describe the component and where it’s used — e.g. a pricing card for a SaaS landing page.
4. Click Generate.

Example: framework React, description a pricing card showing plan name, price, and a call-to-action button returns a working component, its styles, and a test file.

Project Configs

What it does: generates the specific configuration file you ask for — .env.example, docker-compose.yml, a CI/CD workflow, or a lint config — correct and ready to use for your stack.

How to use it:

1. Open Project Configs.
2. Name your stack — e.g. Node.js, Python.
3. Name the exact file you need — e.g. GitHub Actions CI for running tests.
4. Click Generate.

Example: stack Node.js, description GitHub Actions workflow that installs dependencies and runs tests on push returns a working .github/workflows/ci.yml.

Frequently asked questions