multi-group-architecture

Automate scalable LINE Bot deployments with per-group isolation and scheduling.

1|Updated Oct 16, 2025
One-click install
npx skills add https://github.com/forever19735/Garbage --skill multi-group-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: multi-group-architecture
Source: https://github.com/forever19735/Garbage/tree/main/.agent/skills/multi-group-architecture
Command: npx skills add https://github.com/forever19735/Garbage --skill multi-group-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design and implement LINE Bot architectures capable of managing multiple groups with complete data and configuration isolation, enabling scalable, tenant-aware deployments.

Core Features & Use Cases

  • Group Isolation: Each LINE group maintains its own data and settings, preventing cross-group leakage.
  • Automatic Registration & Join/Leave Handling: The bot auto-registers groups when they join and cleans up on leave.
  • Independent Scheduling: Groups can have unique broadcast times and schedules without interference.
  • Migration Path: Provides patterns to migrate from single-group to multi-group deployments.

Quick Start

To begin, implement a per-group registry, per-group data stores, and per-group scheduling logic so that each group operates independently within the same bot.

Frequently Asked Questions about multi-group-architecture

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

FAQPage Schema
How do I scale a LINE Bot to handle multiple groups with isolated data?▼

To scale a LINE Bot for multiple groups with isolated data, implement a per-group registry and per-group data stores. This architecture ensures complete group isolation, preventing cross-group data leakage during multi-tenant operation.

What is the best way to migrate a single-group LINE Bot to a multi-group architecture?▼

Migrating a single-group LINE Bot to a multi-group architecture requires implementing migration strategies that sustain transitions. You establish a group registry and per-group scheduling logic so each group operates independently within the same bot.

How does automatic group registration work for multi-tenant LINE Bots?▼

Automatic group registration for multi-tenant LINE Bots works by auto-registering groups when the bot joins. It enforces context awareness and handles join/leave events, automatically cleaning up data when the bot leaves a group.

Can I set independent broadcast schedules for each LINE group in the same bot?▼

Yes, you can set independent broadcast schedules for each LINE group in the same bot. The architecture supports independent scheduling, allowing unique broadcast times and per-group scheduling without interference between groups.

Does multi-group LINE Bot architecture support per-group member data?▼

Yes, multi-group LINE Bot architecture supports per-group member data. By utilizing a per-group registry and isolated data stores, each group maintains its own member data and group-specific settings without cross-group leakage.