القائمة
Run TypeScript type checking on the Lessley React frontend without emitting output. Use when: checking for type errors, validating refactors, or debugging import issues.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | react-typecheck |
| description | Run TypeScript type checking on the Lessley React frontend without emitting output. Use when: checking for type errors, validating refactors, or debugging import issues. |
| argument-hint | react-typecheck to check TypeScript types |
| user-invocable | true |
Run the TypeScript compiler in check-only mode (no output files).
cd lessley-frontend && npm run typecheck
@/* → ./src/*noUnusedLocals, noUnusedParameters, noFallthroughCasesInSwitchenum, no constructor parameter properties)| Error | Fix |
|---|---|
TS1294: erasableSyntaxOnly | Use status: number as a field, not public status: number in constructor |
Cannot find module '@/...' | Check that the file exists under src/ and the path alias is correct |
| Unused variable | Prefix with _ or remove if genuinely unused |
Build the Lessley React frontend for production. Use when: preparing a deployment, checking that TypeScript compiles, or verifying the production bundle before shipping.
Start the Vite dev server for the Lessley React frontend. Use when: developing UI features, testing visual changes, debugging frontend behavior, or verifying that components render correctly.
Guide for creating new features in the Lessley React frontend. Use when: adding a new page, feature module, or API integration following the established architecture patterns.
Run ESLint on the Lessley React frontend. Use when: checking code quality, enforcing consistent patterns, or before committing frontend changes.
Run Vitest tests for the Lessley React frontend. Use when: verifying component behavior, testing hooks, checking auth store logic, validating route guards, or running the test suite before committing.
Explains and enforces the layered architecture used in Lessley services. Use when: reviewing or writing controllers, services, or repositories; deciding where new logic should live; or ensuring a controller does not contain business logic.