Arrow JS
Developmentarrow-jsArrow JS is an Agent Skill for development published in the standardagents/arrow-js repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when working on Arrow apps, templates, reactivity, components, SSR, hydration, routing, or Vite-based Arrow projects.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/standardagents/arrow-js/blob/HEAD/packages/skill/resources/skill/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/arrow-js, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Arrow
Use this skill when the project uses Arrow packages such as @arrow-js/core, @arrow-js/framework, @arrow-js/ssr, @arrow-js/hydrate, or the Vite scaffold generated by create-arrow-js.
Quick workflow
- Confirm whether the task is core-only Arrow or full-framework Arrow.
- Read the smallest relevant reference:
- Getting started / scaffold shape:
references/getting-started.md - API surface and package split:
references/api.md - Common patterns and examples:
references/examples.md
- Getting started / scaffold shape:
- Prefer idiomatic Arrow:
reactive()for statehtmltagged templates for DOMcomponent()for reusable view unitswatch()only for side effects
- In scaffolded SSR apps, treat
routeToPage(url)as the route entry point. - If SSR or hydration is involved, preserve payload, metadata, and boundary behavior.
Rules of thumb
- Expression slots are static by default. They only stay live when passed as callable functions.
- Pass reactive state directly as component props unless narrowing is clearly needed.
- Compose views with nested templates and component calls instead of imperative DOM work.
- Keep no-build Arrow honest. Avoid introducing benchmark-only patterns or unnecessary compiler assumptions.
- In framework apps, remember the package split:
@arrow-js/core: reactive state, templates, components, watch@arrow-js/framework: render, async component runtime, boundary@arrow-js/ssr:renderToString,serializePayload@arrow-js/hydrate:hydrate,readPayload
References
references/getting-started.mdreferences/api.mdreferences/examples.md