create-recipe

To turn an existing project into a reusable blueprint, you analyze its architecture, patterns, and integration glue, then generate a recipe skill that captures these elements for replication in a new codebase. This process extracts the working project into a repeatable format.

A project recipe is a reusable skill that captures a project's architecture, patterns, and implementation details. You need one when you want to extract a working project or subsystem into a repeatable blueprint for cross-repo collaboration and new codebase setup.

Extracting a subsystem recipe for cross-repo collaboration involves cloning the source project into a temporary workspace, analyzing its integration glue, and writing a new SKILL.md into the canonical recipes repository to produce a repeatable blueprint.

The best way to document integration glue between technologies is to analyze the project subsystem and produce a recipe skill that captures the architecture and patterns, generating a phase-driven skeleton in the recipes repository for replication.

Yes, creating a new recipe skill requires cloning the canonical recipes repository. The workflow writes the new SKILL.md file into the plugins/recipes/skills directory structure and follows a phased process from setup through publishing.

Yes, you can create a subsystem recipe instead of a full project recipe. The analysis process supports extracting specific subsystems by documenting their architecture, patterns, and integration glue to guide targeted cross-repo collaboration.