route-and-menu-config

Register ITSM module routes and menus across router.go, Sidebar, and seed_data.sql.

57|13|Updated Jul 12, 2025
One-click install
npx skills add https://github.com/heidsoft/itsm --skill route-and-menu-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: route-and-menu-config
Source: https://github.com/heidsoft/itsm/tree/main/.trae/skills/route-and-menu-config
Command: npx skills add https://github.com/heidsoft/itsm --skill route-and-menu-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

IT teams often struggle with inconsistent route registration, missing frontend menu entries, and stale seed data when adding new ITSM modules. This guide provides a repeatable workflow to wire backend routes, frontend navigation, and database menus to ensure new modules are accessible and consistent.

Core Features & Use Cases

  • Backend Route Registration: add controllers and register routes in router.go to expose new module APIs.
  • Frontend Menu Configuration: ensure dynamic menus in the Sidebar or static fallbacks are updated to reflect new modules.
  • Database Seed Data: create or update seed_data.sql to seed menus with correct paths, icons, and permissions.
  • Use Case: When introducing a new ITSM module, follow this workflow to align backend, frontend, and DB entries so users can access the new module seamlessly.

Quick Start

Add a new module by creating its controller, registering routes, seeding menu data, and verifying the UI and API endpoints.

Frequently Asked Questions about route-and-menu-config

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

FAQPage Schema
How do I configure ITSM routes and menus for a new module?

To configure ITSM routes and menus, you must register backend APIs in router.go, map frontend paths in the Sidebar configuration, and insert consistent menu records into seed_data.sql to ensure the new module is accessible and functional.

Why does my frontend navigation break after adding a new ITSM module?

Frontend navigation breaks when ITSM route registration is inconsistent, typically due to missing Sidebar path mappings or stale seed data that fails to align the new module's UI paths with its backend APIs.

What is the best way to update UI paths and routing for ITSM modules?

The best way to update UI paths and routing is to follow a repeatable workflow that simultaneously wires backend controllers in router.go, updates frontend Sidebar navigation, and synchronizes database menu seeds to prevent API or navigation issues.

Do I need to update seed_data.sql when adding new menus to my ITSM application?

Yes, you need to update seed_data.sql to seed menus with correct paths, icons, and permissions, ensuring the database entries match the frontend Sidebar configuration and backend route registration for seamless access.

How does backend route registration work with frontend menu configuration?

Backend route registration exposes module APIs via router.go, while frontend menu configuration maps those APIs to accessible UI paths in the Sidebar, requiring synchronized seed_data.sql entries to maintain consistent navigation and prevent broken endpoints.

Can I use this route registration workflow to update existing ITSM modules?

Yes, you can use this workflow to update existing ITSM modules by modifying router.go for backend APIs, adjusting the Sidebar configuration for frontend navigation, and refreshing seed_data.sql to maintain consistent menu paths and permissions.