Feature Request: Add Boilerplate Templates to rc-apps create

Open
#181 1 comment 0 reactions 0 assignees View on GitHub

@ShubhamS2005 is already working on this.

Since Mar 17, 2026.

  • #182 by @ShubhamS2005 — open
  • #193 by @dwakshar — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript

Research direction

Start with the rc-apps create command and inspect the existing templates folder to understand how generated app files are selected and copied. Define how the --boilerplate option handles slash-command, api-endpoint, and settings, then verify that each selected option produces the corresponding template file in the new app.

Written by the indexing model from the issue text.

Description

Problem
When developers create a new Rocket.Chat app using the rc-apps create command, the generated project only contains the basic app structure. Developers often need to manually create common components such as:

  • Slash Commands
  • API Endpoints
  • App Settings

This requires additional manual setup and boilerplate code.

Proposed Solution

Add a --boilerplate flag to the create command that allows users to automatically generate common starter templates during app creation.

Example usage:

rc-apps create --name=MyApp --boilerplate slash-command

Supported options could include:

  • slash-command
  • api-endpoint
  • settings

The CLI would then generate the corresponding template file inside the newly created app.

Benefits

  • Reduces manual setup for developers
  • Improves developer experience
  • Helps new developers start building Rocket.Chat apps faster

Additional Notes

The boilerplate templates already exist in the repository under the templates folder, so the feature mainly connects them to the create command.

I would be happy to work on implementing this feature.

Dominant language
TypeScript
Stars
49
Forks
40
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from RocketChat/Rocket.Chat.Apps-cli

All issues in RocketChat/Rocket.Chat.Apps-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.