rainbond-fullstack-bootstrap

Creates Rainbond application topology and components from project manifests.

7|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/goodrain/rainskills --skill rainbond-fullstack-bootstrap-goodrain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rainbond-fullstack-bootstrap
Source: https://github.com/goodrain/rainskills/tree/main/rainbond-fullstack-bootstrap
Command: npx skills add https://github.com/goodrain/rainskills --skill rainbond-fullstack-bootstrap-goodrain

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up a multi-component application on Rainbond requires manually creating each component, wiring dependencies, configuring ports, envs, and storage. This Skill automates that initial topology bootstrap from a prepared manifest so the app reaches a state ready for troubleshooting or delivery verification. ## Core Features & Use Cases - Topology Creation: Creates or reuses Rainbond apps and components from rainbond.app.json, compose profiles, Git sources, or container images, applying minimum ports, dependencies, and startup configuration. - Dependency & Config Wiring: Wires explicit and env-inferred dependency edges, configures provider connection envs, build parameters, and persistent storage for stateful services. - Bounded Handoff: Stops at the first deeper runtime issue and hands off to troubleshooting or delivery verification with a structured BootstrapResult. - Use Case: After initializing a project with a manifest, ask the agent to create the app and component topology only, without entering fault diagnosis. ## Quick Start Ask the agent to create the Rainbond app and component topology for the current project from its manifest, without continuing into troubleshooting.

Frequently Asked Questions about rainbond-fullstack-bootstrap

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

FAQPage Schema
How do I create a Rainbond app topology from a manifest?

Provide a rainbond.app.json manifest and linked .rainbond/local.json in the project, then ask the agent to create the app and components. The Skill creates or reuses components, wires dependencies, applies ports and envs, and deploys the affected components.

When should I use bootstrap instead of the Rainbond app assistant?

Use bootstrap only when the next action is explicitly creating app topology or components from a known manifest. Generic requests like deploying the current project should route to rainbond-app-assistant, and runtime fault diagnosis belongs to rainbond-fullstack-troubleshooter.

Does it support deploying from Git source or container images?

Yes. It infers the creation method from the request: Git URLs trigger source mode, image tags trigger image mode, and compose profiles or manifests drive multi-component topologies. Complex off-the-shelf suites require a compose file, manifest, or confirmed plan first.

How are component dependencies and database connections configured?

Dependencies are created with rainbond_manage_component_dependency for every declared or env-inferred edge, verified by a completeness gate. Provider connection envs are set on the provider component, and consumers receive host and port values through dependency injection.

What happens when bootstrap hits a build or runtime failure?

Bootstrap has a bounded retry budget and stops at the first deeper runtime issue, reporting a normalized blocking bucket. It then hands off to rainbond-fullstack-troubleshooter, rainbond-delivery-verifier, or a code/build handoff instead of attempting fallback delivery modes.

Can it deploy stateful services like databases with persistence?

Yes. For stateful services created in image mode, it attaches shared-file storage volumes before deploying, since the platform cannot convert stateless components to stateful. High-IOPS local storage requires an app-market template instead.