<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Welcome to Doks on My Docs</title><link>/</link><description>Recent content in Welcome to Doks on My Docs</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2020-2026 Thulite</copyright><lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0800</lastBuildDate><atom:link href="/index.xml" rel="self" type="application/rss+xml"/><item><title>Example Post</title><link>/blog/example-post/</link><pubDate>Mon, 16 Feb 2026 16:31:32 +0100</pubDate><guid>/blog/example-post/</guid><description>Use blog posts to communicate product updates and new features in a clear and consistent format.</description></item><item><title>AI-native 通用问题</title><link>/docs/common_qa/ai-native-%E9%80%9A%E7%94%A8%E9%97%AE%E9%A2%98/</link><pubDate>Sun, 07 Jun 2026 00:00:00 +0800</pubDate><guid>/docs/common_qa/ai-native-%E9%80%9A%E7%94%A8%E9%97%AE%E9%A2%98/</guid><description>&lt;h3 id="1-什么是-ai-native-创业和传统创业的核心区别是什么">1. 什么是 AI-native 创业，和传统创业的核心区别是什么&lt;/h3>
&lt;p>AI-native 创业指的是把 AI 当作技术和组织发展的核心基础设施来搭公司，而不是在已有团队上额外加几个 AI 工具。核心区别在于传统创业默认每进入一个新阶段就要更大的团队、新的技能组合和一轮新融资，而 AI-native 创业把这套预期打破了，一个创始人靠 agentic coding 就能干过去一个工程团队的活。简单说传统创业是&amp;quot;招人换阶段&amp;quot;，AI-native 是&amp;quot;用 AI 杠杆换阶段&amp;quot;。结果是 2026 年一个好点子能比以前走得远得多，验证、原型、上线的时间被压成了几周甚至几天。&lt;/p></description></item><item><title>Example Guide</title><link>/docs/guides/example-guide/</link><pubDate>Thu, 07 Sep 2023 16:04:48 +0200</pubDate><guid>/docs/guides/example-guide/</guid><description>&lt;p>Guides lead a user through a specific task they want to accomplish, often with a sequence of steps. Writing a good guide requires thinking about what your users are trying to do.&lt;/p></description></item><item><title>Example Reference</title><link>/docs/reference/example-reference/</link><pubDate>Thu, 07 Sep 2023 16:13:18 +0200</pubDate><guid>/docs/reference/example-reference/</guid><description>&lt;p>Reference pages are ideal for outlining how things work in terse and clear terms. Less concerned with telling a story or addressing a specific use case, they should give a comprehensive outline of what your documenting.&lt;/p></description></item><item><title>Resources</title><link>/docs/resources/</link><pubDate>Tue, 27 Feb 2024 09:30:56 +0100</pubDate><guid>/docs/resources/</guid><description>&lt;p>Link to valuable, relevant resources.&lt;/p></description></item><item><title>Page not found</title><link>/404/</link><pubDate>Tue, 17 Feb 2026 13:06:19 +0100</pubDate><guid>/404/</guid><description>&lt;p>Sorry, we can&amp;rsquo;t find the page you&amp;rsquo;re looking for.&lt;/p>
&lt;p>Use the navigation above or go back to the 

&lt;a class="link link--text" href="/">homepage&lt;/a>.&lt;/p></description></item><item><title>Privacy Policy</title><link>/privacy/</link><pubDate>Thu, 07 Sep 2023 17:19:07 +0200</pubDate><guid>/privacy/</guid><description>&lt;p>We value your privacy and are committed to protecting your personal data. This Privacy Policy explains what information we collect, how we use it, and the choices you have.&lt;/p></description></item></channel></rss>