fix: move templates to examples/ to fix GitHub import

The importer reads ALL .json files in agents/, projects/, automations/
with no underscore filtering. The _template.json in automations/ used
an invalid action type (taskade_ai_prompt) that failed Zod validation.

Move all three templates to examples/ which is not a scanned directory.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: deanzaka

README.md

@@ -80,23 +80,20 @@ cortex/
 ├── cortex.tsk                  One-click import bundle (generated)
 │
 ├── agents/                     Intelligence layer
-│   ├── _template.json          Blank template — copy to create your own
 │   ├── strategist.json
 │   ├── editor.json
 │   ├── researcher.json
 │   ├── critic.json
 │   └── builder.json
 │
 ├── projects/                   Memory layer
-│   ├── _template.json
 │   ├── company-context.json
 │   ├── decision-log.json
 │   ├── playbook-*.json         (5 playbooks)
 │   ├── library-*.json          (2 libraries)
 │   └── welcome.json
 │
 ├── automations/                Reflexes layer
-│   ├── _template.json
 │   ├── daily-standup.json
 │   ├── decision-council.json
 │   ├── weekly-review.json
@@ -107,6 +104,11 @@ cortex/
 ├── apps/
 │   └── cortex.json             Genesis app (React SPA)
 │
+├── examples/                   Blank templates for creating new artifacts
+│   ├── agent-template.json
+│   ├── project-template.json
+│   └── automation-template.json
+│
 ├── docs/                       Guides
 │   ├── GENESIS-101.md
 │   ├── AGENT-GUIDE.md
@@ -127,8 +129,8 @@ cortex/
 
 Every JSON file is a standalone artifact. Swap any of them:
 
-- **Replace an agent** — copy `agents/_template.json`, write your persona prompt, delete the old one
-- **Add a project** — copy `projects/_template.json`, structure your content, save
+- **Replace an agent** — copy `examples/agent-template.json` into `agents/`, write your persona prompt, delete the old one
+- **Add a project** — copy `examples/project-template.json` into `projects/`, structure your content, save
 - **Modify a flow** — edit trigger/action pairs in `automations/*.json`
 - **Redesign the app** — edit the FileSystemTree in `apps/cortex.json`
 

docs/AGENT-GUIDE.md

@@ -81,4 +81,4 @@ Agents can be connected to projects as knowledge sources via the `variables` and
 - One agent, one job. Don't make a Swiss Army knife.
 - Test your prompt by reading it aloud. If it's vague when spoken, it's vague to the model.
 - Commands should cover the agent's 2-4 most common use cases.
-- Start with `agents/_template.json` and modify from there.
+- Start with `examples/agent-template.json` — copy it into `agents/` and modify from there.

docs/AUTOMATION-GUIDE.md

@@ -69,4 +69,4 @@ Actions can reference trigger data and previous action outputs using template sy
 - Start simple: one trigger, one action. Add complexity only when needed.
 - Use webhooks for integrations; use cron for recurring internal processes.
 - Template variables (`{{trigger.*}}`) make flows reusable.
-- Start with `automations/_template.json` and build from there.
+- Start with `examples/automation-template.json` — copy it into `automations/` and build from there.

docs/FORK-AND-CUSTOMIZE.md

@@ -24,7 +24,7 @@ Each file in `agents/` is a standalone agent definition. To modify one:
 4. Change `name`, `avatar`, and `introduction`
 
 To add a new agent:
-1. Copy `agents/_template.json` to `agents/my-agent.json`
+1. Copy `examples/agent-template.json` to `agents/my-agent.json`
 2. Fill in all fields
 3. Run `npm run validate` to check
 
@@ -41,7 +41,7 @@ Projects in `projects/` are structured knowledge. To modify:
 3. Keep the root structure intact — one top-level child with nested content
 
 To add a new project:
-1. Copy `projects/_template.json`
+1. Copy `examples/project-template.json` into `projects/`
 2. Replace the title and content nodes
 3. Set a descriptive avatar emoji
 
@@ -91,6 +91,6 @@ After importing, you can continue editing in Taskade's UI. When you want to expo
 ## Tips
 
 - Start by changing one thing, importing, and verifying it works
-- The `_template.json` files are ignored by the assembler (files starting with `_` are skipped)
+- Template files live in `examples/` — they are not scanned by the importer
 - Validation runs in CI on every push — broken JSON will be caught automatically
 - See [GENESIS-101.md](GENESIS-101.md) to understand how the four layers connect

docs/PROJECT-GUIDE.md

@@ -57,5 +57,5 @@ Each project is a node tree in Taskade's internal format (taskast):
 
 - Keep project names descriptive — agents use them to decide relevance
 - Prefer many focused projects over one mega-document
-- Start with `projects/_template.json` and build from there
+- Start with `examples/project-template.json` — copy it into `projects/` and build from there
 - Use the avatar emoji to make projects visually scannable

agents/_template.json examples/agent-template.jsonagents/_template.json renamed to examples/agent-template.json

@@ -26,12 +26,7 @@ function listJsonFiles(dirName) {
 
   return fs
     .readdirSync(dirPath, { withFileTypes: true })
-    .filter(
-      (entry) =>
-        entry.isFile() &&
-        entry.name.endsWith(".json") &&
-        !entry.name.startsWith("_"),
-    )
+    .filter((entry) => entry.isFile() && entry.name.endsWith(".json"))
     .map((entry) => path.join(dirPath, entry.name));
 }
 

automations/_template.json examples/automation-template.jsonautomations/_template.json renamed to examples/automation-template.json

@@ -13,12 +13,7 @@ function listJsonFiles(dirName) {
 
   return fs
     .readdirSync(dirPath, { withFileTypes: true })
-    .filter(
-      (entry) =>
-        entry.isFile() &&
-        entry.name.endsWith(".json") &&
-        !entry.name.startsWith("_"),
-    )
+    .filter((entry) => entry.isFile() && entry.name.endsWith(".json"))
     .map((entry) => entry.name)
     .sort();
 }