claude-yolo · Oct 20, 2026 · Oct 20, 2026
diff --git a/content/.metadata.json b/content/.metadata.json
diff --git a/content/claude-code-manifest.json b/content/claude-code-manifest.json
@@ -116,7 +116,6 @@
   "_nodeVersion": "24.21.0",
   "dependencies": {},
   "_hasShrinkwrap": false,
-  "readmeFilename": "README.md",
   "optionalDependencies": {
     "@anthropic-ai/claude-code-linux-x64": "2.1.304",
     "@anthropic-ai/claude-code-win32-x64": "2.1.304",

diff --git a/content/claude/build/overview.md b/content/claude/build/overview.md
@@ -17,34 +17,32 @@ When the plugin is ready, you can [submit it](/docs/directory/publish) to Anthro
 
 ## Choose a starting page
 
-<CardGroup cols={2}>
-  <Card title="Build a plugin" icon="box" href="/docs/plugins/build" arrow>
-    Lay out the plugin folder and manifest, write the skills, reference your MCP server, and test the plugin in Claude.
-  </Card>
-
-  <Card title="Write skills" icon="book-open" href="/docs/skills/how-to" arrow>
-    Teach Claude your workflows: the SKILL.md frontmatter, the instructions, reference files, and scripts.
-  </Card>
-
-  <Card title="Build an MCP server" icon="server" href="/docs/connectors/building/index" arrow>
-    Give the plugin access to your product or data: implement the server, set up authentication for Claude's clients, and test it.
-  </Card>
-
-  <Card title="Add interactive UI" icon="window" href="/docs/connectors/building/mcp-apps/getting-started" arrow>
-    Have your MCP server show interactive components in the conversation with MCP Apps. Optional.
-  </Card>
-</CardGroup>
-
-<Card title="Submit your plugin or MCP server" icon="store" href="/docs/directory/publish" horizontal arrow>
-  List it in Anthropic's directory so anyone can add it: who can submit, what review involves, and the developer portal steps. Submit your MCP server as a connector too, even when your plugin references it.
-</Card>
-
-<Note>
-  * If you want to connect a tool or install a plugin for yourself, see the [Customize Claude](/docs/extend/overview) tab
-  * If you're not sure whether your plugin needs an MCP server at all, see [Decide what to include in your plugin](/docs/connectors/building/what-to-build)
-  * If you're distributing only inside your organization, see [Roll out a plugin to your whole organization](/docs/plugins/org-rollout)
-  * If you're building only for Claude Code's terminal and IDE users, see the [Claude Code plugin docs](https://code.claude.com/docs/en/plugins/create), which cover what that surface alone supports
-</Note>
+> **[Build a plugin](/docs/plugins/build)**
+>
+> Lay out the plugin folder and manifest, write the skills, reference your MCP server, and test the plugin in Claude.
+
+> **[Write skills](/docs/skills/how-to)**
+>
+> Teach Claude your workflows: the SKILL.md frontmatter, the instructions, reference files, and scripts.
+
+> **[Build an MCP server](/docs/connectors/building/index)**
+>
+> Give the plugin access to your product or data: implement the server, set up authentication for Claude's clients, and test it.
+
+> **[Add interactive UI](/docs/connectors/building/mcp-apps/getting-started)**
+>
+> Have your MCP server show interactive components in the conversation with MCP Apps. Optional.
+
+> **[Submit your plugin or MCP server](/docs/directory/publish)**
+>
+> List it in Anthropic's directory so anyone can add it: who can submit, what review involves, and the developer portal steps. Submit your MCP server as a connector too, even when your plugin references it.
+
+> [!NOTE]
+>
+> * If you want to connect a tool or install a plugin for yourself, see the [Customize Claude](/docs/extend/overview) tab
+> * If you're not sure whether your plugin needs an MCP server at all, see [Decide what to include in your plugin](/docs/connectors/building/what-to-build)
+> * If you're distributing only inside your organization, see [Roll out a plugin to your whole organization](/docs/plugins/org-rollout)
+> * If you're building only for Claude Code's terminal and IDE users, see the [Claude Code plugin docs](https://code.claude.com/docs/en/plugins/create), which cover what that surface alone supports
 
 ## Steps to build and publish a plugin
 

diff --git a/content/claude/claude-science/admin-controls.md b/content/claude/claude-science/admin-controls.md
@@ -65,9 +65,9 @@ The control on the **Claude Science** page is the upper limit, and roles narrow
 
 Turning on the **Claude Science** capability in a role also turns on the seven under it, and you can then turn off the ones that role shouldn't have. Any capability whose control your organization can't turn on stays off. Turning the **Claude Science** capability off turns them all off. A role whose **Capability access** setting is **All capabilities** already includes all seven. A role set to **All generally available** gets them when you turn on its **Claude Science** capability (see [Who gets access after you enable](/docs/claude-science/enable-claude-science#who-gets-access-after-you-enable)).
 
-<Note>
-  Giving a custom role the **Claude Science** capability gives its members the app. For skills from claude.ai and your organization's plugins to reach those members, their custom roles also need one of the capability options listed under [Organization skills](#organization-skills).
-</Note>
+> [!NOTE]
+>
+> Giving a custom role the **Claude Science** capability gives its members the app. For skills from claude.ai and your organization's plugins to reach those members, their custom roles also need one of the capability options listed under [Organization skills](#organization-skills).
 
 For a member whose custom roles don't include a capability, the feature behaves as it does when you turn its control off (see [How changes reach members](#how-changes-reach-members)). The setting is grayed out in the Claude Science app, and what the member set up earlier is kept. To give that member the feature, turn on the capability in one of their roles. A change to a role's capabilities can take up to 15 minutes to reach members, and then applies on the member's next turn or request.
 

diff --git a/content/claude/claude-science/artifacts.md b/content/claude/claude-science/artifacts.md
@@ -8,9 +8,9 @@
 
 In Claude Science, an artifact is a file Claude saves into the project: a figure, processed dataset, report, notebook, or other output. Artifacts are stored on your computer in the app's data folder and persist until you delete them. Other files Claude writes during a session are temporary and are cleared a few hours after the session ends; ask Claude to save a scratch file if you want to keep it.
 
-<Note>
-  If you use artifacts in a claude.ai chat rather than the Claude Science app, see [What are artifacts and how do I use them?](https://support.claude.com/en/articles/17153992-what-are-artifacts-and-how-do-i-use-them) in the help center instead.
-</Note>
+> [!NOTE]
+>
+> If you use artifacts in a claude.ai chat rather than the Claude Science app, see [What are artifacts and how do I use them?](https://support.claude.com/en/articles/17153992-what-are-artifacts-and-how-do-i-use-them) in the help center instead.
 
 ## Working with artifacts