본문으로 건너뛰기
cccskills
무료GitHub에 공개

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
설치 방법 보기

포함된 파일(26)

  • SKILL.md3.5 KB
  • references/api-services.md966 B
  • references/architecture.md1.5 KB
  • references/components-ui.md4.2 KB
  • references/components/agent-suggestion.md2.9 KB
  • references/components/button.md1.1 KB
  • references/components/card.md589 B
  • references/components/component-contracts.md4.0 KB
  • references/components/drawer.md2.7 KB
  • references/components/font.md822 B
  • references/components/icon.md864 B
  • references/components/input.md360 B
  • references/components/modal.md2.1 KB
  • references/components/model-selector.md2.7 KB
  • references/components/paginator.md323 B
  • references/components/README.md1.2 KB
  • references/components/resource-add-button.md1.8 KB
  • references/components/resource-picker.md10.1 KB
  • references/components/selected-resource-row.md2.2 KB
  • references/components/style.md147 B
  • references/components/table.md2.3 KB
  • references/components/thread-history-pins.md2.6 KB
  • references/components/tour.md1.6 KB
  • references/hooks.md1.1 KB
  • references/pages.md1.2 KB
  • references/types.md830 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Nexent frontend changes

Repository paths below are relative to the root; reference links resolve from this skill.

  1. Read architecture, the affected feature, and frontend/package.json before choosing APIs or dependencies. For frontend visual work, read the authoritative sibling document ../docs/前端ui.md from the repository root when it is available, then apply the linked English component references.
  2. Load relevant detailed rules only.
WorkReference
Route entries, layouts, loading UI, localizationPages
Components, visual layout, forms, modals, icons, user-visible copyComponents and UI, then the relevant documents under components
State, effects, shared API data, mutationsHooks
Requests, responses, endpoint configurationAPI services
Shared types, constants, runtime guardsTypes
  1. Keep route entries thin, reuse existing shared UI, and extract abstractions when reuse or complexity warrants it.
  2. 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.
  3. Report references consulted, checks run, and blocked checks. Do not enforce these conventions by changing unrelated legacy code.

UI source synchronization

  • Treat ../docs/前端ui.md as the visual source of truth. Do not invent visual values that it does not define; use the existing frontend references only for unspecified defaults.
  • Translate every first-level heading into one English Markdown reference under references/components/; keep nested headings in that reference.
  • Convert documented visual values to Tailwind CSS in the reference and implement reusable components under frontend/components/common/ when the source defines a reusable component contract.
  • Keep user-facing default text localized through the existing translation namespace. Create component test pages only as explicitly requested temporary local debug entries; do not add them to Nexent feature routes or navigation, and remove them after debugging is complete.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

external-memory-plugin

무료

Develop, adapt, review, test, and troubleshoot Nexent external memory provider plugins, including plugin.yaml manifests, searchable and ingestible provider protocols, error mapping, network-isolated unit tests, deployment configuration, and Mem0-based examples. Use when adding a new external memory vendor, changing an existing memory plugin, validating partner adapters, or diagnosing plugin discovery, authentication, retrieval, ingestion, or CI failures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ModelEngine-Group/nexent6천2026년 10월 19일 업데이트

nexent-backend

무료

Use when designing, implementing, debugging, or reviewing Nexent relational schemas, FastAPI endpoints, backend services, database access, SQL migrations, or backend/SDK configuration. Includes table/field naming, types, JSONB boundaries, audit fields, keys, and indexes even before code paths exist. Skip frontend-only work and unrelated SDK algorithms.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ModelEngine-Group/nexent6천2026년 10월 19일 업데이트

nexent-daily-test

무료

在 Ubuntu 自托管测试机上编排 Nexent 每日分层全量测试、维护本地测试基线和 P0 Playwright 候选代码，并将证据仅保存在本机。用于 OpenCode 执行 Daily/手工全量测试；不用于 PR 测试或外部结果发布。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ModelEngine-Group/nexent6천2026년 10월 19일 업데이트

nexent-python-tests

무료

Implement and maintain Nexent's traditional Python UT for product changes and bugfixes under test/backend, test/sdk, and test/ext_components. Cover unit behavior, boundaries, errors and regression assertions with isolated pytest tests. Formal D1-D5 assets in test-e2e use nexent-test-assets.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ModelEngine-Group/nexent6천2026년 10월 19일 업데이트

nexent-spec-coding

무료

Run Nexent requirements and bugfixes through SPEC acceptance, traditional UT and applicable D1-D5 test design, product/test implementation, local verification, and delivery evidence. Use for features, fixes, refactors and post-development test backfill across APIs, UI, model and Agent behavior.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ModelEngine-Group/nexent6천2026년 10월 19일 업데이트

nexent-test-assets

무료

Create and maintain Nexent's repository-owned feature catalog, D1-D5 case-local contracts and fixed scripts, change records, generated execution registry and Excel view. Use for requirements, bug regressions, post-development test backfill, test implementation, and formal asset migration. Traditional UT uses nexent-python-tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ModelEngine-Group/nexent6천2026년 10월 19일 업데이트

ModelEngine-Group의 스킬 모두 보기

이 스킬의 문제 신고