Menu
ReDBox business logic is encapsulated in TypeScript services in `@researchdatabox/redbox-core`.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | Redbox Services |
| description | ReDBox business logic is encapsulated in TypeScript services in `@researchdatabox/redbox-core`. |
ReDBox business logic is encapsulated in TypeScript services in @researchdatabox/redbox-core.
packages/redbox-core/src/services/packages/redbox-core/src/services/index.tsServices.Core.Service.bootstrap() for initialization._exportedMethods to define exposed methods.declare var Record: Model;).(object as any), as any, or other deliberate any casts to bypass TypeScript compilation errors. Fix the types, declare appropriate interfaces, or request guidance in the skill instead. Maintaining type safety helps prevent runtime errors and keeps the codebase maintainable.Use the redbox-dev-tools CLI generator generate_service:
name: Service name (e.g., Records) as an argument.--methods <list>: Comma-separated initial methods.Use redbox-dev-tools generate method to add methods to an existing service:
--file <path>: Path to the service file.--method <name>: Method name.When adding a service, update packages/redbox-core/src/services/index.ts:
ServiceExports with a lazy getter.Hooks can override core services by registering them in registerRedboxServices.
Override services should extend the core service they are replacing.
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.