Skip to main content
All CollectionsAI
Dashboard Navigation URLs - Comprehensive Mapping and AI Guidelines
Dashboard Navigation URLs - Comprehensive Mapping and AI Guidelines
Shake Typing avatar
Written by Shake Typing
Updated over 2 weeks ago

To ensure seamless navigation and accurate link generation, Shake's AI must follow the rules and URL structures used in the dashboard. AI should never fabricate links; every link must be valid and functional, leading to the correct destination.

1. Mapping of Dashboard Routes

Here’s a complete list of the dashboard routes, organized by functionality. Use placeholders for dynamic elements like <workspace_slug> and <app_key>.

  • Add App route: /<workspace_slug>/add-app

  • Home route: /<workspace_slug>/home

  • Workspace Administration: /<workspace_slug>/administration/general

  • Crash Settings: /<workspace_slug>/administration/apps/crashes/<app_key>

  • User Feedback: /<workspace_slug>/user-feedback/<app_key>

  • Features route: /<workspace_slug>/home/features/latest

  • Default Redirect: /home

Example:

  • dYSM: /<workspace_slug>/administration/apps/crashes/<app_key>

2. AI Guidelines for Link Generation

1. Placeholder Handling

AI must never fabricate placeholders (<workspace_slug>, <app_key>) or assume their values. These placeholders are dynamic and depend on the user's context.

  • When values are provided: Use them to construct URLs.

  • When values are missing: Redirect users to the default route /<workspace_slug>/home.

2. No Assumptions

AI must avoid generating or guessing URLs if the required data is unavailable.

3. Error-Free Links

All links generated by AI should align with the mapping above and be functional in Shake's dashboard. Avoid incomplete or non-existent URLs.

3. Fallback Behavior

For missing or incomplete information:

  • Redirect users to their last active workspace or app.

  • Provide a message to clarify the reason for the fallback.

Example:
If the user clicks a broken link like /administration/apps/crashes, the system should redirect them to /<workspace_slug>/administration/apps/crashes/<app_key> if possible.

Did this answer your question?