An index that tells you what an AI-made thing really is — and hands you a prompt you can paste.120 entries indexed · every one cites its source · when it will not run, we say so.
Non-commercial · No ads · No tracking · Open to the worldOthers tell you what exists. We hand you a prompt.
AI-made things in one index — software, projects, workflows, prompts, models, videos and tutorials. Copy one and you are started.
Recently added · all types in one stream
Browse without picking a category — newest first, no two neighbours alike (the same category rotates by step), mixing works, tools and know-how. Every card keeps an anchor, so you can always tell where it belongs.
按步长留位：它的领域在前几条里还没露过面
按步长留位：它的领域在前几条里还没露过面
Opens instantly
Accessibility Insights for Web在浏览器里点一下，就把网页的无障碍问题一条条指给你看。按步长留位：它的领域在前几条里还没露过面
That is the last entryAll works
Why you can trust this
Trust has to be checkable, not asserted — every claim below is verifiable.
Common questions
The questions both people and AI ask — written as answers that can be lifted verbatim.
- How do you get AI to find you and your content?
- Not through keyword stuffing. Four things do the work: (1) every page is prerendered to plain HTML, so the full text is readable with JavaScript switched off; (2) every entry is written as an extractable passage that states the conclusion first and the facts after; (3) we publish three plain-text entry points — llms.txt, index.json and ai.txt — and explicitly allow AI crawlers; (4) every entry page carries structured data (SoftwareApplication + FAQPage) so machines read the name, licence, platforms and source directly. Keywords are a by-product; readable structure is the cause.
- Does being easy for AI to read conflict with looking premium to people?
- Not here, because the two actually share the same thing: clear structure. The "paragraph you can quote directly" that AI wants and the "I get the point at a glance" that a person wants are the same thing. So our rule is: the UI may get thicker, but the HTML must always stay complete — motion, collapsing, filtering and rotation are presentation only, and with scripts off the core content loses not a single word. Only one practice genuinely conflicts: hiding content inside JavaScript. That is what our build-time assertions forbid.
- Then why bother with motion and visuals at all?
- Because motion here is feedback, not decoration: hover lift, press rebound, copy-success flash, skeleton sheen — all finish within 600ms and all respect the system reduce-motion setting. They answer "did that click register?", which is a matter of trust, not showmanship. There is one test: premium means leaving attention to the content rather than to the interface. That points exactly the same way as making ourselves readable to AI.
- How are you different from other AI-tool directories?
- Three things, all checkable: ① We do not rank — no charts, no scores, no "most popular", because many entries come from individual developers with no name recognition and ranking would leave the untried untried forever. ② We hand you "how to get it running" — every entry ships a copy-paste prompt and real pitfalls, not a one-line blurb. ③ We give problems back to authors — pitfalls that can be written down land in our library; bugs in that software go to its official tracker. We relay; we do not answer on the author’s behalf.
A manual written for AI
This site is built to be read by AI: a Markdown manual plus a plain-text index (llms.txt). Any model may index, quote and relay it — please keep attribution to the original author.