Features

Features and how it works

This page is the plain-English overview of what GRU953-Studio does and how a project moves along, from your first idea to a finished app. If you've just arrived, you might read the Installation guide first; if you're already set up, this is the map of the whole journey.

GRU953-Studio is a helper you talk to in everyday words, inside Anthropic's coding assistant, Claude Code. You describe an app in your own language, answer a few simple multiple-choice questions, and a team of behind-the-scenes specialists designs it, shows you a clickable mock-up, writes it, fills it with real content, tests it, and — only when you say the word — publishes it to your own GitHub account. You never write or read a single line of code.

---

Features at a glance

Here's what you get, in plain terms.

• See it before it's built. You get a clickable mock-up of your app (we call it a "warframe" — a rough, tappable preview of the screens), plus a plain-English plan of what gets built first and what comes later. You approve both before a single line of real code is written, so there are no surprises.

• Real content, in your own language. The words in your app — buttons, welcome messages, notices — are written properly, in Bangla and English, not left as placeholder filler. If you'd also like generated pictures, sound, or video, the studio can make those too, using your own Google account, always telling you the cost and asking first.

• Every platform, one team. Whether your app is for Android, iPhone, iPad, Mac, Windows, or Linux, there's a dedicated specialist for each of 10 programming languages (a programming language is simply the kind of instructions a computer understands). The right expert builds the right platform, so nothing is a rough approximation.

• You stay in control. You can pause, resume, stop, skip, or schedule any piece of work for later, all in plain words. A single visual dashboard shows your app's idea, its design, the full build plan, and a live board of every task's status, in one place.

• It never loses your place. Everything is saved as plain-text notes on your own computer. Close your laptop, come back next week — or carry on from a web browser — and it picks up exactly where it stopped.

• The cheaper option first, always. An automatic chooser picks a sensible level of effort for each individual step, spending more only where it genuinely matters, and it pauses to ask before anything unusually costly. (An "AI model" is just the particular engine doing the thinking; some are quicker and cheaper, some are more powerful.)

• It grows in safe stages. You get the smallest useful version first, then improvements added in order — with a private backup of your work saved after every stage, so nothing is ever lost along the way.

• Safety is built in, not bolted on. Before anything is published, automatic checks look for leaked passwords, known weaknesses, and licence problems (a licence is the rule for who is allowed to use something and how). Publishing is private by default, and making an app public is always a separate, deliberate step.

---

How it works, step by step

Every project follows the same friendly loop, in eight plain steps.

1. Tell it your idea. Type it between square brackets, like [ a simple habit tracker for my phone ], or just type /studio.

2. Answer a short interview. It asks only as many pop-up questions as it genuinely needs — never a wall of them. Each one is a simple multiple choice, with a recommended answer already marked.

3. It sizes the job. It tells you plainly whether your project is Tiny, Standard, or Complex, and what that means for how much checking and care it will apply. (There's more on this just below.)

4. You see it before it's built. You get a clickable mock-up of the screens, plus a plain-English plan of what ships first and what comes later. Nothing is really built until you approve both.

5. It writes the real content. Buttons, messages, and welcome text are written in Bangla and English. If you'd like generated pictures, sound, or video too, it asks first and shows you the cost each time.

6. It builds, checks, and tests — in stages. The smallest useful version first, then improvements in order, with a private backup after each stage. If anything gets stuck, it tells you plainly what's wrong and what your choices are; it never leaves something quietly broken.

7. It publishes — only when you say so. Your app goes to your own GitHub account (GitHub is a widely used online home for software; it's free to use, no cost, for a personal account), kept private by default. Making it public is a separate step you choose later, if ever.

8. It remembers everything. Your whole project is saved as plain-text notes in your own folder. Pause any time, come back whenever you like, and it carries on from exactly where you left off.

---

How big is your project?

Before it starts, the studio needs to know roughly how much care your project calls for — a one-page list of your favourite films is a lighter job than a shop that takes card payments. So it asks three simple yes/no questions.

1. Does it store your data beyond this session? (A session is simply one sitting with the tool. This question means: does the app remember things after you close it — a saved list, entries you've typed in?)
2. Does it handle money, logins, or personal details?
3. Does it connect to two or more other apps or websites? (For example, a payment service and a Google sign-in.)

Your answers place the project into one of three sizes.

Size	When it applies	What it means for you
Tiny	You answered no to all three	A single page, a small script, or a one-off tool — light checks and a quick plan.
Standard	Yes to storing data only (no money, personal details, or multiple connections)	A typical app with saved data or logins — a proper design pass and independent testing before it ships.
Complex	Yes to money or personal details, or to connecting two or more other services	The full team, with extra security checks, a privacy review, and tests for what happens when things go wrong — not just when they go right.

The studio always shows you the size it has chosen and why, in plain English. You can ask it to raise or lower the size at any time — it's your call, not a fixed verdict.

---

The command centre

You steer a project with a handful of short typed instructions called slash commands. A slash command is simply an instruction you type starting with a forward slash (/). You never need to memorise them — the studio guides you — but here is the full set and what each one does.

Command	What it does
/studio	Starts a new project from your idea, or picks up the existing one where it left off.
/studio-status	Gives a plain-English progress report: what's done, what's happening now, and what's next.
/studio-pause	Pauses the current piece of work so you can safely stop and come back to that exact spot later.
/studio-resume	Carries on from where a paused or scheduled task left off.
/studio-stop	Ends the work session cleanly and sets everything down safely — nothing is lost, and the current task is kept for next time.
/studio-skip	Sets the current task aside for now and moves to the next one. The skipped task is kept, not deleted, and comes back later.
/studio-schedule	Arranges for a task to resume later, at a time you choose (for example, "tomorrow 9am").
/studio-dashboard	Opens a single visual page showing your whole project at a glance — its idea, its design, the full plan, and every task's status. It stays private and is never published.
/studio-publish	Publishes your finished app privately to your own GitHub account, after its safety checks pass and you confirm once. It can never make anything public on its own.

Pause or stop — what's the difference? Pausing sets down one task so you can pick up that same spot with /studio-resume. Stopping ends the whole work session tidily; you start again any time with /studio or /studio-resume. Either way, everything is saved and nothing is lost.

---

Where to go next

• Curious who's actually doing all this work behind the scenes? Meet the team — 38 specialists, coordinated for you, that you never have to manage by hand.
• Want to know the playbooks the team quietly follows to keep things reliable? See skills and capabilities.
• Ready to try it? The installation guide walks you through set-up, and sample use cases shows the kinds of things people build.

For the technical detail behind everything above, the project's main page is the README, and the full project lives at the GRU953-Studio repository.