Screenmap
aleqsio/screenmap
Generate a visual navigation map of an Expo / React Native or NativeScript app.
Use Expo DOM components to run web code in a webview on native and as-is on web.
$ npx skills add mweinbach/agent-coworker --skill use-dom -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mweinbach/agent-coworker use-dom --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mweinbach/agent-coworker.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/mobile/.agents/skills/use-dom .claude/skills/use-dom && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "use-dom" agent skill from https://github.com/mweinbach/agent-coworker/tree/main/apps/mobile/.agents/skills/use-dom into .claude/skills/use-dom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-dom", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mweinbach/agent-coworker/tree/main/apps/mobile/.agents/skills/use-domType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mweinbach/agent-coworker --skill use-dom -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mweinbach/agent-coworker use-dom --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mweinbach/agent-coworker.git skills-src && mkdir -p .agents/skills && cp -r skills-src/apps/mobile/.agents/skills/use-dom .agents/skills/use-dom && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "use-dom" agent skill from https://github.com/mweinbach/agent-coworker/tree/main/apps/mobile/.agents/skills/use-dom into .agents/skills/use-dom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-dom", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mweinbach/agent-coworker --skill use-dom -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mweinbach/agent-coworker use-dom --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mweinbach/agent-coworker.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/apps/mobile/.agents/skills/use-dom .cursor/skills/use-dom && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "use-dom" agent skill from https://github.com/mweinbach/agent-coworker/tree/main/apps/mobile/.agents/skills/use-dom into .cursor/skills/use-dom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-dom", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mweinbach/agent-coworker.git --path apps/mobile/.agents/skills/use-dom--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mweinbach/agent-coworker --skill use-dom -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mweinbach/agent-coworker use-dom --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mweinbach/agent-coworker.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/apps/mobile/.agents/skills/use-dom .gemini/skills/use-dom && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "use-dom" agent skill from https://github.com/mweinbach/agent-coworker/tree/main/apps/mobile/.agents/skills/use-dom into .gemini/skills/use-dom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-dom", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mweinbach/agent-coworker use-domInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mweinbach/agent-coworker --skill use-dom -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mweinbach/agent-coworker.git skills-src && mkdir -p .github/skills && cp -r skills-src/apps/mobile/.agents/skills/use-dom .github/skills/use-dom && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "use-dom" agent skill from https://github.com/mweinbach/agent-coworker/tree/main/apps/mobile/.agents/skills/use-dom into .github/skills/use-dom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-dom", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mweinbach/agent-coworker --skill use-dom -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mweinbach/agent-coworker use-dom --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mweinbach/agent-coworker.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/apps/mobile/.agents/skills/use-dom .opencode/skills/use-dom && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "use-dom" agent skill from https://github.com/mweinbach/agent-coworker/tree/main/apps/mobile/.agents/skills/use-dom into .opencode/skills/use-dom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-dom", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
use-domUse Expo DOM components to run web code in a webview on native and as-is on web.
Use Dom is an agent skill from mweinbach/agent-coworker. Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Mobile, covering Cross-platform mobile apps. It works with Expo and React. The repository describes itself as: Terminal-first coworker agent (Bun + OpenTUI). The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit aab9dc6. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Use Dom loads about 2.4k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 494 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mweinbach/agent-coworker at commit aab9dc6, republished under its MIT licence (© mweinbach). 494 words, ~2,419 tokens.
.claude/skills/use-dom/SKILL.md (or your agent's skills folder).DOM components allow web code to run verbatim in a webview on native platforms while rendering as-is on web. This enables using web-only libraries like recharts, react-syntax-highlighter, or any React web library in your Expo app without modification.
Use DOM components when you need:
Avoid DOM components when:
_layout files cannot be DOM componentsCreate a new file with the 'use dom'; directive at the top:
// components/WebChart.tsx
"use dom";
export default function WebChart({
data,
}: {
data: number[];
dom: import("expo/dom").DOMProps;
}) {
return (
<div style={{ padding: 20 }}>
<h2>Chart Data</h2>
<ul>
{data.map((value, i) => (
<li key={i}>{value}</li>
))}
</ul>
</div>
);
}'use dom'; directive at the top of the filedom PropEvery DOM component receives a special dom prop for webview configuration. Always type it in your props:
"use dom";
interface Props {
content: string;
dom: import("expo/dom").DOMProps;
}
export default function MyComponent({ content }: Props) {
return <div>{content}</div>;
}dom Prop Options// Disable body scrolling
<DOMComponent dom={{ scrollEnabled: false }} />
// Flow under the notch (disable safe area insets)
<DOMComponent dom={{ contentInsetAdjustmentBehavior: "never" }} />
// Control size manually
<DOMComponent dom={{ style: { width: 300, height: 400 } }} />
// Combine options
<DOMComponent
dom={{
scrollEnabled: false,
contentInsetAdjustmentBehavior: "never",
style: { width: '100%', height: 500 }
}}
/>Pass async functions as props to expose native functionality to the DOM component:
// app/index.tsx (native)
import { Alert } from "react-native";
import DOMComponent from "@/components/dom-component";
export default function Screen() {
return (
<DOMComponent
showAlert={async (message: string) => {
Alert.alert("From Web", message);
}}
saveData={async (data: { name: string; value: number }) => {
// Save to native storage, database, etc.
console.log("Saving:", data);
return { success: true };
}}
/>
);
}// components/dom-component.tsx
"use dom";
interface Props {
showAlert: (message: string) => Promise<void>;
saveData: (data: {
name: string;
value: number;
}) => Promise<{ success: boolean }>;
dom?: import("expo/dom").DOMProps;
}
export default function DOMComponent({ showAlert, saveData }: Props) {
const handleClick = async () => {
await showAlert("Hello from the webview!");
const result = await saveData({ name: "test", value: 42 });
console.log("Save result:", result);
};
return <button onClick={handleClick}>Trigger Native Action</button>;
}DOM components can use any web library:
// components/syntax-highlight.tsx
"use dom";
import SyntaxHighlighter from "react-syntax-highlighter";
import { docco } from "react-syntax-highlighter/dist/esm/styles/hljs";
interface Props {
code: string;
language: string;
dom?: import("expo/dom").DOMProps;
}
export default function SyntaxHighlight({ code, language }: Props) {
return (
<SyntaxHighlighter language={language} style={docco}>
{code}
</SyntaxHighlighter>
);
}// components/chart.tsx
"use dom";
import {
LineChart,
Line,
XAxis,
YAxis,
CartesianGrid,
Tooltip,
} from "recharts";
interface Props {
data: Array<{ name: string; value: number }>;
dom: import("expo/dom").DOMProps;
}
export default function Chart({ data }: Props) {
return (
<LineChart width={400} height={300} data={data}>
<CartesianGrid strokeDasharray="3 3" />
<XAxis dataKey="name" />
<YAxis />
<Tooltip />
<Line type="monotone" dataKey="value" stroke="#8884d8" />
</LineChart>
);
}CSS imports must be in the DOM component file since they run in isolated context:
// components/styled-component.tsx
"use dom";
import "@/styles.css"; // CSS file in same directory
export default function StyledComponent({
dom,
}: {
dom: import("expo/dom").DOMProps;
}) {
return (
<div className="container">
<h1 className="title">Styled Content</h1>
</div>
);
}Or use inline styles / CSS-in-JS:
"use dom";
const styles = {
container: {
padding: 20,
backgroundColor: "#f0f0f0",
},
title: {
fontSize: 24,
color: "#333",
},
};
export default function StyledComponent({
dom,
}: {
dom: import("expo/dom").DOMProps;
}) {
return (
<div style={styles.container}>
<h1 style={styles.title}>Styled Content</h1>
</div>
);
}The expo-router <Link /> component and router API work inside DOM components:
"use dom";
import { Link, useRouter } from "expo-router";
export default function Navigation({
dom,
}: {
dom: import("expo/dom").DOMProps;
}) {
const router = useRouter();
return (
<nav>
<Link href="/about">About</Link>
<button onClick={() => router.push("/settings")}>Settings</button>
</nav>
);
}These hooks don't work directly in DOM components because they need synchronous access to native routing state:
useLocalSearchParams()useGlobalSearchParams()usePathname()useSegments()useRootNavigation()useRootNavigationState()Solution: Read these values in the native parent and pass as props:
// app/[id].tsx (native)
import { useLocalSearchParams, usePathname } from "expo-router";
import DOMComponent from "@/components/dom-component";
export default function Screen() {
const { id } = useLocalSearchParams();
const pathname = usePathname();
return <DOMComponent id={id as string} pathname={pathname} />;
}// components/dom-component.tsx
"use dom";
interface Props {
id: string;
pathname: string;
dom?: import("expo/dom").DOMProps;
}
export default function DOMComponent({ id, pathname }: Props) {
return (
<div>
<p>Current ID: {id}</p>
<p>Current Path: {pathname}</p>
</div>
);
}Check if code is running in a DOM component:
"use dom";
import { IS_DOM } from "expo/dom";
export default function Component({
dom,
}: {
dom?: import("expo/dom").DOMProps;
}) {
return <div>{IS_DOM ? "Running in DOM component" : "Running natively"}</div>;
}Prefer requiring assets instead of using the public directory:
"use dom";
// Good - bundled with the component
const logo = require("../assets/logo.png");
export default function Component({
dom,
}: {
dom: import("expo/dom").DOMProps;
}) {
return <img src={logo} alt="Logo" />;
}Import and use DOM components like regular components:
// app/index.tsx
import { View, Text } from "react-native";
import WebChart from "@/components/web-chart";
import CodeBlock from "@/components/code-block";
export default function HomeScreen() {
return (
<View style={{ flex: 1 }}>
<Text>Native content above</Text>
<WebChart data={[10, 20, 30, 40, 50]} dom={{ style: { height: 300 } }} />
<CodeBlock
code="const x = 1;"
language="javascript"
dom={{ scrollEnabled: true }}
/>
<Text>Native content below</Text>
</View>
);
}| Platform | Behavior |
|---|---|
| iOS | Rendered in WKWebView |
| Android | Rendered in WebView |
| Web | Rendered as-is (no webview wrapper) |
On web, the dom prop is ignored since no webview is needed.
© mweinbach, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in apps/mobile/.agents/skills/use-dom of mweinbach/agent-coworker.
Open the folder on GitHubat commit aab9dc6
We found 11 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 5 other GitHub owners. This page covers the copy in mweinbach/agent-coworker, which our catalogue first saw on October 7, 2026.
Use Dom next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Use Dom this skillmweinbach/agent-coworker | 156 | 5 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Screenmapaleqsio/screenmap | 243 | — | ~7.2k | Automated safety check: Pass | MIT | |
| Lovdacnlovdacn/ui | 107 | — | ~3.9k | Automated safety check: Pass | MIT | |
| ThemingCode-with-Beto/skills | 140 | — | ~2.5k | Automated safety check: Pass | None | |
| Stream React Nativeadrianhajdin/react-native-lingua | 152 | — | ~2.8k | Automated safety check: Pass | None | |
| Expo Upgradeexpo/skills | 2.7k | 9 repos | ~1.9k | Automated safety check: Pass | MIT |
aleqsio/screenmap
Generate a visual navigation map of an Expo / React Native or NativeScript app.
lovdacn/ui
Manages lovdacn (lvcn) components and projects for Expo & React Native — adding, initializing, fixing, debugging, styling, theming, and composing UI with NativeWind or Uniwind.
Code-with-Beto/skills
Scaffold a unified, cross-platform color theme system into an Expo Router app.
adrianhajdin/react-native-lingua
Create, build, and integrate Stream Chat React Native apps in React Native Community CLI and Expo.
expo/skills
Guidelines for upgrading Expo SDK versions and fixing dependency issues
tech-leads-club/agent-skills
Guides React Native and Expo work for cross-platform apps: Expo Router navigation, fast lists, Reanimated animation, platform-specific code and project structure.
mweinbach/agent-coworker
Adds AI Elements components such as conversations, messages, tool displays and prompt inputs to a Next.js project that uses shadcn/ui.
mweinbach/agent-coworker
Helps add Expo and React Native to an existing native iOS or Android app, and choose between a prebuilt AAR or XCFramework and a fully integrated build.
mweinbach/agent-coworker
Quick reference for using Bun to run TypeScript and JavaScript, install packages, bundle code, run tests and serve HTTP, with the key files and commands.
mweinbach/agent-coworker
Author and run a deterministic multi-agent workflow — a JavaScript script that fans out, pipelines, loops, and judges across many child agents.
mweinbach/agent-coworker
Audit a codebase's animation and motion, produce prioritized improvement plans, and execute selected plans when requested.
mweinbach/agent-coworker
A skill your agent uses when the user asks to view, list, inspect, add, create, edit, correct, update, or manage long-term memories for the current chat or workspace.
Categories
Use Expo DOM components to run web code in a webview on native and as-is on web. Use Dom is an agent skill from mweinbach/agent-coworker. Use Expo DOM components to run web code in a webview on native and as-is on web.
Use Dom fits situations like: tasks that involve Cross-platform mobile apps.
Run `npx skills add mweinbach/agent-coworker --skill use-dom -a claude-code`. Or copy the skill folder (apps/mobile/.agents/skills/use-dom in mweinbach/agent-coworker) into .claude/skills/use-dom in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mweinbach/agent-coworker --skill use-dom -a codex`. Or copy the skill folder (apps/mobile/.agents/skills/use-dom in mweinbach/agent-coworker) into .agents/skills/use-dom in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mweinbach/agent-coworker --skill use-dom -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/use-dom, .gemini/skills/use-dom, .github/skills/use-dom and .opencode/skills/use-dom in your project.
SKILL.md names no scripts, command-line tools or credentials: Use Dom is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Use Dom is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.4k tokens (SKILL.md is roughly 9.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Use Dom: Screenmap (aleqsio/screenmap, 243 stars), Lovdacn (lovdacn/ui, 107 stars), Theming (Code-with-Beto/skills, 140 stars) and Stream React Native (adrianhajdin/react-native-lingua, 152 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mweinbach (a GitHub user) maintains it in mweinbach/agent-coworker, which has 156 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 8, 2026.
Source: mweinbach/agent-coworker on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.