Stop chasing the next tool.
Get your material in order, and let AI learn you.
I work with professional knowledge workers and small teams of five to ten people:
you can build an AI workflow and a knowledge base with nothing but written documents and organized folders.
AI can only help you once it understands you.
Hand this site's URL to the AI you already use, and it can start working for you right away.
Hi, I'm Mika, Coach Jiang's AI assistant. ChatGPT, Gemini, Codex, Claude and Cowork can all read me.
Please read the content of this site, introduce it to me in Mika's voice, and guide me based on what I need:
https://jiangyude.com/en/index.html
Or keep browsing yourself. Pick one below to start.
① Free courses · talks
Free online talks every month
Pick the ones you want to learn.
See the schedule →
② Self-study resources
Articles and tutorials live here
Tell me what you want to read and I'll find it for you.
Enter self-study →
③ AI Office · Skill Packages
Let Mika handle your paperwork
Basic admin, folder cleanup, document work. Skill packages are free to download; the full AI Office is built with you during individual coaching.
See the AI Office →
④ Quiz · just for fun
How strong is your AI game?
Twenty floors, about six minutes. Climb from junior staff to business owner, then get your brain multiplier, execution multiplier, and power archetype.
Push the door open →
I'm a tacit knowledge distiller. I help you pull out the judgment and experience you already have in your head but have never written down.
What I actually sell is capability: distilling, accumulating and structuring your knowledge so it becomes an asset you own.
Get your judgment out of your head
Your judgment, your methods, your standards are scattered across documents, meetings and conversations. AI helps you find them.
Store it as your knowledge base
What you distill needs a home. Every time you finish a piece of work, the knowledge base gets a little thicker.
Let AI work to your standards
Once the knowledge base is there, AI can finally act your way. It remembers you, so it stops guessing.

All three steps do the same thing: turn your judgment into rules AI can follow.
Want to take a class? See Courses. Want to understand my method? See Knowledge Architecture. Want to dig around yourself? Go to self-study. Want to talk about working together? See Services.
Paid courses, monthly free talks and invited teaching, all on one page, filterable by type and format.
See courses →Documents as the system, three stores plus a control layer, and how this whole thing grew over three years.
See the architecture →Learning maps, post-class decks, skill packages and AI trend notes, strung into a path you can pick from.
Enter self-study →Talks, individual coaching, team coaching, and free skill packages you can take with you.
See services →
I run two free online talks every month.
Details are posted in my LINE community.
Use AI to amplify what you're already good at.
This site isn't built for human readers alone. From search engines to AI assistants, I want every kind of reader to find me, understand me and put me to use. The whole method is public.
Search engines can find it
Sitemap, structured data, clean URLs. Google can find it and knows what each page is about.
AI summaries can read it
A site summary written for AI (llms.txt). ChatGPT and Claude read it and understand in one pass who I am and what I do.
Generative engines will cite it
Content shaped so AI can pick it up and retell it. When someone asks an AI about these topics, I'm more likely to come up.
AI agents read the data directly
Services, positioning and the full site index are published as open data files. AI agents don't guess and don't need a key. They just read.
The layer that decides how the whole thing runs
AGENTS.md, skill retrieval, the tag dictionary, hooks, loops and review rules.
Websites used to serve one kind of reader: people. These days the thing looking something up for you, or helping you decide, is often an AI. So I upgraded this site until both kinds of reader could follow it.
The first layer is static data files: the full site index site-index.json, my positioning profile.json, my services offers.json, and a summary written for AI llms.txt. Fixed URLs, open formats. Paste one into any AI and it can read it.
The second layer is dynamic endpoints: small services that compute in real time, like the view counter.
(Every filename below is a live link. Click one and you'll see exactly what it looks like.)
This data exists so people and AI can find me. It was never meant to be gated or charged for. So I deliberately made it public, no signup, read it straight. When people ask how to apply for a key, my answer is: you don't. Just read the URL.
For things like positioning and services I maintain a single source, and the rest of the site updates from it automatically. That way what a person sees and what an AI reads are always the same version, with no two stories that fail to line up.