Skip to main content

nexent-frontend

Use when implementing, debugging, or reviewing Nexent frontend pages, React components, hooks, API services, TypeScript types, styling, or localization under frontend/. Includes UI requests without file paths. Skip backend-only work, Python tests, and documentation-only changes with no frontend behavior.

소스 정보

저장소
ModelEngine-Group/nexent
최근 소스 활동
2026년 9월 14일 13:32
감지된 SKILL.md 언어
영어
스타
5,917
포크
738

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
7 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
nexent-frontend
description
Use when implementing, debugging, or reviewing Nexent frontend pages, React components, hooks, API services, TypeScript types, styling, or localization under frontend/. Includes UI requests without file paths. Skip backend-only work, Python tests, and documentation-only changes with no frontend behavior.
# Nexent frontend changes Repository paths below are relative to the root; reference links resolve from this skill. 1. Read [architecture](references/architecture.md), the affected feature, and `frontend/package.json` before choosing APIs or dependencies. 2. Load relevant detailed rules only. | Work | Reference | | --- | --- | | Route entries, layouts, loading UI, localization | [Pages](references/pages.md) | | Components, visual layout, forms, modals, icons, user-visible copy | [Components and UI](references/components-ui.md) | | State, effects, shared API data, mutations | [Hooks](references/hooks.md) | | Requests, responses, endpoint configuration | [API services](references/api-services.md) | | Shared types, constants, runtime guards | [Types](references/types.md) | 3. Keep route entries thin, reuse existing shared UI, and extract abstractions when reuse or complexity warrants it. 4. Verify affected behavior, including loading/error states and localization for UI changes. Select checks from `frontend/package.json`; use `npm run check-all` for broad verification when warranted. Do not install dependencies solely because obsolete examples name them. 5. Report references consulted, checks run, and blocked checks. Do not enforce these conventions by changing unrelated legacy code.
GitHub에서 보기