project-init

Automates Cloudflare multi-worker fork personalization including IDs, names and branding.

10|Updated May 22, 2025
One-click install
npx skills add https://github.com/firtoz/cf-multiworker-starter-kit --skill project-init-firtoz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-init
Source: https://github.com/firtoz/cf-multiworker-starter-kit/tree/main/agents/skills/project-init
Command: npx skills add https://github.com/firtoz/cf-multiworker-starter-kit --skill project-init-firtoz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Personalizes a fork of this Cloudflare multi-worker monorepo—Alchemy application ids (await alchemy literals + --app), npm workspace names (--filter), README, and UI—so Cloudflare dashboards and Turbo filters are not confusing. Use when the user created a repo from the template, wants to deploy their own app, or asks to rename workers, rebrand, or remove generic starter kit copy. Skip when developing the upstream starter kit (origin URL contains firtoz/cf-multiworker-starter-kit; canonical https://github.com/firtoz/cf-multiworker-starter-kit) unless the user explicitly asks.

Core Features & Use Cases

  • Guard: If the upstream is detected, the flow is skipped unless explicitly requested to rename or template work.
  • Aligns Alchemy IDs and workspace names across the fork (e.g., CF_STARTER_APPS, alchemy(...), and package.json names) to prevent drift.
  • Provides guidance for forking, renaming workers, branding, and updating docs to reflect the forked project.

Quick Start

Run the project-init flow after forking to apply your app IDs, workspace names, and branding, then verify dashboards reflect your fork.

Frequently Asked Questions about project-init

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

FAQPage Schema
How do I personalize a forked Cloudflare multi-worker starter kit?

To personalize a forked Cloudflare multi-worker starter kit, run the project-init flow to automatically update Alchemy app IDs, npm workspace names, and UI branding to reflect your own project. This ensures Cloudflare dashboards and Turbo filters align correctly with your repository.

Why do my Alchemy app IDs and Cloudflare workspace names drift after forking?

Alchemy app IDs and Cloudflare workspace names drift after forking because upstream template identifiers remain unchanged in the codebase. Aligning the alchemy.run.ts app IDs, CF_STARTER_APPS keys, and package.json workspace names prevents misconfiguration and dashboard confusion.

Can I rename workers and rebrand my Cloudflare monorepo automatically?

Yes, you can rename workers and rebrand your Cloudflare monorepo automatically by applying the project-init flow. It replaces generic starter kit copy and updates configuration files to ensure consistent alignment across your Alchemy application and npm workspaces.

Does the project-init flow run on the upstream cf-multiworker-starter-kit repository?

No, the project-init flow skips automatically if it detects the upstream cf-multiworker-starter-kit repository origin URL. It only runs on the upstream template if you explicitly request renaming or templating work to avoid modifying the canonical codebase.

What is the best way to update Alchemy application IDs in a forked Cloudflare project?

The best way to update Alchemy application IDs in a forked Cloudflare project is to use an automation flow that synchronizes await alchemy literals, --app arguments, and CF_STARTER_APPS keys. This prevents drift between your configuration files and Cloudflare dashboards.

When do I need to update Cloudflare starter kit branding and workspace names?

You need to update Cloudflare starter kit branding and workspace names immediately after forking the upstream template. Applying these updates before deploying your own app ensures that Turbo filters, npm workspaces, and Cloudflare dashboards reflect your specific forked project.