Skip to content
Skills Library
Data & analytics · Building & coding

react-dashboard-application

/react-dashboard-application

Interactive data-dashboard frontend generation: toggleable overlaid time-series charts and sortable/rankable tables over the same dataset. Use for Literate AI workflow tasks. Delta of the front-end parent.

Repository
literate-ai ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

85/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content20 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Interactive data-dashboard frontend generation: toggleable overlaid time-series charts and sortable/rankable tables over the same dataset. Use for Literate AI workflow tasks. Delta of the front-end parent.

Original author description

Interactive data-dashboard frontend generation: toggleable overlaid time-series charts and sortable/rankable tables over the same dataset. Use for Literate AI workflow tasks. Delta of the front-end parent.

How it works

  1. Series selection state
  2. Graph view
  3. Table view
  4. View switching
  5. Browser-observable dashboard state
Original SKILL.md headings · 51 lines, 441 words
SKILL.md preview
---
name: "react-dashboard-application"
description: "Interactive data-dashboard frontend generation: toggleable overlaid time-series charts and sortable/rankable tables over the same dataset. Use for Literate AI workflow tasks. Delta of the front-end parent."
metadata:
  author: "Literate AI maintainers <literate-ai-maintainers@users.noreply.github.com>"
schema: "urn:literate-ai:schema:v1:specification-to-source-skill"
skill_id: "react-dashboard-application"
version: "1.2.0"
title: "React dashboard application generation"
stages:
  - "plan"
  - "generate"
dependencies:
  - schema: "urn:literate-ai:schema:v1:skill-reference"
    skill_id: "frontend-application"
    version: "1.1.0"
    identity:
      schema: "urn:literate-ai:schema:v1:content-identity"
      algorithm: "sha256"
      digest: "38b1a9f0031943567c57e34dd3ccf6a271a5b58a613421d14a7cf43e50578ad9"
limitations:
  - "Do not re-fetch or discard already-loaded data when the user only changes which series are displayed or how the view is sorted; toggling display state must not force a new network round trip for data already in hand."
  - "Do not invent a chart or table interaction the specification did not request; only build the exact toggle/sort/view-switch behavior described."
  - "Do not copy the front-end parent's module, npm, language-axis, or panel-isolation rules; inherit them."
trust: "repository-reviewed"
---
# React dashboard application generation

This skill is a delta of `frontend-application`. Pin the parent in the recipe.
Generate a single-page dashboard over one tabular, time-series dataset (one row per
entity per observation, one column per statistic). The same underlying dataset backs
two interchangeable views the user can switch between at will: a graph view and a
table view.

## Series selection state

Track which statistic/resource columns are currently selected for display as one small
piece of local UI state (e.g. a set of column identifiers), independent of the fetched
data itself. Toggling a resource on or off adds or removes it from that set and must
never trigger a re-fetch of already-loaded data; the fetched dataset already contains
every column, and the selection only controls what is rendered. Reach for a shared
state mechanism (context, external store) only if more than one distant component needs
the same selection; a single dashboard's selection state normally lives in one
component and flows down as props.

## Graph view

Every currently selected statistic renders as its own series on one shared time-series
chart, so multiple resources overlay for direct visual comparison. Adding or removing a
series must not remount or reset the other series' rendering (zoom level, visible time
range). Give each series a stable, unique key derived from its identity (statistic name
plus entity, not its position in an array), since selection order changes.

## Table view

Every column in the table view is one statistic type the backend exports; every column
independently supports ascending and descending sort, and the active sort column and
direction are visible in the UI. Support ranking by more than one statistic at once
(a primary sort key with one or more tie-breaking secondary keys), not only a single
column at a time. Table rows use a stable unique key derived from entity identity, not
row position, so sorting does not corrupt row-local UI state (e.g. an expanded row).

## View switching

Switching between graph and table view is a display-mode toggle over the same already
fetched dataset and current selection/sort state; it must not discard the current
selection, sort order, or loaded data, and must not require a new fetch.

## Browser-observable dashboard state

Expose graph/table mode, selected series, active sort keys, row count, and independently
loading panel states through native controls and accessible names inherited by browser
instrumentation. Deterministic dashboard fixtures must exercise enough rows and series to
make sorting, scrolling, responsive collapse, and selection changes observable. A generated
test that only searches returned HTML for headings is not evidence that these interactions
render or work; leave stable seams for the parent's post-build browser verification.

Versions

The database has no other skills named react-dashboard-application.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 2b03dc5ae5a1 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 85react-application
    React JSX component structure, rendering, and local state as a JavaScript UI-framework Flavor. Use for Literate AI workflow tasks when ui-react is selected. Delta of the front-end parent.
  • 85frontend-application
    Fundamental browser front-end generation in JavaScript. Use for Literate AI workflow tasks that build a page UI. Nested React and WebMCP skills are deltas of this parent.
  • 91build-dashboard
    Build an interactive HTML dashboard — a Data Schematic — with charts, filters, and tables. Use when creating a dashboard, an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple…
  • 90dashboard
    Use this for a dashboard, metrics page, KPI tracker, scorecard, data visualization or recurring report: a page or scroll story of charts, numbers and tables of data, whatever the data and wherever it comes from. Read it when creating, filling, refreshing or revising one. You…
  • 91build-dashboard
    Build an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.
  • 91build-dashboard
    Build an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.