Guide Nexent backend design, implementation, debugging, and review across database schemas, FastAPI endpoints, services, and configuration. Check existing interfaces, consult references for each affected layer, and verify successful and failed behavior while preserving public contracts.
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.
Review the instructions the agent will receive before you install.
Repository paths below are relative to the root; reference links resolve from this skill directory.
| 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 |
nexent-python-tests linked from root AGENTS.md. Unit-test mocks do not establish live-integration acceptance.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Develop and troubleshoot plugins that connect external memory services to Nexent. Define plugin settings, implement search and ingestion, map errors, test with simulated network responses, and verify deployment, authentication, and runtime monitoring.
Run Nexent daily or manual full test suites on a self-hosted Ubuntu machine, using the appropriate test layer for each check. Keep results and evidence local, and prepare maintenance candidates for local test assets.
Implement, debug, or review Nexent frontend pages and React components using existing architecture and UI guidance. Cover API connections, shared data and types, styling, and localization, with checks for loading states, errors, and affected behavior.
Add and maintain Nexent Python unit tests with pytest. Isolate external dependencies, cover successful behavior, boundaries, and errors, and add regression assertions that detect fixed bugs. Review existing coverage and record test results separately from formal acceptance cases.
Develop and fix Nexent features by connecting written specifications, acceptance criteria, implementation, and verification evidence. Plan unit tests and appropriate staged checks, maintain their links to requirements, and fill confirmed test gaps after development.
Organize Nexent test assets into a traceable chain from requirements and bugs to cases, scripts, and results. Review existing coverage, maintain execution settings, and generate a registry and Excel views for formal testing.