Developing Wayfinder Paths

When to use

Use this skill when you are:

• Creating a new Path (bundle) to share a strategy/script/skill/contract UI
• Creating a compiled strategy-pipeline path with fixed phases, artifacts, and evals
• Adding a static applet UI to a path
• Publishing a new path version
• Emitting signals/receipts to make a path page feel “alive”
• Adding live data fetching or interactive controls to a path applet
• Defining canonical path skill source in wfpath.yaml, policy/default.yaml, pipeline/graph.yaml, skill/instructions.md, and skill/agents/
• Generating host-specific skill exports for Claude Code and OpenCode, with Codex/OpenClaw/portable thin exports as secondary targets

How to use

• To scaffold a normal path, start with poetry run wayfinder path init <slug> --dir <base-dir>.
• To scaffold a compiled strategy pipeline, use poetry run wayfinder path init <slug> --dir <base-dir> --template pipeline --archetype <conditional-router|hedge-finder|spread-radar>.
• path init uses --dir, while the later path commands (fmt, doctor, render-skill, build, publish) use --path.
• For pipeline paths, run poetry run wayfinder path eval --path . before publishing or exporting skills.
• rules/manifest.md - wfpath.yaml schema + required fields for MVP
• rules/applet.md - Static applet requirements + build output expectations
• rules/build-and-publish.md - wayfinder path build/publish + required config/env vars
• rules/signals.md - wayfinder path signal emit patterns
• rules/security.md - MVP hosting constraints and safe defaults
• rules/path-skills.md - Defining the skill layer, agent layer, and host-specific exports