building-project-visual-dashboards

Builds self-contained repository-owned human projections and Visual Maps explaining project systems, evidence, and next work.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/alsdmlals4-eng/Base --skill building-project-visual-dashboards-alsdmlals4-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: building-project-visual-dashboards
Source: https://github.com/alsdmlals4-eng/Base/tree/main/skills/building-project-visual-dashboards
Command: npx skills add https://github.com/alsdmlals4-eng/Base --skill building-project-visual-dashboards-alsdmlals4-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Project knowledge often gets scattered across links, raw AI/System metadata, and hidden subpages, forcing people to hunt through many pages just to understand what a project is and how it works. This Skill builds a self-contained, repository-owned human projection (Project Home) plus optional Visual Maps so a person can understand the project's direction, core loop, systems, project-specific data, visual state, evidence status, and next work from one main surface. ## Core Features & Use Cases - Self-contained Project Home: Structures a living GDD visual dashboard with a 30-second overview, 5-minute core Flow/System/Data/Visual section, and drilldown links, without replacing repository truth. - Project-specific core data modeling: Identifies the unique data each project needs (e.g., forging/durability for a blacksmith game, characters/factions for a fiction project) instead of forcing a universal game template. - Evidence and traceability binding: Separates PASS / PARTIAL / NOT_RUN / BLOCKED_UNVERIFIED states, preserves AI-System implementation detail, and verifies exact destination readback after writes. - Use Case: When resuming a game project after weeks away, use this Skill to rebuild the repository human projection so the Home alone explains the core loop, key systems, approved visuals, current blockers, and next work. ## Quick Start Ask the AI to rebuild or update the Project Home for a specific project as a self-contained repository human projection with its core loop, systems, project-specific data, evidence status, and next work.

Frequently Asked Questions about building-project-visual-dashboards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a self-contained project dashboard in a repository?

Use this Skill's modes: frame the project scope, map canonical sources, build the Home with a 30-second overview plus 5-minute core Flow/System/Data/Visual section, bind evidence status, then verify the destination with an exact readback. The Home must explain core direction without relying on drilldown links.

What is a repository human projection versus repository truth?

A human projection is a derived Markdown/PDF view that helps people understand, compare, and learn the project. Structured and runtime truth stays owned by the repository; the projection never becomes a duplicate canonical source.

Can I use Notion as the project dashboard destination?

Notion is allowed only as an explicitly approved and scoped V4 exception. The default path is a repository-owned human projection, and standalone HTML dashboards or localhost project-management UIs are prohibited as new authorities.

Why should project dashboards avoid universal game data templates?

Forcing identical sections like monsters, economy, and items onto every game weakens project identity and invents irrelevant content. The Skill requires identifying each project's actual core data first, such as forging and durability for a blacksmith game or characters and factions for a fiction project.

How does the Skill handle image generation requests?

Image generation follows a hard two-turn gate: present a text brief and stop, wait for explicit user approval in the next message, generate exactly one image, then stop again. Missing images are never auto-generated while organizing the Home.

What are the limitations of this dashboard approach?

It does not replace repository truth, runtime evidence, or AI-System implementation detail, and it forbids standalone HTML dashboards as current authority. Verification claims must distinguish PASS, PARTIAL, NOT_RUN, and BLOCKED_UNVERIFIED rather than overstating unrun checks.