Skip to content
Back to skills

Ssot Dashboard

ASecurity

Designs and structures the Movemental living SSOT dashboard (HTML/CSS/JS). Use when creating or refining the single-source-of-truth dashboard, sidebar and content structure, or when aligning Movemental vision and docs into a docs-first, token-based, agent-friendly dashboard.

  • 2 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added October 26, 2026
designgoreactrails

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 26, 2026

npx -y skills add JoshuaShepherd/my-skills --skill ssot-dashboard --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ssot Dashboard?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ssot Dashboard
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/joshuashepherd-ssot-dashboard/badge)](https://www.skillsdirectory.com/skills/joshuashepherd-ssot-dashboard)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ssot-dashboard
description: Designs and structures the Movemental living SSOT dashboard (HTML/CSS/JS). Use when creating or refining the single-source-of-truth dashboard, sidebar and content structure, or when aligning Movemental vision and docs into a docs-first, token-based, agent-friendly dashboard.
---

# Movemental SSOT Dashboard

## When to Use

- User asks to design or refine the "SSOT dashboard," "living source of truth," or "dashboard as first link in the chain."
- User works in `ssot-dashboard/` or asks about sidebar structure, content sections, or Movemental vision in dashboard form.
- User wants to align `_docs` content into one navigable, well-designed dashboard for humans and agents.

## Instructions

1. **Ground in Movemental docs**  
   Read or reference: `_docs/site-docs/01_site_purpose_and_order.md`, `10_complete_site_map.md`, `_docs/type/11_PLATFORM_ARCHITECTURE_AT_A_GLANCE.md`, `_docs/ai-vision/01_ai-vision-overview.md`, `_docs/ai-vision/04_ui-ux-proposal.md`, `_docs/_guides/typography-2026.md`, `_docs/business-docs/00_foundation/README.md`.

2. **Propose or refine dashboard structure**  
   Sidebar sections should map to: Foundation (purpose, order), Site order & sitemap, Platform & type safety, AI vision, Design system & tokens. Main area shows one section at a time as the living doc.

3. **Apply docs-first design**  
   Use typography and spacing for hierarchy; token-based components (cards, sections); layout that is scannable and reading-optimized. Keep semantic HTML and clear headings/IDs for agents.

4. **Ensure dual audience**  
   Output must be usable by both humans (readable, clear nav) and agents (semantic structure, stable landmarks, optional meta like "Last updated").

## Sidebar Taxonomy (Canonical)

- **Foundation** — Why Movemental exists, scope, governance.
- **Core Story / VIM** — 500-word anchor story; Vision (what will change), Intention (what it will take), Means (how we'll do it); Dallas Willard VIM.
- **Site order & sitemap** — Fit → Why → Path → Credibility → Knowledge → Learning → Access → Homepage.
- **Platform & type safety** — Stack, six-layer chain, multi-tenant.
- **AI vision** — Movemental Intelligence, amplification not replacement, network-aware.
- **Design system & tokens** — Typography, color, component tokens.
- **Value proposition** — Primary/segment value props, one-liner, Start with Why.
- **Audience** — Who we serve, naming, demographics, psychographic, six archetypes.
- **Principles** — Four non-negotiables, ranked values (content guardrails).
- **Narrative & story** — Story we tell, pricing language, invitation.
- **Canonical copy** — Hero, Sound familiar, key page prose (master for React).
- **Voice & tone** — Platform voice; what we avoid; leader-specific refs.
- **Content types** — Article, course, book, video, podcast; creation rules.

## Output Conventions

- Edit or add files under `ssot-dashboard/`: `index.html`, `css/*.css`, `js/main.js`, `content/*.html`.
- Preserve token-based styling; do not hardcode colors or type sizes.
- For new content sections, add a corresponding sidebar entry and a `content/<section>.html` (or inlined section in `index.html`).

## Reference

- Full doc paths and persona: see project rule "SSOT dashboard co-creator" (globs: `**/ssot-dashboard/**`, `**/design-system/**`).
- For detailed Movemental pillars and governance: [reference.md](reference.md).

Files in this skill

  • SKILL.md3.4 KB
  • reference.md1.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.