Nexent Backend
Use when designing, implementing, debugging, or reviewing Nexent relational schemas...
Install
npx skills add ModelEngine-Group/nexent --skill nexent-backend -g -a claude-code -y- Repository
- ModelEngine-Group/nexent6.1k
- Category
- Design
- Updated
- 4d ago
- License
- MIT
- Context cost
- Lightabout 385 tokens
- Runs scripts
- No, instructions only
What it does
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.
Nexent backend changes
Repository paths below are relative to the root; reference links resolve from this skill directory.
- Identify the affected boundary and inspect existing callers and contracts. Apps handle HTTP, services orchestrate business logic, and database modules own persistence.
- Read only the references matching the work. For end-to-end changes, read each affected layer before editing.
| Work | Reference |
|---|---|
| HTTP routes, validation, identity, response/error mapping | HTTP layer |
| Business orchestration and domain errors | Services |
| Relational schema design, models, keys/indexes, queries, transactions, SQL migrations | Database |
| Environment configuration and SDK configuration parameters | Configuration |
| Threads, worker pools, blocking calls, background loops, streaming resource lifetime | Thread lifecycle |
- Preserve public contracts. Apply conventions to the changed scope; do not refactor unrelated legacy behavior merely to satisfy a rule.
- Verify affected success and failure behavior. For Python unit tests, use
nexent-python-testslinked from rootAGENTS.md. Unit-test mocks do not establish live-integration acceptance. - Report references consulted, affected contracts, and verification results. Resolve material contract conflicts using concrete evidence; routine implementation choices do not require additional permission.
