Menü
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.
| name | create-migration |
| description | 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. |
Use this skill for any EduHub schema change.
Do not consider a schema-change task complete until all relevant steps are done:
backend/migrations/default/up.sql and down.sqlfunctions/ for affected table or column usage and update function logic if neededUse:
backend/migrations/default/{timestamp}_{action}_{description}/
Examples:
backend/migrations/default/1753957404053_add_column_status_to_mail_log/
backend/migrations/default/1753957404053_create_table_AttendanceAudit/
up.sql should do the real changedown.sql should reverse it cleanlyAfter schema changes:
backend/metadata/ when permissions, tables, or relationships changedfrontend-nx/apps/edu-hub/queries/ if field shape changedregenerate-types skill for codegenThis repo has serverless consumers under functions/.
For every changed table or column:
functions/ for the old and new namesfunctions/callNodeFunction/, functions/sendMail/, and related modulesSuggested search:
rg "<table_or_column_name>" functions/
created_at, updated_at{tableName}IdWhen asked to make a schema change, carry the work through this checklist and state clearly which of the six required follow-up steps were completed.
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.
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.
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.
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.