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.
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.
Review the instructions the agent will receive before you install.
Repository paths below are relative to the root; reference links resolve from this skill.
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.| Work | Reference |
|---|---|
| Route entries, layouts, loading UI, localization | Pages |
| Components, visual layout, forms, modals, icons, user-visible copy | Components and UI, then the relevant documents under components |
| State, effects, shared API data, mutations | Hooks |
| Requests, responses, endpoint configuration | API services |
| Shared types, constants, runtime guards | Types |
frontend/package.json; use npm run check-all for broad verification when warranted. Do not install dependencies solely because obsolete examples name them.../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.references/components/; keep nested headings in that reference.frontend/components/common/ when the source defines a reusable component contract.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.
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.
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.
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.