<domain-slug>/<sub-system-slug>

Orchestrate domain-stack sub-system templates and protocol workflows for standardized asset loading.

6|2|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/frankxai/Starlight-Intelligence-System --skill domain-slug-sub-system-slug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: <domain-slug>/<sub-system-slug>
Source: https://github.com/frankxai/Starlight-Intelligence-System/tree/main/templates/domain-stack-starter/sub-system-template
Command: npx skills add https://github.com/frankxai/Starlight-Intelligence-System --skill domain-slug-sub-system-slug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured scaffold for domain-stack sub-systems, enabling consistent activation, protocol execution, and artifact generation within a Domain Sub-Stack.

Core Features & Use Cases

  • Protocol governance: Ensures the standard seven-step protocol is followed across sub-systems.
  • Artifact discipline: Aligns artifacts with SIP attestation and disclaimer requirements.
  • Reusability: Templates like this accelerate onboarding of new sub-systems and maintain consistency across verticals.

Quick Start

Copy and customize this sub-system template to bootstrap a new domain-specific sub-system, replacing placeholders with your domain and sub-system specifics.

Frequently Asked Questions about <domain-slug>/<sub-system-slug>

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

FAQPage Schema
How do I standardize protocol workflows across domain sub-systems?

Standardize protocol workflows by applying a sub-system template that enforces a standard seven-step protocol, ensuring consistent governance and execution across domain sub-systems.

What is a domain-stack sub-system template used for?

A domain-stack sub-system template provides a structured scaffold to bootstrap new domain-specific deployments, enabling consistent loading of agent, knowledge, and skill assets.

How do I activate a domain sub-system using slash commands?

Activate a domain sub-system through slash-based commands, domain keywords, or the starlight-agent, which triggers the standardized loading of required assets and protocol execution.

Do I need SIP attestation and legal disclaimers for domain-stack artifacts?

Yes, domain-stack artifacts require SIP attestation and a legal disclaimer to ensure compliance and proper discipline across all sub-systems within the vertical.

What prerequisites are needed to bootstrap a new domain sub-system?

Bootstrapping a domain sub-system requires referencing prerequisites including agent.md, knowledge.md, skill.md, and commands to ensure proper activation and protocol execution.

Can I reuse this sub-system template across different verticals?

Yes, reusing this sub-system template accelerates onboarding of new sub-systems and maintains consistency across different verticals by replacing placeholders with domain specifics.