init

Creates a structured workspace directory for plugin development projects.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Ameng2001/astra-studio-plugins --skill init-ameng2001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init
Source: https://github.com/Ameng2001/astra-studio-plugins/tree/main/studio-core/skills/init
Command: npx skills add https://github.com/Ameng2001/astra-studio-plugins --skill init-ameng2001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It sets up the required studio/ workspace so plugin development can start consistently and with version control instead of being scattered across notes and ad-hoc files.

Core Features & Use Cases

  • Workspace initialization: Creates a ready-to-commit studio/ directory (config.yaml, changes/, agents/, archive/) when missing, and stops safely when it already exists.
  • Config bootstrapping: Copies the default config.yaml template from the skill’s template path to ensure standardized studio settings.
  • Plugin workflow readiness: Prepares the long-lived planning structure (design workspaces) and the place where generated implementation files will go.

Quick Start

Run /studio-core:init to create the studio/ directory in your current project and prepare it for planning your first plugin.

Frequently Asked Questions about init

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

FAQPage Schema
How do I set up a plugin development workspace with git tracking?

You can set up a git-tracked plugin development workspace by running an initialization command that creates a standardized studio/ directory structure with config.yaml and .gitkeep files to ensure version control for empty directories.

How do I bootstrap configuration for a new plugin studio project?

To bootstrap configuration for a new plugin studio project, the initialization process copies a default config.yaml template verbatim into the studio/ directory, ensuring standardized settings before development begins.

What happens if I run workspace initialization when a studio directory already exists?

If a studio directory already exists, the workspace initialization performs a pre-check and stops safely without overwriting your existing project files or configuration.

What directory structure is created when scaffolding a plugin development studio?

Scaffolding a plugin development studio creates a studio/ directory containing config.yaml, changes/, agents/, and archive/ subdirectories, preparing a long-lived planning structure for design and generated implementation files.

Do I need manual git commands to track empty directories in my studio workspace?

No, you do not need manual git commands to track empty directories because the workspace initialization automatically writes .gitkeep files into the empty studio subdirectories to ensure they are version controlled.

When should I use a studio workspace initialization for plugin development?

You should use studio workspace initialization when starting plugin development in a new or missing studio/ project to ensure consistent directory scaffolding and version control instead of scattered ad-hoc files.