01
Mindset — AI as partner
Articulate when AI helps, when it does not, and what you always own as the human.
/fluency
General AI Fluency
Build the habits, judgment, and workflows that make AI a reliable teammate.
Overview
What this track proves.
Fluency
This track is for anyone who wants to change how they work with AI — not just learn one tool. You will move through the FlyRank AI Builder Ladder across Mindset, Practice, Output, and Judgment. Specialization interns get these foundations automatically; you can also choose this track on its own.
Pace
4-6 hrs/week
Prerequisites
Curiosity and willingness to ship small public work. No engineering background required.
Capstone
Personal AI operating system scored against the four ladder dimensions.
Review
Async feedback on manifesto, workflow doc, public artifact, and capstone system.
Good fit
This is for you if...
Use this section as a practical gut check before you apply.
You want a structured path to AI fluency before or instead of a role-specific track.
You are Curious or Tinkerer on the Builder Ladder and want to reach Builder.
You care about judgment and accountability, not just faster drafts.
Outcomes
What you can leave with.
The goal is proof of work, not passive course completion.
Locate yourself honestly on the AI Builder Ladder and set a starting baseline.
Document a repeatable daily AI workflow with clear handoffs between tools.
Ship one public artifact where AI was a core partner.
Build a personal quality checklist for evaluating AI output before you ship.
Optional Anthropic courses when partner access allows. Read the FAQ. Your capstone remains the main credential proof.
Curriculum
The work, in order.
02
Practice — daily workflows
Use chat, IDE, and automation tools in a repeatable loop — not one-off prompts.
03
Output — ship in public
Finish and publish one small artifact so you cross the Tinkerer-to-Builder line.
04
Judgment — quality bars
Evaluate AI output against criteria you set — accuracy, context, tone, completeness.
Capstone examples
The artifact can take a few shapes.
A personal AI operating system: prompt library, eval checklist, and one shipped workflow.
A documented failure-mode log with process changes for each case.
A compounding workflow asset others could reuse on the next project.
Builder signal
What Builder-level work looks like.
Builder means you ship real work with AI as a partner — at least one public artifact, a documented workflow, and judgment you can explain.
Tool access
What you need to start.
The track is designed around accessible tools and clear alternatives. Use this as a practical setup check before applying.
ToolAccessAlternatives and caveats
AI assistant
Required
ChatGPT, Claude, Gemini, or another general AI chat tool
Free tiers are enough for manifesto, workflow, and checklist work.
Builder environment
Recommended
Cursor, Copilot, Claude Desktop, or another IDE-integrated assistant
Helpful for Practice assignments; chat-only is acceptable for fluency-only path.
Public output target
Required
GitHub repo, deployed page, published post, or portfolio link
The Output assignment requires something another person can open without extra context.
ChatGPT or ClaudeCursor or CopilotNotion or DocsPublic repo or deploy target