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.

Workspace Guide

Structure your context so every session gets better over time, with memory, briefs, and working files that stay close to the tool you use.

Start HereWorkspace GuideInterfaces Guide
Workspace for Claude Code

Optimize the repo for repeated terminal sessions for Claude Code

Claude Code gets stronger when the repo explains itself clearly. The priority is stable commands, explicit guardrails, and memory that compounds through CLAUDE.md and skills.

  • Keep CLAUDE.md near the root and treat it like working memory, not marketing copy.
  • Codify frequent workflows as slash commands or reusable skills instead of retyping prompts.
  • Bias toward runnable commands and diff-based proof inside the repo.

Recommended structure

Favor a compact root, a strong CLAUDE.md, and explicit command paths so Claude Code can orient fast in a terminal session.

Start here

Start with a lean root `CLAUDE.md`, then add modules only after you repeat the same explanation twice. Keep the repo easy for the CLI to inspect and easy for you to verify.

Ignore for now

Ignore big skill libraries, hooks, and fancy context routing until your basic plan → execute → verify loop is stable in one real repo.

·CLAUDE.mdRoot rules file, behavioral mandates only, under 200 lines
·AGENTS.mdOptional: extra repo instructions and tool documentation
▾modules/Detailed docs that CLAUDE.md references
·module-index.mdIndex of all modules
·testing.mdTest conventions and patterns
·deployment.mdDeploy checklist and steps
·post-mortems.mdLessons from past failures
▾key-facts/Per-system summaries the agent reads before touching a tool
·auth.mdAuth system notes
·database.mdDB schema and patterns
▾docs/Architecture decisions, API contracts, ADRs
·architecture.mdSystem overview
▸adr/Architecture decision records
Next: Interfaces Guide →