redbox-portal

ReDBox uses embedded Angular applications within EJS views instead of a single SPA. Each feature is often its own Angular project.

Angular services in ReDBox typically extend `HttpClientService` to handle base URLs, configuration, and CSRF protection.

ReDBox controllers live in `@researchdatabox/redbox-core` and are surfaced to Sails.js through generated shims.

Create detailed feature designs, implementation plans, and task lists for ReDBox/Redbox features that use Waterline models, services, webservice (REST) controllers, ajax controllers, embedded Angular apps, views, and navigation config. Use when asked to design/plan a feature or produce a task list for this stack, especially when explicit sections, non-SPA Angular patterns, and interleaved tests are required.

Review completed ReDBox feature implementations against a growing ruleset and emit structured issues for agent remediation.

Build or update ReDBox form field components end-to-end across Angular form rendering and sails-ng-common config typing/visitor infrastructure. Use when creating a new form component class/model, adding component config properties, wiring component dictionaries, handling config migration/template extraction, or adding form-component tests.

ReDBox uses a JSON-based DSL for configuring record forms, workflows, and record types.

ReDBox hooks are NPM packages that extend or customize ReDBox functionality. They are loaded during the Sails lift process.

ReDBox business logic is encapsulated in TypeScript services in `@researchdatabox/redbox-core`.

Ensure every new service or controller gets Mocha or Bruno coverage by analyzing the implemented code and writing integration tests.

ReDBox uses Mocha for integration testing and Bruno for API testing. All integration tests are run within Docker containers managed by docker-compose profiles.

This skill outlines the workflow for verifying the Redbox Portal web interface using the Agent's built-in browser capabilities and natural language test scripts.

This skill outlines the workflow for verifying the Redbox Portal web interface using the Agent's built-in browser capabilities and natural language test scripts.