Loading...
Loading...
Found 18 Skills
Steedos CLI commands reference. Covers project lifecycle commands (start, restart), data import/export, source management, package operations, and authentication. Use this skill when running, restarting, or managing Steedos projects from the command line, especially for AI-assisted development workflows that need automatic restart after code changes.
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.
Create analytics question files (.question.yml) in Steedos projects. Questions are report/chart definitions stored as YAML seed data files, based on the @steedos-labs/analytics package (Metabase engine). Covers file format, dataset_query structure (MBQL), display types, visualization_settings, result_metadata, and file naming conventions.
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/.
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.
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).
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 list views for displaying Steedos object records in table format. List views are .listview.yml files in objects/{name}/listviews/. Covers column configuration, filter operators and conditions, date-based filters, searchable fields, sorting, mobile columns, view types (grid, calendar, kanban), crud_mode, shared settings, and filter scope.
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.
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.
Defines Steedos object data models using YAML. Objects represent database tables with fields, permissions, list views, and behaviors. Use this skill to create and configure objects, define fields, set up relationships, configure feature flags, and establish naming conventions. Modern format uses separate .field.yml, .listview.yml, .permission.yml, .button.yml files in subfolders.
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.