PTENES
TRACK 2

🚀 Build

Hands-on: from scratch to a live website, then apps, anything—and make it look professional.

4
Modules
24
Topics
~4h
Duration
Beginner→Intermediate
Level
0% 0 of 24
1 · Website 2 · Apps 3 · Anything Professional product

Learning path map

Detailed content

2.1~75 min

🚀 Website from Scratch to Deploy

Research references, write a brief, build in parallel, and publish on the web.

What it is:

Study sites that already work before inventing something from scratch.

Why learn:

Proven patterns prevent mistakes and speed up results.

Key concepts:

Reference · validated pattern · adapt, don't copy.

What it is:

Use the agent to analyze competitors and find gaps.

Why learn:

You find out where you can stand out before building.

Key concepts:

Competitor · gap · differentiator.

What it is:

A document that describes the site's purpose, audience, and style.

Why learn:

A clear brief = the right result on the first try.

Key concepts:

Goal · audience · visual tone.

What it is:

Generate several website proposals at once and compare them.

Why learn:

More options in less time, and you choose the best one.

Key concepts:

Parallel · variation · choose.

What it is:

Fix UI details one by one and prepare the SEO.

Why learn:

The details separate the amateur from the professional.

Key concepts:

Small adjustment · metadata · get discovered.

What it is:

Publish the site at a public URL, for free, in minutes.

Why learn:

A project only truly exists when it's live.

Key concepts:

Deploy · public URL · domain.

View Complete
2.2~60 min

🧩 Building Apps

The difference between a website and an app, databases, login, layers, and how to publish.

What it is:

A website shows content; an app stores data and responds to the user.

Why learn:

Knowing what you want keeps you from building the wrong thing.

Key concepts:

Static · interactive · state.

What it is:

The place where the app stores data permanently.

Why learn:

Without a database, everything disappears when the page closes.

Key concepts:

Table · record · persistence.

What it is:

Each user signs in with their own account and sees only what belongs to them.

Why learn:

It’s the foundation of any app with more than one person.

Key concepts:

Authentication · session · permission.

What it is:

Build the app in parts, validating each one before moving on to the next.

Why learn:

Layer by layer prevents the chaos of doing everything at once.

Key concepts:

Increment · validate · stack.

What it is:

Simulate real app usage from beginning to end.

Why learn:

Catches bugs before users do and gives you confidence to publish.

Key concepts:

Real workflow · bug · coverage.

What it is:

Put the app online with the database and login working.

Why learn:

Only once it’s live will you find out whether the app solves the problem.

Key concepts:

Deploy · production · real feedback.

View Complete
2.3~45 min

🧩 Build Anything

First principles, a 5-step protocol, and the universal stack for any project.

What it is:

Break any project down into its most basic elements.

Why learn:

Without blindly copying, you can solve problems you've never seen before.

Key concepts:

Decompose · essence · from basics to the whole.

What it is:

A fixed sequence that takes you from idea to finished project.

Why learn:

A repeatable method that always gets you past square one.

Key concepts:

Step by step · repeatable · checklist.

What it is:

A lean set of tools that covers almost everything.

Why learn:

Mastering a few tools is worth more than knowing many.

Key concepts:

Stack · standard · reuse.

What it is:

Define the target and collect data about it on the web.

Why learn:

The right data turns a vague idea into a real project.

Key concepts:

Target · scraping · collection.

What it is:

Review, complete, and organize the data into something useful.

Why learn:

Raw data is worthless; processed data is gold.

Key concepts:

Validate · enrich · package.

What it is:

Take initiative and use AI to improve the request itself.

Why learn:

People who take action and ask better questions get much more out of the agent.

Key concepts:

Initiative · meta-prompt · iterate.

View Complete
2.4~55 min

🎨 Design Systems

Design became code: extract an identity, use skills, and create a reusable system.

What it is:

Design decisions become rules that the agent applies directly.

Why learn:

You direct the style without knowing how to open Figma.

Key concepts:

Design as code · rules · consistency.

What it is:

Turn good design principles into clear instructions.

Why learn:

"Make it look good" doesn’t work; explicit rules do.

Key concepts:

Spacing · hierarchy · typography.

What it is:

Design packages the agent applies to any project.

Why learn:

You reuse your visual style without having to explain everything again.

Key concepts:

Skill · ready-made style · reuse.

What it is:

Extract colors, fonts, and tone from a reference and apply them again.

Why learn:

Keeps everything on-brand effortlessly.

Key concepts:

Palette · font · brand tone.

What it is:

Add images, motion, and 3D effects to the project.

Why learn:

These touches make the result memorable.

Key concepts:

Image · animation · 3D.

What it is:

A kit with your design rules for all projects.

Why learn:

Everything you create comes out with the same identity.

Key concepts:

System · tokens · reuse.

View Complete
← Previous track: Fundamentals Next track: Operate & Profit →