菜单
ReDBox uses a JSON-based DSL for configuring record forms, workflows, and record types.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | Redbox Form Config |
| description | ReDBox uses a JSON-based DSL for configuring record forms, workflows, and record types. |
ReDBox uses a JSON-based DSL for configuring record forms, workflows, and record types.
config/form.jsconfig/workflow.jsconfig/recordtype.jsrdmp) and its search filters.draft, review), transitions, roles, and which form to use at each stage.class (usually Container), a compClass (the Angular component name, e.g., TextBlockComponent), and a definition.Use the redbox-dev-tools CLI generator generate_form_field:
name: Field name as an argument.--type <type>: Record type (e.g., rdmp).Dynamic behavior is handled via expressions:
/form_tab/source_field::field.value.changed).Labels and messages should use keys (starting with @) that map to entries in assets/locales/<language>/translation.json.