Imported from 54Xander/ai-forge (AGENTS.md). Install upstream with npx skills add 54Xander/ai-forge. Copyright stays with the author.

Project instructions

Start here

• Read README.md and inspect the intended files before editing. This project is now a Git repository connected to https://github.com/54Xander/ai-forge.git, following the user's explicit request to submit the website. Check Git status before changes, preserve existing history and user edits, and do not reinitialize the repository.
• This is an existing static HTML/CSS/JavaScript demo. Use the preview and validation commands in README.md; do not scaffold a framework, add global dependencies, or adopt a new harness without a scoped reason and authorization for material changes.

Content and scope

• Keep the team name 爱智造 and the existing English name AI Forge until the user decides otherwise. The rest of the interface is English.
• Preserve the original demo's blue/teal palette (#1f3a5f, #2c6e91, #1abc9c), light gray background (#f7f9fc), Segoe UI typography, and rounded white cards. The user rejected the sage/green editorial redesign; do not reintroduce it or otherwise redesign without a request.
• Use five independent pages with the exact navigation labels Home, Research, Team, Our work, Contact. Keep shared navigation consistent and mark the current page. Do not combine these into one scrolling page.
• Keep Home in a desktop left/right layout with equal-width columns: team introduction and research tags on the left, a single-image carousel on the right. Stack these on smaller screens. Show images edge-to-edge without an outer border, shadow, padding, or an inset dashed placeholder frame. Keep each image's natural aspect ratio, without cropping or adding letterboxing; the current local placeholder is 4:3. Use compact manual previous/next buttons and slide dots in a centered row close to the image, without autoplay. Do not show a heading above the carousel; place one brief caption over a compact translucent strip at the bottom of each image, with minimal padding. Use local image placeholders with editable captions until real images are supplied. Do not reintroduce team-count cards, their explanatory note, or the redundant Meet the team / Explore our work buttons; the main navigation provides those destinations.
• Keep Research in a single column at all screen widths, with one full-width card per row and natural height for longer descriptions. Place each title to the right of its number in the same header row, with the description spanning the full width below; long titles wrap within the right-hand column.
• Show all Team members in consecutive Doctoral Researchers, Master's Students, and Undergraduates sections, each with a small heading and divider. Use two wider, compact cards per desktop row and one card per mobile row, with education and research-area tags side by side. Keep the original avatar area and initials sizing; make cards more compact through layout rather than shrinking the avatar. Present each member's name, academic role, description, education, and research-area tags directly in the card without truncating content. Use small, multicolored tags for research focus, cycling through soft green, purple, amber, and blue backgrounds with darker matching text. Keep this color treatment scoped to member tags, without repeating focus as prose or showing a duplicate tag row. Do not display member index badges or Team role fields. Do not add View profile buttons, separate profile pages, detail dialogs, member filters, or pagination. Preserve the visible To be added labels and distinguish illustrative focus areas from confirmed details.
• Show every Our work entry in an individual card with bibliographic content (title, authors, venue, year, volume/issue/pages, and direct DOI/project links), grouped by year from newest to oldest. Do not add Code links, numbered references, filters, search, pagination, or Details dialogs. Put entries without a confirmed year at the end; preserve sample labels and never invent bibliographic metadata.
• Keep Contact as the collaboration introduction and a mailto email link, without a copy-email button or clipboard interaction.
• Target GitHub Pages in 54Xander/ai-forge as explicitly requested, using main and the repository root as the publishing source. Keep index.html, .nojekyll, and relative asset/page paths compatible with /ai-forge/. Do not register/deploy a separate Sites-hosted site or change the target repository without a request. Report successful source submission separately from actual Pages deployment; a push alone does not confirm the website is live.
• The ten-person composition (2 doctoral, 4 master's, 4 undergraduate) is illustrative. Preserve the visible placeholder and sample labels until the user supplies confirmed data.
• Preserve the original member profile, research directions, DistRMI/RSID entries, and contact address. Do not invent names, academic affiliations, publication details, achievements, or contact information.
• Routine design and implementation choices within the user's request can proceed. Humans decide scope, acceptance, deployment, and important architectural/resource changes. Preserve unrelated user edits.
• Keep editable member/work content in assets/team-data.js, use text insertion for data, and avoid remote fonts, external placeholder-image services, and runtime dependencies. Home image sources and captions are editable directly in index.html.

Validation and delivery

• Run python3 scripts/check-site.py and both documented JavaScript syntax checks after relevant changes. Check actual browser behavior for changed interactions, independent page navigation, desktop/mobile layout, keyboard navigation, local resources, and runtime errors. Check repository-prefixed paths when deployment routes change.
• Keep README instructions in sync with data fields, commands, and behavior. Add checks only when justified by changed behavior or validation scope.
• Report the result, changed files, applicable harness rules, verification results, Git state, and remaining factual inputs. Do not claim sample content is verified team output or claim publishing occurred.