skills.rest
orkestra-cc
orkestra-ccOFFICIAL
Explore all skills by this author →
GitHub

orkestra-addon

Standardize Orkestra addon modules with tenant-scoping, RBAC, and i18n isolation.

1|1|Updated Dec 20, 2025
Search Tags:#typescript#architecture#golang#rbac#module#saas#orkestra
One-click install
npx skills add https://github.com/orkestra-cc/orkestra --skill orkestra-addon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orkestra-addon
Source: https://github.com/orkestra-cc/orkestra/tree/main/.claude/skills/orkestra-addon
Command: npx skills add https://github.com/orkestra-cc/orkestra --skill orkestra-addon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the complexity of maintaining consistency across modular SaaS architectures by enforcing strict naming, scoping, and integration rules for Orkestra addons.

Core Features & Use Cases

  • End-to-End Scaffolding: Provides a unified recipe for backend modules and frontend-admin pages.
  • Architectural Guardrails: Enforces tenant-scoping, RBAC, and i18n namespace isolation to prevent cross-module pollution.
  • Use Case: When building a new feature like a custom reporting module, use this skill to ensure your database collections, API routes, and frontend manifests follow the core-only base conventions required for production stability.

Quick Start

Use the orkestra-addon skill to validate your new module structure against the required naming and dependency conventions.

Frequently Asked Questions about orkestra-addon

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

FAQPage Schema
How do I scaffold a new SaaS module without causing cross-module pollution?▼

To scaffold a SaaS module without cross-module pollution, use standardized recipes that enforce tenant-scoping, RBAC, and i18n namespace isolation. This ensures backend services and frontend-admin manifests follow strict naming conventions for production stability.

How does the ServiceRegistry handle cross-module communication in a modular architecture?▼

The ServiceRegistry governs cross-module communication by enforcing integration rules within the core-only base architecture. It ensures optional modules interact safely without violating tenant-scoping boundaries or introducing unauthorized dependencies between services.

What is the best way to enforce RBAC and tenant-scoping when building custom reporting modules?▼

The best way to enforce RBAC and tenant-scoping for custom reporting modules is to validate the module structure against core-only base conventions. This applies architectural guardrails to database collections, API routes, and frontend manifests automatically.

How do I validate backend and frontend-admin manifests for new Orkestra addons?▼

You validate new Orkestra addons by checking the backend services and frontend-admin pages against required naming and dependency conventions. This end-to-end scaffolding recipe ensures strict adherence to production-grade SaaS module integration standards.

Can I use TypeScript and Golang when integrating optional modules into a core-only base?▼

Yes, TypeScript and Golang are supported when integrating optional modules into a core-only base. The scaffolding standardizes development across both backend services and frontend-admin pages while maintaining required tenant-scoping and i18n namespace isolation.

Related Skills

Explore More Software Engineering Skills→
NBXXFNBXXF
6

xxf-foundation

Expose core protocols, typealiases, and utilities for XXF modules.

Community
Basic
thc1006thc1006
20

k8s-security-policies

Implement Kubernetes NetworkPolicy, PodSecurityPolicy, and RBAC security policies.

Community
Advanced
zinohomezinohome
1

rbac-permissions-builder

Implement role-based access control with permission matrices and route guards.

Community
Advanced
HellKaiser45HellKaiser45

fullstack-dev

Codify end-to-end full-stack development workflows with mandatory architecture and testing steps.

Community
Advanced