space-portfolio-schema

Create and validate typed Space Portfolio schemas for Systems, Planets, and Moons.

Updated Apr 2, 2026

Search Tags:#documentation #validation #schema #portfolio #types #data-model #systems

Ready to run

npx skills add https://github.com/DSalischiker/portfolio-space-exploration --skill space-portfolio-schema

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: space-portfolio-schema
Source: https://github.com/DSalischiker/portfolio-space-exploration/tree/main/.agents/skills/space-portfolio-schema
Command: npx skills add https://github.com/DSalischiker/portfolio-space-exploration --skill space-portfolio-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Space Portfolio Schema provides a structured, typed model for organizing projects, experiences, and skills as System nodes with hierarchical Planet and Moon components. It ensures consistent data definitions, promotes best practices, and guides contributors to maintain a cohesive portfolio dataset across the codebase.

Core Features & Use Cases

Three-level data hierarchy (System -> Planet -> Moon) to represent high-level projects, facets, and sub-details, all stored in src/data/systems.ts and typed by src/types/systems.ts.
Clear core schema rules that enforce required fields (id, name, position, type, starColor, planets) and provide optional metadata for SEO, discovery, and relationships.
Guidance and validation workflows for adding new systems, auditing existing data, and documenting schema decisions.

Quick Start

Create a new System entry in src/data/systems.ts for a project with an id, name, valid position, type 'project', a hex starColor, and at least one Planet describing the overview.

Frequently Asked Questions about space-portfolio-schema

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

FAQPage Schema

How do I structure a data model for a portfolio with projects and sub-components?▼

A portfolio data model uses a three-level hierarchy of System, Planet, and Moon nodes to represent high-level projects, facets, and sub-details. This structure ensures consistent data definitions across your codebase.

What required fields must be enforced when validating a space portfolio schema?▼

Schema validation enforces required fields including id, name, position, type, starColor, and planets for each System entry. Planet and Moon structures must also follow specific type definitions to pass validation.

How do I add a new system to a typed space portfolio dataset?▼

To add a new system, create an entry in your systems data file with a valid id, name, position, type, hex starColor, and at least one Planet. Validate the new entry against your core schema rules.

Can I include optional metadata for SEO and cross-file references in my portfolio schema?▼

Optional metadata can be included in your portfolio schema to support SEO, discovery, and cross-file relationships. These fields supplement the required data without breaking core validation rules.

What is the best way to document schema decisions for a hierarchical portfolio dataset?▼

Documenting schema decisions involves recording best practices and validation workflows for auditing existing data. This guides contributors to maintain a cohesive dataset across the codebase.

Why does my space portfolio validation fail when adding a new project system?▼

Validation fails when a new project system is missing required fields or contains incorrect types. Ensure your entry has a valid position, type 'project', a hex starColor, and correctly structured Planet components.