fix: docs links

apps/docs/src/content/docs/design/dependencies.md

@@ -12,8 +12,8 @@ The risk is real as we were told ["Stop using dapps"](https://decrypt.co/209804/
 
 In the web context, dependencies make the bundle larger and the site slower.  [Island Architecture](https://docs.astro.build/en/concepts/islands/) --  we try to contain comopnents into static ones as plain markups and text when possible, and limit interacitivt to speicifc componenst. This help simplify diff across versions and make a larger chunk of the dApp served by IPFS which is immutable. This also help rendering infrequently updated contnet faster, composing different frameworks in a page and encourages pushing slow operations to the server. Typically, we postpone hydration for components requiring a connected wallet. 
 
-In the context of autonomous agent, a simple package-lock.json is not sufficient to guarantee your agent keep running autonomously and safely. As dev we are just tired of [https://en.wikipedia.org/wiki/Dependency_hell].
-As we argued in [Architecture](/architecture.md) the challenge is even more prominent for diverse, decentralized agents than dApps.
+In the context of autonomous agent, a simple package-lock.json is not sufficient to guarantee your agent keep running autonomously and safely. As dev we are just tired of [dependency hell](https://en.wikipedia.org/wiki/Dependency_hell).
+As we argued in [Architecture](/design/architecture/), the challenge is even more prominent for diverse, decentralized agents than dApps.
 
 
 
@@ -37,22 +37,30 @@ Many framework adopt a plugin system, some limit dependencies to only plugin bei
 s
 ### Scenario #1
 
+```mermaid
 sequenceDiagram
     Agent->>ToolPlugin: invoke
     ToolPlugin-->>Dependencies: invoke
     Dependencies->>Protocol: invoke
+```
 
 ### Scenario #2
+
+```mermaid
 sequenceDiagram
     Agent->>Agent: invoke
     Agent-->>Dependencies: invoke
     Dependencies->>Protocol: invoke
+```
 
 
 ### Scenario #3
+
+```mermaid
 sequenceDiagram
     Agent->ImmutableTool: invoke
     ImmutableTool->>Protocol: invoke
+```
 
 Improve scenario in #2 (reduced dependencies by design and removing wrapper)
 Enable Scenario #3 where common , immutable hosted on IPFS and work with Lit Action.
@@ -65,7 +73,7 @@ viem
 
 This documents rationale behind opionated dependencies
 
-- For graphql / store related, refers to [/data.md]
+- For graphql / store related, refers to [data](/design/data)
 
 - `vitest` over `jest`
   - used by shadcn, scaffold and generally author find less issues for typscript setup as in jest.
@@ -83,4 +91,3 @@ This documents rationale behind opionated dependencies
 
 ## Form
 - we opt for shadcn form (react-hook-form) instead of radix ui form 
-

apps/docs/src/content/docs/design/starter-kit.md

@@ -67,7 +67,7 @@ We want to be agnostic regarding
 | Base           | onchainkit                                                                                                                                                      | 8k        |                                                                                 |
 | Stark          | [@starknet-react/core](https://www.npmjs.com/package/@starknet-react/core)                                                                                      | 2k        |                                                                                 |
 | XMTP           | [react-xmtp](https://www.google.com/search?q=xmtp-react&oq=xmtp-react&gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIGCAEQLhhA0gEIMTY5N2owajGoAgCwAgA&sourceid=chrome&ie=UTF-8) | 2k        |                                                                                 |
-| EAS            | [@ethereum-attestation-service/eas-sdk](@ethereum-attestation-service/eas-sdk)                                                                                  | 3k        |                                                                                 |
+| EAS            | [@ethereum-attestation-service/eas-sdk](https://www.npmjs.com/package/@ethereum-attestation-service/eas-sdk)                                                                                  | 3k        |                                                                                 |
 | ENS            | ensjs, react                                                                                                                                                    |           |                                                                                 |
 | Mina           | o1js                                                                                                                                                            | 2k        | [zkapp-cli](https://docs.minaprotocol.com/zkapps/tutorials/zkapp-ui-with-react) |
 | MUD            | @latticexyz/react                                                                                                                                               | 3k        |                                                                                 |
@@ -76,4 +76,4 @@ We want to be agnostic regarding
 
 
 ### Wagmi
-- https://wagmi.sh/react/comparisons#overview
+- https://wagmi.sh/react/comparisons#overview

apps/docs/src/content/docs/guides/installation.md

@@ -17,4 +17,4 @@ title: Installation
 
 - You can look for components to use and identify the registry item url, then install via
 
-- `pnpm exec shadcn@canary add https://ddev.geist.network/components/account/balance.json`
+- `pnpm exec shadcn@canary add https://ddev.geist.network/components/account/balance.json`

apps/docs/src/content/docs/guides/shadcn-cli.md

@@ -9,6 +9,7 @@ We support using shadcn cli AS-IS to add geist components, which is deployed ont
 
 
 - `shadcn add <geist-repo-url>/styles/default/identity_address-badge.json`
+
 - Note we are still pointing default shadcn url (i.e. REGISTRY_URL) to original registry, so as to support adding components from both shadcn & geist registry
 
 - We currently do not support adding new components out of this repository to geist registry, but you can host your own registry
@@ -21,4 +22,5 @@ We support using shadcn cli AS-IS to add geist components, which is deployed ont
 
 ## Bulking
 - Note shadcn registry entry contains source code for all related components/lib/hooks, which reduce http round trip.
+
 - Meanwhile currently it requires explicitly specifiying dependencies at e.g. register-ui.tsx over analyzing imports of the component

apps/docs/src/content/docs/intro/introduction.md

@@ -100,7 +100,7 @@ Faster: Build size is generally not the major concern given treeshaking at moder
 
 
 ## How is this different from Scaffold-ETH (or Scaffold-X)
-- check [/starter-kit.md]
+- check [starter-kit](/design/starter-kit)
 
 ## Which frameworks are supported
 - Currently we focus on React with wagmi, but make it framework agnostic and support solid.js is a goal (reaplcing underlying @radix ui components) .
@@ -114,4 +114,3 @@ We're not infosec experts and precisely for that reason we do best-effort to ali
 ## Acknolwedgement
 - Thanks shadcn released with MIT license to make this possible
 - Thank you for contribution
-

apps/storybook/src/stories/decorators/wallet-control.tsx

@@ -1,38 +1,42 @@
 import { AddressBadge } from "@geist/ui-react/components/identity/address-badge";
 import { privateKeyToAccount } from "viem/accounts";
 
+// Abstracted component for the story wrapper with address badge
+const StoryWrapperWithAddress = ({
+	address,
+	children,
+}: { address?: string; children: React.ReactNode }) => (
+	<div className="w-full top-0">
+		<div className="float-right">
+			{address && <AddressBadge address={address} />}
+		</div>
+		<div className="p-10">{children}</div>
+	</div>
+);
+
 export const withWalletControl = () => {
 	return (Story: any, context: any) => {
 		const { privateKey } = context?.args;
 		const account = privateKeyToAccount(privateKey);
 		const { address } = account;
 
 		return (
-			<div>
-				<AddressBadge address={address} />
-				<div className="p-10">
-					<Story args={context.args} />
-				</div>
-			</div>
+			<StoryWrapperWithAddress address={address}>
+				<Story args={context.args} />
+			</StoryWrapperWithAddress>
 		);
 	};
 };
 
 export const withWalletControlWagmi = () => {
 	return (Story: any, context: any) => {
 		const { account } = context?.args;
-
 		const { address } = account;
 
 		return (
-			<div className="w-full top-0">
-				<div className="float-right">
-					{address && <AddressBadge address={address} />}
-				</div>
-				<div className="p-10">
-					<Story args={context.args} />
-				</div>
-			</div>
+			<StoryWrapperWithAddress address={address}>
+				<Story args={context.args} />
+			</StoryWrapperWithAddress>
 		);
 	};
 };