ryanallen

Stage and commit at repo root and in nested work when work/.git exists; push only the nested work repo (Apply-Work), never the Apply root. Run only when user explicitly says "save", "commit", or /save. Never save otherwise. In Claude Code and Cursor, /skills lists all.

Research all existing work/ (READMEs, refs) and output findings for the Documentor to merge into the current job's README. Use after the job post is documented in Apply to a job flow. Trigger: "research work", "existing work", /research-work.

Align resume and cover letter to the job post (keywords, reverse chronology, action verbs, quantifiable results, experience cutoff). Before building, ask user for any more info (e.g. people at company). Output: resume-alignment.md, cover-letter.md, and connection-message.md for Documentor. Trigger: "resume alignment", "align resume", /resume-alignment.

Take research output and produce structured, enhanced markdown documentation with mermaid diagrams. Use when user says "write up", "document", or /document-findings. In Claude Code and Cursor, /skills lists all.

Gather from a job post (URL, paste, or file) and follow links up to 5 levels deep. Use when user says "learn about this", "look at this", or /learn. In Claude Code and Cursor, /skills lists all.

Find hiring/recruiting contacts from the job post and LinkedIn, document them with links and tastes, and draft a LinkedIn connection message. Use in Apply flow after job is documented. Trigger: "recruiting contacts", "hiring people", "connection message", or when user provides recruiter LinkedIn URLs.

After step 6 in Apply to a job, validate the README and resume against all rules. On failure, Strategist diagnoses fix and Documentor applies; repeat until pass. Trigger: "validate", "validation", /validate-application.

Sync from upstream remote's main branch and push to origin's main branch. Use when user says "sync", "pull", or /sync-upstream. In Claude Code and Cursor, /skills lists all.

Commit and push releases. Always runs the sync-docs skill first to keep the docs truthful, then proceeds. App (Rust) changes bump the version, tag, and trigger CI builds; site-only changes (README/index.html/site/imgs) just push — no version bump. Always cleans up GitHub Pages deployments to keep only the newest. Never co-authors commits. Use only when user instructs git operations like "bump and push", "release version X", or "release the site". Use when user says bump, release, push with tag, commit and push.

Update the docs under docs/ (and the /docs site nav) so they match the current app. Reviews recent app/feature changes and edits the right doc page(s), keeping them renderable by the leaftext web renderer, then regenerates the SEO/AIO/LLM discovery files (robots.txt, sitemap.xml, sitemap-md.txt, llms.txt, llms-full.txt) so search and AI crawlers stay current. Run it before a release or whenever app behavior changes. Never touches git. Use when the user says "sync the docs", "update the docs", "bundle the docs", "refresh documentation", "update the sitemap/llms.txt", or "make the docs match the code".