rainbond-project-init

Initializes local projects for Rainbond by generating manifests and app bindings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Connecting a local project to Rainbond for the first time requires creating a correct manifest, resolving team/region/app identity, and linking the workspace to a platform app. This Skill automates that first-time onboarding so deployment workflows can proceed without manual configuration. ## Core Features & Use Cases - Manifest Generation: Inspects repository structure (package.json, Dockerfile, docker-compose.yml, frontend/backend directories) and generates a bootstrap-compatible rainbond.app.json with inferred components, roles, ports, and dependencies. - App Linking & Adoption: Finds or creates the target Rainbond app, then writes .rainbond/local.json with verified binding metadata, or adopts an existing app without creating duplicates. - Execution Summary: Classifies each component as image, source, template, or blocked with ready/needs_confirmation status so users know what can run immediately. - Use Case: You have a full-stack repo with a React frontend, Express backend, and Postgres in docker-compose. Ask the agent to initialize the project, and it infers the three components, generates the manifest, creates the Rainbond app, and links the workspace ready for deployment. ## Quick Start Initialize the current project for Rainbond and link it to an app so it is ready for deployment.

Frequently Asked Questions about rainbond-project-init

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

FAQPage Schema
How do I initialize a local project for Rainbond deployment?

Run the initialization flow in your project directory. It checks for rainbond.app.json and .rainbond/local.json, generates a manifest from repository structure if missing, finds or creates the Rainbond app, and writes the local binding file.

What files does Rainbond project initialization create?

It creates or updates two files: rainbond.app.json, the component topology manifest, and .rainbond/local.json, the local binding containing team, region, app name, app_id, and environment preferences. Secrets are never stored in these files.

Can I deploy a Git URL or Docker image without a local project?

No. A bare Git URL or image reference with no local project context is rejected by the address-only guard. That scenario is handled by the app assistant using platform context instead of local project initialization.

Does the manifest support source-based components from Git repositories?

Yes. Business code components in a Git repo are inferred as source-backed with git_url, code_version, and subdirectories fields. Docs and Docusaurus sites also default to source-backed rather than generic static images.

When should I not use project initialization?

Skip it when the project is already linked and you need routine deploys, runtime troubleshooting, or code repair. Initialization is only for first-time onboarding; day-2 operations belong to downstream deployment and troubleshooting skills.

What happens if the Rainbond connection is unavailable during initialization?

The manifest and a provisional local binding can still be written, but the result is reported as pending_verification. Full initialization requires online verification of the app's existence and app_id through the Rainbond connection.