菜单
Use when reviewing, critiquing, or redesigning the visual design of this Jekyll website. Applies to homepage hierarchy, typography, color system, imagery, navigation, page composition, consistency across sections/pages, and recommending or implementing a stronger visual direction.
| name | site-design-review |
| description | Use when reviewing, critiquing, or redesigning the visual design of this Jekyll website. Applies to homepage hierarchy, typography, color system, imagery, navigation, page composition, consistency across sections/pages, and recommending or implementing a stronger visual direction. |
Use this skill for visual design work in this repository.
This skill is for design critique and redesign guidance, not just functional site maintenance.
Read the relevant files first:
_sass/jekyll-theme-prologue.scss_layouts/_includes/content/_sections/content/pages/content/index.mdIf screenshots are available, use them as the primary evaluation surface.
Evaluate the site against:
When reviewing:
When implementing:
_sass/jekyll-theme-prologue.scss.content/, but visual consistency should be driven from shared layout and CSS layers._internal/ and .codex/ must never become part of the site output.Use when drafting, revising, or evaluating blog posts for this repository's ML-Affairs site. Applies to new post ideas, post outlines, editorial feedback, title refinement, and rewriting blog content to match the repo's stored content strategy and writing style.
Use when preparing to publish or review changes for this repository's website or blog. Applies to pre-publish QA, content release checks, accidental page exposure checks, metadata review, and final verification before merging or deploying site changes.
Use when updating the LaTeX CV in this repository, compiling it, publishing the latest PDF, or creating a job-targeted CV variant from a job description. Applies to edits under cv/latex, tailoring the summary and bullets for a role, generating role-specific variants, and keeping assets/pdfs/cv.pdf aligned only when explicitly requested.
Use when committing or pushing changes in this repository. Applies to staging review, semantic commit messages, hook-aware commit workflow, and safe direct pushes when the user explicitly wants them.
Use when maintaining or modifying the structure, templates, styling, navigation, configuration, analytics, or content publishing behavior of this Jekyll website. Applies to layout fixes, page additions, homepage section changes, internal-doc exposure issues, and general repository hygiene for the site.