config-menus

Build hierarchical, permission-aware application menus stored in a database with tenant templates.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Adrinc/camsys --skill config-menus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-menus
Source: https://github.com/Adrinc/camsys/tree/main/.agent/skills/config-menus
Command: npx skills add https://github.com/Adrinc/camsys --skill config-menus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers implement dynamic, hierarchical menus that are stored in a database and can be customized per tenant via templates, with support for permissions-based filtering and drag-and-drop reordering.

Core Features & Use Cases

  • Hierarchical menus stored in DB with parent-child relationships and display order.
  • Templates per tenant to assign predefined menu structures to tenants and support easy customization.
  • Permission-based filtering and reordering to ensure only allowed items are visible and ordering is adjustable via drag-and-drop.
  • Icon customization and frontend integration to render rich, navigable menus in admin dashboards and apps.

Quick Start

Create and display the tenant-specific dynamic menu by loading items from the database and applying the tenant's template.

Frequently Asked Questions about config-menus

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

FAQPage Schema
How do I build dynamic menus stored in a database for a multi-tenant application?

Dynamic menus for multi-tenant apps are built by storing hierarchical items with parent-child relationships in a database and applying per-tenant templates. This allows each tenant to receive a customized menu structure loaded via SQL queries and rendered on the frontend.

How does permission-based filtering work for hierarchical application menus?

Permission-based filtering for hierarchical menus works by applying authorization rules to database query results before frontend rendering. This ensures only allowed menu items are visible to users, while still supporting parent-child relationships and display order adjustments.

What is the best way to assign predefined menu templates to different tenants?

Assigning predefined menu templates to tenants involves creating template structures in the database that map to specific tenant IDs. This approach supports easy customization by allowing tenants to inherit a base menu structure and modify it through drag-and-drop reordering.

Can I implement drag-and-drop reordering for database-driven admin dashboard menus?

Yes, drag-and-drop reordering for database-driven admin dashboard menus is supported by storing a display order value in the database. Backend handlers update the hierarchical menu ordering based on frontend interactions, ensuring persistent sequence adjustments across tenants.

Does this approach provide the database schema and backend handlers needed for multi-tenant menus?

Yes, this approach provides the database schema, SQL queries, and backend handlers required for multi-tenant menus. It also includes a frontend model to render and manage the dynamic hierarchical items, covering the full stack implementation.

When do I need database-stored hierarchical menus instead of static frontend configurations?

Database-stored hierarchical menus are needed when building multi-tenant apps or admin dashboards that require per-tenant customization, permission-based authorization, and dynamic drag-and-drop reordering. Static frontend configurations lack this template assignment and dynamic filtering capability.