菜单
Run ONE pass of the IT-Journey frontend canary — crawl it-journey.dev for UI/UX/a11y/theme defects, classify theme-vs-content, dedup, and file the theme issues upstream to bamr87/zer0-mistakes. Use when asked to test the it-journey.dev frontend, scout for theme bugs, run the frontend canary, or file theme issues upstream. Drives the theme-scout agent.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run one incremental pass of the IT-Journey content-improvement loop. Use when asked to curate/improve content, run the daily CMS loop, work the .cms worklist, fix frontmatter/SEO/freshness across pages, or group content improvements into a PR.
Run one agentic, on-brand content-improvement pass for a single IT-Journey collection and open one gated PR. The Lane B (substantive) executor that wires the cms-curator loop to the brand-voice system. Use when asked to "improve a collection", "run the content factory", or driven by content-factory.yml in CI.
Consume ONE walkthrough's verified evidence and apply the smallest content-only edits that fix its VERIFIED issues, under a deterministic keep/revert gate. The fix-lane inverse of quest-walkthrough — the walker plays a slice and witnesses where it breaks; this skill repairs exactly what it witnessed, proving each edit helped with a deterministic signal (never the model's own grade). Use when asked to "fix a walked quest", run the quest fix lane, or driven by the fix arm of the quest-perfection loop. Writes only quest content; never branches, commits, or merges.
Forge a "quest-forge proposal" GitHub issue into a complete, validated epic-quest campaign in pages/_quests/codex/ and open one gated PR. Use when asked to "forge a quest from an issue", turn an epic-quest proposal into content, or driven by quest-forge.yml in CI. Composes the deterministic collector (forge_issue.py) + quest.instructions + brand-voice.
PostHog integration for any Ruby application using the Ruby SDK
Load IT-Journey brand context (values, voice, style, section guide) before drafting or editing a post or muse. Use when writing a new article, writing a short-form devops-news muse, rewriting for voice/tone, or checking that content matches a section's brand profile.
| name | theme-scout |
| description | Run ONE pass of the IT-Journey frontend canary — crawl it-journey.dev for UI/UX/a11y/theme defects, classify theme-vs-content, dedup, and file the theme issues upstream to bamr87/zer0-mistakes. Use when asked to test the it-journey.dev frontend, scout for theme bugs, run the frontend canary, or file theme issues upstream. Drives the theme-scout agent. |
it-journey.dev runs the bamr87/zer0-mistakes theme via remote_theme, so it is a live canary for the theme. One pass: test the frontend → classify findings → dedup → file the theme ones upstream. Deterministic spine, AI judgment at the filing step. Runs identically locally (/loop / make) and in CI (theme-scout.yml).
.frontend/config.yml — routes, viewports, the theme-vs-content classification
rules, the upstream repo, and the per-run cap..frontend/README.md — the contract and how to run it.BASE_URL=https://it-journey.dev node scripts/frontend/crawl.mjs
The crawler drives a real browser over every configured route at mobile + desktop and writes .frontend/findings.jsonl: page/HTTP errors (incl. the theme-injected link 404s), console errors, mobile horizontal overflow, missing alt text, and axe-core WCAG violations. It is read-only — it never logs in or submits anything.
python3 scripts/frontend/triage_findings.py
Groups findings by signature, decides which are theme (site-wide / theme- injected) vs content (one page), dedups against existing upstream issues, and writes .frontend/upstream-candidates.json (capped).
The theme-scout agent reads the candidates, makes the final theme-vs-content call, searches upstream once more to avoid paraphrased duplicates, and files each genuine theme bug with gh issue create --repo bamr87/zer0-mistakes (title + repro/evidence + bug + area:* labels). Filing upstream needs a PAT with issues:write on the theme repo (the workflow provides it as THEME_REPO_TOKEN).
dedup.max_new_issues_per_run).State what you filed (URLs), what you skipped as duplicates, and what you judged content (for it-journey to handle). Never imply you found everything — this is one bounded canary pass over a sample of routes.