Skills and Capabilities

Skills and capabilities

A skill is a step-by-step playbook the team quietly follows — for example, how a clickable mock-up gets approved, how content gets a rights check, or how the cheapest suitable AI model gets picked for a job.

GRU953-Studio has 32 of these playbooks. You never load or run any of them yourself. The team reaches for the right one automatically as your project moves along, and each project uses only the playbooks it actually needs. This page is here purely for anyone curious about how the reliability happens behind the scenes — you can build a whole app without ever reading it.

Skills are the "how"; the team is the "who". A specialist follows a skill the way a chef follows a recipe. If you want the bigger picture of what the tool does for you day to day, see Features.

Each group below lists its skills in a small table: the playbook's short name on the left, and what it does in plain English on the right.

The coordinator

The one playbook that runs the whole show.

Skill	What it does
studio	The master playbook — how the Project Lead runs the whole nine-stage journey from your idea to a finished app, sizes your project, and brings in the right specialists.

Staying on track over a long build

Six playbooks that stop a big project from wandering, overspending or cutting corners.

Skill	What it does
focus-guard	Keeps a tiny, always-current note of the one active goal, so a long project never quietly drifts off course — even across many separate sittings.
quality-gate	A checklist nothing can skip before a stage is backed up or published — tests, an independent review, security and licence checks, accessibility, and up-to-date documentation.
audit-loop	The plan for any "keep checking until it's clean" request — it maps out the full round of checks upfront, rather than adding one check at a time.
yagni-rules	The lean-building rule the whole team follows: build only what's genuinely needed, nothing "just in case". (YAGNI is short for "you aren't gonna need it".)
cost-guard	The cheapest-suitable-option-first spending default, and the plan for a long build that might span several days.
model-router	Automatically picks the right AI model and effort level for each individual step, spending more only where it genuinely matters. (An AI model is the underlying "brain" doing the thinking; some are quicker and cheaper, others slower and more capable.)

Remembering everything between sessions

Two playbooks that let you stop and pick up later without losing your place.

Skill	What it does
dev-memory	The plain-text notebook system that makes a project resumable — in the same sitting, or a brand-new one days later.
memory-graph	A compact index plus a small "map" of how everything connects, so recalling a big project costs far less and surfaces just what's relevant.

Planning, mock-ups and building in stages

Four playbooks that turn an idea into an orderly, checkable plan before real code is written.

Skill	What it does
warframe-prototype	The rule that a clickable mock-up must be shown to you and approved before any real code is written. (A mock-up is a tap-through preview that looks like the app but doesn't do the real work yet.)
phased-roadmap	Turns the approved design into "smallest useful version first, then improvements in order".
micro-task-planning	Breaks the plan into small, independently checkable steps, each with one clear way to prove it's finished.
tdd-workflow	On bigger projects, makes sure a test that must fail is written before the matching code exists — proof-first, not proof-after. (A test is a small automatic check that the code does what it should.)

The command centre

One playbook that puts you in charge of the work.

Skill	What it does
command-centre	Defines pause, resume, stop, skip and schedule-for-later, plus the one-page dashboard showing your app's concept, its design, the build plan, and a live task board of what's done, in progress and still to do.

Real content, real AI, always with your consent

Three playbooks for making the app's actual words and media, and for choosing which AI does it — never without asking you.

Skill	What it does
content-creation	The whole content stage: planning your app's real text and media, and the record that tracks each item's approval and rights.
gemini-integration	The opt-in playbook for generating images, audio and video with your own Google account — always with a cost estimate and your yes first. See Connecting Gemini.
ollama-integration	The playbook for using a free (no cost), local AI model on your own computer instead of the cloud — always your choice, always asking first. See Connecting Ollama.

Shipping safely

Two playbooks for getting a finished app out, privately and without losing work.

Skill	What it does
publish-github	How a finished project is published privately to your own GitHub account, with a separate, explicit step if you later choose to make it public.
checkpoint-commit	The private backup taken after each build stage, so nothing is lost even before you're ready to publish.

Fixing things quietly

One playbook that handles small hiccups without pestering you.

Skill	What it does
self-healing	Lets the Fixer quietly try a couple of small repairs on its own first, and only interrupt you if that doesn't work.

Getting started and finding existing tools

Two playbooks for your very first run and for spotting when a ready-made tool already fits.

Skill	What it does
first-run	The one-off "getting to know you" setup that runs before your very first project, and never again after.
ecosystem-finder	Suggests an existing Claude Code tool when one already solves a specific need — always asking before anything is installed.

A toolchain pack for every language

The last 10 skills are language packs. A toolchain is simply the set of tools used to build software in one programming language. Each pack holds the exact build, test, tidy-up and dependency commands for one language, so its matching specialist (see the team) can stay focused on the actual work. (A dependency is outside code your project relies on.)

Pack	Platform / use
lang-dart	Dart and Flutter — the cross-platform default
lang-kotlin	Android
lang-swift	iPhone, iPad and Mac
lang-java	General-purpose, cross-platform Java software
lang-csharp	Windows and cross-platform .NET
lang-python	Scripts, tools and services
lang-rust	Fast, memory-safe software
lang-go	Services, command-line tools and Linux
lang-cpp	Performance-critical desktop software
lang-typescript	Web apps and cross-platform tools

The full count

The numbers add up to 32 skills in total:

Group	Skills
The coordinator	1
Staying on track over a long build	6
Remembering everything between sessions	2
Planning, mock-ups and building in stages	4
The command centre	1
Real content, real AI, always with your consent	3
Shipping safely	2
Fixing things quietly	1
Getting started and finding existing tools	2
Language packs	10
Total	32

Where to go next

• Meet the specialists who follow these playbooks on the team.
• See what all of this adds up to for you in Features.
• Watch the skills at work in sample use cases.
• Turn on the two optional AI connections: Connecting Ollama and Connecting Gemini.
• New here? Start with Installation, and keep Troubleshooting and the FAQ close by.

Want to see the playbooks themselves? Each one lives in its own folder under plugins/gru953-studio/skills in the repository.