gen-wiring

Generate runnable application artifacts from manifests and targets.

37|5|Updated Nov 18, 2025
One-click install
npx skills add https://github.com/BellaBe/lean-os --skill gen-wiring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-wiring
Source: https://github.com/BellaBe/lean-os/tree/main/.claude/skills/engineering-gen-wiring
Command: npx skills add https://github.com/BellaBe/lean-os --skill gen-wiring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate wiring: entry points, DI container, config, and infrastructure.

Core Features & Use Cases

  • Entry points: main.py, handlers
  • DI container: wiring dependencies
  • Infrastructure: Docker, compose

Quick Start

Provide morphisms manifest; returns wiring files.

Frequently Asked Questions about gen-wiring

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

FAQPage Schema
How do I generate application wiring and infrastructure from manifests?

Application wiring generation reads manifest files (functors.yaml, transformations.yaml, effects.yaml, targets.yaml, types-manifest.yaml, morphisms-manifest.yaml) and outputs entry points, dependency injection container setup, and infrastructure configuration files like Dockerfile and docker-compose.yaml.

Can I generate wiring for microservices, serverless, and monolith architectures?

Yes. Wiring generation supports topology-aware code generation across monolith, microservices, library, and serverless deployment patterns, producing deployment-specific entry points and infrastructure files for each.

What files does wiring generation produce?

Wiring generation outputs actual code and configuration files—not YAML—including entry points (main.py, handlers), dependency injection container wiring, middleware composition, Dockerfile, docker-compose.yaml, pyproject.toml, and a wiring-manifest.yaml summary.

Do I need to manually write entry points and DI container setup?

No. Wiring generation automatically produces entry points, dependency injection containers, and configuration from your morphisms manifest, eliminating manual boilerplate for container wiring and infrastructure.

What input manifests do I need to provide for wiring generation?

Provide morphisms-manifest.yaml along with functors.yaml, transformations.yaml, effects.yaml, targets.yaml, types-manifest.yaml in the artifacts/v{N}/build directory; wiring generation reads these to produce application wiring and infrastructure.

Does wiring generation support multiple programming languages?

Yes. Wiring generation outputs language-specific code to artifacts/v{N}/gen/{language}/, supporting multiple target languages for entry points, DI container configuration, and deployment artifacts.