How do I install the Framejs Origins skill?

Run npx skillmds@latest add metapages/framejs-origins in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Framejs Origins safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Framejs Origins?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Framejs Origins free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Framejs Origins?

metapages (@metapages) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Framejs Origins by metapages — Agent Skill

Name: Framejs Origins
Author: metapages

Framejs Origins

Maps the framejs.io / framejs.app origin split between this repo and its sibling framejs-nhost repo, plus each one's local dev address. Load whenever working with cross-app URLs, FRAMEJS_APP_ORIGIN/FRAMEJS_IO_ORIGIN env vars, or debugging requests between the rendering runtime and the account layer.

metapages Updated Sep 22, 2026

File contents

framejs.io / framejs.app origin map

This repo (metaframe-js) serves framejs.io — the public rendering runtime (uploads, screenshots, the metaframe that actually executes user code). Docker Compose + Traefik stack (worker/).

Its sibling, framejs-nhost, at /Users/dion/dev/git/metapages/framejs-nhost, serves framejs.app — the account layer: auth, frame storage, Hasura/nhost backend (api/) + Deno Fresh worker (frontend/worker/).

App	Repo (this machine)	Production	Local dev
framejs.io	`metaframe-js` (here)	`https://framejs.io`	`https://framejs-io.localhost:4470`
framejs.app	`framejs-nhost` (`.../framejs-nhost`)	`https://framejs.app`	`https://framejs-app.localhost:5173`

Source of truth, don't hardcode: local ports/hosts can drift from the table above. Check this repo's .env (FRAMEJS_APP_ORIGIN) for what it currently points at for framejs.app, and the sibling repo's frontend/worker/.env (FRAMEJS_IO_ORIGIN) for what it points at here. Both vars are read live by the framejs Agent Skill helper (worker/static/skill/framejs/scripts/framejs.mjs) — see worker/static/skill/README.md for the canonical table and the skill-dev workflow that consumes it.

Run both stacks locally:

framejs.io (here): just dev → https://framejs-io.localhost:4470
framejs.app (sibling): cd .../framejs-nhost/api && just dev (nhost stack), then cd frontend/worker && just dev → https://framejs-app.localhost:5173

Both bind dedicated *.localhost hosts (never bare localhost) over HTTPS via mkcert, so the two apps' cookies/sessions don't collide. If a host doesn't resolve, see that repo's _hostcheck justfile recipe.

For the mirror of this file, see framejs-nhost/.claude/skills/framejs-origins/SKILL.md.

---name: framejs-originsdescription: Maps the framejs.io / framejs.app origin split between this repo and its sibling framejs-nhost repo, plus each one's local dev address. Load whenever working with cross-app URLs, FRAMEJS_APP_ORIGIN/FRAMEJS_IO_ORIGIN env vars, or debugging requests between the rendering runtime and the account layer.---# framejs.io / framejs.app origin mapThis repo (`metaframe-js`) serves **framejs.io** — the public renderingruntime (uploads, screenshots, the metaframe that actually executes usercode). Docker Compose + Traefik stack (`worker/`).Its sibling, `framejs-nhost`, at`/Users/dion/dev/git/metapages/framejs-nhost`, serves **framejs.app** — theaccount layer: auth, frame storage, Hasura/nhost backend (`api/`) + Deno Freshworker (`frontend/worker/`).| App | Repo (this machine) | Production | Local dev || ----------- | ------------------------------------------------- | ---------------------- | ------------------------------------- || framejs.io | `metaframe-js` (here) | `https://framejs.io` | `https://framejs-io.localhost:4470` || framejs.app | `framejs-nhost` (`.../framejs-nhost`) | `https://framejs.app` | `https://framejs-app.localhost:5173` |**Source of truth, don't hardcode:** local ports/hosts can drift from the tableabove. Check this repo's `.env` (`FRAMEJS_APP_ORIGIN`) for what it currentlypoints at for framejs.app, and the sibling repo's `frontend/worker/.env`(`FRAMEJS_IO_ORIGIN`) for what it points at here. Both vars are read live bythe `framejs` Agent Skill helper(`worker/static/skill/framejs/scripts/framejs.mjs`) — see`worker/static/skill/README.md` for the canonical table and the skill-devworkflow that consumes it.Run both stacks locally:- framejs.io (here): `just dev` → `https://framejs-io.localhost:4470`- framejs.app (sibling): `cd .../framejs-nhost/api && just dev` (nhost stack), then `cd frontend/worker && just dev` → `https://framejs-app.localhost:5173`Both bind dedicated `*.localhost` hosts (never bare `localhost`) over HTTPS viamkcert, so the two apps' cookies/sessions don't collide. If a host doesn'tresolve, see that repo's `_hostcheck` justfile recipe.For the mirror of this file, see`framejs-nhost/.claude/skills/framejs-origins/SKILL.md`.

Frequently asked questions