From Idea to App Store:
12 Claude Skills

From Idea to App Store:
12 Claude Skills

From Idea to App Store:
12 Claude Skills

A team of 12 Claude skills that hand off to each other, from a rough idea to a launched app. One of them is a project manager: you talk to it, and it knows which skill comes next.

Project manager · Idea · Requirements · UX · UI · Design system · Build · UX review · Launch · App store

Developed by Jad · AI Tooltip

How it works

You talk to the project manager. It runs the team.

You talk to the project manager. It runs the team.

Building an app gets confusing fast: UX, UI, a design system, the build, hosting, a database, and then handing it all over. This set splits that into 12 skills, one job each. You don’t brief every designer and developer yourself. You talk to the project manager, and it tells you which skill to run next. The skills do the legwork. You make every decision.

Inside the set

12 Skills, One Job Each

12 Skills, One Job Each

Every skill saves a file and the next one reads it. Use the whole set, or only the ones your project needs.

The skills

Skill

What it does

/project-manager

Picks your path, tracks every step and tells you what’s next. Never does the work itself.

/idea-brainstorm

Thinks your raw idea through and is honest about what’s weak.

/requirements-interview

Interviews you and finds the right problem to solve.

/ux-discovery

Three solution concepts, then the flows and every screen.

/journey-map

The whole app in one diagram: journey, flows, site map. Finds the gaps.

/ui-rule-of-three

Finds the look: 3 directions, 3 variations, then every screen.

/design-system

Locks your approved look into colors, type, spacing and components.

/build

Builds the app screen by screen and checks it against the design.

/ux-review

Uses the app like a real user and ranks what to fix.

/launch

Puts it online with only what it needs: code, hosting, database, sign-in.

/native-app

Apps only: turns the live web app into an iPhone and Android app.

/handoff-package

One folder with everything, for a developer, a client or your team.

Each one works on its own too. If the file it needs is missing, it offers to run the step before it.

Setup

Install the Skills in Your Project

Install the Skills in Your Project

I don’t install skills in my Claude account. I install them per project, so another project never pulls in skills it doesn’t need. For your next project, copy the folder over and do the same.

Download it and add it to your project

Download it and add it to your project

Unzip it and put the ai-tooltip-skill-set folder inside the folder where you’ll build your app.

Unzip it and put the ai-tooltip-skill-set folder inside the folder where you’ll build your app.

Ask Claude to install them

Ask Claude to install them

Open that folder in Claude Code and send this. Then start a new session so the skills load.

Open that folder in Claude Code and send this. Then start a new session so the skills load.

Install the skills from the ai-tooltip-skill-set folder into this project.

Or clone github.com/AiTooltip/ai-tooltip-skill-set. Prefer to install it yourself? In the project folder, run: mkdir -p .claude/skills && cp -R ai-tooltip-skill-set/* .claude/skills/

Start

Start With the Project Manager

Start With the Project Manager

Start every project with the project manager, not a plain sentence. Type the command and describe your idea. A rough idea is fine.

In Claude Code

/project-manager

For example

/project-manager I want to build an AI assistant app that helps me remember things and stay on top of my responsibilities and social life.

/project-manager I want to build an AI assistant app that helps me remember things and stay on top of my responsibilities and social life.

It starts with a reality check on your idea, then suggests a path. Pick one and it writes the plan: every step with its skill and its output file, plus a project-status.html you can open in your browser any time.

Pick a path

Path

Good for

Full path

All 12 steps. A new product where the idea is still open. Ends with a launched app.

Short path

Skips the brainstorm, the journey map and the UX review. A small site or a first version.

Design only

Requirements to finished screens, for when someone else builds it.

One skill

/ux-review and /design-system work on any product.

The project manager recommends one. You pick.

1

Step 1 · The right idea

Brainstorm

Brainstorm

Run /idea-brainstorm and answer the questions. It looks at the job behind your idea and what people use today, gives you three framings, checks what already exists, and tests your assumptions.

Your call

Answer the questions and pick a framing.

It’s an honest partner: it tells you what’s weak, then helps you fix it.

Output

idea-brief.md

2

Step 2 · The right problem

Requirements

Requirements

Run /requirements-interview. Claude interviews you in short rounds, every question with options and a recommended answer, until there’s one clear problem statement. It skips anything your idea brief already settled.

Your call

Answer the questions and confirm the problem.

The recommended answer is a suggestion, not a decision. If you accept everything without reading, the AI is deciding again.

Output

requirements.md

3

Step 3 · The right solution

UX Discovery + Journey Map

UX Discovery + Journey Map

This is where the app takes shape. Not visually yet, but as an experience. /ux-discovery gives you 3 concepts with pros and cons. Then /journey-map lays out the whole app in one diagram: the journey with an emotional curve, every flow and the site map. It’s the blueprint of your app, so take your time with it.

Your call

Pick 1 of 3 concepts, then choose which gaps to fix.

Claude runs your main user through every scenario and lists the gaps it finds in the flow. You decide which ones to fix.

Output

ux-brief.md

design-brief.md

journey-map.html

4

Step 4 · The rule of three

UI Direction

UI Direction

Start a new session and run /ui-rule-of-three. It shows you 3 directions at a time. If none of them work, say why. That feedback is how it gets closer to your vision and your taste.

Your call

Pick 1 of 3 until you have a look you like.

Keep exploring. Tell it what you don’t like and why, and narrow it down to one main screen.

Output

Claude Design canvas

ui-progress.md

5

Step 5 · Lock the look

Design System

Design System

/design-system turns your approved screen into a full design system: colors, type, spacing and components with all their states. Go through it and adjust anything, or approve it as is, since it’s built from your own UI.

Your call

Approve the design system.

Every screen after this, and the build, follows it.

Output

design-system.md

design-tokens.css

6

Step 6 · Every screen

UI Screens

UI Screens

Back to /ui-rule-of-three. Same rule of three: for every design decision you get 3 options, until every screen is done. Then test it as a prototype and give your feedback.

Your call

Pick the best option for each screen.

Before the build, check in with the project manager. It tells you if any features are still missing.

Output

designs/final/

ui-progress.md

7

Step 7 · Make it real

Build

Build

Start a new session and run /build. It builds in phases, and you test each phase before it moves on. At every phase it compares the build with your design, and it gives you a QR code to test the app on your phone.

Your call

Test each phase and say what to change.

This is where you shape how it feels. Try it, and tell it how you want each interaction to behave.

Output

site/

build-progress.md

8

Step 8 · Use it like a user

UX Review

UX Review

Run /ux-review. It uses your app like a real person and finds what’s confusing, unclear or buggy, ranked from major to minor. Add your own test notes too.

Your call

Pick which fixes to make.

It only applies the fixes you pick, then checks them again.

Output

ux-review.md

9

Step 9 · Go live

Launch

Launch

Start a new session and run /launch. It asks how you want it set up (the AI model, sign-in and the database) and plans it on free accounts before you scale up. It creates a private GitHub repo for your app and walks you through hosting and the database.

Your call

Choose the services and approve each step.

You only sign up and approve. Claude does the rest.

Output

launch-plan.md

10

Step 10 · Optional

Native App

Native App

/native-app turns your launched web app into an iPhone and Android app, with the same code and the same design, and takes it through TestFlight, the App Store and Google Play. Apps only, not websites.

Your call

Decide if it belongs on phones, which native touches it gets, and when it goes to the stores.

You create the Apple and Google developer accounts yourself. Nothing goes to a store until you say so.

Output

ios/ + android/

native-progress.md

11

Step 11 · Any time

Handoff Package

/handoff-package puts the whole project in one folder: every document, the approved screens, the design system and one overview page that explains it all. For a developer, a client or your team.

Your call

Decide who it’s for and what goes in.

It works at any point in the project, not only at the end. It copies your files, never moves them, and leaves out passwords and keys.

Output

handoff/

Tips

Stay on Track

Stay on Track

You can stop any time. Start a new session, run /project-manager, and it picks up where you left off.

Check in with the project manager

Do this

When

A new session

For each big step. Rename your chats so you can find them.

/project-manager

Any time: where you are and what’s next

what’s up

Mid-step: the project manager updates the plan

project-status.html

Open it in your browser to see your progress

Every step saves a file in your project folder, so the project manager always knows where you are.

Need design help?

Need design help?

These skills get you high quality UX & UI. But if you want to take it to the next level with custom professional work, submit your project and Jad will review your product and help you upgrade it.

Submit your design

Worried the code is safe to launch?

Worried the code is safe to launch?

AI generated code can look fine and still hide security holes or performance problems. Taz is a software engineer who will review your code for any problems, so you know it is production ready before you launch.

Submit your code

Weekly Newsletter

Get one useful AI workflow every week.

A short, curated email with tools worth trying, prompts that worked, and practical ways to build faster without the noise.

No spam, just the useful info.

Weekly Newsletter

Get one useful AI workflow every week.

A short, curated email with tools worth trying, prompts that worked, and practical ways to build faster without the noise.

No spam, just the useful info.

Weekly Newsletter

Get one useful AI workflow every week.

A short, curated email with tools worth trying, prompts that worked, and practical ways to build faster without the noise.

No spam, just the useful info.

Guides and prompts that improve AI-generated apps.

Human assistance for UI/UX & code.

Youtube tutorials that are easy to follow.

Weekly newsletter with the latest workflows.

© 2026 AI Tooltip

Guides and prompts that improve AI-generated apps.

Human assistance for UI/UX & code.

Youtube tutorials that are easy to follow.

Weekly newsletter with the latest workflows.

© 2026 AI Tooltip

Guides and prompts that improve AI-generated apps.

Human assistance for UI/UX & code.

Youtube tutorials that are easy to follow.

Weekly newsletter with the latest workflows.

© 2026 AI Tooltip