القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | regenerate-types |
| description | 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. |
http://localhost:8080/v1/graphqldocker compose up hasura (from project root)Run from the frontend-nx directory with the GraphQL URI:
cd frontend-nx && GRAPHQL_URI=http://localhost:8080/v1/graphql yarn apollo
Run codegen after:
Ensure Hasura is running:
docker compose up hasura
Clear and regenerate:
rm -rf frontend-nx/apps/edu-hub/queries/__generated__/*
cd frontend-nx && GRAPHQL_URI=http://localhost:8080/v1/graphql yarn apollo
frontend-nx/apps/edu-hub/queries/__generated__/If you're making database schema changes, ensure you also:
create-migration skillWork 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.