메뉴
Build the Lessley React frontend for production. Use when: preparing a deployment, checking that TypeScript compiles, or verifying the production bundle before shipping.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
Run TypeScript type checking on the Lessley React frontend without emitting output. Use when: checking for type errors, validating refactors, or debugging import issues.
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.
| name | react-build |
| description | Build the Lessley React frontend for production. Use when: preparing a deployment, checking that TypeScript compiles, or verifying the production bundle before shipping. |
| argument-hint | react-build to compile and bundle the frontend |
| user-invocable | true |
Build the Lessley frontend for production deployment.
cd lessley-frontend && npm run build
tsc -b)dist/Production files are written to lessley-frontend/dist/:
index.html — entry pointassets/*.js — JavaScript chunks (one per lazy route + shared)assets/*.css — compiled Tailwind CSS| Problem | Fix |
|---|---|
| TypeScript errors | Run npm run typecheck for detailed errors |
| Missing dependencies | Run npm install first |
| Build warnings about SignalR | Safe to ignore — upstream /*#__PURE__*/ annotation placement |