Loading...
Loading...
Found 18 Skills
Steedos Server real-time WebSocket system using Socket.IO. Covers the AppGateway (@WebSocketGateway), connection authentication via cookies, room-based event routing (tenant-scoped rooms), subscribe/unsubscribe events, metadata change notifications, record change events, notification broadcasting, and Moleculer event integration for cross-service real-time communication.
Define navigation tabs for Steedos applications. Tabs appear in the application sidebar and support three types: object (shows list view), page (renders a micro page), and url (opens internal/external URL). Covers .tab.yml structure, permissions per permission_set, icon/label configuration, desktop/mobile visibility, iframe/new-window options, license restrictions, and URL template variables.
Define initial seed data for Steedos objects using .data.json, .data.yml, or .data.csv files in main/default/data/. Records are imported on service startup (insert-only) and on space initialization (upsert). Covers file naming, record structure, _id requirement, template variables (${space_id}, ${space_owner_id}), EJSON date format, and import behavior (onlyInsert vs upsert).
Configure Steedos Server via environment variables and YAML settings files. Covers required env vars (MONGO_URL, ROOT_URL, B6_TRANSPORTER, B6_CACHER), steedos-config.yml project settings, default.steedos.settings.yml template with env interpolation, datasources, tenant settings, CFS file storage (local, aliyun, aws, steedosCloud), SSO/OIDC, email, SMS, push notifications, and frontend asset URLs.
Understand Steedos Server (builder6/server) architecture. NestJS 11 + Moleculer 0.14 hybrid backend with Express middleware, Socket.IO real-time, Redis sessions/caching, and ObjectQL data access. Covers module organization, bootstrap sequence, middleware stack, guards, dependency injection, and builder6 package ecosystem (@builder6/core, moleculer, tables, files, rooms, pages, oidc, etc.).
Steedos metadata internationalization (i18n) system. Two file types: translation files (.translation.yml) for app names, tab labels, and custom labels; objectTranslation files (.objectTranslation.yml) for object labels, field labels/help/options, listview labels, action labels, group labels, and object-scoped CustomLabels. Covers directory structure, naming conventions, supported languages (en, zh-CN), and all translatable metadata sections.
Define server-side JavaScript functions for Steedos objects using YAML. Functions are callable via REST API or from buttons/triggers. Covers function definition (.function.yml files in main/default/functions/), inline script with ctx/objects/global context, REST API exposure, calling from amis_button schemas, and examples for CRUD operations, data processing, and external API integration.
Comprehensive guide to Steedos field types and configurations. Fields are defined as .field.yml files in objects/{name}/fields/. Covers text fields, numeric fields (number, currency, percent, autonumber), date/time, boolean/select, relationship fields (lookup, master-detail), computed fields (formula, summary), file/media, and special types. Includes field properties, amis UI customization, visible_on formulas, validation, defaults, and dependencies.
Learn how to create and structure Steedos projects using Node.js/TypeScript. Covers minimal project requirements, package.json configuration, steedos-config.yml setup, directory structure, environment variables, and installation procedures. Use when creating a new Steedos project or understanding project organization.
Validate a Steedos package after creation or modification. Run this tool to check that all files conform to Steedos conventions: correct naming, required fields, valid enum values, proper file organization. TRIGGER: After creating or modifying files in a Steedos package (objects, fields, buttons, triggers, functions, listviews, permissions, apps, tabs, pages). Run before completing the task to catch issues early. SKIP: When only reading files, answering questions, or working outside a Steedos package context.
Develop custom React + Vite webapps in Steedos packages (webapps/ directory). Build custom amis Renderer components via IIFE compilation, with JSX runtime shimming (amisRequire), CSS scope isolation (postcss-prefix-selector), ScopedContext registration, Express router for SPA access, Tailwind v4 workarounds, and multi-webapp management. Covers vite.amis.config.ts, amis-entry.ts, amis-jsx-shim.ts, client loader files (main/default/client/*.client.js with waitForThing/loadJs/loadCss), build scripts, and deployment to public/.
TRIGGER when: user asks about querying or mutating Steedos data via GraphQL (POST /graphql); asks about auto-generated GraphQL operations ({object}, {object}__findOne, {object}__count, {object}__insert, {object}__update, {object}__delete); asks about __expand for lookup expansion, _display for formatted values, _permissions for record permissions, _related_* for related records, or DataLoader batching; asks about filters/pagination/sorting in a GraphQL query against Steedos; asks about Apollo Playground at /graphql. SKIP: user wants REST API CRUD — use steedos-server-api or steedos-builder6-api; user wants to call a server function — use steedos-object-functions + steedos-server-api; user is building a generic GraphQL server unrelated to Steedos. Steedos GraphQL API auto-generated from object metadata at /graphql. Covers all CRUD queries/mutations, lookup expansion, display formatting, record permissions, related records, filters, pagination, and authentication.