docs: add MicroMod connector guide

.github/workflows/bun-build.yml

@@ -0,0 +1,26 @@
+# Created using @tscircuit/plop (npm install -g @tscircuit/plop)
+name: Build
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Install dependencies
+        run: bun install
+
+      - name: Run build
+        run: bun run build

.github/workflows/bun-formatcheck.yml

@@ -0,0 +1,26 @@
+# Created using @tscircuit/plop (npm install -g @tscircuit/plop)
+name: Format Check
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  format-check:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Install dependencies
+        run: bun install
+
+      - name: Run format check
+        run: bun run format:check

.github/workflows/bun-typecheck.yml

@@ -0,0 +1,26 @@
+# Created using @tscircuit/plop (npm install -g @tscircuit/plop)
+name: Type Check
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  type-check:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Install dependencies
+        run: bun i
+
+      - name: Run type check
+        run: bunx tsc --noEmit

.github/workflows/stalebot.yml

@@ -0,0 +1,29 @@
+name: 'Close stale issues and PRs'
+on:
+  schedule:
+    - cron: '30 1 * * *'  # Runs at 1:30 AM UTC every day
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v9
+        with:
+          # Issues config
+          stale-issue-message: 'This issue has been automatically marked as stale because it has had no recent activity. It will be closed if no further activity occurs.'
+          close-issue-message: 'This issue was closed because it has been inactive for 14 days since being marked as stale.'
+          days-before-issue-stale: 60
+          days-before-issue-close: 14
+
+          # Pull request config
+          stale-pr-message: 'This PR has been automatically marked as stale because it has had no recent activity. It will be closed if no further activity occurs.'
+          close-pr-message: 'This PR was closed because it has been inactive for 1 day since being marked as stale.'
+          days-before-pr-stale: 2
+          days-before-pr-close: 1
+
+          # General config
+          exempt-issue-labels: 'pinned,security,help-wanted'
+          exempt-pr-labels: 'pinned,security,help-wanted'
+          stale-issue-label: 'no-issue-activity'
+          stale-pr-label: 'no-pr-activity'
+          operations-per-run: 100

.gitignore

@@ -1,6 +1,6 @@
 # Dependencies
 /node_modules
-
+package-lock.json
 # Production
 /build
 

AGENTS.md

@@ -0,0 +1,41 @@
+# tscircuit docs - Development Guidelines
+
+- Use `bun` not `node`/`npx`/`npm`
+
+## Commands
+
+- **Start development server**: `bun run start`
+- **Build site**: `bun run build`
+- **Serve built site**: `bun run serve`
+- **Type check**: `bun run typecheck`
+- **Format code**: `bunx @biomejs/biome format --write .`
+- **Lint code**: `bunx @biomejs/biome lint .`
+
+## Code Style
+
+- **Formatting**: Use Biome formatter with space indentation
+- **Imports**: Use organized imports (auto-sortable by Biome)
+- **JSX**: Use double quotes for JSX attributes
+- **Semicolons**: Prefer to omit except when necessary
+- **Naming**: Use kebab-case for filenames
+- **Types**: TypeScript is used throughout, explicit "any" is allowed
+- **Error handling**: Follow React/Docusaurus error boundary patterns
+- **Markdown**: Follow standard Docusaurus MDX patterns
+
+## Documentation Standards
+
+- Keep documentation concise and example-focused
+- Include working code examples where possible
+- Use proper heading hierarchy (h1 → h2 → h3)
+- Images should include descriptive alt text
+
+## Testing tscircuit TSX Code
+
+- To test tscircuit TSX code, create a new file in the `codetestingplayground`
+  directory and add the code you want to test, then run `tsci build <filename>.circuit.tsx`
+- You may also want to generate snapshots via `tsci snapshot <filename>.circuit.tsx`
+  and inspect the results
+- The autorouter and DRC often throws errors and this is expected since the
+  product is in early stages of development, use `tsci build --ignore-errors` to ignore
+  non-fatal errors
+- Prefer `bunx` over `npx`

CLAUDE.md

@@ -0,0 +1,41 @@
+# tscircuit docs - Development Guidelines
+
+- Use `bun` not `node`/`npx`/`npm`
+
+## Commands
+
+- **Start development server**: `bun run start`
+- **Build site**: `bun run build`
+- **Serve built site**: `bun run serve`
+- **Type check**: `bun run typecheck`
+- **Format code**: `bunx @biomejs/biome format --write .`
+- **Lint code**: `bunx @biomejs/biome lint .`
+
+## Code Style
+
+- **Formatting**: Use Biome formatter with space indentation
+- **Imports**: Use organized imports (auto-sortable by Biome)
+- **JSX**: Use double quotes for JSX attributes
+- **Semicolons**: Prefer to omit except when necessary
+- **Naming**: Use kebab-case for filenames
+- **Types**: TypeScript is used throughout, explicit "any" is allowed
+- **Error handling**: Follow React/Docusaurus error boundary patterns
+- **Markdown**: Follow standard Docusaurus MDX patterns
+
+## Documentation Standards
+
+- Keep documentation concise and example-focused
+- Include working code examples where possible
+- Use proper heading hierarchy (h1 → h2 → h3)
+- Images should include descriptive alt text
+
+## Testing tscircuit TSX Code
+
+- To test tscircuit TSX code, create a new file in the `codetestingplayground`
+  directory and add the code you want to test, then run `tsci build <filename>.circuit.tsx`
+- You may also want to generate snapshots via `tsci snapshot <filename>.circuit.tsx`
+  and inspect the results
+- The autorouter and DRC often throws errors and this is expected since the
+  product is in early stages of development, use `tsci build --ignore-errors` to ignore
+  non-fatal errors
+- Prefer `bunx` over `npx`

README.md

@@ -1,41 +1,3 @@
-# Website
+# [docs.tscircuit.com](https://docs.tscircuit.com)
 
-This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator.
-
-### Installation
-
-```
-$ yarn
-```
-
-### Local Development
-
-```
-$ yarn start
-```
-
-This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
-
-### Build
-
-```
-$ yarn build
-```
-
-This command generates static content into the `build` directory and can be served using any static contents hosting service.
-
-### Deployment
-
-Using SSH:
-
-```
-$ USE_SSH=true yarn deploy
-```
-
-Not using SSH:
-
-```
-$ GIT_USER=<Your GitHub username> yarn deploy
-```
-
-If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.
+The [tscircuit](https://github.com/tscircuit/tscircuit) docs

biome.json

@@ -7,8 +7,18 @@
     "enabled": true,
     "indentStyle": "space"
   },
+  "css": {
+    "parser": {
+      "cssModules": true
+    }
+  },
   "files": {
-    "ignore": ["cosmos-export", "dist", "package.json"]
+    "ignore": [
+      "cosmos-export",
+      "dist",
+      "package.json",
+      "!./codetestingplayground"
+    ]
   },
   "javascript": {
     "formatter": {
@@ -31,6 +41,9 @@
       "complexity": {
         "noForEach": "info"
       },
+      "correctness": {
+        "useExhaustiveDependencies": "off"
+      },
       "style": {
         "noUnusedTemplateLiteral": "off",
         "noUselessElse": "off",