eduhub

Work with Pencil .pen design files via the Pencil MCP (batch_design, variables, guidelines). Use when creating or editing .pen files, exploring UI layouts in Pencil, generating wireframes for EduHub, or when the user mentions Pencil, .pen, or the highagency Pencil extension.

Inspect UI via cursor-ide-browser (Cursor Browser tab); fall back to user-playwright if internal browser MCP is unavailable. Use for @Browser, open tab, layout checks, localhost — or when user explicitly asks for Playwright.

Use this skill to generate well-branded interfaces and assets for EduHub by opencampus.sh, either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.

Draft and review EduHub commit messages using the repository's conventional-commit and semantic-release workflow. Use when writing commit messages, choosing feat vs fix vs chore, deciding whether a body is needed, preparing merge commit messages, or explaining release impact.

Create a GitHub issue on eduhub-org/eduhub and add it to the "EduHub Development" project board with a chosen Status (Backlog / Todo / In Progress / Done). Use when the user asks to "create an issue", "file a ticket", "add to backlog", or otherwise wants a new issue tracked on the project board.

Create and review EduHub Hasura schema migrations. Use when adding tables, columns, constraints, relationships, or other database schema changes, and when coordinating the required metadata, query, type-generation, and function follow-up steps.

Apply EduHub frontend conventions for components, layout, translations, TableGrid usage, and responsive behavior. Use when creating or refactoring frontend components or pages in the Next.js app.

Apply EduHub GraphQL, Hasura, and schema-change conventions. Use when editing queries, mutations, fragments, metadata, role-based GraphQL hooks, or backend changes that affect frontend GraphQL usage.

Backport EduHub production hotfixes into develop and optionally staging. Use when a fix landed directly on production and must be cherry-picked into the normal promotion branches.

Run and interpret EduHub frontend linting. Use when checking code style, running ESLint, fixing lint errors, or matching the repository's frontend lint behavior from CI.

Regenerate EduHub GraphQL TypeScript types. Use after GraphQL schema changes, query or mutation edits, metadata changes, or when updating generated query types from Hasura.

Guide EduHub release preparation and branch-promotion work. Use when preparing release PRs, promoting changes across develop, staging, and production, drafting merge commit messages for release branches, or explaining how semantic-release behaves in this repository.

Run and interpret EduHub tests. Use when executing the Jest suite, running a subset of frontend tests, checking coverage, or verifying changes before merge.

Apply EduHub authentication, authorization, and security conventions. Use when working on Keycloak, NextAuth, JWT/session handling, role checks, Hasura permissions, or security-sensitive frontend and backend behavior.

Start and inspect the EduHub local development environment. Use when bringing up the Docker stack, checking service URLs and ports, tailing logs, or resetting the local dev environment.

Write user-facing EduHub release summaries in plain language. Use when turning release notes or commit history into Slack posts, release announcements, newsletters, or other non-technical update summaries.

Run ESLint on the EduHub frontend. Use when the user asks to lint code, check code style, fix lint errors, or run eslint.

Regenerate TypeScript types from GraphQL schema using Apollo codegen. Use when the user asks to update types, regenerate types, run codegen, after GraphQL schema changes, after database migrations, or after modifying Hasura metadata.

Run Jest tests for EduHub. Use when the user asks to run tests, execute test suite, check test coverage, or verify code changes.

Start EduHub development environment with Docker. Use when the user asks to start dev server, run locally, start development, or set up the environment.

Create Hasura database migrations for EduHub. Use when adding tables, columns, constraints, or any database schema changes. Also use after schema changes to ensure migrations are created.

Cherry-pick hotfix commits from production to develop. Use when a hotfix was pushed directly to production and needs to be backported to develop branch.