frontend-deployment

Deploy frontend applications defined in aramb.toml with environment variables.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/clode-labs/aramb-skills --skill frontend-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-deployment
Source: https://github.com/clode-labs/aramb-skills/tree/main/frontend-deployment
Command: npx skills add https://github.com/clode-labs/aramb-skills --skill frontend-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Frontend Deployment skill automates the end-to-end process of deploying frontend apps defined in aramb.toml. It creates a frontend service, resolves any backend references from deployment outputs, builds static assets when needed, and deploys with required environment variables, returning a public URL.

Core Features & Use Cases

  • Create frontend service from aramb.toml and attach metadata for the aramb orchestrator.
  • Resolve backend references from deployment outputs to inject into environment variables.
  • Detect, build, and deploy static assets for React, Vue, Next.js, and other frameworks.
  • Use cases include pushing a new frontend after backend deployments, or redeploying with updated environment variables.

Quick Start

Use the frontend-deployment skill to deploy a project defined by aramb.toml in the repository root.

Frequently Asked Questions about frontend-deployment

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

FAQPage Schema
How do I automate frontend deployment for React, Vue, or Next.js using aramb.toml?

Automating frontend deployment with aramb.toml involves creating a frontend service, resolving backend references, building static assets, and deploying with environment variables to return a public URL. The process supports React, Vue, Next.js, Angular, and static HTML workflows.

What environment variables do I need to set before deploying a frontend from aramb.toml?

Before deploying a frontend from aramb.toml, you must set ARAMB_API_TOKEN and APPLICATION_ID as environment variables. Additionally, aramb-cli must be present in your PATH, and a valid aramb.toml file must exist in the repository root.

Can I resolve backend API references and inject them into frontend environment variables during deployment?

Yes, resolving backend API references from deployment outputs to inject into frontend environment variables is supported. The deployment process reads these references and automatically configures the required environment variables for the frontend service.

Does the aramb.toml deployment workflow support static HTML sites alongside JavaScript frameworks?

Yes, the aramb.toml deployment workflow supports static HTML sites alongside React, Vue, Next.js, and Angular. It detects, builds, and deploys static assets automatically when a buildable or static asset path is specified.

What is the best way to redeploy a frontend with updated environment variables after a backend deployment?

Redeploying a frontend with updated environment variables after a backend deployment is handled by re-running the deployment process. It resolves the latest backend references from deployment outputs and applies the new environment variables to generate a fresh deployment URL.

Why does my frontend deployment fail when aramb-cli is not in the system PATH?

Frontend deployment fails without aramb-cli in the system PATH because the automation relies on the aramb-cli executable to create services, build static assets, and deploy the application defined in aramb.toml. Ensure the CLI is installed and accessible.

Related Skills