steedos-project-package

Creates Steedos projects and packages with YAML metadata structures and yarn workflows.

1.6k|414|Updated Mar 4, 2019
One-click install
npx skills add https://github.com/steedos/steedos-platform --skill steedos-project-package
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steedos-project-package
Source: https://github.com/steedos/steedos-platform/tree/main/skills/steedos-project-package
Command: npx skills add https://github.com/steedos/steedos-platform --skill steedos-project-package

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up a Steedos low-code project or package requires knowing the exact directory layout, required files, metadata file types, and naming conventions. This Skill provides the complete structural reference so you can scaffold projects and packages correctly the first time.

Core Features & Use Cases

  • Project Scaffolding: Defines the minimal and complete project structure including package.json, .env configuration, and yarn workspace setup.
  • Package Structure Reference: Documents the full package layout with objects, fields, triggers, functions, pages, applications, permissions, and 18+ metadata file types.
  • Naming & Best Practices: Enforces snake_case API names, bilingual labels, and correct file placement rules (triggers in triggers/, not object folders).
  • Use Case: You need to build an order management module on Steedos. Use this Skill to create the project, add a package with an orders object, list views, permissions, and an approval process, all following platform conventions.

Quick Start

Create a new Steedos project called order-management with a package containing an orders object and its fields, list views, and permissions.

Frequently Asked Questions about steedos-project-package

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Where should trigger files be placed in a Steedos package?

Trigger files (.trigger.yml) belong in the triggers/ folder at the package root, not inside object folders. The same rule applies to functions, which go in the functions/ folder.