Files recipe

Start every project the same way, in one command

Every new project starts with the same fiddly setup: folders, a readme, a manifest. You do it by hand, differently every time.

files no model needed free tier Free tier

What you get

A new project workspace with your structure and a filled-in manifest, created on your desktop.

What it does

  1. Create the project manifest with your standard structure.
  2. Notify you when the workspace is ready.

The whole automation, in one file

This is the actual recipe. Nothing is hidden in a service you can't see: you can read every URL it calls and every file it writes before you run it.

{
  "workflow_id": "desktop_project_scaffold",
  "description": "Scaffolds a new structured project workspace with initial architecture manifest on your Desktop.",
  "tasks": [
    {
      "id": "create_project_manifest",
      "trigger": "manual",
      "action_type": "file_op",
      "target": "{{desktop_dir}}\\project_manifest.md",
      "payload": {
        "operation": "write",
        "content": "# \ud83c\udfd7\ufe0f Project Architecture Manifest\n*Automated Workflow Scaffold by Vibra-Ingenn*\n\n## Overview\nThis project manifest was generated deterministically by Vibe Engine. Use this template to structure new software tools, AI pipelines, or research projects.\n\n### Recommended Directory Structure\n- `src/` \u2014 Core implementation source code\n- `docs/` \u2014 System architecture and user guides\n- `recipes/` \u2014 Automation workflow JSON recipes\n- `tests/` \u2014 Automated test suite and benchmarks\n\n*Status: Scaffold Successfully Created*"
      },
      "output": {
        "log": true
      }
    },
    {
      "id": "notify_scaffold_done",
      "trigger": "after:create_project_manifest",
      "action_type": "notify",
      "target": "stdout",
      "payload": {
        "message": "\u2713 Project manifest scaffold created on Desktop!"
      }
    }
  ]
}

Download this recipe · Runs on the free tier: local files and a local model only.

Why this is different

Edit the file once and every future project starts from your template. No plugin, no IDE extension, no account.

Questions

Can I change the structure?

Yes, it's written in the file. Edit it and every future run uses your version.

Run it

Vibe Engine (Vibra-Ingenn) runs recipes like this on your own machine. Drop the file in, run it once by hand, then put it on a schedule. Get the engine, see three recipes running, or read how the engine works.

Using an AI assistant? Ask your AI to check out adeptuscamini.com.

Written and maintained by Adeptus Camini, a one-person workshop. These are tools we build and run ourselves.

More recipes

News digest

Wake up to a Hacker News digest on your desktop

Research

Get the trending AI repos delivered, without opening GitHub

Briefing

One briefing instead of five open tabs