Agent Instructions

Project Context

This repository is a personal academic website built with Jekyll and hosted on GitHub Pages.
The site uses the remote theme BDHU/minimalist with local overrides in _includes/, _layouts/, assets/css/custom-layout.css, and assets/js/theme-toggle.js.
Generated output lives in _site/; do not edit or commit generated files.
Deployment happens from the main branch through .github/workflows/jekyll.yml.
The Pages workflow uses Ruby 3.2, Bundler cache, JEKYLL_ENV=production, and bundle exec jekyll build --baseurl "$".
.github/workflows/weekly_cleanup.yml runs a Jules maintenance workflow every Monday at 02:00 UTC and can also be triggered manually.

Install dependencies with bundle install.
Build the site with bundle exec jekyll build.
Match the GitHub Pages production build locally with JEKYLL_ENV=production bundle exec jekyll build --baseurl "".
Run locally with bundle exec jekyll serve.
If file watching fails, use bundle exec jekyll serve --no-watch.
Check whitespace issues with git diff --check.

Keep changes small and focused. Avoid broad rewrites of theme overrides unless the task requires them.
Prefer editing local includes, layouts, CSS, or JavaScript over modifying generated output.
Preserve the existing Jekyll/Liquid structure and GitHub Pages compatibility.
Keep site metadata centralized in _config.yml when possible, especially social/profile links.
Use semantic HTML and accessible labels for interactive elements.
Keep custom styling in assets/css/custom-layout.css unless an existing include is clearly the right place.
Keep JavaScript minimal and dependency-free unless a task explicitly requires a library.
Do not commit local build artifacts, caches, vendor/, _site/, or *:Zone.Identifier files.

For content-only Markdown changes, inspect the rendered page when the change affects visible content.
For layout, CSS, Liquid, JavaScript, or config changes, run:
```
bundle exec jekyll build
git diff --check
```
Restart bundle exec jekyll serve after changing _config.yml; Jekyll does not reload that file automatically.
When changing external links, metadata, icons, or structured data, verify both the visible page and generated HTML if possible.
For layout, CSS, image, or interaction changes, verify the rendered site across representative screen sizes and devices, including mobile, tablet, and desktop widths. Check portrait and landscape orientations when relevant, resize the viewport to catch breakpoint issues, and ensure content remains readable, navigation remains usable, images scale correctly, and no elements overlap or overflow horizontally.

The change is limited to files relevant to the task.
The site builds successfully when required by the change type.
No whitespace or formatting issues are introduced.
The rendered result is checked when the change affects visible content or layout.
No generated files, caches, or unrelated files are modified.