Skip to content
Agentic Levels

Everything starts here.

GuestLocal progress only
PreferencesSign in
01Start with one taskBest first move for beginners.02Check your LevelMeasure where you are.03Score an AI resultFind the habit to practice first.04Return to Your WorkScores, links, and checkpoints.
Start here

Begin

HomeThe main entry point.New to AIStart with one useful task.
Know where you are

Measure

Check your LevelUse this after you have tried AI.Fluency ScoreScore an AI result you can review.
Build the habit

Learn

LevelsLessonsTracks
Find the reference

Library

PromptsReferenceResourcesCompare Tools
Turn it into work

Apply

Your Next MoveChoose what AI should change next.Tool SetupGet the tools ready.
Come back later

Return

Your WorkScores, links, and checkpoints.My PathContinue from your level.Updates
Site

Site

PricingAboutFAQ & FeedbackPreferences

© 2026 Fuentes Studio

Privacy·Terms
yourCouncil
Ready to help
✦

What do you want to understand?

Ask anything about what you're learning.

Agentic Reference

Commands, workflow shapes, and shortcuts — adapted to your selected tool.

How to use Claude Code reference

Start here if you want the shortest path: how this tool works, what matters first, and what to ignore until later.

Reference for Claude Code

From commands to durable operating habits for Claude Code

The reference area is most literal in Claude Code because the commands and workflow patterns map directly to the terminal.

  • Use the commands list as your pattern bank for recurring work.
  • Keep the starting flow short, then upgrade into repo-native memory.
  • Prefer proof-producing loops over long one-shot prompts.
Claude Code Focus

This page is the literal reference version

For Claude Code, the command catalog is not an analogy. It is the real control surface for many of the level jumps described elsewhere on the site.

Use it as a lookup table

When you forget a command, shortcut, or workflow shape, come here first instead of reconstructing it from memory.

Pair commands with memory

A command is most useful when the repo already contains the rules and context that make the command worth running.

Graduate into automation

As you move up levels, commands stop being shortcuts and start becoming the building blocks of repeatable systems.