跳到正文
cccskills
免费在 GitHub 公开

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.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(6)

  • SKILL.md1.9 KB
  • references/configuration.md844 B
  • references/database.md9.3 KB
  • references/http.md2.4 KB
  • references/services.md1.1 KB
  • references/thread-lifecycle.md5.5 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Nexent backend changes

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

  1. Identify the affected boundary and inspect existing callers and contracts. Apps handle HTTP, services orchestrate business logic, and database modules own persistence.
  2. Read only the references matching the work. For end-to-end changes, read each affected layer before editing.
WorkReference
HTTP routes, validation, identity, response/error mappingHTTP layer
Business orchestration and domain errorsServices
Relational schema design, models, keys/indexes, queries, transactions, SQL migrationsDatabase
Environment configuration and SDK configuration parametersConfiguration
Threads, worker pools, blocking calls, background loops, streaming resource lifetimeThread lifecycle
  1. Preserve public contracts. Apply conventions to the changed scope; do not refactor unrelated legacy behavior merely to satisfy a rule.
  2. Verify affected success and failure behavior. For Python unit tests, use nexent-python-tests linked from root AGENTS.md. Unit-test mocks do not establish live-integration acceptance.
  3. Report references consulted, affected contracts, and verification results. Resolve material contract conflicts using concrete evidence; routine implementation choices do not require additional permission.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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/nexent59802026年10月19日 更新

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

中文简介正在准备中。当前显示原文说明。

ModelEngine-Group/nexent59802026年10月19日 更新

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/nexent59802026年10月19日 更新

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/nexent59802026年10月19日 更新

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/nexent59802026年10月19日 更新

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/nexent59802026年10月19日 更新

查看 ModelEngine-Group 的全部技能

报告此技能的问题