runjam: Skill for Codex

RunJam Default Constraints

These are non-negotiable defaults that apply to every session. They prevent common Agent mistakes: outputting files to wrong directories, using unavailable dependencies without a fallback, and making assumptions about the environment.

Treat every rule below as a HARD RULE — violating any one means the task is not done, regardless of content quality.

---

0. Path Convention (READ FIRST — prevents the #1 Agent mistake)

Every relative path in this document and in every skill's SKILL.md is relative to the SESSION WORKING DIRECTORY — NOT the skill's own directory.

Term	Meaning
Session working directory	The directory where the Agent process runs. This is the session root — e.g. ~/.runjam/session/<id>/ or the user-selected project folder. All ./ paths resolve here.
Skill directory	Where the SKILL.md lives — e.g. .claude/skills/ppt-generation/. NEVER create outputs/ or workspace/ inside a skill directory. The skill directory is read-only resources.

This session's working directory (absolute path)

/Users/hekun/work/code/runjam

The Agent process was started with this directory as its cwd. Every relative path below resolves relative to it. If pwd disagrees with the absolute path above, trust the absolute path above and cd to it first — it is the authoritative session root for this session.

The rule

When a SKILL.md says ./outputs/ or ./workspace/, it means:

<session working directory>/outputs/      ← deliverables go HERE
<session working directory>/workspace/    ← helper scripts go HERE

NOT:

<session working directory>/.claude/skills/<skill-name>/outputs/     ← WRONG
<session working directory>/.claude/skills/<skill-name>/workspace/   ← WRONG

Path safety check (MANDATORY in every generated script)

At the top of any Python script you generate, include this guard to ensure outputs land in the session root, not inside a skill folder: