cat-init

Scaffold CaT projects with config files and GitHub Actions workflows.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/rleroi/catspec --skill cat-init
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cat-init
Source: https://github.com/rleroi/catspec/tree/main/skills/cat-init
Command: npx skills add https://github.com/rleroi/catspec --skill cat-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up a new CaT (Code as Text) project requires manually creating multiple configuration files, defining provider integrations, and setting up CI workflows for transpilation, which is time-consuming and prone to human error for developers.

Core Features & Use Cases

  • Interactive Guided Setup: Walks users through stack selection (framework, database, auth, styling, etc.) and provider configuration with sensible POC defaults, including a "use defaults" option for fast setup.
  • Automated File Generation: Creates all required CaT project files out of the box: cat.config.yaml with transpiler settings and provider entries, bacon/system.md with system identity and stack metadata, and a GitHub Actions workflow for bacon-driven transpilation.
  • Safe Existing File Handling: Detects pre-existing CaT files and prompts users to skip, overwrite, or abort operations to prevent accidental loss of custom configuration. Use Case: A developer starting a new Next.js + Supabase project can use this skill to get fully configured CaT scaffolding and CI setup in under a minute, instead of manually creating and configuring 3+ separate files.

Quick Start

Use the cat-init skill to scaffold a new CaT project for a Next.js app with Supabase database and authentication, using the default POC stack and preconfigured GitHub Actions transpile workflow.

Frequently Asked Questions about cat-init

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

FAQPage Schema
How do I scaffold a new Code as Text project without manual file setup?▼

Scaffolding a Code as Text project involves generating multiple configuration files and CI workflows. An interactive initializer automates this setup by creating cat.config.yaml, bacon/system.md, and GitHub Actions workflows based on your stack selection.

What files are required for a bacon-driven transpilation workflow?▼

A bacon-driven transpilation workflow requires cat.config.yaml for transpiler settings and provider entries, bacon/system.md for system identity and stack metadata, and a GitHub Actions workflow configuration to automate the process.

Can I add CaT project structure to an existing repository without losing custom files?▼

You can add CaT structure to existing repositories safely because the initializer detects pre-existing CaT files and prompts you to skip, overwrite, or abort operations, preventing accidental loss of custom configuration.

How do I configure CI workflows for a new Next.js and Supabase project?▼

Configuring CI workflows for Next.js and Supabase involves selecting your stack during interactive setup to automatically generate a GitHub Actions workflow for bacon-driven transpilation with preconfigured provider defaults.

Does interactive project initialization support custom stack and provider selection?▼

Interactive project initialization supports custom stack and provider selection by walking you through framework, database, and auth options, while also offering a 'use defaults' option for fast setup with POC defaults.