bl-init

Automates BrickLayer 2.0 project bootstrapping via guided questionnaire and template copying.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Nerfherder16/BrickLayer --skill bl-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bl-init
Source: https://github.com/Nerfherder16/BrickLayer/tree/main/.claude/skills/bl-init
Command: npx skills add https://github.com/Nerfherder16/BrickLayer --skill bl-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the initial setup of a BrickLayer 2.0 project, replacing manual scaffolding with a guided bootstrap workflow.

Core Features & Use Cases

  • Guided questionnaire collects system name, primary goal, and target path.
  • Copies the appropriate project template based on the chosen goal and creates a ready-to-use project scaffold.
  • Prevents accidental overwrites by enforcing a non-overwrite policy and validating destination paths.
  • Generates project.json with essential metadata and prints clear startup instructions for next steps.

Quick Start

Provide the three required inputs (system name, primary goal, target path) when prompted to bootstrap a BrickLayer 2.0 project.

Frequently Asked Questions about bl-init

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

FAQPage Schema
How do I bootstrap a BrickLayer 2.0 project from a template?

Bootstrapping a BrickLayer 2.0 project requires three inputs: system name, primary goal, and target path. The tool uses these to select a template, copy scaffolding, generate project.json, and print next steps.

What is automated project scaffolding for BrickLayer 2.0?

Automated project scaffolding replaces manual setup by copying a predefined template based on your primary goal. It creates a ready-to-use BrickLayer 2.0 project structure with essential project.json metadata.

Can I use an existing directory path for BrickLayer project setup?

You must provide an empty target path because the tool enforces a non-overwrite policy. It validates destination paths during scaffolding to prevent accidental file overwrites during the BrickLayer project setup.

What do I need to start a BrickLayer 2.0 project setup?

Starting a BrickLayer 2.0 project setup requires providing a system name, primary goal, and target path. The guided questionnaire collects these inputs to automate template selection and configuration.

Does project scaffolding include a project.json configuration file?

Yes, the scaffolding process automatically generates a project.json configuration file with essential metadata. The tool creates this file during template copying to ensure your project is properly configured.

What are the limitations of automated BrickLayer project bootstrapping?

A key limitation is the strict non-overwrite policy, which prevents bootstrapping into directories containing existing files. The tool is designed solely for initial project creation and does not update existing BrickLayer 2.0 projects.