// Start, stop, and manage the local Jekyll development server for PlanExe-web. Use this skill when doing web development on the site — editing CSS, layouts, index.md, examples, or any site content that needs a local preview.
Replace or improve an existing example plan on the PlanExe-web Jekyll site (planexe.org) while preserving its name, images, title, and description. Use this skill whenever the user wants to replace, improve, or update an existing plan's zip and report. Trigger on mentions of "replace plan", "improve plan", "update plan", "plan needs updating", "replace the report", or any reference to updating an existing plan on the planexe.org examples gallery.
Add a new example plan to the PlanExe-web Jekyll site (planexe.org). Use this skill whenever the user wants to add a new example plan to the examples gallery. Trigger on mentions of "add plan", "new example", "new plan", "examples.yml", "plan zip", "report HTML", "process the input", "process input", or any reference to adding to the planexe.org examples gallery — even if the user just says something like "I have a new plan to add" or "process the input".
| name | jekyll |
| description | Start, stop, and manage the local Jekyll development server for PlanExe-web. Use this skill when doing web development on the site — editing CSS, layouts, index.md, examples, or any site content that needs a local preview. |
Ruby 3.3 is required. The PATH must include the Ruby 3.3 bin directory.
Run Jekyll in a background Bash process so it stays alive for the duration of the session:
PATH="/opt/homebrew/opt/ruby@3.3/bin:$PATH" LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 bundle exec jekyll serve --port 4000
Use run_in_background: true with the Bash tool. This keeps the server running while you continue working.
After starting, wait a few seconds then verify it's up:
curl -s -o /dev/null -w "%{http_code}" http://localhost:4000/
The user browses to http://localhost:4000/ to preview.
Jekyll has auto-regeneration enabled by default. When you edit files (index.md, CSS, _data/examples.yml, layouts, etc.), Jekyll detects the change and rebuilds _site/ automatically. The user just refreshes their browser — do NOT restart the server after editing files.
Only stop the server when the user explicitly asks, or when the session is ending. Kill it with:
pkill -f "jekyll serve"
upsert_plan/start_jekyll.py or upsert_plan/stop_jekyll.py for web development. Those scripts are for plan management workflows only.--port 4001.