agentleFS
JetBrainsKnown publisherJetBrains/ij-perf-report-aggregator/.agents/skills/add-dashboard-page/SKILL.md

add-dashboard-page

Skill24 starsChanged 5 days agoApache-2.0View on GitHub

Add a new page (tab) to an existing dashboard category

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. its-shitzu/AgentStack★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add a new page to the existing $0 category.

    line 7
  2. Very specific:

    All changes go in dashboard/new-dashboard/src/routes.ts and optionally a new Vue component.

    line 9
  3. Very specific:

    Use existing label constants when applicable: TESTS_LABEL, DASHBOARD_LABEL, STARTUP_LABEL, PRODUCT_METRICS_LABEL, COMPARE_BUILDS_LABEL, …

    line 29
  4. Very specific:

    Add a new entry to the category's existing routes array using the route-builder helpers (defined near the top of routes.ts).

    line 33
  5. Very specific:

    Only needed for custom dashboard pages (not for Tests/Compare/Startup pages, which use shared components).

    line 81
  6. Very specific:

    Use standard route constants (TEST_ROUTE, DEV_TEST_ROUTE, DASHBOARD_ROUTE, STARTUP_ROUTE, PRODUCT_METRICS_ROUTE, COMPARE_ROUTE, …

    line 105
  7. Very specific:

    Only drop to a raw object literal with satisfies TypedRouteRecord<...> for special cases the helpers don't cover (e.g.

    line 108

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add a new page to the existing $0 category. Page type: $1. Label: $2.

All changes go in dashboard/new-dashboard/src/routes.ts and optionally a new Vue component.

Steps

1. Add route enum entry

In the ROUTES enum, add a new entry using the category's ROUTE_PREFIX:

MyCategoryNewPage = `${ROUTE_PREFIX.MyCategory}/newPage`,

2. Add tab to the Product definition

Find the existing Product const for the category and add a tab(url, label) entry to its tabs array:

tab(ROUTES.MyCategoryNewPage, "New Page"),

Use existing label constants when applicable: TESTS_LABEL, DASHBOARD_LABEL, STARTUP_LABEL, PRODUCT_METRICS_LABEL, COMPARE_BUILDS_LABEL, COMPARE_BRANCHES_LABEL, COMPARE_MODES_LABEL.

3. Add route handler

Add a new entry to the category's existing routes array using the route-builder helpers (defined near the top of routes.ts).

For a Tests page (uses the shared PerformanceTests.vue component via perfTests(path, props, pageTitle)):

perfTests(
  ROUTES.MyCategoryNewPage,
  { dbName: "<dbName>", table: "<table>", initialMachine: MACHINES.HETZNER, withInstaller: false },
  "My Category Performance tests"
),

props is typed as PerformanceTestsProps (dbName, table, initialMachine, and optional withInstaller, unit, releaseConfigurator, branch, withoutAccidents, machineGroupFilter). The satisfies TypedRouteRecord<PerformanceTestsProps> annotation lives inside the helper.

For a Dashboard page (custom Vue component via dashboard(path, component, pageTitle, props?)):

dashboard(ROUTES.MyCategoryNewPage, () => import("./components/myCategory/NewPageDashboard.vue"), "My Category New Page"),

For a Startup dashboard (startupDashboard(path, { table, defaultProject? }, pageTitle)):

startupDashboard(ROUTES.MyCategoryStartup, { table: "<table>", defaultProject: "<project>" }, "My Category Startup dashboard"),

For a Compare Builds page (compareBuilds(path, { dbName, table }, pageTitle?)):

compareBuilds(ROUTES.MyCategoryCompare, { dbName: "<dbName>", table: "<table>" }),

For a Compare Branches page (compareBranches(path, { dbName, table, metricsNames? }, pageTitle?)):

compareBranches(ROUTES.MyCategoryCompareBranches, { dbName: "<dbName>", table: "<table>" }),

For a Compare Modes page (compareModes(path, { dbName, table }, pageTitle?)):

compareModes(ROUTES.MyCategoryCompareModes, { dbName: "<dbName>", table: "<table>" }),

The pageTitle argument of the three compare helpers defaults to the standard label (Compare Builds / Compare Branches / Compare Modes), so pass it only to override.

4. Create Vue component (if needed)

Only needed for custom dashboard pages (not for Tests/Compare/Startup pages, which use shared components).

Create dashboard/new-dashboard/src/components/<category>/NewPageDashboard.vue:

<template>
  <DashboardPage
    db-name="<dbName>"
    table="<table>"
    persistent-id="<category>_<page>_dashboard"
    initial-machine="linux-blade-hetzner"
    :with-installer="false"
  />
</template>

<script setup lang="ts">
import DashboardPage from "../common/DashboardPage.vue"
</script>

Conventions

  • Route enum keys use PascalCase: KotlinNotebooksTests
  • Route URL paths use camelCase: /kotlinNotebooks/tests
  • Use standard route constants (TEST_ROUTE, DEV_TEST_ROUTE, DASHBOARD_ROUTE, STARTUP_ROUTE, PRODUCT_METRICS_ROUTE, COMPARE_ROUTE, COMPARE_BRANCHES_ROUTE, COMPARE_MODES_ROUTE) when the page type matches
  • Build tabs with tab(url, label); build routes with the perfTests / dashboard / startupDashboard / compareBuilds / compareBranches / compareModes helpers
  • Reference machines via MACHINES.HETZNER / MACHINES.AWS_LINUX instead of raw strings
  • Only drop to a raw object literal with satisfies TypedRouteRecord<...> for special cases the helpers don't cover (e.g. the PerformanceUnitTests.vue component, or a :subproject? path param)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.