skills.rest
AAbdulghany
AAbdulghanyCOMMUNITY
Explore all skills by this author →
𝕏@AAbdulghanyyGitHub

setup

Bootstrap a new ApexYard fork through a three-exchange setup.

Updated Apr 15, 2026
Search Tags:#onboarding#setup#portfolio#fork#apexyard#split-portfolio
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill setup-aabdulghany
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/setup
Command: npx skills add https://github.com/AAbdulghany/fms --skill setup-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up a new ApexYard fork for a production-ready workflow can be error-prone and time-consuming. This skill guides teams through a deterministic, first-run bootstrap that configures onboarding, portfolio paths, and environment defaults, ensuring a clean, auditable starting point.

Core Features & Use Cases

  • Deterministic first-run bootstrap for ApexYard forks, reducing setup drift.
  • Supports both single-fork bootstraps with in-fork defaults and split-portfolio migrations using a private portfolio repository.
  • Generates and validates onboarding.yaml, registry paths, and workspace structures, ensuring auditable starting state.
  • Use Case: A team forks ApexYard and wants a fast, repeatable setup that aligns all developers and operators from day one.

Quick Start

Run /setup to bootstrap a fresh ApexYard fork with a guided first-run and optional split-portfolio setup.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I bootstrap a new ApexYard fork with a split-portfolio setup?▼

A deterministic first-run bootstrap for ApexYard forks reduces setup drift by generating and validating onboarding.yaml, registry paths, and workspace structures. This ensures all developers and operators align from day one with an auditable starting state.

What is the guided describe propose confirm workflow for repository onboarding?▼

The setup process supports both single-fork bootstraps with in-fork defaults and split-portfolio migrations using a private portfolio repository. It relies on the framework's onboarding templates and .claude/hooks helpers to validate the configuration.

Do I need a private portfolio repository to set up an ApexYard fork?▼

The setup skill relies on the framework's onboarding templates, .claude/hooks helpers, and portfolio path resolution to generate a robust initial state. These components work together to ensure deterministic configuration and reduce setup drift.

Why does ApexYard fork setup require validating onboarding.yaml and registry paths?▼

The setup generates and validates onboarding.yaml, registry paths, and workspace structures to create a robust, auditable initial state. This deterministic approach prevents the error-prone manual configuration that typically slows down production-ready workflows.

Related Skills

Explore More Software Engineering Skills→
me2reshme2resh
489

setup

Configure onboarding.yaml and validate portfolio layout for ApexYard forks.

Community
Advanced
kaptinlinkaptinlin
23

project-initializing

Orchestrate initial setup of single-module and multi-module Go repositories.

Community
Intermediate
AAbdulghanyAAbdulghany

update

Sync an ApexYard fork with upstream via merge or rebase and migrations.

Community
Advanced
me2reshme2resh
489

split-portfolio

Migrate ApexYard adopters from a public fork to a split-portfolio layout with private sibling repo.

Community
Advanced