agentleFS
UwayxtUwayxt/agent-skills/.agents/skills/dashboard-scaffolding-contract/SKILL.md

dashboard-scaffolding-contract

Skill4 starsChanged 3 months agoMITView on GitHub

Establish a manifest-driven dashboard shell. Use when designing scalable, module-agnostic layouts.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Delete the legacy hardcoded routing table.

    line 27
  2. Distinctive:

    All styling and typography use system tokens.

    line 34

≈ “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

Dashboard Scaffolding Contract

The dashboard shell is a strict contract, not a bespoke painting. It must blindly host modules via manifests without knowing their internal logic.

1. Establish the Shell Pattern

The shell pattern (sidebar+topbar, topbar-only, full-bleed) is selected via dashboard-layout-patterns. This skill implements that selection as a manifest-driven shell.

2. Apply Design Systems

Integrate visual and interaction foundations:

  • Styling: The shell's visual styling (sidebar colors, topbar height, grid gaps) references design-tokens, not raw values.
  • Typography: Nav item labels, section headers, and widget text follow the typography-system scale.
  • Motion: Sidebar collapse/expand uses micro-interaction-motion-design tokens. Widget card hover uses transition-hover.

3. Implement the Manifest Contract

Design the shell to parse module.manifest.json files. The shell reads navigation labels, icons, routes, and permissions directly from the registry, hardcoding nothing.

4. Retrofit Hardcoded Dashboards

For existing legacy dashboards:

  1. Extract hardcoded nav items into temporary JSON manifests.
  2. Replace hardcoded React/Vue nav components with a dynamic map function iterating over the manifests.
  3. Migrate the temporary manifests into standard module.manifest.json files per module.
  4. Delete the legacy hardcoded routing table.

Growth Contract

The shell guarantees: adding a valid module.manifest.json to the modules directory results in the module appearing in nav + shortcuts within one build/deploy cycle, with zero changes to the shell code.

Completion criteria

  • Shell layout reads purely from manifest data.
  • All styling and typography use system tokens.
  • Adding a new module requires zero shell code modification.

Output format

Produce the shell layout components and the manifest parsing utility logic.

Anti-patterns

  • Hardcoding a new nav item just this once because "it's faster."
  • Letting modules dictate shell layout rules.
  • Mixing shell state with module state.

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.