event-hub

Enforce the current web CSS architecture and warm editorial styling conventions in this repository. Use when creating or changing styles, theming, design tokens, component visuals, layout classes, or page atmosphere in web/src/css.

Build, review, and maintain the Academic Events web app (Express SSR shell plus bundled vanilla JavaScript UI). Use when changing or reviewing the home, login, week, or dashboard pages, client auth and event flows, frontend tests, browser validation, styles, webpack behavior, static serving, or API integration from the web layer.

Build and maintain REST API endpoints for authentication, moderation, notifications, and academic events in `api/`. Use when adding or modifying routes, request validation, auth flows, response contracts, background side effects, model behavior, or MySQL-backed persistence.

Add focused JSDoc and comments to touched reusable Event Hub code while avoiding noisy narration of obvious statements.

Keep Event Hub documentation, agent guidance, prompts, skills, comments, and validation instructions synchronized with the real implementation after code, route, config, CSS, build, Compose, or test changes.

Deliver feature work, frontend test design, and refactors in this Academic Events repository with tests or explicit validation. Use when changing behavior, adding features, fixing regressions, updating tests, reviewing missing coverage, validating browser interactions, or documenting testing gaps across api/ and web/.

Deeply review the Academic Events API in `api/` for logic bugs, contract mismatches, authorization gaps, state-transition defects, background-task failures, time/date bugs, and missing regression coverage. Use when auditing API code for bugs or pairing bug-finding with deterministic Jest test creation and reruns.

Diagnose runtime and integration issues across API and Web services in this Academic Events project. Use when services fail to boot, auth or event flows break, API responses are unexpected, frontend rendering is incorrect, or Docker development behavior is unstable.

Configure and run the Academic Events API and Web services with Docker Compose in development mode. Use when starting the stack, rebuilding images, inspecting container logs, or troubleshooting compose networking, ports, and environment propagation.

Work with domain models for users and events, including password hashing, defaults, serialization, and MySQL-backed query helpers. Use when changing model behavior, filtering semantics, or fields that affect API contracts.

Deeply review the Academic Events frontend in `web/` for SSR and template contract mismatches, interaction regressions, query-state bugs, auth and redirect defects, date/time issues, accessibility gaps, and missing regression coverage. Use when auditing frontend code, reviewing UI bugs, or pairing findings with deterministic `web/tests` updates and browser validation.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Agent's capabilities with specialized knowledge, workflows, or tool integrations.

Auto-detect when generated code, prompts, or repeated agent behavior indicate a reusable workflow or durable rule. Update README, SKILL.md files, prompts, Copilot instructions, or durable coding conventions to reflect those lessons. Auto-invoke when user or agent text contains the exact phrases: "update docs", "update the skill", "fix Copilot instructions", "create new skill", "update skill", "document recurring pattern", "capture reusable workflow", or "this should be a skill".