@agiflowai/scaffold-mcp 1.0.24 → 1.0.26

package/README.md

@@ -2,17 +2,7 @@
 
 > MCP server for scaffolding applications with templates and feature generators
 
-Generate consistent, convention-following code for your AI coding agents. scaffold-mcp provides templates for common patterns (routes, components, services) so agents don't write boilerplate from scratch.
-
-## Why Use This?
-
-When you ask an AI agent to "add a new page," it generates working code—but not necessarily code that follows your team's patterns. scaffold-mcp solves this by:
-
-1. **Providing templates** for common patterns your team has standardized
-2. **Enforcing structure** so every route, component, or service looks the same
-3. **Reducing boilerplate** by generating the repetitive parts automatically
-
-Think of it as "Rails generators" or "Angular schematics" for any stack.
+Use this server to generate projects and feature boilerplate from template-defined scaffolds.
 
 ---
 
@@ -45,7 +35,7 @@ Add to your MCP config (`.mcp.json`, `.cursor/mcp.json`, etc.):
 
 ### 3. Start Using
 
-Your AI agent now has access to scaffolding tools:
+Your agent can now call scaffold tools:
 
 ```
 You: "Create a new Next.js app called dashboard"
@@ -93,9 +83,9 @@ apps/
 │           └── page.tsx                   └── src/             ← Template files (.liquid)
 ```
 
-1. **Templates define patterns**: Each template has a `scaffold.yaml` that defines boilerplates and features
-2. **Projects reference templates**: Your `project.json` has a `sourceTemplate` field pointing to the template
-3. **Tools generate code**: MCP tools read the template and generate files in your project
+1. Templates define boilerplates and features in `scaffold.yaml`
+2. Projects reference templates with `sourceTemplate`
+3. Tools read the template and generate files
 
 ---
 
@@ -162,6 +152,22 @@ npx @agiflowai/scaffold-mcp mcp-serve \
   --fallback-tool-config '{"model":"claude-sonnet-4-6"}'
 ```
 
+For `.toolkit/settings.yaml` or `.toolkit/settings.local.yaml`, you can define multiple ordered fallbacks:
+
+```yaml
+scaffold-mcp:
+  mcp-serve:
+    fallbacks:
+      - tool: gemini-cli
+        config:
+          model: gemini-2.0-flash
+      - tool: codex
+        config:
+          model: gpt-5.2-mini
+```
+
+The first valid entry is used when `fallbackTool` is not set.
+
 | Option | Description | Default |
 |--------|-------------|---------|
 | `-t, --type` | Transport: `stdio`, `http`, `sse` | `stdio` |
@@ -170,13 +176,13 @@ npx @agiflowai/scaffold-mcp mcp-serve \
 | `--admin-enable` | Enable template creation tools | `false` |
 | `--prompt-as-skill` | Render MCP prompts with Claude Code skill front matter, exposing them as `/skill` commands | `false` |
 | `--fallback-tool` | LLM tool for scaffold operations (`claude-code`, `gemini-cli`, `codex`) | disabled |
-| `--fallback-tool-config` | JSON config for the fallback tool (e.g., `{"model":"claude-sonnet-4-6"}`) | `{}` |
+| `--fallback-tool-config` | JSON config for the CLI fallback tool; settings files may also use ordered `fallbacks` entries | `{}` |
 
 ---
 
 ## Creating Custom Templates
 
-### Option 1: Using Admin Tools (Recommended)
+### Option 1: Using Admin Tools
 
 Ask your AI agent:
 ```
@@ -184,8 +190,8 @@ Ask your AI agent:
 ```
 
 The agent will use:
-1. `generate-boilerplate` - Creates scaffold.yaml entry
-2. `generate-boilerplate-file` - Adds template files
+1. `generate-boilerplate`
+2. `generate-boilerplate-file`
 
 ### Option 2: Manually
 

package/dist/{ListScaffoldingMethodsTool-Cx-0gpV3.mjs → ListScaffoldingMethodsTool-D6BkKQyK.mjs}

@@ -974,7 +974,7 @@ Please follow this **instruction**: \n ${method.instruction ? this.processScaffo
 
 //#endregion
 //#region src/instructions/tools/list-scaffolding-methods/description.md?raw
-var description_default = "Lists all available scaffolding methods (features) that can be added to an existing project{% if not isMonolith %} or for a specific template{% endif %}.\n\nThis tool:\n{% if isMonolith %}\n- Reads your project's sourceTemplate from toolkit.yaml at workspace root\n{% else %}\n- Reads the project's sourceTemplate from project.json (monorepo) or toolkit.yaml (monolith), OR\n- Directly uses the provided templateName to list available features\n{% endif %}\n- Returns available features for that template type\n- Provides variable schemas for each scaffolding method\n- Shows descriptions of what each method creates\n\nUse this FIRST when adding features to understand:\n- What scaffolding methods are available\n- What variables each method requires\n- What files/features will be generated\n\nExample methods might include:\n- Adding new React routes (for React apps)\n- Creating API endpoints (for backend projects)\n- Adding new components (for frontend projects)\n- Setting up database models (for API projects)\n";
+var description_default = "Lists all available scaffolding methods (features) that can be added to an existing project{% if not isMonolith %} or for a specific template{% endif %}.\n\nThis tool:\n{% if isMonolith %}\n- Reads your project's sourceTemplate from .toolkit/settings.yaml at workspace root\n{% else %}\n- Reads the project's sourceTemplate from project.json (monorepo) or .toolkit/settings.yaml (monolith), OR\n- Directly uses the provided templateName to list available features\n{% endif %}\n- Returns available features for that template type\n- Provides variable schemas for each scaffolding method\n- Shows descriptions of what each method creates\n\nUse this FIRST when adding features to understand:\n- What scaffolding methods are available\n- What variables each method requires\n- What files/features will be generated\n\nExample methods might include:\n- Adding new React routes (for React apps)\n- Creating API endpoints (for backend projects)\n- Adding new components (for frontend projects)\n- Setting up database models (for API projects)\n";
 
 //#endregion
 //#region src/tools/ListScaffoldingMethodsTool.ts

package/dist/{ListScaffoldingMethodsTool-CkIkgP_u.cjs → ListScaffoldingMethodsTool-DBwZzJTA.cjs}

@@ -1003,7 +1003,7 @@ Please follow this **instruction**: \n ${method.instruction ? this.processScaffo
 
 //#endregion
 //#region src/instructions/tools/list-scaffolding-methods/description.md?raw
-var description_default = "Lists all available scaffolding methods (features) that can be added to an existing project{% if not isMonolith %} or for a specific template{% endif %}.\n\nThis tool:\n{% if isMonolith %}\n- Reads your project's sourceTemplate from toolkit.yaml at workspace root\n{% else %}\n- Reads the project's sourceTemplate from project.json (monorepo) or toolkit.yaml (monolith), OR\n- Directly uses the provided templateName to list available features\n{% endif %}\n- Returns available features for that template type\n- Provides variable schemas for each scaffolding method\n- Shows descriptions of what each method creates\n\nUse this FIRST when adding features to understand:\n- What scaffolding methods are available\n- What variables each method requires\n- What files/features will be generated\n\nExample methods might include:\n- Adding new React routes (for React apps)\n- Creating API endpoints (for backend projects)\n- Adding new components (for frontend projects)\n- Setting up database models (for API projects)\n";
+var description_default = "Lists all available scaffolding methods (features) that can be added to an existing project{% if not isMonolith %} or for a specific template{% endif %}.\n\nThis tool:\n{% if isMonolith %}\n- Reads your project's sourceTemplate from .toolkit/settings.yaml at workspace root\n{% else %}\n- Reads the project's sourceTemplate from project.json (monorepo) or .toolkit/settings.yaml (monolith), OR\n- Directly uses the provided templateName to list available features\n{% endif %}\n- Returns available features for that template type\n- Provides variable schemas for each scaffolding method\n- Shows descriptions of what each method creates\n\nUse this FIRST when adding features to understand:\n- What scaffolding methods are available\n- What variables each method requires\n- What files/features will be generated\n\nExample methods might include:\n- Adding new React routes (for React apps)\n- Creating API endpoints (for backend projects)\n- Adding new components (for frontend projects)\n- Setting up database models (for API projects)\n";
 
 //#endregion
 //#region src/tools/ListScaffoldingMethodsTool.ts

package/dist/{claudeCode-DBoEGOeu.cjs → claudeCode-B6CWgRYJ.cjs}

@@ -1,5 +1,6 @@
-const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-CkIkgP_u.cjs');
-require('./tools-CC-lrhQ8.cjs');
+const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-DBwZzJTA.cjs');
+require('./tools-DsnQImJ1.cjs');
+const require_shared = require('./shared-fkWett9D.cjs');
 let __agiflowai_aicode_utils = require("@agiflowai/aicode-utils");
 let node_path = require("node:path");
 node_path = require_ListScaffoldingMethodsTool.__toESM(node_path);
@@ -188,25 +189,10 @@ var UseScaffoldMethodHook = class {
 				message: "Not a tool use event"
 			};
 			const filePath = context.tool_input?.file_path;
-			if (!filePath || context.tool_name !== "Write") return {
+			const absoluteFilePath = await require_shared.resolveNewFileWriteTarget(context.cwd, context.tool_name, filePath);
+			if (!absoluteFilePath || !filePath) return {
 				decision: __agiflowai_hooks_adapter.DECISION_SKIP,
-				message: "Not a file write operation"
-			};
-			const absoluteFilePath = node_path.default.isAbsolute(filePath) ? filePath : node_path.default.join(context.cwd, filePath);
-			if (!absoluteFilePath.startsWith(context.cwd + node_path.default.sep) && absoluteFilePath !== context.cwd) return {
-				decision: __agiflowai_hooks_adapter.DECISION_SKIP,
-				message: "File is outside working directory - skipping scaffold method check"
-			};
-			let fileExists = false;
-			try {
-				await node_fs_promises.default.access(absoluteFilePath);
-				fileExists = true;
-			} catch (accessErr) {
-				if (!(accessErr instanceof Error && "code" in accessErr && accessErr.code === "ENOENT")) throw accessErr;
-			}
-			if (fileExists) return {
-				decision: __agiflowai_hooks_adapter.DECISION_SKIP,
-				message: "File already exists - skipping scaffold method check"
+				message: "Not a new file write operation"
 			};
 			const executionLog = new __agiflowai_hooks_adapter.ExecutionLogService(context.session_id);
 			if (await executionLog.hasExecuted({
@@ -255,9 +241,7 @@ var UseScaffoldMethodHook = class {
 					message: "No scaffolding methods are available for this project template. You should write new files directly using the Write tool."
 				};
 			}
-			let message = "Before writing new files, use `use-scaffold-method` if any of these match your needs:\n\n";
-			for (const method of data.methods) message += `- **${method.name}**: ${method.description || "No description available"}\n`;
-			if (data.nextCursor) message += `\n_More methods available (cursor: "${data.nextCursor}")._\n`;
+			const message = require_shared.formatScaffoldMethodsHookMessage(data.methods);
 			await executionLog.logExecution({
 				filePath,
 				operation: "list-scaffold-methods",

package/dist/{claudeCode-lHW7zQ5G.mjs → claudeCode-Dozuzn4S.mjs}

@@ -1,5 +1,6 @@
-import { t as ListScaffoldingMethodsTool } from "./ListScaffoldingMethodsTool-Cx-0gpV3.mjs";
-import "./tools-DtGTxmf-.mjs";
+import { t as ListScaffoldingMethodsTool } from "./ListScaffoldingMethodsTool-D6BkKQyK.mjs";
+import "./tools-t-HMGLVh.mjs";
+import { n as resolveNewFileWriteTarget, t as formatScaffoldMethodsHookMessage } from "./shared-oDx2Btq0.mjs";
 import { ProjectFinderService, TemplatesManagerService } from "@agiflowai/aicode-utils";
 import path from "node:path";
 import fs from "node:fs/promises";
@@ -185,25 +186,10 @@ var UseScaffoldMethodHook = class {
 				message: "Not a tool use event"
 			};
 			const filePath = context.tool_input?.file_path;
-			if (!filePath || context.tool_name !== "Write") return {
+			const absoluteFilePath = await resolveNewFileWriteTarget(context.cwd, context.tool_name, filePath);
+			if (!absoluteFilePath || !filePath) return {
 				decision: DECISION_SKIP,
-				message: "Not a file write operation"
-			};
-			const absoluteFilePath = path.isAbsolute(filePath) ? filePath : path.join(context.cwd, filePath);
-			if (!absoluteFilePath.startsWith(context.cwd + path.sep) && absoluteFilePath !== context.cwd) return {
-				decision: DECISION_SKIP,
-				message: "File is outside working directory - skipping scaffold method check"
-			};
-			let fileExists = false;
-			try {
-				await fs.access(absoluteFilePath);
-				fileExists = true;
-			} catch (accessErr) {
-				if (!(accessErr instanceof Error && "code" in accessErr && accessErr.code === "ENOENT")) throw accessErr;
-			}
-			if (fileExists) return {
-				decision: DECISION_SKIP,
-				message: "File already exists - skipping scaffold method check"
+				message: "Not a new file write operation"
 			};
 			const executionLog = new ExecutionLogService(context.session_id);
 			if (await executionLog.hasExecuted({
@@ -252,9 +238,7 @@ var UseScaffoldMethodHook = class {
 					message: "No scaffolding methods are available for this project template. You should write new files directly using the Write tool."
 				};
 			}
-			let message = "Before writing new files, use `use-scaffold-method` if any of these match your needs:\n\n";
-			for (const method of data.methods) message += `- **${method.name}**: ${method.description || "No description available"}\n`;
-			if (data.nextCursor) message += `\n_More methods available (cursor: "${data.nextCursor}")._\n`;
+			const message = formatScaffoldMethodsHookMessage(data.methods);
 			await executionLog.logExecution({
 				filePath,
 				operation: "list-scaffold-methods",

package/dist/cli.cjs

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
-const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-CkIkgP_u.cjs');
-const require_src = require('./src-B4ixzARA.cjs');
-const require_tools = require('./tools-CC-lrhQ8.cjs');
+const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-DBwZzJTA.cjs');
+const require_src = require('./src-DxoKQE4s.cjs');
+const require_tools = require('./tools-DsnQImJ1.cjs');
 let __agiflowai_aicode_utils = require("@agiflowai/aicode-utils");
 let node_path = require("node:path");
 node_path = require_ListScaffoldingMethodsTool.__toESM(node_path);
@@ -196,6 +196,17 @@ function parseJsonConfig(value, flagName) {
 		throw new Error(`Invalid JSON for ${flagName}: ${error instanceof Error ? error.message : String(error)}`);
 	}
 }
+function resolveFallbackConfig$1(config) {
+	if (config.fallbackTool) return {
+		tool: config.fallbackTool,
+		config: config.fallbackToolConfig
+	};
+	const firstValidFallback = config.fallbacks?.find((entry) => entry?.tool);
+	return firstValidFallback ? {
+		tool: firstValidFallback.tool,
+		config: firstValidFallback.config
+	} : {};
+}
 /**
 * Start MCP server with given transport handler
 */
@@ -239,8 +250,9 @@ const mcpServeCommand = new commander.Command("mcp-serve").description("Start MC
 		const transportType = (options.type ?? fileConfig.type ?? "stdio").toLowerCase();
 		const adminEnable = options.adminEnable || fileConfig.adminEnable || false;
 		const promptAsSkill = options.promptAsSkill || fileConfig.promptAsSkill || false;
-		const fallbackTool = parseLlmToolOption(options.fallbackTool ?? fileConfig.fallbackTool, "--fallback-tool");
-		const fallbackToolConfig = options.fallbackToolConfig ? parseJsonConfig(options.fallbackToolConfig, "--fallback-tool-config") : fileConfig.fallbackToolConfig;
+		const configuredFallback = resolveFallbackConfig$1(fileConfig);
+		const fallbackTool = parseLlmToolOption(options.fallbackTool ?? configuredFallback.tool, "--fallback-tool");
+		const fallbackToolConfig = options.fallbackToolConfig ? parseJsonConfig(options.fallbackToolConfig, "--fallback-tool-config") : configuredFallback.config;
 		let isMonolith = false;
 		try {
 			isMonolith = (await __agiflowai_aicode_utils.ProjectConfigResolver.resolveProjectConfig(process.cwd())).type === "monolith";
@@ -536,6 +548,18 @@ function parseJsonConfigOption(value, flagName) {
 		throw new Error(`Invalid JSON for ${flagName}. Expected format: '{"key":"value"}'. Parse error: ${error instanceof Error ? error.message : String(error)}`);
 	}
 }
+function resolveFallbackConfig(config) {
+	if (!config) return {};
+	if (config["fallback-tool"]) return {
+		tool: config["fallback-tool"],
+		config: config["fallback-tool-config"]
+	};
+	const firstValidFallback = config.fallbacks?.find((entry) => entry?.tool);
+	return firstValidFallback ? {
+		tool: firstValidFallback.tool,
+		config: firstValidFallback.config
+	} : {};
+}
 /**
 * Hook command for executing scaffold hooks
 */
@@ -545,8 +569,9 @@ const hookCommand = new commander.Command("hook").description("Execute scaffold
 		const { agent, hookMethod } = (0, __agiflowai_hooks_adapter.parseHookType)(options.type);
 		const methodConfig = ((await __agiflowai_aicode_utils.TemplatesManagerService.readToolkitConfig())?.["scaffold-mcp"]?.hook)?.[agent]?.[hookMethod];
 		const marker = options.marker ?? "@scaffold-generated";
-		const fallbackToolStr = options.fallbackTool ?? methodConfig?.["llm-tool"];
-		const fallbackToolConfig = options.fallbackToolConfig ? parseJsonConfigOption(options.fallbackToolConfig, "--fallback-tool-config") : methodConfig?.["tool-config"];
+		const configuredFallback = resolveFallbackConfig(methodConfig);
+		const fallbackToolStr = options.fallbackTool ?? methodConfig?.["fallback-tool"] ?? methodConfig?.["llm-tool"] ?? configuredFallback.tool;
+		const fallbackToolConfig = options.fallbackToolConfig ? parseJsonConfigOption(options.fallbackToolConfig, "--fallback-tool-config") : methodConfig?.["fallback-tool-config"] ?? methodConfig?.["tool-config"] ?? configuredFallback.config;
 		if (fallbackToolStr && !(0, __agiflowai_coding_agent_bridge.isValidLlmTool)(fallbackToolStr)) throw new Error(`Invalid --fallback-tool: ${fallbackToolStr}. Supported: ${__agiflowai_coding_agent_bridge.SUPPORTED_LLM_TOOLS.join(", ")}`);
 		const adapterConfig = {};
 		if (fallbackToolConfig) adapterConfig.tool_config = fallbackToolConfig;
@@ -554,7 +579,7 @@ const hookCommand = new commander.Command("hook").description("Execute scaffold
 		const resolvedAdapterConfig = Object.keys(adapterConfig).length > 0 ? adapterConfig : void 0;
 		if (!isHookMethod(hookMethod)) process.exit(0);
 		if (agent === __agiflowai_coding_agent_bridge.CLAUDE_CODE) {
-			const hookModule = await Promise.resolve().then(() => require("./claudeCode-DBoEGOeu.cjs"));
+			const hookModule = await Promise.resolve().then(() => require("./claudeCode-B6CWgRYJ.cjs"));
 			const claudeCallbacks = [];
 			if (hookModule.UseScaffoldMethodHook) {
 				const hookInstance = new hookModule.UseScaffoldMethodHook();
@@ -569,7 +594,7 @@ const hookCommand = new commander.Command("hook").description("Execute scaffold
 			if (claudeCallbacks.length === 0) process.exit(0);
 			await new __agiflowai_hooks_adapter.ClaudeCodeAdapter().executeMultiple(claudeCallbacks, resolvedAdapterConfig);
 		} else if (agent === __agiflowai_coding_agent_bridge.GEMINI_CLI) {
-			const hookModule = await Promise.resolve().then(() => require("./geminiCli-BHyWDBcF.cjs"));
+			const hookModule = await Promise.resolve().then(() => require("./geminiCli-COS3X1P7.cjs"));
 			const geminiCallbacks = [];
 			if (hookModule.UseScaffoldMethodHook) {
 				const hookInstance = new hookModule.UseScaffoldMethodHook();

package/dist/cli.mjs

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
-import { a as createServer, i as StdioTransportHandler, n as HttpTransportHandler, o as version, r as SseTransportHandler, t as TransportMode } from "./src-COn3FXEz.mjs";
-import { n as ScaffoldingMethodsService, s as FileSystemService } from "./ListScaffoldingMethodsTool-Cx-0gpV3.mjs";
-import { l as BoilerplateService } from "./tools-DtGTxmf-.mjs";
+import { a as createServer, i as StdioTransportHandler, n as HttpTransportHandler, o as version, r as SseTransportHandler, t as TransportMode } from "./src-sY88BbkJ.mjs";
+import { n as ScaffoldingMethodsService, s as FileSystemService } from "./ListScaffoldingMethodsTool-D6BkKQyK.mjs";
+import { l as BoilerplateService } from "./tools-t-HMGLVh.mjs";
 import { ProjectConfigResolver, TemplatesManagerService, icons, messages, print, sections } from "@agiflowai/aicode-utils";
 import path from "node:path";
 import { Command } from "commander";
@@ -195,6 +195,17 @@ function parseJsonConfig(value, flagName) {
 		throw new Error(`Invalid JSON for ${flagName}: ${error instanceof Error ? error.message : String(error)}`);
 	}
 }
+function resolveFallbackConfig$1(config) {
+	if (config.fallbackTool) return {
+		tool: config.fallbackTool,
+		config: config.fallbackToolConfig
+	};
+	const firstValidFallback = config.fallbacks?.find((entry) => entry?.tool);
+	return firstValidFallback ? {
+		tool: firstValidFallback.tool,
+		config: firstValidFallback.config
+	} : {};
+}
 /**
 * Start MCP server with given transport handler
 */
@@ -238,8 +249,9 @@ const mcpServeCommand = new Command("mcp-serve").description("Start MCP server w
 		const transportType = (options.type ?? fileConfig.type ?? "stdio").toLowerCase();
 		const adminEnable = options.adminEnable || fileConfig.adminEnable || false;
 		const promptAsSkill = options.promptAsSkill || fileConfig.promptAsSkill || false;
-		const fallbackTool = parseLlmToolOption(options.fallbackTool ?? fileConfig.fallbackTool, "--fallback-tool");
-		const fallbackToolConfig = options.fallbackToolConfig ? parseJsonConfig(options.fallbackToolConfig, "--fallback-tool-config") : fileConfig.fallbackToolConfig;
+		const configuredFallback = resolveFallbackConfig$1(fileConfig);
+		const fallbackTool = parseLlmToolOption(options.fallbackTool ?? configuredFallback.tool, "--fallback-tool");
+		const fallbackToolConfig = options.fallbackToolConfig ? parseJsonConfig(options.fallbackToolConfig, "--fallback-tool-config") : configuredFallback.config;
 		let isMonolith = false;
 		try {
 			isMonolith = (await ProjectConfigResolver.resolveProjectConfig(process.cwd())).type === "monolith";
@@ -535,6 +547,18 @@ function parseJsonConfigOption(value, flagName) {
 		throw new Error(`Invalid JSON for ${flagName}. Expected format: '{"key":"value"}'. Parse error: ${error instanceof Error ? error.message : String(error)}`);
 	}
 }
+function resolveFallbackConfig(config) {
+	if (!config) return {};
+	if (config["fallback-tool"]) return {
+		tool: config["fallback-tool"],
+		config: config["fallback-tool-config"]
+	};
+	const firstValidFallback = config.fallbacks?.find((entry) => entry?.tool);
+	return firstValidFallback ? {
+		tool: firstValidFallback.tool,
+		config: firstValidFallback.config
+	} : {};
+}
 /**
 * Hook command for executing scaffold hooks
 */
@@ -544,8 +568,9 @@ const hookCommand = new Command("hook").description("Execute scaffold hooks for
 		const { agent, hookMethod } = parseHookType(options.type);
 		const methodConfig = ((await TemplatesManagerService.readToolkitConfig())?.["scaffold-mcp"]?.hook)?.[agent]?.[hookMethod];
 		const marker = options.marker ?? "@scaffold-generated";
-		const fallbackToolStr = options.fallbackTool ?? methodConfig?.["llm-tool"];
-		const fallbackToolConfig = options.fallbackToolConfig ? parseJsonConfigOption(options.fallbackToolConfig, "--fallback-tool-config") : methodConfig?.["tool-config"];
+		const configuredFallback = resolveFallbackConfig(methodConfig);
+		const fallbackToolStr = options.fallbackTool ?? methodConfig?.["fallback-tool"] ?? methodConfig?.["llm-tool"] ?? configuredFallback.tool;
+		const fallbackToolConfig = options.fallbackToolConfig ? parseJsonConfigOption(options.fallbackToolConfig, "--fallback-tool-config") : methodConfig?.["fallback-tool-config"] ?? methodConfig?.["tool-config"] ?? configuredFallback.config;
 		if (fallbackToolStr && !isValidLlmTool(fallbackToolStr)) throw new Error(`Invalid --fallback-tool: ${fallbackToolStr}. Supported: ${SUPPORTED_LLM_TOOLS.join(", ")}`);
 		const adapterConfig = {};
 		if (fallbackToolConfig) adapterConfig.tool_config = fallbackToolConfig;
@@ -553,7 +578,7 @@ const hookCommand = new Command("hook").description("Execute scaffold hooks for
 		const resolvedAdapterConfig = Object.keys(adapterConfig).length > 0 ? adapterConfig : void 0;
 		if (!isHookMethod(hookMethod)) process.exit(0);
 		if (agent === CLAUDE_CODE) {
-			const hookModule = await import("./claudeCode-lHW7zQ5G.mjs");
+			const hookModule = await import("./claudeCode-Dozuzn4S.mjs");
 			const claudeCallbacks = [];
 			if (hookModule.UseScaffoldMethodHook) {
 				const hookInstance = new hookModule.UseScaffoldMethodHook();
@@ -568,7 +593,7 @@ const hookCommand = new Command("hook").description("Execute scaffold hooks for
 			if (claudeCallbacks.length === 0) process.exit(0);
 			await new ClaudeCodeAdapter().executeMultiple(claudeCallbacks, resolvedAdapterConfig);
 		} else if (agent === GEMINI_CLI) {
-			const hookModule = await import("./geminiCli-DBdxdDMM.mjs");
+			const hookModule = await import("./geminiCli-CzgQDDMl.mjs");
 			const geminiCallbacks = [];
 			if (hookModule.UseScaffoldMethodHook) {
 				const hookInstance = new hookModule.UseScaffoldMethodHook();

package/dist/{geminiCli-BHyWDBcF.cjs → geminiCli-COS3X1P7.cjs}

@@ -1,4 +1,5 @@
-const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-CkIkgP_u.cjs');
+const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-DBwZzJTA.cjs');
+const require_shared = require('./shared-fkWett9D.cjs');
 let __agiflowai_aicode_utils = require("@agiflowai/aicode-utils");
 let __agiflowai_hooks_adapter = require("@agiflowai/hooks-adapter");
 
@@ -20,8 +21,14 @@ var UseScaffoldMethodHook = class {
 	*/
 	async preToolUse(context) {
 		try {
+			const filePath = context.tool_input?.file_path;
+			const absoluteFilePath = await require_shared.resolveNewFileWriteTarget(context.cwd, context.tool_name, filePath);
+			if (!absoluteFilePath || !filePath) return {
+				decision: __agiflowai_hooks_adapter.DECISION_SKIP,
+				message: "Not a new file write operation"
+			};
 			const executionLog = new __agiflowai_hooks_adapter.ExecutionLogService(context.session_id);
-			const sessionKey = `list-scaffold-methods-${context.session_id}`;
+			const sessionKey = filePath;
 			if (await executionLog.hasExecuted({
 				filePath: sessionKey,
 				decision: __agiflowai_hooks_adapter.DECISION_DENY
@@ -41,7 +48,9 @@ var UseScaffoldMethodHook = class {
 				decision: __agiflowai_hooks_adapter.DECISION_SKIP,
 				message: "Templates folder not found - skipping scaffold method check"
 			};
-			const result = await new require_ListScaffoldingMethodsTool.ListScaffoldingMethodsTool(templatesPath, false).execute(context.tool_input || {});
+			const tool = new require_ListScaffoldingMethodsTool.ListScaffoldingMethodsTool(templatesPath, false);
+			const projectPath = (await new __agiflowai_aicode_utils.ProjectFinderService(await __agiflowai_aicode_utils.TemplatesManagerService.getWorkspaceRoot(context.cwd)).findProjectForFile(absoluteFilePath))?.root || context.cwd;
+			const result = await tool.execute({ projectPath });
 			const firstContent = result.content[0];
 			if (firstContent?.type !== "text") return {
 				decision: __agiflowai_hooks_adapter.DECISION_SKIP,
@@ -75,19 +84,7 @@ var UseScaffoldMethodHook = class {
 					message: "No scaffolding methods are available for this project template. You should write new files directly using the Write tool."
 				};
 			}
-			let message = "🎯 **Scaffolding Methods Available**\n\n";
-			message += "Before writing new files, check if any of these scaffolding methods match your needs:\n\n";
-			for (const method of data.methods) {
-				message += `**${method.name}**\n`;
-				message += `${method.instruction || method.description || "No description available"}\n`;
-				if (method.variables_schema?.required && method.variables_schema.required.length > 0) message += `Required: ${method.variables_schema.required.join(", ")}\n`;
-				message += "\n";
-			}
-			if (data.nextCursor) message += `\n_Note: More methods available. Use cursor "${data.nextCursor}" to see more._\n\n`;
-			message += "\n**Instructions:**\n";
-			message += "1. If one of these scaffold methods matches what you need to create, use the `use-scaffold-method` MCP tool instead of writing files manually\n";
-			message += "2. If none of these methods are relevant to your task, proceed to write new files directly using the Write tool\n";
-			message += "3. Using scaffold methods ensures consistency with project patterns and includes all necessary boilerplate\n";
+			const message = require_shared.formatScaffoldMethodsHookMessage(data.methods, { includeRequiredVars: true });
 			await executionLog.logExecution({
 				filePath: sessionKey,
 				operation: "list-scaffold-methods",

package/dist/{geminiCli-DBdxdDMM.mjs → geminiCli-CzgQDDMl.mjs}

@@ -1,5 +1,6 @@
-import { t as ListScaffoldingMethodsTool } from "./ListScaffoldingMethodsTool-Cx-0gpV3.mjs";
-import { TemplatesManagerService } from "@agiflowai/aicode-utils";
+import { t as ListScaffoldingMethodsTool } from "./ListScaffoldingMethodsTool-D6BkKQyK.mjs";
+import { n as resolveNewFileWriteTarget, t as formatScaffoldMethodsHookMessage } from "./shared-oDx2Btq0.mjs";
+import { ProjectFinderService, TemplatesManagerService } from "@agiflowai/aicode-utils";
 import { DECISION_ALLOW, DECISION_DENY, DECISION_SKIP, ExecutionLogService } from "@agiflowai/hooks-adapter";
 
 //#region src/hooks/geminiCli/useScaffoldMethod.ts
@@ -20,8 +21,14 @@ var UseScaffoldMethodHook = class {
 	*/
 	async preToolUse(context) {
 		try {
+			const filePath = context.tool_input?.file_path;
+			const absoluteFilePath = await resolveNewFileWriteTarget(context.cwd, context.tool_name, filePath);
+			if (!absoluteFilePath || !filePath) return {
+				decision: DECISION_SKIP,
+				message: "Not a new file write operation"
+			};
 			const executionLog = new ExecutionLogService(context.session_id);
-			const sessionKey = `list-scaffold-methods-${context.session_id}`;
+			const sessionKey = filePath;
 			if (await executionLog.hasExecuted({
 				filePath: sessionKey,
 				decision: DECISION_DENY
@@ -41,7 +48,9 @@ var UseScaffoldMethodHook = class {
 				decision: DECISION_SKIP,
 				message: "Templates folder not found - skipping scaffold method check"
 			};
-			const result = await new ListScaffoldingMethodsTool(templatesPath, false).execute(context.tool_input || {});
+			const tool = new ListScaffoldingMethodsTool(templatesPath, false);
+			const projectPath = (await new ProjectFinderService(await TemplatesManagerService.getWorkspaceRoot(context.cwd)).findProjectForFile(absoluteFilePath))?.root || context.cwd;
+			const result = await tool.execute({ projectPath });
 			const firstContent = result.content[0];
 			if (firstContent?.type !== "text") return {
 				decision: DECISION_SKIP,
@@ -75,19 +84,7 @@ var UseScaffoldMethodHook = class {
 					message: "No scaffolding methods are available for this project template. You should write new files directly using the Write tool."
 				};
 			}
-			let message = "🎯 **Scaffolding Methods Available**\n\n";
-			message += "Before writing new files, check if any of these scaffolding methods match your needs:\n\n";
-			for (const method of data.methods) {
-				message += `**${method.name}**\n`;
-				message += `${method.instruction || method.description || "No description available"}\n`;
-				if (method.variables_schema?.required && method.variables_schema.required.length > 0) message += `Required: ${method.variables_schema.required.join(", ")}\n`;
-				message += "\n";
-			}
-			if (data.nextCursor) message += `\n_Note: More methods available. Use cursor "${data.nextCursor}" to see more._\n\n`;
-			message += "\n**Instructions:**\n";
-			message += "1. If one of these scaffold methods matches what you need to create, use the `use-scaffold-method` MCP tool instead of writing files manually\n";
-			message += "2. If none of these methods are relevant to your task, proceed to write new files directly using the Write tool\n";
-			message += "3. Using scaffold methods ensures consistency with project patterns and includes all necessary boilerplate\n";
+			const message = formatScaffoldMethodsHookMessage(data.methods, { includeRequiredVars: true });
 			await executionLog.logExecution({
 				filePath: sessionKey,
 				operation: "list-scaffold-methods",

package/dist/index.cjs

@@ -1,6 +1,6 @@
-const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-CkIkgP_u.cjs');
-const require_src = require('./src-B4ixzARA.cjs');
-const require_tools = require('./tools-CC-lrhQ8.cjs');
+const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-DBwZzJTA.cjs');
+const require_src = require('./src-DxoKQE4s.cjs');
+const require_tools = require('./tools-DsnQImJ1.cjs');
 
 exports.BoilerplateGeneratorService = require_tools.BoilerplateGeneratorService;
 exports.BoilerplateService = require_tools.BoilerplateService;

package/dist/index.mjs

@@ -1,5 +1,5 @@
-import { a as createServer, i as StdioTransportHandler, n as HttpTransportHandler, r as SseTransportHandler, t as TransportMode } from "./src-COn3FXEz.mjs";
-import { a as ScaffoldProcessingService, i as ScaffoldService, l as TemplateService, n as ScaffoldingMethodsService, o as ScaffoldConfigLoader, r as VariableReplacementService, s as FileSystemService, t as ListScaffoldingMethodsTool } from "./ListScaffoldingMethodsTool-Cx-0gpV3.mjs";
-import { a as GenerateFeatureScaffoldTool, c as ScaffoldGeneratorService, i as ListBoilerplatesTool, l as BoilerplateService, n as UseScaffoldMethodTool, o as GenerateBoilerplateTool, r as UseBoilerplateTool, s as GenerateBoilerplateFileTool, t as WriteToFileTool, u as BoilerplateGeneratorService } from "./tools-DtGTxmf-.mjs";
+import { a as createServer, i as StdioTransportHandler, n as HttpTransportHandler, r as SseTransportHandler, t as TransportMode } from "./src-sY88BbkJ.mjs";
+import { a as ScaffoldProcessingService, i as ScaffoldService, l as TemplateService, n as ScaffoldingMethodsService, o as ScaffoldConfigLoader, r as VariableReplacementService, s as FileSystemService, t as ListScaffoldingMethodsTool } from "./ListScaffoldingMethodsTool-D6BkKQyK.mjs";
+import { a as GenerateFeatureScaffoldTool, c as ScaffoldGeneratorService, i as ListBoilerplatesTool, l as BoilerplateService, n as UseScaffoldMethodTool, o as GenerateBoilerplateTool, r as UseBoilerplateTool, s as GenerateBoilerplateFileTool, t as WriteToFileTool, u as BoilerplateGeneratorService } from "./tools-t-HMGLVh.mjs";
 
 export { BoilerplateGeneratorService, BoilerplateService, FileSystemService, GenerateBoilerplateFileTool, GenerateBoilerplateTool, GenerateFeatureScaffoldTool, HttpTransportHandler, ListBoilerplatesTool, ListScaffoldingMethodsTool, ScaffoldConfigLoader, ScaffoldGeneratorService, ScaffoldProcessingService, ScaffoldService, ScaffoldingMethodsService, SseTransportHandler, StdioTransportHandler, TemplateService, TransportMode, UseBoilerplateTool, UseScaffoldMethodTool, VariableReplacementService, WriteToFileTool, createServer };

package/dist/shared-fkWett9D.cjs

@@ -0,0 +1,58 @@
+const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-DBwZzJTA.cjs');
+let node_path = require("node:path");
+node_path = require_ListScaffoldingMethodsTool.__toESM(node_path);
+let node_fs_promises = require("node:fs/promises");
+node_fs_promises = require_ListScaffoldingMethodsTool.__toESM(node_fs_promises);
+
+//#region src/hooks/shared.ts
+const MAX_SCAFFOLD_METHODS_IN_HOOK = 5;
+const MAX_REQUIRED_VARS_IN_HOOK = 3;
+const REQUIRED_VARS_METHOD_LIMIT = 2;
+async function resolveNewFileWriteTarget(cwd, toolName, filePath) {
+	if (!filePath || toolName.toLowerCase() !== "write") return null;
+	const absoluteFilePath = node_path.default.isAbsolute(filePath) ? filePath : node_path.default.join(cwd, filePath);
+	if (!absoluteFilePath.startsWith(cwd + node_path.default.sep) && absoluteFilePath !== cwd) return null;
+	try {
+		await node_fs_promises.default.access(absoluteFilePath);
+		return null;
+	} catch (error) {
+		if (error instanceof Error && "code" in error && error.code === "ENOENT") return absoluteFilePath;
+		throw error;
+	}
+}
+function formatScaffoldMethodsHookMessage(methods, options) {
+	const maxMethods = options?.maxMethods ?? MAX_SCAFFOLD_METHODS_IN_HOOK;
+	const requiredVarsMethodLimit = options?.requiredVarsMethodLimit ?? REQUIRED_VARS_METHOD_LIMIT;
+	const maxRequiredVars = options?.maxRequiredVars ?? MAX_REQUIRED_VARS_IN_HOOK;
+	const visibleMethods = methods.slice(0, maxMethods);
+	const hiddenCount = Math.max(methods.length - visibleMethods.length, 0);
+	let message = "Before writing this new file, use `use-scaffold-method` if any of these fit:\n\n";
+	for (const [index, method] of visibleMethods.entries()) {
+		message += `- **${method.name}**: ${method.description || "No description available"}\n`;
+		if (options?.includeRequiredVars && index < requiredVarsMethodLimit) {
+			const requiredVars = method.variables_schema?.required ?? [];
+			if (requiredVars.length > 0) {
+				const visibleVars = requiredVars.slice(0, maxRequiredVars);
+				const moreCount = Math.max(requiredVars.length - visibleVars.length, 0);
+				const suffix = moreCount > 0 ? `, +${moreCount} more` : "";
+				message += `  Required: ${visibleVars.join(", ")}${suffix}\n`;
+			}
+		}
+	}
+	if (hiddenCount > 0) message += `\n...and ${hiddenCount} more methods. Call \`list-scaffolding-methods\` for the full list.\n`;
+	return message.trimEnd();
+}
+
+//#endregion
+Object.defineProperty(exports, 'formatScaffoldMethodsHookMessage', {
+  enumerable: true,
+  get: function () {
+    return formatScaffoldMethodsHookMessage;
+  }
+});
+Object.defineProperty(exports, 'resolveNewFileWriteTarget', {
+  enumerable: true,
+  get: function () {
+    return resolveNewFileWriteTarget;
+  }
+});

package/dist/shared-oDx2Btq0.mjs

@@ -0,0 +1,44 @@
+import path from "node:path";
+import fs from "node:fs/promises";
+
+//#region src/hooks/shared.ts
+const MAX_SCAFFOLD_METHODS_IN_HOOK = 5;
+const MAX_REQUIRED_VARS_IN_HOOK = 3;
+const REQUIRED_VARS_METHOD_LIMIT = 2;
+async function resolveNewFileWriteTarget(cwd, toolName, filePath) {
+	if (!filePath || toolName.toLowerCase() !== "write") return null;
+	const absoluteFilePath = path.isAbsolute(filePath) ? filePath : path.join(cwd, filePath);
+	if (!absoluteFilePath.startsWith(cwd + path.sep) && absoluteFilePath !== cwd) return null;
+	try {
+		await fs.access(absoluteFilePath);
+		return null;
+	} catch (error) {
+		if (error instanceof Error && "code" in error && error.code === "ENOENT") return absoluteFilePath;
+		throw error;
+	}
+}
+function formatScaffoldMethodsHookMessage(methods, options) {
+	const maxMethods = options?.maxMethods ?? MAX_SCAFFOLD_METHODS_IN_HOOK;
+	const requiredVarsMethodLimit = options?.requiredVarsMethodLimit ?? REQUIRED_VARS_METHOD_LIMIT;
+	const maxRequiredVars = options?.maxRequiredVars ?? MAX_REQUIRED_VARS_IN_HOOK;
+	const visibleMethods = methods.slice(0, maxMethods);
+	const hiddenCount = Math.max(methods.length - visibleMethods.length, 0);
+	let message = "Before writing this new file, use `use-scaffold-method` if any of these fit:\n\n";
+	for (const [index, method] of visibleMethods.entries()) {
+		message += `- **${method.name}**: ${method.description || "No description available"}\n`;
+		if (options?.includeRequiredVars && index < requiredVarsMethodLimit) {
+			const requiredVars = method.variables_schema?.required ?? [];
+			if (requiredVars.length > 0) {
+				const visibleVars = requiredVars.slice(0, maxRequiredVars);
+				const moreCount = Math.max(requiredVars.length - visibleVars.length, 0);
+				const suffix = moreCount > 0 ? `, +${moreCount} more` : "";
+				message += `  Required: ${visibleVars.join(", ")}${suffix}\n`;
+			}
+		}
+	}
+	if (hiddenCount > 0) message += `\n...and ${hiddenCount} more methods. Call \`list-scaffolding-methods\` for the full list.\n`;
+	return message.trimEnd();
+}
+
+//#endregion
+export { resolveNewFileWriteTarget as n, formatScaffoldMethodsHookMessage as t };

package/dist/{src-B4ixzARA.cjs → src-DxoKQE4s.cjs}

@@ -1,5 +1,5 @@
-const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-CkIkgP_u.cjs');
-const require_tools = require('./tools-CC-lrhQ8.cjs');
+const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-DBwZzJTA.cjs');
+const require_tools = require('./tools-DsnQImJ1.cjs');
 let __agiflowai_aicode_utils = require("@agiflowai/aicode-utils");
 let __modelcontextprotocol_sdk_server_index_js = require("@modelcontextprotocol/sdk/server/index.js");
 let __modelcontextprotocol_sdk_types_js = require("@modelcontextprotocol/sdk/types.js");
@@ -12,11 +12,11 @@ let node_crypto = require("node:crypto");
 let __modelcontextprotocol_sdk_server_streamableHttp_js = require("@modelcontextprotocol/sdk/server/streamableHttp.js");
 
 //#region package.json
-var version = "1.0.23";
+var version = "1.0.25";
 
 //#endregion
 //#region src/instructions/server.md?raw
-var server_default = "Use this MCP server to {% if isMonolith %}create your monolith project and add features (pages, components, services, etc.){% else %}create new projects and add features (pages, components, services, etc.){% endif %}.\n\n## Workflow:\n{% if not isMonolith %}\n1. **Creating New Project**: Use `list-boilerplates` → `use-boilerplate`\n2. **Adding Features**: Use `list-scaffolding-methods` → `use-scaffold-method`\n{% else %}\n1. **Creating Project**: Use `use-boilerplate` (boilerplateName auto-detected from toolkit.yaml)\n2. **Adding Features**: Use `list-scaffolding-methods` → `use-scaffold-method`\n{% endif %}\n\n## AI Usage Guidelines:\n{% if not isMonolith %}\n- Always call `list-boilerplates` first when creating new projects to see available options\n{% endif %}\n- Always call `list-scaffolding-methods` first when adding features to understand what's available\n- Follow the exact variable schema provided - validation will fail if required fields are missing\n{% if not isMonolith %}\n- Use kebab-case for project names (e.g., \"my-new-app\")\n{% else %}\n- In monolith mode, parameters like `boilerplateName` and `templateName` are auto-detected from toolkit.yaml\n- You only need to provide `variables` when calling `use-boilerplate` or `use-scaffold-method`\n{% endif %}\n- The tools automatically handle file placement, imports, and code generation\n- Check the returned JSON schemas to understand required vs optional variables\n{% if adminEnabled %}\n\n## Admin Mode (Template Generation):\n\nWhen creating custom boilerplate templates for frameworks not yet supported:\n\n1. **Create Boilerplate Configuration**: Use `generate-boilerplate` to add a new boilerplate entry to a template's scaffold.yaml\n   - Specify template name, boilerplate name, description, target folder, and variable schema\n   - This creates the scaffold.yaml structure following the nextjs-15 pattern\n   - Optional: Add detailed instruction about file purposes and design patterns\n\n2. **Create Feature Configuration**: Use `generate-feature-scaffold` to add a new feature entry to a template's scaffold.yaml\n   - Specify template name, feature name, generator, description, and variable schema\n   - This creates the scaffold.yaml structure for feature scaffolds (pages, components, etc.)\n   - Optional: Add detailed instruction about file purposes and design patterns\n   - Optional: Specify patterns to match existing files this feature works with\n\n3. **Create Template Files**: Use `generate-boilerplate-file` to create the actual template files\n   - Create files referenced in the boilerplate's or feature's includes array\n   - Use {{ variableName }} syntax for Liquid variable placeholders\n   - Can copy from existing source files or provide content directly\n   - Files automatically get .liquid extension\n\n4. **Test the Template**: Use `list-boilerplates`/`list-scaffolding-methods` and `use-boilerplate`/`use-scaffold-method` to verify your template works\n\nExample workflow for boilerplate:\n```\n1. generate-boilerplate { templateName: \"react-vite\", boilerplateName: \"scaffold-vite-app\", ... }\n2. generate-boilerplate-file { templateName: \"react-vite\", filePath: \"package.json\", content: \"...\" }\n3. generate-boilerplate-file { templateName: \"react-vite\", filePath: \"src/App.tsx\", content: \"...\" }\n4. list-boilerplates (verify it appears)\n5. use-boilerplate { boilerplateName: \"scaffold-vite-app\", variables: {...} }\n```\n\nExample workflow for feature:\n```\n1. generate-feature-scaffold { templateName: \"nextjs-15\", featureName: \"scaffold-nextjs-component\", generator: \"componentGenerator.ts\", ... }\n2. generate-boilerplate-file { templateName: \"nextjs-15\", filePath: \"src/components/Component.tsx\", content: \"...\" }\n3. list-scaffolding-methods (verify it appears)\n4. use-scaffold-method { scaffoldName: \"scaffold-nextjs-component\", variables: {...} }\n```\n{% endif %}\n";
+var server_default = "Use this MCP server to {% if isMonolith %}create your monolith project and add features (pages, components, services, etc.){% else %}create new projects and add features (pages, components, services, etc.){% endif %}.\n\n## Workflow:\n{% if not isMonolith %}\n1. **Creating New Project**: Use `list-boilerplates` → `use-boilerplate`\n2. **Adding Features**: Use `list-scaffolding-methods` → `use-scaffold-method`\n{% else %}\n1. **Creating Project**: Use `use-boilerplate` (boilerplateName auto-detected from `.toolkit/settings.yaml`)\n2. **Adding Features**: Use `list-scaffolding-methods` → `use-scaffold-method`\n{% endif %}\n\n## AI Usage Guidelines:\n{% if not isMonolith %}\n- Always call `list-boilerplates` first when creating new projects to see available options\n{% endif %}\n- Always call `list-scaffolding-methods` first when adding features to understand what's available\n- Follow the exact variable schema provided - validation will fail if required fields are missing\n{% if not isMonolith %}\n- Use kebab-case for project names (e.g., \"my-new-app\")\n{% else %}\n- In monolith mode, parameters like `boilerplateName` and `templateName` are auto-detected from `.toolkit/settings.yaml`\n- You only need to provide `variables` when calling `use-boilerplate` or `use-scaffold-method`\n{% endif %}\n- The tools automatically handle file placement, imports, and code generation\n- Check the returned JSON schemas to understand required vs optional variables\n{% if adminEnabled %}\n\n## Admin Mode (Template Generation):\n\nWhen creating custom boilerplate templates for frameworks not yet supported:\n\n1. **Create Boilerplate Configuration**: Use `generate-boilerplate` to add a new boilerplate entry to a template's scaffold.yaml\n   - Specify template name, boilerplate name, description, target folder, and variable schema\n   - This creates the scaffold.yaml structure following the nextjs-15 pattern\n   - Optional: Add detailed instruction about file purposes and design patterns\n\n2. **Create Feature Configuration**: Use `generate-feature-scaffold` to add a new feature entry to a template's scaffold.yaml\n   - Specify template name, feature name, generator, description, and variable schema\n   - This creates the scaffold.yaml structure for feature scaffolds (pages, components, etc.)\n   - Optional: Add detailed instruction about file purposes and design patterns\n   - Optional: Specify patterns to match existing files this feature works with\n\n3. **Create Template Files**: Use `generate-boilerplate-file` to create the actual template files\n   - Create files referenced in the boilerplate's or feature's includes array\n   - Use {{ variableName }} syntax for Liquid variable placeholders\n   - Can copy from existing source files or provide content directly\n   - Files automatically get .liquid extension\n\n4. **Test the Template**: Use `list-boilerplates`/`list-scaffolding-methods` and `use-boilerplate`/`use-scaffold-method` to verify your template works\n\nExample workflow for boilerplate:\n```\n1. generate-boilerplate { templateName: \"react-vite\", boilerplateName: \"scaffold-vite-app\", ... }\n2. generate-boilerplate-file { templateName: \"react-vite\", filePath: \"package.json\", content: \"...\" }\n3. generate-boilerplate-file { templateName: \"react-vite\", filePath: \"src/App.tsx\", content: \"...\" }\n4. list-boilerplates (verify it appears)\n5. use-boilerplate { boilerplateName: \"scaffold-vite-app\", variables: {...} }\n```\n\nExample workflow for feature:\n```\n1. generate-feature-scaffold { templateName: \"nextjs-15\", featureName: \"scaffold-nextjs-component\", generator: \"componentGenerator.ts\", ... }\n2. generate-boilerplate-file { templateName: \"nextjs-15\", filePath: \"src/components/Component.tsx\", content: \"...\" }\n3. list-scaffolding-methods (verify it appears)\n4. use-scaffold-method { scaffoldName: \"scaffold-nextjs-component\", variables: {...} }\n```\n{% endif %}\n";
 
 //#endregion
 //#region src/instructions/prompts/generate-boilerplate.md?raw
@@ -80,7 +80,7 @@ var GenerateBoilerplatePrompt = class GenerateBoilerplatePrompt {
 
 //#endregion
 //#region src/instructions/prompts/generate-feature-scaffold.md?raw
-var generate_feature_scaffold_default = "{% if promptAsSkill %}---\nname: generate-feature-scaffold\ndescription: Create a new feature scaffold configuration for adding features to existing projects. Use this skill when the user wants to define a reusable feature template (e.g., page, component, service, API route) that can be used to add functionality to projects of a specific type. This is an admin/developer tool for creating the feature scaffold definitions themselves, not for using existing scaffolds. It generates feature configurations in scaffold.yaml and template files with Liquid syntax and conditional includes.\n---\n\n{% endif %}You are helping create a new feature scaffold configuration using the scaffold-mcp MCP tools.\n\n{% if request %}User request: {{ request }}\n{% endif %}\nYour task:\n\n1. **Gather Information**: Ask for any missing details:\n   {% if not isMonolith %}- Template name (e.g., \"nextjs-15\", \"react-vite\"){% else %}- Template name (will be auto-detected from toolkit.yaml){% endif %}\n   - Feature name (prefixed with \"scaffold-\", e.g., \"scaffold-nextjs-page\")\n   - Feature type (page, component, service, etc.)\n   - Variables needed\n   - Files to include\n\n2. **Use MCP Tools** in order:\n   - `generate-feature-scaffold` - Creates the feature configuration\n   - `generate-boilerplate-file` - Creates each template file\n   - `list-scaffolding-methods` - Verify it appears\n   - `use-scaffold-method` - Test the feature\n\nImportant:\n- Feature names: prefix with \"scaffold-\"\n- Conditional includes: use \"file.tsx?withLayout=true\"\n- Template syntax: use {{ variableName }}\n{% if isMonolith %}- Template name will be auto-detected from toolkit.yaml{% endif %}\n\n**Description Field Guidelines (CRITICAL)**:\nThe description should explain what the feature scaffold generates (2-3 sentences):\n- Sentence 1: What type of code it generates (component, page, service, etc.)\n- Sentence 2: Key features or capabilities included\n- Sentence 3: Primary use cases or when to use it\n\nExample:\n\"Generate a new service class for TypeScript libraries following best practices. Creates a service class with interface, implementation, and unit tests. Perfect for creating reusable service modules with dependency injection patterns.\"\n\n**Instruction Field Guidelines (CRITICAL)**:\nThe instruction should provide specific guidance for using the generated feature:\n\n1. **Pattern explanation**: Describe the architectural pattern used\n2. **File organization**: Where files should be placed\n3. **Naming conventions**: How to name things (PascalCase, camelCase, etc.)\n4. **Usage guidelines**: How to use the generated code\n5. **Testing approach**: How to test the feature\n\nExample structure:\n\"[Feature type] follow a [pattern name] pattern with [key characteristics].\n[Explanation of how it works and integrates with the project].\nPlace [files] in [directory].\nFor [features with X], define [Y] in [Z] for better separation of concerns.\n[Feature names] should be [case style] and [suffix/prefix rules].\nWrite comprehensive [tests/docs] for all [public methods/exports].\"\n\nKeep it concise but informative - focus on the patterns and conventions that AI needs to understand to work with the generated code effectively.\n\nTemplate File Content Guidelines:\n- Keep content MINIMAL and business-agnostic\n- Focus on structure and patterns, not business logic\n- Use placeholder/generic examples only\n- Include essential boilerplate code only\n- Let AI fill in specific logic later\n- Add clear headers with design patterns and coding standards\n";
+var generate_feature_scaffold_default = "{% if promptAsSkill %}---\nname: generate-feature-scaffold\ndescription: Create a new feature scaffold configuration for adding features to existing projects. Use this skill when the user wants to define a reusable feature template (e.g., page, component, service, API route) that can be used to add functionality to projects of a specific type. This is an admin/developer tool for creating the feature scaffold definitions themselves, not for using existing scaffolds. It generates feature configurations in scaffold.yaml and template files with Liquid syntax and conditional includes.\n---\n\n{% endif %}You are helping create a new feature scaffold configuration using the scaffold-mcp MCP tools.\n\n{% if request %}User request: {{ request }}\n{% endif %}\nYour task:\n\n1. **Gather Information**: Ask for any missing details:\n   {% if not isMonolith %}- Template name (e.g., \"nextjs-15\", \"react-vite\"){% else %}- Template name (will be auto-detected from `.toolkit/settings.yaml`){% endif %}\n   - Feature name (prefixed with \"scaffold-\", e.g., \"scaffold-nextjs-page\")\n   - Feature type (page, component, service, etc.)\n   - Variables needed\n   - Files to include\n\n2. **Use MCP Tools** in order:\n   - `generate-feature-scaffold` - Creates the feature configuration\n   - `generate-boilerplate-file` - Creates each template file\n   - `list-scaffolding-methods` - Verify it appears\n   - `use-scaffold-method` - Test the feature\n\nImportant:\n- Feature names: prefix with \"scaffold-\"\n- Conditional includes: use \"file.tsx?withLayout=true\"\n- Template syntax: use {{ variableName }}\n{% if isMonolith %}- Template name will be auto-detected from `.toolkit/settings.yaml`{% endif %}\n\n**Description Field Guidelines (CRITICAL)**:\nThe description should explain what the feature scaffold generates (2-3 sentences):\n- Sentence 1: What type of code it generates (component, page, service, etc.)\n- Sentence 2: Key features or capabilities included\n- Sentence 3: Primary use cases or when to use it\n\nExample:\n\"Generate a new service class for TypeScript libraries following best practices. Creates a service class with interface, implementation, and unit tests. Perfect for creating reusable service modules with dependency injection patterns.\"\n\n**Instruction Field Guidelines (CRITICAL)**:\nThe instruction should provide specific guidance for using the generated feature:\n\n1. **Pattern explanation**: Describe the architectural pattern used\n2. **File organization**: Where files should be placed\n3. **Naming conventions**: How to name things (PascalCase, camelCase, etc.)\n4. **Usage guidelines**: How to use the generated code\n5. **Testing approach**: How to test the feature\n\nExample structure:\n\"[Feature type] follow a [pattern name] pattern with [key characteristics].\n[Explanation of how it works and integrates with the project].\nPlace [files] in [directory].\nFor [features with X], define [Y] in [Z] for better separation of concerns.\n[Feature names] should be [case style] and [suffix/prefix rules].\nWrite comprehensive [tests/docs] for all [public methods/exports].\"\n\nKeep it concise but informative - focus on the patterns and conventions that AI needs to understand to work with the generated code effectively.\n\nTemplate File Content Guidelines:\n- Keep content MINIMAL and business-agnostic\n- Focus on structure and patterns, not business logic\n- Use placeholder/generic examples only\n- Include essential boilerplate code only\n- Let AI fill in specific logic later\n- Add clear headers with design patterns and coding standards\n";
 
 //#endregion
 //#region src/prompts/GenerateFeatureScaffoldPrompt.ts
@@ -140,7 +140,7 @@ var GenerateFeatureScaffoldPrompt = class GenerateFeatureScaffoldPrompt {
 
 //#endregion
 //#region src/instructions/prompts/scaffold-application.md?raw
-var scaffold_application_default = "{% if promptAsSkill %}---\nname: scaffold-application\ndescription: Create a new application or project from a boilerplate template. Use this skill when the user wants to start a new project, create a new app, or bootstrap a new codebase from scratch. This skill lists available boilerplate templates (React, Next.js, Express, etc.), gathers required configuration variables, generates the complete project structure, and provides guidance on next steps including adding features.\n---\n\n{% endif %}You are helping create a new {% if isMonolith %}monolith application{% else %}application{% endif %} using the scaffold-mcp MCP tools.\n\n{% if request %}User request: {{ request }}\n{% endif %}\nYour task is to scaffold a new application by following this workflow:\n\n## Step 1: {% if isMonolith %}Prepare to Create Application{% else %}List Available Boilerplates{% endif %}\n{% if isMonolith %}You will use the `use-boilerplate` tool to create your monolith application. The boilerplate name will be auto-detected from your toolkit.yaml file.{% else %}Use the `list-boilerplates` tool to see all available project templates.\n\n**What to look for:**\n- Boilerplate name (e.g., \"scaffold-nextjs-app\", \"scaffold-vite-app\")\n- Description of what the boilerplate creates\n- Target folder where projects will be created (e.g., \"apps\", \"packages\")\n- Required and optional variables in the variables_schema{% endif %}\n\n## Step 2: Gather Required Information\nBased on the {% if isMonolith %}toolkit.yaml{% else %}selected boilerplate's variables_schema{% endif %}, collect:\n{% if not isMonolith %}- **Project name**: Must be kebab-case (e.g., \"my-new-app\", not \"MyNewApp\")\n{% endif %}- **Required variables**: All variables marked as required: true\n- **Optional variables**: Variables with required: false (ask user if needed)\n\nCommon variables:\n- `appName` or `packageName`: The project name (kebab-case)\n- `description`: Brief description of what the project does\n- `author`: Author name\n\n## Step 3: Execute the Boilerplate\nUse the `use-boilerplate` tool with:\n{% if not isMonolith %}- `boilerplateName`: Exact name from list-boilerplates response\n{% endif %}- `variables`: Object matching the variables_schema exactly\n\n**Example:**\n```json\n{\n{% if not isMonolith %}  \"boilerplateName\": \"scaffold-nextjs-app\",\n{% endif %}  \"variables\": {\n    \"appName\": \"my-dashboard\",\n    \"description\": \"Admin dashboard for managing users\",\n    \"author\": \"John Doe\"\n  }\n}\n```\n\n## Important Guidelines:\n{% if not isMonolith %}- **Always call `list-boilerplates` first** to see available options and their schemas{% else %}- The boilerplate name is auto-detected from toolkit.yaml{% endif %}\n- **Use exact variable names** from the schema (case-sensitive)\n- **Provide all required variables** - the tool will fail if any are missing\n{% if not isMonolith %}- **Use kebab-case for project names** (e.g., \"user-dashboard\", not \"UserDashboard\")\n- The tool will create the project in the appropriate directory automatically{% else %}- The tool will create files at the workspace root{% endif %}\n- After creation, inform the user {% if isMonolith %}what files were created{% else %}where the project was created{% endif %}\n\n## Step 4: Review and Add Features (If Needed)\nAfter the boilerplate is created, **consider if additional features are needed**:\n1. **READ** the generated {% if isMonolith %}application{% else %}project{% endif %} structure to understand what was created\n2. **REVIEW** the user's request to see if they asked for specific features (e.g., \"with tool for X\", \"with prompt for Y\")\n3. **If features are needed**:\n   - Use `list-scaffolding-methods`{% if not isMonolith %} with the new project path{% endif %}\n   - Use `use-scaffold-method` to add tools, services, prompts, etc.\n   - **IMPLEMENT** the actual logic in the scaffolded feature files\n   - **REMOVE the `// @scaffold-generated` marker** from each file after implementing it (see below)\n   - **REGISTER** the features in `src/server/index.ts`\n4. **Install dependencies**: Remind user to run `pnpm install`\n5. **Report** the complete setup including any features added\n\n## Scaffold Marker — Remove After Implementing\nGenerated `.ts`/`.tsx`/`.js`/`.jsx` files contain `// @scaffold-generated` at the top. This comment flags unimplemented boilerplate files.\n\n**You MUST delete this line once a file is fully implemented.** Leaving it in place marks the file as a \"phantom\" — a scaffolded file whose logic was never written. The marker is checked at session boundaries to catch files that were accidentally left as empty templates.\n\n## Example Workflow:\n{% if not isMonolith %}1. Call `list-boilerplates` → See available templates\n2. Ask user which template to use (or infer from request)\n3. Collect required variables based on schema\n4. Call `use-boilerplate` with boilerplateName and variables{% else %}1. Collect required variables based on toolkit.yaml variables_schema\n2. Call `use-boilerplate` with variables (boilerplateName auto-detected){% endif %}\n5. **Review if user requested specific features (tools, prompts, etc.)**\n6. **If features needed**: Add them using `list-scaffolding-methods` and `use-scaffold-method`\n7. **READ and IMPLEMENT** the scaffolded feature files with actual logic\n8. **REMOVE `// @scaffold-generated`** from each file once implemented\n9. Report success and next steps to the user\n";
+var scaffold_application_default = "{% if promptAsSkill %}---\nname: scaffold-application\ndescription: Create a new application or project from a boilerplate template. Use this skill when the user wants to start a new project, create a new app, or bootstrap a new codebase from scratch. This skill lists available boilerplate templates (React, Next.js, Express, etc.), gathers required configuration variables, generates the complete project structure, and provides guidance on next steps including adding features.\n---\n\n{% endif %}You are helping create a new {% if isMonolith %}monolith application{% else %}application{% endif %} using the scaffold-mcp MCP tools.\n\n{% if request %}User request: {{ request }}\n{% endif %}\nYour task is to scaffold a new application by following this workflow:\n\n## Step 1: {% if isMonolith %}Prepare to Create Application{% else %}List Available Boilerplates{% endif %}\n{% if isMonolith %}You will use the `use-boilerplate` tool to create your monolith application. The boilerplate name will be auto-detected from your `.toolkit/settings.yaml` file (or legacy `toolkit.yaml` if present).{% else %}Use the `list-boilerplates` tool to see all available project templates.\n\n**What to look for:**\n- Boilerplate name (e.g., \"scaffold-nextjs-app\", \"scaffold-vite-app\")\n- Description of what the boilerplate creates\n- Target folder where projects will be created (e.g., \"apps\", \"packages\")\n- Required and optional variables in the variables_schema{% endif %}\n\n## Step 2: Gather Required Information\nBased on the {% if isMonolith %}`.toolkit/settings.yaml` sourceTemplate{% else %}selected boilerplate's variables_schema{% endif %}, collect:\n{% if not isMonolith %}- **Project name**: Must be kebab-case (e.g., \"my-new-app\", not \"MyNewApp\")\n{% endif %}- **Required variables**: All variables marked as required: true\n- **Optional variables**: Variables with required: false (ask user if needed)\n\nCommon variables:\n- `appName` or `packageName`: The project name (kebab-case)\n- `description`: Brief description of what the project does\n- `author`: Author name\n\n## Step 3: Execute the Boilerplate\nUse the `use-boilerplate` tool with:\n{% if not isMonolith %}- `boilerplateName`: Exact name from list-boilerplates response\n{% endif %}- `variables`: Object matching the variables_schema exactly\n\n**Example:**\n```json\n{\n{% if not isMonolith %}  \"boilerplateName\": \"scaffold-nextjs-app\",\n{% endif %}  \"variables\": {\n    \"appName\": \"my-dashboard\",\n    \"description\": \"Admin dashboard for managing users\",\n    \"author\": \"John Doe\"\n  }\n}\n```\n\n## Important Guidelines:\n{% if not isMonolith %}- **Always call `list-boilerplates` first** to see available options and their schemas{% else %}- The boilerplate name is auto-detected from `.toolkit/settings.yaml` (or legacy `toolkit.yaml`){% endif %}\n- **Use exact variable names** from the schema (case-sensitive)\n- **Provide all required variables** - the tool will fail if any are missing\n{% if not isMonolith %}- **Use kebab-case for project names** (e.g., \"user-dashboard\", not \"UserDashboard\")\n- The tool will create the project in the appropriate directory automatically{% else %}- The tool will create files at the workspace root{% endif %}\n- After creation, inform the user {% if isMonolith %}what files were created{% else %}where the project was created{% endif %}\n\n## Step 4: Review and Add Features (If Needed)\nAfter the boilerplate is created, **consider if additional features are needed**:\n1. **READ** the generated {% if isMonolith %}application{% else %}project{% endif %} structure to understand what was created\n2. **REVIEW** the user's request to see if they asked for specific features (e.g., \"with tool for X\", \"with prompt for Y\")\n3. **If features are needed**:\n   - Use `list-scaffolding-methods`{% if not isMonolith %} with the new project path{% endif %}\n   - Use `use-scaffold-method` to add tools, services, prompts, etc.\n   - **IMPLEMENT** the actual logic in the scaffolded feature files\n   - **REMOVE the `// @scaffold-generated` marker** from each file after implementing it (see below)\n   - **REGISTER** the features in `src/server/index.ts`\n4. **Install dependencies**: Remind user to run `pnpm install`\n5. **Report** the complete setup including any features added\n\n## Scaffold Marker — Remove After Implementing\nGenerated `.ts`/`.tsx`/`.js`/`.jsx` files contain `// @scaffold-generated` at the top. This comment flags unimplemented boilerplate files.\n\n**You MUST delete this line once a file is fully implemented.** Leaving it in place marks the file as a \"phantom\" — a scaffolded file whose logic was never written. The marker is checked at session boundaries to catch files that were accidentally left as empty templates.\n\n## Example Workflow:\n{% if not isMonolith %}1. Call `list-boilerplates` → See available templates\n2. Ask user which template to use (or infer from request)\n3. Collect required variables based on schema\n4. Call `use-boilerplate` with boilerplateName and variables{% else %}1. Collect required variables based on the monolith template's variables_schema from `.toolkit/settings.yaml`\n2. Call `use-boilerplate` with variables (boilerplateName auto-detected){% endif %}\n5. **Review if user requested specific features (tools, prompts, etc.)**\n6. **If features needed**: Add them using `list-scaffolding-methods` and `use-scaffold-method`\n7. **READ and IMPLEMENT** the scaffolded feature files with actual logic\n8. **REMOVE `// @scaffold-generated`** from each file once implemented\n9. Report success and next steps to the user\n";
 
 //#endregion
 //#region src/prompts/ScaffoldApplicationPrompt.ts

package/dist/{src-COn3FXEz.mjs → src-sY88BbkJ.mjs}

@@ -1,5 +1,5 @@
-import { l as TemplateService, t as ListScaffoldingMethodsTool } from "./ListScaffoldingMethodsTool-Cx-0gpV3.mjs";
-import { a as GenerateFeatureScaffoldTool, i as ListBoilerplatesTool, n as UseScaffoldMethodTool, o as GenerateBoilerplateTool, r as UseBoilerplateTool, s as GenerateBoilerplateFileTool, t as WriteToFileTool } from "./tools-DtGTxmf-.mjs";
+import { l as TemplateService, t as ListScaffoldingMethodsTool } from "./ListScaffoldingMethodsTool-D6BkKQyK.mjs";
+import { a as GenerateFeatureScaffoldTool, i as ListBoilerplatesTool, n as UseScaffoldMethodTool, o as GenerateBoilerplateTool, r as UseBoilerplateTool, s as GenerateBoilerplateFileTool, t as WriteToFileTool } from "./tools-t-HMGLVh.mjs";
 import { TemplatesManagerService } from "@agiflowai/aicode-utils";
 import { Server } from "@modelcontextprotocol/sdk/server/index.js";
 import { CallToolRequestSchema, GetPromptRequestSchema, ListPromptsRequestSchema, ListToolsRequestSchema, isInitializeRequest } from "@modelcontextprotocol/sdk/types.js";
@@ -11,11 +11,11 @@ import { randomUUID } from "node:crypto";
 import { StreamableHTTPServerTransport } from "@modelcontextprotocol/sdk/server/streamableHttp.js";
 
 //#region package.json
-var version = "1.0.23";
+var version = "1.0.25";
 
 //#endregion
 //#region src/instructions/server.md?raw
-var server_default = "Use this MCP server to {% if isMonolith %}create your monolith project and add features (pages, components, services, etc.){% else %}create new projects and add features (pages, components, services, etc.){% endif %}.\n\n## Workflow:\n{% if not isMonolith %}\n1. **Creating New Project**: Use `list-boilerplates` → `use-boilerplate`\n2. **Adding Features**: Use `list-scaffolding-methods` → `use-scaffold-method`\n{% else %}\n1. **Creating Project**: Use `use-boilerplate` (boilerplateName auto-detected from toolkit.yaml)\n2. **Adding Features**: Use `list-scaffolding-methods` → `use-scaffold-method`\n{% endif %}\n\n## AI Usage Guidelines:\n{% if not isMonolith %}\n- Always call `list-boilerplates` first when creating new projects to see available options\n{% endif %}\n- Always call `list-scaffolding-methods` first when adding features to understand what's available\n- Follow the exact variable schema provided - validation will fail if required fields are missing\n{% if not isMonolith %}\n- Use kebab-case for project names (e.g., \"my-new-app\")\n{% else %}\n- In monolith mode, parameters like `boilerplateName` and `templateName` are auto-detected from toolkit.yaml\n- You only need to provide `variables` when calling `use-boilerplate` or `use-scaffold-method`\n{% endif %}\n- The tools automatically handle file placement, imports, and code generation\n- Check the returned JSON schemas to understand required vs optional variables\n{% if adminEnabled %}\n\n## Admin Mode (Template Generation):\n\nWhen creating custom boilerplate templates for frameworks not yet supported:\n\n1. **Create Boilerplate Configuration**: Use `generate-boilerplate` to add a new boilerplate entry to a template's scaffold.yaml\n   - Specify template name, boilerplate name, description, target folder, and variable schema\n   - This creates the scaffold.yaml structure following the nextjs-15 pattern\n   - Optional: Add detailed instruction about file purposes and design patterns\n\n2. **Create Feature Configuration**: Use `generate-feature-scaffold` to add a new feature entry to a template's scaffold.yaml\n   - Specify template name, feature name, generator, description, and variable schema\n   - This creates the scaffold.yaml structure for feature scaffolds (pages, components, etc.)\n   - Optional: Add detailed instruction about file purposes and design patterns\n   - Optional: Specify patterns to match existing files this feature works with\n\n3. **Create Template Files**: Use `generate-boilerplate-file` to create the actual template files\n   - Create files referenced in the boilerplate's or feature's includes array\n   - Use {{ variableName }} syntax for Liquid variable placeholders\n   - Can copy from existing source files or provide content directly\n   - Files automatically get .liquid extension\n\n4. **Test the Template**: Use `list-boilerplates`/`list-scaffolding-methods` and `use-boilerplate`/`use-scaffold-method` to verify your template works\n\nExample workflow for boilerplate:\n```\n1. generate-boilerplate { templateName: \"react-vite\", boilerplateName: \"scaffold-vite-app\", ... }\n2. generate-boilerplate-file { templateName: \"react-vite\", filePath: \"package.json\", content: \"...\" }\n3. generate-boilerplate-file { templateName: \"react-vite\", filePath: \"src/App.tsx\", content: \"...\" }\n4. list-boilerplates (verify it appears)\n5. use-boilerplate { boilerplateName: \"scaffold-vite-app\", variables: {...} }\n```\n\nExample workflow for feature:\n```\n1. generate-feature-scaffold { templateName: \"nextjs-15\", featureName: \"scaffold-nextjs-component\", generator: \"componentGenerator.ts\", ... }\n2. generate-boilerplate-file { templateName: \"nextjs-15\", filePath: \"src/components/Component.tsx\", content: \"...\" }\n3. list-scaffolding-methods (verify it appears)\n4. use-scaffold-method { scaffoldName: \"scaffold-nextjs-component\", variables: {...} }\n```\n{% endif %}\n";
+var server_default = "Use this MCP server to {% if isMonolith %}create your monolith project and add features (pages, components, services, etc.){% else %}create new projects and add features (pages, components, services, etc.){% endif %}.\n\n## Workflow:\n{% if not isMonolith %}\n1. **Creating New Project**: Use `list-boilerplates` → `use-boilerplate`\n2. **Adding Features**: Use `list-scaffolding-methods` → `use-scaffold-method`\n{% else %}\n1. **Creating Project**: Use `use-boilerplate` (boilerplateName auto-detected from `.toolkit/settings.yaml`)\n2. **Adding Features**: Use `list-scaffolding-methods` → `use-scaffold-method`\n{% endif %}\n\n## AI Usage Guidelines:\n{% if not isMonolith %}\n- Always call `list-boilerplates` first when creating new projects to see available options\n{% endif %}\n- Always call `list-scaffolding-methods` first when adding features to understand what's available\n- Follow the exact variable schema provided - validation will fail if required fields are missing\n{% if not isMonolith %}\n- Use kebab-case for project names (e.g., \"my-new-app\")\n{% else %}\n- In monolith mode, parameters like `boilerplateName` and `templateName` are auto-detected from `.toolkit/settings.yaml`\n- You only need to provide `variables` when calling `use-boilerplate` or `use-scaffold-method`\n{% endif %}\n- The tools automatically handle file placement, imports, and code generation\n- Check the returned JSON schemas to understand required vs optional variables\n{% if adminEnabled %}\n\n## Admin Mode (Template Generation):\n\nWhen creating custom boilerplate templates for frameworks not yet supported:\n\n1. **Create Boilerplate Configuration**: Use `generate-boilerplate` to add a new boilerplate entry to a template's scaffold.yaml\n   - Specify template name, boilerplate name, description, target folder, and variable schema\n   - This creates the scaffold.yaml structure following the nextjs-15 pattern\n   - Optional: Add detailed instruction about file purposes and design patterns\n\n2. **Create Feature Configuration**: Use `generate-feature-scaffold` to add a new feature entry to a template's scaffold.yaml\n   - Specify template name, feature name, generator, description, and variable schema\n   - This creates the scaffold.yaml structure for feature scaffolds (pages, components, etc.)\n   - Optional: Add detailed instruction about file purposes and design patterns\n   - Optional: Specify patterns to match existing files this feature works with\n\n3. **Create Template Files**: Use `generate-boilerplate-file` to create the actual template files\n   - Create files referenced in the boilerplate's or feature's includes array\n   - Use {{ variableName }} syntax for Liquid variable placeholders\n   - Can copy from existing source files or provide content directly\n   - Files automatically get .liquid extension\n\n4. **Test the Template**: Use `list-boilerplates`/`list-scaffolding-methods` and `use-boilerplate`/`use-scaffold-method` to verify your template works\n\nExample workflow for boilerplate:\n```\n1. generate-boilerplate { templateName: \"react-vite\", boilerplateName: \"scaffold-vite-app\", ... }\n2. generate-boilerplate-file { templateName: \"react-vite\", filePath: \"package.json\", content: \"...\" }\n3. generate-boilerplate-file { templateName: \"react-vite\", filePath: \"src/App.tsx\", content: \"...\" }\n4. list-boilerplates (verify it appears)\n5. use-boilerplate { boilerplateName: \"scaffold-vite-app\", variables: {...} }\n```\n\nExample workflow for feature:\n```\n1. generate-feature-scaffold { templateName: \"nextjs-15\", featureName: \"scaffold-nextjs-component\", generator: \"componentGenerator.ts\", ... }\n2. generate-boilerplate-file { templateName: \"nextjs-15\", filePath: \"src/components/Component.tsx\", content: \"...\" }\n3. list-scaffolding-methods (verify it appears)\n4. use-scaffold-method { scaffoldName: \"scaffold-nextjs-component\", variables: {...} }\n```\n{% endif %}\n";
 
 //#endregion
 //#region src/instructions/prompts/generate-boilerplate.md?raw
@@ -79,7 +79,7 @@ var GenerateBoilerplatePrompt = class GenerateBoilerplatePrompt {
 
 //#endregion
 //#region src/instructions/prompts/generate-feature-scaffold.md?raw
-var generate_feature_scaffold_default = "{% if promptAsSkill %}---\nname: generate-feature-scaffold\ndescription: Create a new feature scaffold configuration for adding features to existing projects. Use this skill when the user wants to define a reusable feature template (e.g., page, component, service, API route) that can be used to add functionality to projects of a specific type. This is an admin/developer tool for creating the feature scaffold definitions themselves, not for using existing scaffolds. It generates feature configurations in scaffold.yaml and template files with Liquid syntax and conditional includes.\n---\n\n{% endif %}You are helping create a new feature scaffold configuration using the scaffold-mcp MCP tools.\n\n{% if request %}User request: {{ request }}\n{% endif %}\nYour task:\n\n1. **Gather Information**: Ask for any missing details:\n   {% if not isMonolith %}- Template name (e.g., \"nextjs-15\", \"react-vite\"){% else %}- Template name (will be auto-detected from toolkit.yaml){% endif %}\n   - Feature name (prefixed with \"scaffold-\", e.g., \"scaffold-nextjs-page\")\n   - Feature type (page, component, service, etc.)\n   - Variables needed\n   - Files to include\n\n2. **Use MCP Tools** in order:\n   - `generate-feature-scaffold` - Creates the feature configuration\n   - `generate-boilerplate-file` - Creates each template file\n   - `list-scaffolding-methods` - Verify it appears\n   - `use-scaffold-method` - Test the feature\n\nImportant:\n- Feature names: prefix with \"scaffold-\"\n- Conditional includes: use \"file.tsx?withLayout=true\"\n- Template syntax: use {{ variableName }}\n{% if isMonolith %}- Template name will be auto-detected from toolkit.yaml{% endif %}\n\n**Description Field Guidelines (CRITICAL)**:\nThe description should explain what the feature scaffold generates (2-3 sentences):\n- Sentence 1: What type of code it generates (component, page, service, etc.)\n- Sentence 2: Key features or capabilities included\n- Sentence 3: Primary use cases or when to use it\n\nExample:\n\"Generate a new service class for TypeScript libraries following best practices. Creates a service class with interface, implementation, and unit tests. Perfect for creating reusable service modules with dependency injection patterns.\"\n\n**Instruction Field Guidelines (CRITICAL)**:\nThe instruction should provide specific guidance for using the generated feature:\n\n1. **Pattern explanation**: Describe the architectural pattern used\n2. **File organization**: Where files should be placed\n3. **Naming conventions**: How to name things (PascalCase, camelCase, etc.)\n4. **Usage guidelines**: How to use the generated code\n5. **Testing approach**: How to test the feature\n\nExample structure:\n\"[Feature type] follow a [pattern name] pattern with [key characteristics].\n[Explanation of how it works and integrates with the project].\nPlace [files] in [directory].\nFor [features with X], define [Y] in [Z] for better separation of concerns.\n[Feature names] should be [case style] and [suffix/prefix rules].\nWrite comprehensive [tests/docs] for all [public methods/exports].\"\n\nKeep it concise but informative - focus on the patterns and conventions that AI needs to understand to work with the generated code effectively.\n\nTemplate File Content Guidelines:\n- Keep content MINIMAL and business-agnostic\n- Focus on structure and patterns, not business logic\n- Use placeholder/generic examples only\n- Include essential boilerplate code only\n- Let AI fill in specific logic later\n- Add clear headers with design patterns and coding standards\n";
+var generate_feature_scaffold_default = "{% if promptAsSkill %}---\nname: generate-feature-scaffold\ndescription: Create a new feature scaffold configuration for adding features to existing projects. Use this skill when the user wants to define a reusable feature template (e.g., page, component, service, API route) that can be used to add functionality to projects of a specific type. This is an admin/developer tool for creating the feature scaffold definitions themselves, not for using existing scaffolds. It generates feature configurations in scaffold.yaml and template files with Liquid syntax and conditional includes.\n---\n\n{% endif %}You are helping create a new feature scaffold configuration using the scaffold-mcp MCP tools.\n\n{% if request %}User request: {{ request }}\n{% endif %}\nYour task:\n\n1. **Gather Information**: Ask for any missing details:\n   {% if not isMonolith %}- Template name (e.g., \"nextjs-15\", \"react-vite\"){% else %}- Template name (will be auto-detected from `.toolkit/settings.yaml`){% endif %}\n   - Feature name (prefixed with \"scaffold-\", e.g., \"scaffold-nextjs-page\")\n   - Feature type (page, component, service, etc.)\n   - Variables needed\n   - Files to include\n\n2. **Use MCP Tools** in order:\n   - `generate-feature-scaffold` - Creates the feature configuration\n   - `generate-boilerplate-file` - Creates each template file\n   - `list-scaffolding-methods` - Verify it appears\n   - `use-scaffold-method` - Test the feature\n\nImportant:\n- Feature names: prefix with \"scaffold-\"\n- Conditional includes: use \"file.tsx?withLayout=true\"\n- Template syntax: use {{ variableName }}\n{% if isMonolith %}- Template name will be auto-detected from `.toolkit/settings.yaml`{% endif %}\n\n**Description Field Guidelines (CRITICAL)**:\nThe description should explain what the feature scaffold generates (2-3 sentences):\n- Sentence 1: What type of code it generates (component, page, service, etc.)\n- Sentence 2: Key features or capabilities included\n- Sentence 3: Primary use cases or when to use it\n\nExample:\n\"Generate a new service class for TypeScript libraries following best practices. Creates a service class with interface, implementation, and unit tests. Perfect for creating reusable service modules with dependency injection patterns.\"\n\n**Instruction Field Guidelines (CRITICAL)**:\nThe instruction should provide specific guidance for using the generated feature:\n\n1. **Pattern explanation**: Describe the architectural pattern used\n2. **File organization**: Where files should be placed\n3. **Naming conventions**: How to name things (PascalCase, camelCase, etc.)\n4. **Usage guidelines**: How to use the generated code\n5. **Testing approach**: How to test the feature\n\nExample structure:\n\"[Feature type] follow a [pattern name] pattern with [key characteristics].\n[Explanation of how it works and integrates with the project].\nPlace [files] in [directory].\nFor [features with X], define [Y] in [Z] for better separation of concerns.\n[Feature names] should be [case style] and [suffix/prefix rules].\nWrite comprehensive [tests/docs] for all [public methods/exports].\"\n\nKeep it concise but informative - focus on the patterns and conventions that AI needs to understand to work with the generated code effectively.\n\nTemplate File Content Guidelines:\n- Keep content MINIMAL and business-agnostic\n- Focus on structure and patterns, not business logic\n- Use placeholder/generic examples only\n- Include essential boilerplate code only\n- Let AI fill in specific logic later\n- Add clear headers with design patterns and coding standards\n";
 
 //#endregion
 //#region src/prompts/GenerateFeatureScaffoldPrompt.ts
@@ -139,7 +139,7 @@ var GenerateFeatureScaffoldPrompt = class GenerateFeatureScaffoldPrompt {
 
 //#endregion
 //#region src/instructions/prompts/scaffold-application.md?raw
-var scaffold_application_default = "{% if promptAsSkill %}---\nname: scaffold-application\ndescription: Create a new application or project from a boilerplate template. Use this skill when the user wants to start a new project, create a new app, or bootstrap a new codebase from scratch. This skill lists available boilerplate templates (React, Next.js, Express, etc.), gathers required configuration variables, generates the complete project structure, and provides guidance on next steps including adding features.\n---\n\n{% endif %}You are helping create a new {% if isMonolith %}monolith application{% else %}application{% endif %} using the scaffold-mcp MCP tools.\n\n{% if request %}User request: {{ request }}\n{% endif %}\nYour task is to scaffold a new application by following this workflow:\n\n## Step 1: {% if isMonolith %}Prepare to Create Application{% else %}List Available Boilerplates{% endif %}\n{% if isMonolith %}You will use the `use-boilerplate` tool to create your monolith application. The boilerplate name will be auto-detected from your toolkit.yaml file.{% else %}Use the `list-boilerplates` tool to see all available project templates.\n\n**What to look for:**\n- Boilerplate name (e.g., \"scaffold-nextjs-app\", \"scaffold-vite-app\")\n- Description of what the boilerplate creates\n- Target folder where projects will be created (e.g., \"apps\", \"packages\")\n- Required and optional variables in the variables_schema{% endif %}\n\n## Step 2: Gather Required Information\nBased on the {% if isMonolith %}toolkit.yaml{% else %}selected boilerplate's variables_schema{% endif %}, collect:\n{% if not isMonolith %}- **Project name**: Must be kebab-case (e.g., \"my-new-app\", not \"MyNewApp\")\n{% endif %}- **Required variables**: All variables marked as required: true\n- **Optional variables**: Variables with required: false (ask user if needed)\n\nCommon variables:\n- `appName` or `packageName`: The project name (kebab-case)\n- `description`: Brief description of what the project does\n- `author`: Author name\n\n## Step 3: Execute the Boilerplate\nUse the `use-boilerplate` tool with:\n{% if not isMonolith %}- `boilerplateName`: Exact name from list-boilerplates response\n{% endif %}- `variables`: Object matching the variables_schema exactly\n\n**Example:**\n```json\n{\n{% if not isMonolith %}  \"boilerplateName\": \"scaffold-nextjs-app\",\n{% endif %}  \"variables\": {\n    \"appName\": \"my-dashboard\",\n    \"description\": \"Admin dashboard for managing users\",\n    \"author\": \"John Doe\"\n  }\n}\n```\n\n## Important Guidelines:\n{% if not isMonolith %}- **Always call `list-boilerplates` first** to see available options and their schemas{% else %}- The boilerplate name is auto-detected from toolkit.yaml{% endif %}\n- **Use exact variable names** from the schema (case-sensitive)\n- **Provide all required variables** - the tool will fail if any are missing\n{% if not isMonolith %}- **Use kebab-case for project names** (e.g., \"user-dashboard\", not \"UserDashboard\")\n- The tool will create the project in the appropriate directory automatically{% else %}- The tool will create files at the workspace root{% endif %}\n- After creation, inform the user {% if isMonolith %}what files were created{% else %}where the project was created{% endif %}\n\n## Step 4: Review and Add Features (If Needed)\nAfter the boilerplate is created, **consider if additional features are needed**:\n1. **READ** the generated {% if isMonolith %}application{% else %}project{% endif %} structure to understand what was created\n2. **REVIEW** the user's request to see if they asked for specific features (e.g., \"with tool for X\", \"with prompt for Y\")\n3. **If features are needed**:\n   - Use `list-scaffolding-methods`{% if not isMonolith %} with the new project path{% endif %}\n   - Use `use-scaffold-method` to add tools, services, prompts, etc.\n   - **IMPLEMENT** the actual logic in the scaffolded feature files\n   - **REMOVE the `// @scaffold-generated` marker** from each file after implementing it (see below)\n   - **REGISTER** the features in `src/server/index.ts`\n4. **Install dependencies**: Remind user to run `pnpm install`\n5. **Report** the complete setup including any features added\n\n## Scaffold Marker — Remove After Implementing\nGenerated `.ts`/`.tsx`/`.js`/`.jsx` files contain `// @scaffold-generated` at the top. This comment flags unimplemented boilerplate files.\n\n**You MUST delete this line once a file is fully implemented.** Leaving it in place marks the file as a \"phantom\" — a scaffolded file whose logic was never written. The marker is checked at session boundaries to catch files that were accidentally left as empty templates.\n\n## Example Workflow:\n{% if not isMonolith %}1. Call `list-boilerplates` → See available templates\n2. Ask user which template to use (or infer from request)\n3. Collect required variables based on schema\n4. Call `use-boilerplate` with boilerplateName and variables{% else %}1. Collect required variables based on toolkit.yaml variables_schema\n2. Call `use-boilerplate` with variables (boilerplateName auto-detected){% endif %}\n5. **Review if user requested specific features (tools, prompts, etc.)**\n6. **If features needed**: Add them using `list-scaffolding-methods` and `use-scaffold-method`\n7. **READ and IMPLEMENT** the scaffolded feature files with actual logic\n8. **REMOVE `// @scaffold-generated`** from each file once implemented\n9. Report success and next steps to the user\n";
+var scaffold_application_default = "{% if promptAsSkill %}---\nname: scaffold-application\ndescription: Create a new application or project from a boilerplate template. Use this skill when the user wants to start a new project, create a new app, or bootstrap a new codebase from scratch. This skill lists available boilerplate templates (React, Next.js, Express, etc.), gathers required configuration variables, generates the complete project structure, and provides guidance on next steps including adding features.\n---\n\n{% endif %}You are helping create a new {% if isMonolith %}monolith application{% else %}application{% endif %} using the scaffold-mcp MCP tools.\n\n{% if request %}User request: {{ request }}\n{% endif %}\nYour task is to scaffold a new application by following this workflow:\n\n## Step 1: {% if isMonolith %}Prepare to Create Application{% else %}List Available Boilerplates{% endif %}\n{% if isMonolith %}You will use the `use-boilerplate` tool to create your monolith application. The boilerplate name will be auto-detected from your `.toolkit/settings.yaml` file (or legacy `toolkit.yaml` if present).{% else %}Use the `list-boilerplates` tool to see all available project templates.\n\n**What to look for:**\n- Boilerplate name (e.g., \"scaffold-nextjs-app\", \"scaffold-vite-app\")\n- Description of what the boilerplate creates\n- Target folder where projects will be created (e.g., \"apps\", \"packages\")\n- Required and optional variables in the variables_schema{% endif %}\n\n## Step 2: Gather Required Information\nBased on the {% if isMonolith %}`.toolkit/settings.yaml` sourceTemplate{% else %}selected boilerplate's variables_schema{% endif %}, collect:\n{% if not isMonolith %}- **Project name**: Must be kebab-case (e.g., \"my-new-app\", not \"MyNewApp\")\n{% endif %}- **Required variables**: All variables marked as required: true\n- **Optional variables**: Variables with required: false (ask user if needed)\n\nCommon variables:\n- `appName` or `packageName`: The project name (kebab-case)\n- `description`: Brief description of what the project does\n- `author`: Author name\n\n## Step 3: Execute the Boilerplate\nUse the `use-boilerplate` tool with:\n{% if not isMonolith %}- `boilerplateName`: Exact name from list-boilerplates response\n{% endif %}- `variables`: Object matching the variables_schema exactly\n\n**Example:**\n```json\n{\n{% if not isMonolith %}  \"boilerplateName\": \"scaffold-nextjs-app\",\n{% endif %}  \"variables\": {\n    \"appName\": \"my-dashboard\",\n    \"description\": \"Admin dashboard for managing users\",\n    \"author\": \"John Doe\"\n  }\n}\n```\n\n## Important Guidelines:\n{% if not isMonolith %}- **Always call `list-boilerplates` first** to see available options and their schemas{% else %}- The boilerplate name is auto-detected from `.toolkit/settings.yaml` (or legacy `toolkit.yaml`){% endif %}\n- **Use exact variable names** from the schema (case-sensitive)\n- **Provide all required variables** - the tool will fail if any are missing\n{% if not isMonolith %}- **Use kebab-case for project names** (e.g., \"user-dashboard\", not \"UserDashboard\")\n- The tool will create the project in the appropriate directory automatically{% else %}- The tool will create files at the workspace root{% endif %}\n- After creation, inform the user {% if isMonolith %}what files were created{% else %}where the project was created{% endif %}\n\n## Step 4: Review and Add Features (If Needed)\nAfter the boilerplate is created, **consider if additional features are needed**:\n1. **READ** the generated {% if isMonolith %}application{% else %}project{% endif %} structure to understand what was created\n2. **REVIEW** the user's request to see if they asked for specific features (e.g., \"with tool for X\", \"with prompt for Y\")\n3. **If features are needed**:\n   - Use `list-scaffolding-methods`{% if not isMonolith %} with the new project path{% endif %}\n   - Use `use-scaffold-method` to add tools, services, prompts, etc.\n   - **IMPLEMENT** the actual logic in the scaffolded feature files\n   - **REMOVE the `// @scaffold-generated` marker** from each file after implementing it (see below)\n   - **REGISTER** the features in `src/server/index.ts`\n4. **Install dependencies**: Remind user to run `pnpm install`\n5. **Report** the complete setup including any features added\n\n## Scaffold Marker — Remove After Implementing\nGenerated `.ts`/`.tsx`/`.js`/`.jsx` files contain `// @scaffold-generated` at the top. This comment flags unimplemented boilerplate files.\n\n**You MUST delete this line once a file is fully implemented.** Leaving it in place marks the file as a \"phantom\" — a scaffolded file whose logic was never written. The marker is checked at session boundaries to catch files that were accidentally left as empty templates.\n\n## Example Workflow:\n{% if not isMonolith %}1. Call `list-boilerplates` → See available templates\n2. Ask user which template to use (or infer from request)\n3. Collect required variables based on schema\n4. Call `use-boilerplate` with boilerplateName and variables{% else %}1. Collect required variables based on the monolith template's variables_schema from `.toolkit/settings.yaml`\n2. Call `use-boilerplate` with variables (boilerplateName auto-detected){% endif %}\n5. **Review if user requested specific features (tools, prompts, etc.)**\n6. **If features needed**: Add them using `list-scaffolding-methods` and `use-scaffold-method`\n7. **READ and IMPLEMENT** the scaffolded feature files with actual logic\n8. **REMOVE `// @scaffold-generated`** from each file once implemented\n9. Report success and next steps to the user\n";
 
 //#endregion
 //#region src/prompts/ScaffoldApplicationPrompt.ts

package/dist/{tools-CC-lrhQ8.cjs → tools-DsnQImJ1.cjs}

@@ -1,4 +1,4 @@
-const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-CkIkgP_u.cjs');
+const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-DBwZzJTA.cjs');
 let __agiflowai_aicode_utils = require("@agiflowai/aicode-utils");
 let zod = require("zod");
 let node_path = require("node:path");
@@ -1181,7 +1181,7 @@ Use this to add custom feature scaffolds (pages, components, services, etc.) for
 
 //#endregion
 //#region src/instructions/tools/list-boilerplates/description.md?raw
-var description_default$1 = "{% if isMonolith %}\nNot available for monolith projects. Monolith uses a single template defined in `toolkit.yaml`.\n\nUse `list-scaffolding-methods` for available features instead.\n{% else %}\nLists all available project boilerplates for creating new applications, APIs, or packages in the monorepo.\n\nEach boilerplate includes:\n- Complete project template with starter files\n- Variable schema for customization\n- Target directory information (e.g., apps/, packages/)\n- Required and optional configuration options\n\nUse this FIRST when creating new projects to understand available templates and their requirements.\n{% endif %}\n";
+var description_default$1 = "{% if isMonolith %}\nNot available for monolith projects. Monolith uses a single template defined in `.toolkit/settings.yaml`.\n\nUse `list-scaffolding-methods` for available features instead.\n{% else %}\nLists all available project boilerplates for creating new applications, APIs, or packages in the monorepo.\n\nEach boilerplate includes:\n- Complete project template with starter files\n- Variable schema for customization\n- Target directory information (e.g., apps/, packages/)\n- Required and optional configuration options\n\nUse this FIRST when creating new projects to understand available templates and their requirements.\n{% endif %}\n";
 
 //#endregion
 //#region src/tools/ListBoilerplatesTool.ts
@@ -1238,7 +1238,7 @@ var ListBoilerplatesTool = class ListBoilerplatesTool {
 
 //#endregion
 //#region src/instructions/tools/use-boilerplate/description.md?raw
-var description_default = "{% if isMonolith %}\nThis tool is not available for monolith projects.\n\nMonolith projects use a single template specified in `toolkit.yaml` (sourceTemplate field). The template cannot be changed through this tool - it's determined by the workspace configuration.\n\nUse `list-scaffolding-methods` and `use-scaffold-method` to add features to your monolith project instead.\n{% else %}\nCreates a new project from a boilerplate template with the specified variables.\n\n**For Monorepo Projects Only:**\nThis tool creates new sub-projects (apps, packages) in your monorepo. Each project can use a different template.\n\nThis tool will:\n- Generate all necessary files from the selected boilerplate template\n- Replace template variables with provided values\n- Create the project in targetFolder/projectName (e.g., apps/my-new-app)\n- Set up initial configuration files (package.json, tsconfig.json, etc.)\n- Create project.json with sourceTemplate reference\n\nIMPORTANT:\n- Always call `list-boilerplates` first to get the exact variable schema\n- Follow the schema exactly - required fields must be provided\n- Use kebab-case for project names (e.g., \"my-new-app\", not \"MyNewApp\")\n- The tool will validate all variables against the schema before proceeding\n- Each new project can use a different boilerplate template\n{% endif %}\n";
+var description_default = "{% if isMonolith %}\nThis tool is not available for monolith projects.\n\nMonolith projects use a single template specified in `.toolkit/settings.yaml` (`sourceTemplate`). The template cannot be changed through this tool - it's determined by the workspace configuration.\n\nUse `list-scaffolding-methods` and `use-scaffold-method` to add features to your monolith project instead.\n{% else %}\nCreates a new project from a boilerplate template with the specified variables.\n\n**For Monorepo Projects Only:**\nThis tool creates new sub-projects (apps, packages) in your monorepo. Each project can use a different template.\n\nThis tool will:\n- Generate all necessary files from the selected boilerplate template\n- Replace template variables with provided values\n- Create the project in targetFolder/projectName (e.g., apps/my-new-app)\n- Set up initial configuration files (package.json, tsconfig.json, etc.)\n- Create project.json with sourceTemplate reference\n\nIMPORTANT:\n- Always call `list-boilerplates` first to get the exact variable schema\n- Follow the schema exactly - required fields must be provided\n- Use kebab-case for project names (e.g., \"my-new-app\", not \"MyNewApp\")\n- The tool will validate all variables against the schema before proceeding\n- Each new project can use a different boilerplate template\n{% endif %}\n";
 
 //#endregion
 //#region src/tools/UseBoilerplateTool.ts

package/dist/{tools-DtGTxmf-.mjs → tools-t-HMGLVh.mjs}

@@ -1,4 +1,4 @@
-import { c as PaginationHelper, i as ScaffoldService, l as TemplateService, n as ScaffoldingMethodsService, o as ScaffoldConfigLoader, r as VariableReplacementService, s as FileSystemService } from "./ListScaffoldingMethodsTool-Cx-0gpV3.mjs";
+import { c as PaginationHelper, i as ScaffoldService, l as TemplateService, n as ScaffoldingMethodsService, o as ScaffoldConfigLoader, r as VariableReplacementService, s as FileSystemService } from "./ListScaffoldingMethodsTool-D6BkKQyK.mjs";
 import { ProjectConfigResolver, ensureDir, generateStableId, log, pathExists, pathExistsSync, readFile, readFileSync, readdir, statSync, writeFile } from "@agiflowai/aicode-utils";
 import { z } from "zod";
 import * as path$1 from "node:path";
@@ -1178,7 +1178,7 @@ Use this to add custom feature scaffolds (pages, components, services, etc.) for
 
 //#endregion
 //#region src/instructions/tools/list-boilerplates/description.md?raw
-var description_default$1 = "{% if isMonolith %}\nNot available for monolith projects. Monolith uses a single template defined in `toolkit.yaml`.\n\nUse `list-scaffolding-methods` for available features instead.\n{% else %}\nLists all available project boilerplates for creating new applications, APIs, or packages in the monorepo.\n\nEach boilerplate includes:\n- Complete project template with starter files\n- Variable schema for customization\n- Target directory information (e.g., apps/, packages/)\n- Required and optional configuration options\n\nUse this FIRST when creating new projects to understand available templates and their requirements.\n{% endif %}\n";
+var description_default$1 = "{% if isMonolith %}\nNot available for monolith projects. Monolith uses a single template defined in `.toolkit/settings.yaml`.\n\nUse `list-scaffolding-methods` for available features instead.\n{% else %}\nLists all available project boilerplates for creating new applications, APIs, or packages in the monorepo.\n\nEach boilerplate includes:\n- Complete project template with starter files\n- Variable schema for customization\n- Target directory information (e.g., apps/, packages/)\n- Required and optional configuration options\n\nUse this FIRST when creating new projects to understand available templates and their requirements.\n{% endif %}\n";
 
 //#endregion
 //#region src/tools/ListBoilerplatesTool.ts
@@ -1235,7 +1235,7 @@ var ListBoilerplatesTool = class ListBoilerplatesTool {
 
 //#endregion
 //#region src/instructions/tools/use-boilerplate/description.md?raw
-var description_default = "{% if isMonolith %}\nThis tool is not available for monolith projects.\n\nMonolith projects use a single template specified in `toolkit.yaml` (sourceTemplate field). The template cannot be changed through this tool - it's determined by the workspace configuration.\n\nUse `list-scaffolding-methods` and `use-scaffold-method` to add features to your monolith project instead.\n{% else %}\nCreates a new project from a boilerplate template with the specified variables.\n\n**For Monorepo Projects Only:**\nThis tool creates new sub-projects (apps, packages) in your monorepo. Each project can use a different template.\n\nThis tool will:\n- Generate all necessary files from the selected boilerplate template\n- Replace template variables with provided values\n- Create the project in targetFolder/projectName (e.g., apps/my-new-app)\n- Set up initial configuration files (package.json, tsconfig.json, etc.)\n- Create project.json with sourceTemplate reference\n\nIMPORTANT:\n- Always call `list-boilerplates` first to get the exact variable schema\n- Follow the schema exactly - required fields must be provided\n- Use kebab-case for project names (e.g., \"my-new-app\", not \"MyNewApp\")\n- The tool will validate all variables against the schema before proceeding\n- Each new project can use a different boilerplate template\n{% endif %}\n";
+var description_default = "{% if isMonolith %}\nThis tool is not available for monolith projects.\n\nMonolith projects use a single template specified in `.toolkit/settings.yaml` (`sourceTemplate`). The template cannot be changed through this tool - it's determined by the workspace configuration.\n\nUse `list-scaffolding-methods` and `use-scaffold-method` to add features to your monolith project instead.\n{% else %}\nCreates a new project from a boilerplate template with the specified variables.\n\n**For Monorepo Projects Only:**\nThis tool creates new sub-projects (apps, packages) in your monorepo. Each project can use a different template.\n\nThis tool will:\n- Generate all necessary files from the selected boilerplate template\n- Replace template variables with provided values\n- Create the project in targetFolder/projectName (e.g., apps/my-new-app)\n- Set up initial configuration files (package.json, tsconfig.json, etc.)\n- Create project.json with sourceTemplate reference\n\nIMPORTANT:\n- Always call `list-boilerplates` first to get the exact variable schema\n- Follow the schema exactly - required fields must be provided\n- Use kebab-case for project names (e.g., \"my-new-app\", not \"MyNewApp\")\n- The tool will validate all variables against the schema before proceeding\n- Each new project can use a different boilerplate template\n{% endif %}\n";
 
 //#endregion
 //#region src/tools/UseBoilerplateTool.ts

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@agiflowai/scaffold-mcp",
   "description": "MCP server for scaffolding applications with boilerplate templates",
-  "version": "1.0.24",
+  "version": "1.0.26",
   "license": "AGPL-3.0",
   "author": "AgiflowIO",
   "repository": {
@@ -43,15 +43,15 @@
     "execa": "^9.5.2",
     "express": "^4.21.2",
     "js-yaml": "4.1.1",
-    "liquidjs": "10.21.1",
+    "liquidjs": "10.25.0",
     "minimatch": "^10.2.3",
     "pino": "^10.0.0",
     "pino-pretty": "^13.1.1",
     "zod": "3.25.76",
-    "@agiflowai/aicode-utils": "1.0.17",
-    "@agiflowai/architect-mcp": "1.0.22",
-    "@agiflowai/coding-agent-bridge": "1.0.20",
-    "@agiflowai/hooks-adapter": "0.0.18"
+    "@agiflowai/aicode-utils": "1.0.19",
+    "@agiflowai/coding-agent-bridge": "1.0.22",
+    "@agiflowai/hooks-adapter": "0.0.20",
+    "@agiflowai/architect-mcp": "1.0.24"
   },
   "devDependencies": {
     "@types/express": "^5.0.0",