onyx-screen-builder

Generates ERP frontend and backend code from a single screen specification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/alabasi2025/manus-skills-library --skill onyx-screen-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onyx-screen-builder
Source: https://github.com/alabasi2025/manus-skills-library/tree/main/onyx-erp/onyx-screen-builder
Command: npx skills add https://github.com/alabasi2025/manus-skills-library --skill onyx-screen-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates the creation of ERP screens across frontend and backend, ensuring consistency with Onyx Pro specifications and accelerating development by turning screen specifications into fully generated code.

Core Features & Use Cases

  • Automated screen scaffolding for header and detail grids that conform to Onyx standards.
  • Automatic generation of Drizzle schema, API routes, and React UI components ready for integration.
  • Use Case: Define a screen spec once and generate a complete ERP screen that can be integrated into the smart-operations-system pipeline.

Quick Start

Provide a screen specification using the template references/screen_definition_template.md and run the generator script to produce outputs under output/<table_name>.

Frequently Asked Questions about onyx-screen-builder

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

FAQPage Schema
How do I automate ERP screen generation for frontend and backend?

Automate ERP screen generation by defining a single specification for headers, grids, and business rules. The generator script produces a deployable ERP UI and API, creating React components and Drizzle schema routes automatically.

What is the process for scaffolding ERP UI components and API routes together?

Scaffolding ERP UI components and API routes uses a YAML frontmatter specification and the generate_screen.py script. This process outputs ready-to-integrate React frontend components and backend Drizzle schema routes under a dedicated output directory.

Can I use a single specification to define both ERP header and detail grids?

Yes, you can define ERP header and detail grids using a single specification. By providing your screen definition via a markdown template, the system processes it to generate conforming frontend UI and backend API code simultaneously.

Do I need to install dependencies to run the ERP code generator script?

No external dependencies are required to run the ERP code generator script. You simply provide a screen specification using the provided template and execute the generation script to produce the frontend and backend code artifacts.

What's the best way to ensure generated ERP screens conform to Onyx Pro specifications?

To ensure generated ERP screens conform to Onyx Pro specifications, define your screen headers, grids, and business rules in the provided template. The generator script automatically processes this to produce standards-compliant UI and API code.

When should I avoid using automated scaffolding for ERP screen creation?

Avoid using automated scaffolding for ERP screen creation when your application requires highly customized UI layouts or complex business logic that cannot be accurately captured in standard header and grid specification templates.