setup

Initialize projects with AI Coding Toolkit components and metadata.

39|5|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/benjaminshoemaker/ai_coding_project_base --skill setup-benjaminshoemaker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/benjaminshoemaker/ai_coding_project_base/tree/main/.claude/skills/setup
Command: npx skills add https://github.com/benjaminshoemaker/ai_coding_project_base --skill setup-benjaminshoemaker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize a new project with the AI Coding Toolkit, ensuring consistent setup across teams and projects.

Core Features & Use Cases

  • Idempotent setup: re-running the setup does not overwrite existing work and creates or updates required toolkit metadata.
  • Validation and provisioning: checks for START_PROMPTS.md and GENERATOR_PROMPT.md, creates necessary directories, and copies toolkit components (.claude, .workstream, .codex templates) as needed.
  • Codex integration: detects Codex CLI, optionally installs Codex skill packs, and can configure essential MCPs for browser verification.
  • Documentation and templates: generates CLAUDE.md when missing and provides a guided path to complete feature or greenfield initialization.

Quick Start

From the toolkit repository, run /setup <target-directory> to initialize a new or existing project. Confirm required prompts exist and review the generated toolkit metadata and component copies after completion.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I bootstrap a project with the AI Coding Toolkit?

The setup process validates required prompts like START_PROMPTS.md and GENERATOR_PROMPT.md, provisions necessary directories, and copies .claude, .workstream, and .codex templates to initialize your project.

Is project bootstrap setup idempotent if I run it multiple times?

This idempotent setup mechanism ensures that re-running initialization on an existing project only updates missing toolkit metadata without destroying your current files.

Does the setup toolkit support Codex integration for existing projects?

For existing projects, the Codex integration detects the CLI and configures MCPs for browser verification without disrupting your current project structure.

What files and directories does project initialization validate?

During component provisioning, the setup checks for required prompt files and generates CLAUDE.md to provide a guided path for completing feature or greenfield initialization.

Can I use this project setup tool to initialize an existing project directory?

Initializing an existing project directory works seamlessly because the setup command performs idempotent validation and only copies missing .claude, .workstream, or .codex templates.