ray-init

Automate Claude Code repository setup with CLAUDE.md and .claude/ scaffolding.

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/soumyaray/ray-ai-skills --skill ray-init
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ray-init
Source: https://github.com/soumyaray/ray-ai-skills/tree/main/ray-init
Command: npx skills add https://github.com/soumyaray/ray-ai-skills --skill ray-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the initial setup for Claude Code in a new repository, standardizing configuration and scaffolding so teams can start coding quickly.

Core Features & Use Cases

  • Automates /init-driven setup to create CLAUDE.md and the initial .claude/ directory with standard planning artifacts.
  • Updates .gitignore with an AI tooling block and optional Sideways manifests, ensuring clean workspaces across machines.
  • Creates CLAUDE.local.md for local planning and optionally generates cross-machine sync manifests (.swcopy and .swsymlink) for shared workflows.

Quick Start

Run the built-in /init to generate CLAUDE.md, move it into .claude/, update .gitignore, and create CLAUDE.local.md along with optional cross-machine sync manifests.

Frequently Asked Questions about ray-init

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

FAQPage Schema
How do I automate Claude Code project setup and scaffolding in a new repository?▼

You can automate Claude Code project setup by running the /init command to generate CLAUDE.md, move it into the .claude/ directory, and update .gitignore with an AI tooling block for clean workspaces.

What is the best way to initialize CLAUDE.md and .claude/ configuration files?▼

The best way to initialize CLAUDE.md and .claude/ configuration files is through an automated /init workflow that standardizes scaffolding and ensures consistent placement across new projects and onboarding workflows.

Does Claude Code setup update .gitignore for AI tooling and cross-machine sync?▼

Yes, Claude Code setup updates .gitignore with an AI tooling block and optionally generates cross-machine sync manifests like .swcopy and .swsymlink to maintain clean workspaces across different machines.

Can I create local planning files separately from shared Claude Code configuration?▼

Yes, you can create CLAUDE.local.md for local planning separately from shared configuration, allowing individual workspace organization while maintaining standard CLAUDE.md scaffolding in the .claude/ directory.

When do I need to generate cross-machine manifests for Claude Code repositories?▼

You need cross-machine manifests when sharing Claude Code workflows across different machines, optionally generating .swcopy and .swsymlink files during /init setup to synchronize planning artifacts and maintain consistent configurations.

Why does standardizing Claude Code scaffolding matter for team onboarding?▼

Standardizing Claude Code scaffolding matters because it ensures consistent CLAUDE.md placement and .claude/ directory structure, allowing teams to start coding quickly without manual configuration discrepancies during onboarding.