lfx-backend-builder

Generate PR-ready Express.js or Go backend code with three-file scaffolding.

8|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-backend-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lfx-backend-builder
Source: https://github.com/linuxfoundation/lfx-skills/tree/main/lfx-backend-builder
Command: npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-backend-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates PR-ready backend code for LFX repos by applying the three-file pattern (service, controller, route), Goa DSL conventions, and normalized logging and NATS messaging across both Express.js proxy layers and Go microservices.

Core Features & Use Cases

  • Enforces the three-file pattern (service → controller → route) with PR-ready scaffolding
  • Applies standard license headers and consistent logging (debug/info/warning) patterns
  • Supports Express.js proxy layers in lfx-v2-ui and Go microservices in resource repos with code-gen and validation
  • Works with upstream API contracts validation and post-generation formatting and lint checks
  • Use Case: Add a new endpoint in an Express.js-based repo or a Go microservice, and get a PR-ready set of files

Quick Start

Describe the target backend task and repository path, and the skill will generate PR-ready three-file scaffolding accordingly.

Frequently Asked Questions about lfx-backend-builder

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

FAQPage Schema
How do I generate PR-ready Express.js proxy endpoint scaffolding?

To generate PR-ready Express.js proxy endpoints, describe your target backend task and repository path. The tool outputs a three-file pattern (service, controller, route) with standard logging, license headers, and formatting checks satisfied for pull requests.

What is the three-file pattern for Go microservice code generation?

The three-file pattern for Go microservices structures generated code into service, controller, and route files. This enforces consistent architecture, applies Goa DSL conventions, and normalizes NATS messaging for pull request readiness.

Does this backend scaffolding tool validate upstream API contracts before generating code?

Yes, the backend scaffolding tool validates upstream API contracts before code generation. This ensures the generated Express.js proxy layers or Go microservice code conforms to expected interfaces before applying formatting and lint checks.

Can I use Goa DSL conventions to scaffold a new endpoint in an lfx-v2-ui repository?

Yes, you can use Goa DSL conventions to scaffold new endpoints in an lfx-v2-ui repository. Provide the target backend task and repository path to generate the three-file pattern with standard NATS messaging patterns.

Why does generated backend code require post-generation formatting and lint checks?

Generated backend code requires post-generation formatting and lint checks to ensure it satisfies PR readiness criteria. This process verifies standard license headers, consistent debug and info logging patterns, and proper file structure before submission.