Claude
Coding, long writing and careful reasoning, from your first prompt to agents.

Free courses, tool guides and quizzes for people who use AI to get something done. Start from the job in front of you, or from the tool you already have open.
5 courses266 techniques187 tool guides40 quizzes
Coding, long writing and careful reasoning, from your first prompt to agents.


An AI code editor with agents, rules and full codebase search.


Build real software by describing it, and keep your users' data safe when you launch.

Each one goes straight to the lesson or guide for that job. These are starting points based on what each tool is built for, not benchmark results.

Draft section by section, then edit in a document instead of a chat thread.

Get an answer with sources you can open and check yourself.

Work from your own PDFs and notes rather than the open web.

Describe the columns, get the chart, and read the code behind it.

Let an agent work in your real project, with tests and review in the loop.

Plan it, build in small pieces, and lock down security before launch.

Turn a prompt you keep retyping into a saved assistant or a chain of steps.

Pick the tool for the medium, then see real results and the prompts behind them.

Run open models locally instead of sending your work to a hosted service.
Say what done looks like, who it's for, and what format you want. A one-line request makes the model guess all three.
Paste the source, the example or the file. A weak answer often comes from missing context, not from a missing magic phrase.
Use a fast model for quick work and a reasoning model when a wrong answer would cost you. Stronger is not always better.
A confident answer can still be wrong. Find the number, quote or assumption the result depends on, and check that against a source.
I need: [the result, in one sentence] It's for: [who will read or use it] What you should know: [facts, files or examples you can't guess] Limits: [length, tone, tools, anything to avoid] Done means: [how I'll judge it] If something important is missing, ask me up to three questions before you start. When you finish, list any claims I should verify.
Setup, pricing, limits and lesser-known tips for 187 AI tools, written from each vendor's docs.
Browse the guides40 quizzes with instant answers and no sign-up.
Your app has a working login screen. What has that proved so far?
A login only proves identity. The server or database must check on every request that this user may touch this record, and the real test takes two accounts.
Real AI results, each with the prompt or skill behind it.
Open the LibraryStart from the job, not the brand. For general questions and writing, ChatGPT, Claude and Gemini are all general assistants, and each has a free plan, so try your real task in two of them and compare. To change code inside a project, use a coding tool such as Cursor or Claude Code. For an answer with sources you can open, try Perplexity. The table of jobs on this page links to the right lesson or guide for each one.
Describe the finished result, give the model the context it can't guess, match the model to the task, and check the part of the answer that matters. Those four habits carry across every tool and do more than any single prompt. The prompt template on this page puts them into a form you can copy.
You need the basics: clear context, a defined result, and an example of what good looks like. You don't need a collection of tricks. Choosing the right tool, managing what the model can see, and checking its output usually matter more.
Both. Each course starts with first steps and moves up through real workflows and advanced techniques, and every technique is tagged by level. If you already use a tool daily, take its quiz first and let your wrong answers show you where to go.
Every course, guide and quiz here is free, with no sign-up. The tools themselves are priced by their vendors. Plans change often, so the tool guides show the date they were checked and link to the vendor's own pages.
Troiana, a design and development studio in Prishtina. Tool guides are written from each vendor's official docs, with sources linked on the page. They report what the docs say, and they don't claim hands-on benchmarks.