Menu
Run ESLint on the EduHub frontend. Use when the user asks to lint code, check code style, fix lint errors, or run eslint.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | lint-project |
| description | Run ESLint on the EduHub frontend. Use when the user asks to lint code, check code style, fix lint errors, or run eslint. |
# From frontend-nx directory
cd frontend-nx
# Lint edu-hub app (matches GitHub Action CI)
yarn lint
# Lint with auto-fix
yarn lint --fix
The GitHub Action (.github/workflows/frontend-code-checks.yml) uses:
yarn lintyarn install --immutable before lintingTo match CI results locally:
yarn lint (as shown in commands above)yarn install --immutable if results differMost formatting issues can be auto-fixed:
yarn lint --fix
eslint apps/edu-hub/components/MyComponent.tsx
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.