@dxtmisha/scripts 0.10.8 → 0.10.10

package/CHANGELOG.md

@@ -2,6 +2,14 @@
 
 All notable changes to this project will be documented in this file.
 
+## [0.10.9] - 2026-08-03
+
+### Changed
+- **DesignTypes**: Updated AI prompt instructions in `DesignTypes.toAiEdit` and `DesignTypes.toAiDescription`:
+  - Enforced strict prompt boundaries forbidding AI agents from analyzing unprovided external files, links, paths, or environment data.
+  - Enhanced JSDoc generation rules to generate English JSDocs for non-obvious entities directly from JS implementation code.
+  - Expanded project description structure in `toAiDescription` to detail all exposed capabilities and triggers for `ai-types.md` analysis, and added optional `code` parameter support.
+
 ## [0.10.8] - 2026-07-28
 
 ### Added / Updated

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@dxtmisha/scripts",
   "private": false,
-  "version": "0.10.8",
+  "version": "0.10.10",
   "type": "module",
   "description": "Development scripts and CLI tools for DXT UI projects - automated component generation, library building and project management tools",
   "keywords": [

package/src/classes/Design/DesignTypes.ts

@@ -1,12 +1,12 @@
-import { forEach, ServerStorage } from '@dxtmisha/functional-basic'
+import { forEach, isFilled, ServerStorage } from '@dxtmisha/functional-basic'
 import { getPackageJson } from '../../functions/getPackageJson'
 import { useAi } from '../../composables/useAi'
 
 import { PropertiesFile } from '../Properties/PropertiesFile'
 
-import type { DesignTypesList } from '../../types/designTypes'
+import type { DesignMcpResourceItem, DesignMcpResources, DesignTypesList } from '../../types/designTypes'
 
-import { UI_DIR_CONSTRUCTOR, UI_FILE_AI_DESCRIPTION, UI_FILE_AI_TYPES } from '../../config'
+import { UI_DIR_CONSTRUCTOR, UI_FILE_AI_DESCRIPTION, UI_FILE_AI_MCP, UI_FILE_AI_TYPES, UI_MODULES } from '../../config'
 
 /**
  * Engine for generating compressed and AI-optimized TypeScript type definitions.
@@ -28,9 +28,11 @@ export class DesignTypes {
    *
    * Конструктор для DesignTypes.
    * @param dir input directory path containing declaration files / входной путь к директории, содержащей файлы деклараций
+   * @param promptsDir input directory path containing prompt files / входной путь к директории, содержащей файлы промптов
    */
   constructor(
-    protected readonly dir: string = 'dist'
+    protected readonly dir: string = 'dist',
+    protected readonly promptsDir: string = 'ai-prompts'
   ) {
     ServerStorage.setErrorStatus(true)
     this.dirArray = this.dir.split('/')
@@ -53,8 +55,18 @@ export class DesignTypes {
     const aiContent = await this.toAiEdit(fullContent, fullJsContent)
     this.save(aiContent)
 
-    const aiDescription = await this.toAiDescription(fullContent)
-    this.saveDescription(aiDescription)
+    const aiDescription = await this.toAiDescription(fullContent, fullJsContent)
+
+    const promptList = this.getListPrompts()
+    const prompts = await this.toAiPrompts(promptList)
+
+    this.saveDescription(`${aiDescription}\n${prompts}`)
+
+    const mcpPrompts = await this.toAiMcpPrompts(promptList)
+
+    if (mcpPrompts) {
+      this.saveMcp(mcpPrompts)
+    }
 
     console.log('DesignTypes: AI types saved.')
   }
@@ -111,6 +123,16 @@ export class DesignTypes {
     return [...this.dirArray, file]
   }
 
+  /**
+   * Returns the project name from package.json.
+   *
+   * Возвращает название проекта из package.json.
+   * @returns project name or 'none' / название проекта или 'none'
+   */
+  protected getProjectName(): string {
+    return getPackageJson()?.name ?? 'none'
+  }
+
   /**
    * Reads the directory recursively.
    *
@@ -164,6 +186,30 @@ export class DesignTypes {
     return this.getListBy(file => this.isFileJs(file))
   }
 
+  /**
+   * Gets a list of prompt files.
+   *
+   * Получает список файлов с промптами.
+   */
+  protected getListPrompts(): DesignTypesList {
+    const files = PropertiesFile.readDirRecursive(this.promptsDir)
+
+    return forEach(
+      files,
+      (file) => {
+        const path = `${this.promptsDir}/${file}`
+        const content = PropertiesFile.readFileOnly(path)
+
+        if (content) {
+          return {
+            path,
+            content
+          }
+        }
+      }
+    ) as DesignTypesList
+  }
+
   /**
    * Reads the content of a file.
    *
@@ -213,6 +259,19 @@ export class DesignTypes {
     )
   }
 
+  /**
+   * Saves the AI-generated MCP server resources to a file.
+   *
+   * Сохраняет сгенерированные ИИ ресурсы MCP-сервера в файл.
+   * @param data data to save / данные для сохранения
+   */
+  protected saveMcp(data: object) {
+    PropertiesFile.writeByPath(
+      UI_FILE_AI_MCP,
+      JSON.stringify(data, null, 2)
+    )
+  }
+
   /**
    * Combines a list of files into a single string.
    *
@@ -270,25 +329,31 @@ export class DesignTypes {
   protected async toAiEdit(content: string, code: string): Promise<string> {
     const generate = await this.toAi(
       content,
-      'TRANSLATE all non-English comments (including JSDocs and inline comments) to English. '
-      + 'Optimize the provided type definitions, improve and supplement them if necessary. '
-      + 'Carefully study the provided JS code to understand its logic and what the code does. '
-      + 'Remove redundant or self-explanatory JSDoc comments for any entity (types, properties, variables, functions, methods, etc.) if their meaning is obvious from their name or signature and does not require documentation. '
-      + 'Keep or add clear English JSDoc comments for entities that are complex, non-obvious, or require explanation. '
-      + 'CRITICAL: Always keep all JSDoc "@example", "@remarks", "@note", and any other notes or warnings. Their contents must NOT be modified, altered, or rewritten—keep them exactly as written, only translating them to English if they are not in English. '
-      + 'CRITICAL: Remove all imports. Remove all local internal re-exports (e.g., `export * from "./..."`), but strictly KEEP any exports from external libraries or packages. '
-      + 'Remove all non-public content: delete all private and protected class methods and properties, and any non-exported elements. The final output must contain only the members and entities that are accessible from outside. '
-      + 'Remove any code segments or data that do not provide useful information for an AI assistant. '
-      + 'You may remove abstract classes or other structures that provide no practical value for code generation, but do so with extreme caution. Maintain a strict balance: if there is even a 5% chance the item might be relevant for understanding the API or generating code, keep it. Think carefully before every deletion. '
-      + 'Remove any large Enums that add excessive length without providing critical context. '
-      + 'Your goal is to create a compact, context-rich file that enables any AI coding assistant to generate high-quality code for a developer. '
-      + 'Ensure that no public API surface, essential data types, or required logic is lost. '
-      + 'Do not delete any "type" definitions; they are strictly required. '
-      + 'Remove all regular comments and inline comments (lines starting with "//" or "/* ... */"). '
-      + 'Do not include empty lines; keep the output compact and tight without blank lines. '
-      + 'CRITICAL: Do NOT return the provided JS code in your response. '
-      + 'All instructions are mandatory and must be executed perfectly. '
-      + 'Return ONLY the resulting optimized type definitions code. No markdown code blocks, no tags, no explanations, and no additional comments from the AI. NOTHING but the pure code.',
+      'Goal: Optimize and generate clean, highly informative TypeScript type definitions based ONLY on the provided code and types.\n\n'
+      + 'CRITICAL CONTEXT & SCOPE RESTRICTIONS:\n'
+      + '- IMPORTANT: The AI coding agent that will write code for developers using this library will NEVER see or have access to the underlying JS implementation code or external files. It will rely EXCLUSIVELY on the output document generated by you in this session. You MUST ensure that your output provides complete, flawless context, clear JSDoc explanations, and precise type contracts so that the reading AI agent can write accurate code without making assumptions.\n'
+      + '- Analyze ONLY the code, type definitions, and text explicitly provided in this prompt. Do NOT attempt to read, search, infer, or assume any external files, imports, project structure, or unprovided environment data.\n'
+      + '- Do NOT include any references, links, file paths, or pointers to external files or local directories in the final output, as AI agents will have no environment file access.\n'
+      + '- Do NOT return the provided JS code in your response.\n\n'
+      + 'JSDOC & COMMENT RULES:\n'
+      + '- STUDY THE PROVIDED JS CODE: You are explicitly provided with the JS implementation code (`File JS Code`). You MUST study the JS code for every function/method/property to understand its exact logic, behavior, and purpose.\n'
+      + '- GENERATE MISSING JSDOCS FROM JS CODE: If an entity lacks a JSDoc comment in the input declarations, but its provided JS code implementation reveals its behavior or purpose, you MUST generate and add a clear, fluff-free English JSDoc description directly above its declaration.\n'
+      + '- DEFINITION OF OBVIOUS (NO JSDOC): An entity is "obvious" ONLY IF its name uses clear, standard English naming conventions (e.g., `isString`, `capitalize`, `copyObject`) AND its functionality is 100% self-evident from its signature alone. Obvious entities MUST NOT have a JSDoc.\n'
+      + '- MANDATORY JSDOC FOR NON-OBVIOUS ENTITIES: Any entity with an obscure, non-standard, custom, abbreviated, or ambiguous name (e.g., `abutaSudatoho`, `transformation`), or complex logic, MUST have a clear English JSDoc description generated by inspecting its JS implementation code.\n'
+      + '- Write JSDoc comments WITHOUT fluff or filler text, focusing strictly on operational logic and behavior.\n'
+      + '- Place all JSDoc comments STRICTLY directly above the target declaration.\n'
+      + '- Translate all non-English comments and JSDocs to English.\n'
+      + '- Remove regular inline comments (`//` or `/* ... */`).\n'
+      + '- STRICTLY PRESERVE all JSDoc tags like `@example`, `@remarks`, `@note`, and warnings—keep them intact, translating only to English if needed.\n\n'
+      + 'CLEANING & OPTIMIZATION:\n'
+      + '- Remove all `import` statements and local internal re-exports (e.g., `export * from "./..."`). Strictly KEEP exports from external packages.\n'
+      + '- Delete all non-public content (private/protected class members, unexported elements). Keep all public API surfaces.\n'
+      + '- Do NOT delete any `type` definitions; they are strictly required.\n'
+      + '- Remove large Enums or structures that add length without critical context.\n'
+      + '- Exercise extreme caution when removing abstract classes: if there is even a 5% chance it helps understand the API or generate code, keep it.\n'
+      + '- Format output tightly with no blank lines.\n\n'
+      + 'OUTPUT REQUIREMENTS:\n'
+      + 'Return ONLY the resulting optimized TypeScript type definitions code. No markdown formatting, no code blocks (```), no explanations, and no additional AI text. NOTHING but pure code.',
       code
     )
 
@@ -300,22 +365,160 @@ export class DesignTypes {
    *
    * Генерирует описание проекта и рекомендации по использованию с помощью ИИ.
    * @param content cleaned type definitions / очищенные определения типов
+   * @param code JS code for analysis / JS код для анализа
+   */
+  protected async toAiDescription(content: string, code?: string): Promise<string> {
+    const generate = await this.toAi(
+      content,
+      'Goal: Generate a CONCISE, high-density project overview for an AI coding assistant to evaluate this library\'s core purpose, key module groupings, and triggers for studying type definitions.\n\n'
+      + 'CRITICAL RESTRICTIONS:\n'
+      + '- Keep the output dense, focused, and fluff-free. Avoid bloated descriptions, exhaustive lists of individual methods, classes, or components by name, or repetitive explanations.\n'
+      + '- Always group components, classes, or methods by functional category (e.g. "form components", "navigation controls", "storage utilities") instead of enumerating every individual name.\n'
+      + '- Analyze ONLY the code, type definitions, and text explicitly provided in this prompt. Do NOT assume external unprovided data.\n'
+      + '- Do NOT include file paths, relative links, URLs, or markdown formatting.\n\n'
+      + 'STRUCTURE REQUIREMENTS (Provide a single cohesive text block):\n'
+      + '1. Core Purpose: 1-2 sentences summarizing the library\'s primary technical function and responsibility.\n'
+      + '2. Key Capabilities & Groupings: Group main classes, composables, or components into high-level functional modules (e.g. API/Network, Storage, Localization, Form Components, Layout Controls, Utilities) and summarize their capabilities in tight sentences. Avoid listing individual component or method names—group them by function instead.\n'
+      + '3. Triggers for Studying ai-types.md: Under what specific coding requirements, keywords, tasks, or architectural needs is it mandatory for the AI to study "ai-types.md"?\n'
+      + '4. Integration Context: 1 sentence explaining how this library connects with other stack frameworks or packages.\n\n'
+      + 'OUTPUT REQUIREMENTS:\n'
+      + 'Return ONLY the resulting concise description text. No markdown code blocks (```), no section headers, no labels (like "Description:"), and no conversational fluff.',
+      code
+    )
+
+    return generate ?? ''
+  }
+
+  /**
+   * Generates project rules and prompt triggers description.
+   *
+   * Генерирует описание правил проекта и триггеров промптов.
+   * @param list list of prompt files / список файлов промптов
+   */
+  protected async toAiPrompts(list: DesignTypesList): Promise<string> {
+    const projectName = this.getProjectName()
+    const promptList = await Promise.all(
+      forEach(list, async (item) => {
+        const content = await this.toAiPromptName(item.content)
+
+        if (isFilled(content)) {
+          return `- '${UI_MODULES}/${projectName}/${item.path}': ${content}`
+        }
+
+        return ''
+      })
+    )
+
+    const prompts = promptList.filter(Boolean).join('\n')
+
+    if (prompts) {
+      return '## Mandatory Rules\n'
+        + 'Read the corresponding file if your task relates to:\n'
+        + `${prompts}`
+    }
+
+    return ''
+  }
+
+  /**
+   * Generates a trigger description for studying a prompt file using AI.
+   *
+   * Генерирует описание-триггер для изучения файла промпта с помощью ИИ.
+   * @param content prompt file content / содержимое файла промпта
    */
-  protected async toAiDescription(content: string): Promise<string> {
+  protected async toAiPromptName(content: string): Promise<string> {
     const generate = await this.toAi(
       content,
-      'Analyze the provided code and generate a highly technical, structured, and concise project overview specifically designed for another AI coding assistant. '
-      + 'The description must enable the reading AI to immediately evaluate whether this library contains code, components, classes, or utilities useful for its current task, and when it is mandatory to read and analyze "ai-types.md". '
-      + 'The description must be objective, factual, precise, and free of marketing fluff. '
-      + 'Include: '
-      + '1. Core Purpose: What is the primary technical function of this library? '
-      + '2. Key Expositions: What are the main classes, hooks, utilities, or components exposed by this project, and what specific tasks do they perform? '
-      + '3. Triggers for Studying ai-types.md: Under what specific conditions, keywords, or coding requirements is this library indispensable, making it mandatory for the AI to study its "ai-types.md" file? '
-      + '4. Integration Context: How does it connect with other technologies in the system stack? '
-      + 'Ensure the structure is clean and enables immediate context retrieval. '
-      + 'Return ONLY the resulting description text. No markdown, no labels like "Description:", no explanations. NOTHING but the pure content.'
+      'Goal: Generate an EXTREMELY SHORT, high-density topic summary for an AI coding assistant describing what rules/topics are covered in this prompt document.\n\n'
+      + 'CRITICAL RESTRICTIONS:\n'
+      + '- The output MUST be EXTREMELY CONCISE: 1 short sentence or clause (maximum 10-15 words).\n'
+      + '- Do NOT include repetitive filler like "When working with...", "you MUST study this document", or "in order to follow...".\n'
+      + '- Analyze ONLY the text explicitly provided in this prompt.\n'
+      + '- Do NOT include file paths, URLs, quotes, or markdown syntax.\n\n'
+      + 'EXAMPLES OF GOOD OUTPUT:\n'
+      + '- "Class structure, typing standards, SSR safety, and primitive helpers"\n'
+      + '- "HTTP client, storage management, localization, and DOM event helpers"\n'
+      + '- "MDX documentation generation rules for TypeScript classes"\n\n'
+      + 'OUTPUT REQUIREMENTS:\n'
+      + 'Return ONLY the resulting short topic summary. No markdown code blocks (```), no labels, no quotes, and no conversational text.'
     )
 
     return generate ?? ''
   }
+
+  /**
+   * Generates MCP server resources structure for prompt files using AI.
+   *
+   * Генерирует структуру ресурсов MCP-сервера для файлов промптов с помощью ИИ.
+   * @param list list of prompt files / список файлов промптов
+   * @returns object with resources array or undefined / объект со массивом ресурсов или undefined
+   */
+  protected async toAiMcpPrompts(list: DesignTypesList): Promise<DesignMcpResources | undefined> {
+    const projectName = this.getProjectName()
+    const resources: DesignMcpResourceItem[] = []
+
+    for (const item of list) {
+      const data = await this.toAiMcpResources(item.content, item.path)
+
+      if (
+        data?.name
+        && data?.description
+      ) {
+        resources.push({
+          uri: `${projectName}/${item.path}`,
+          name: data.name,
+          mimeType: data.mimeType ?? 'text/markdown',
+          description: data.description
+        })
+      }
+    }
+
+    if (resources.length > 0) {
+      return resources
+    }
+
+    return undefined
+  }
+
+  /**
+   * Generates MCP server resource metadata for a prompt document using AI.
+   *
+   * Генерирует метаданные ресурса MCP-сервера для документа промпта с помощью ИИ.
+   * @param content prompt file content / содержимое файла промпта
+   * @param file prompt file path or name / путь или имя файла промпта
+   * @returns resource metadata object or undefined / объект метаданных ресурса или undefined
+   */
+  protected async toAiMcpResources(content: string, file?: string): Promise<Partial<DesignMcpResourceItem> | undefined> {
+    const generate = await this.toAi(
+      content,
+      (file ? `File Name: ${file}\n\n` : '')
+      + 'Goal: Generate an MCP (Model Context Protocol) server resource metadata object in valid JSON format for this prompt document.\n\n'
+      + 'CRITICAL RESTRICTIONS:\n'
+      + '- The output MUST be a valid JSON object with keys: "name", "mimeType", and "description".\n'
+      + '- All text values MUST be strictly in English. Non-English languages are strictly forbidden.\n'
+      + '- "name": A concise, clear English title (2-4 words, e.g. "Coding Standards", "API Reference").\n'
+      + '- "mimeType": Must be strictly "text/markdown".\n'
+      + '- "description": A high-density, professional description strictly in English (1-2 sentences) summarizing what rules, APIs, or architectural conventions are covered in this document.\n'
+      + '- Do NOT include markdown code block wrappers (```json). Return ONLY the raw JSON string.\n\n'
+      + 'EXAMPLES OF GOOD OUTPUT:\n'
+      + '{\n'
+      + '  "name": "Coding Standards",\n'
+      + '  "mimeType": "text/markdown",\n'
+      + '  "description": "Strict architectural conventions and code implementation standards for the product."\n'
+      + '}\n\n'
+      + 'OUTPUT REQUIREMENTS:\n'
+      + 'Return ONLY the JSON object. No explanations, no markdown formatting, no conversational text.'
+    )
+
+    if (generate) {
+      try {
+        const cleaned = generate.replace(/```json|```/g, '').trim()
+        return JSON.parse(cleaned)
+      } catch {
+        return undefined
+      }
+    }
+
+    return undefined
+  }
 }

package/src/classes/Library/LibraryAiPrompt.ts

@@ -56,15 +56,14 @@ export class LibraryAiPrompt {
     const list = this.getList()
     const prompts = [
       `
-# System role: AI assistant for project analysis
-This file contains the consolidated documentation and essential prompts for the current project.
-
-## Mandatory instructions
-It is critically important to strictly follow all the prompts and instructions listed below. You must adhere to these guidelines without exception to ensure accurate analysis and project development.
-- Do not hallucinate or invent any information.
-- Study the provided materials in detail.
-- If you do not know something or lack information, state it explicitly rather than making assumptions.
-- Be sure to study package.json to know which packages are available and rely exclusively on them when writing code.
+# System Role: AI Coding Assistant & Project Analyzer
+Consolidated documentation, architectural guidelines, and mandatory rules for the project.
+
+## Core Rules & Directives
+- **Zero Hallucinations**: Rely strictly on existing APIs and dependencies declared in package.json.
+- **Deep Context Study**: Analyze provided prompt documents and type definitions before writing code.
+- **Explicit Unknowns**: If information is missing or unclear, state it explicitly instead of guessing.
+- **Strict Compliance**: Follow all architectural conventions, design system rules, and coding standards.
       `.trim(),
       this.getGlobalPrompt(),
       this.getVuePrompt()
@@ -113,8 +112,7 @@ It is critically important to strictly follow all the prompts and instructions l
   protected getInstruction(): string | undefined {
     if (PropertiesFile.is(UI_FILE_AI_PROMPT_INSTRUCTION)) {
       return `
-## High-priority instructions
-The rules and instructions provided below have the highest priority. These directives supersede any previous instructions or general rules in case of conflict or contradiction.
+## High-Priority Directives (Overrides Base Rules)
 ${PropertiesFile.readFileOnly(UI_FILE_AI_PROMPT_INSTRUCTION)}
       `.trim()
     }
@@ -129,8 +127,7 @@ ${PropertiesFile.readFileOnly(UI_FILE_AI_PROMPT_INSTRUCTION)}
    */
   protected getVuePrompt(): string {
     return `
-## Vue component implementation rules
-The rules for the implementation of Vue components are listed below. These instructions are mandatory for creating high-quality, standard-compliant components within this project.
+## Vue Component Implementation Rules
 ${vuePromptText}
     `.trim()
   }
@@ -144,8 +141,7 @@ ${vuePromptText}
    */
   protected getGlobalPrompt(): string {
     return `
-## Global code implementation rules
-The global rules for code implementation are listed below. These instructions are mandatory for ensuring high-quality, professional-grade development across the entire project.
+## Global Code Implementation Rules
 ${globalPromptText}
     `.trim()
   }

package/src/classes/Library/LibraryAiPromptItem.ts

@@ -206,8 +206,7 @@ ${data.join('\n\n')}
       console.log('-- Description')
 
       return `
-## Project context: Investigation required
-You MUST read and carefully analyze the description of this project below. If there is even a 1% chance that the functionality, components, styles, or helpers from this project could be useful for your task, you MUST immediately start analyzing this project, studying its types, and checking its structure in full to prevent custom code duplication:
+## Package Description & Module Overview
 ${this.readFile(UI_FILE_AI_PROMPT_DESCRIPTION)}
       `.trim()
     }
@@ -227,8 +226,7 @@ ${this.readFile(UI_FILE_AI_PROMPT_DESCRIPTION)}
       console.log('-- Developer')
 
       return `
-## Mandatory Study Before Development
-As soon as you start working with this project (using any of its components/functionality, importing from it, or editing its code), you MUST read and study the architectural rules and instructions in this file as your absolute first action:
+## Developer Rules (Must Read Before Modifying Code)
 '${this.getPathString()}/${UI_FILE_AI_PROMPT_DEVELOPER}'
       `.trim()
     }
@@ -248,8 +246,7 @@ As soon as you start working with this project (using any of its components/func
       console.log('-- Info')
 
       return `
-## Project information: Core overview
-This section contains essential information and the core overview of the project. Review this to understand the fundamental architecture and key features.
+## Package Core Information
 ${this.readFile(UI_FILE_AI_PROMPT_INFO)}
       `.trim()
     }
@@ -269,8 +266,7 @@ ${this.readFile(UI_FILE_AI_PROMPT_INFO)}
       console.log('-- Types')
 
       return `
-## Project types: Essential for analysis
-This file contains the complete type definitions, available utilities, and component structures for the project. As soon as you start working with this project (using any of its components/functionality, importing from it, or editing its code), you MUST read, analyze, and study this type definition file COMPLETELY and IN FULL (NOT partially), as your absolute first action using the view_file tool. This is mandatory to fully understand its API, locate all existing utilities/helpers (полезности), and prevent writing duplicate code:
+## Package Type Definitions (Must Read in Full When Working with Package)
 '${this.getPathString()}/${UI_FILE_AI_PROMPT_TYPES}'
       `.trim()
     }
@@ -293,8 +289,7 @@ This file contains the complete type definitions, available utilities, and compo
 
       const screenshot: string = list.map(item => `- '${this.getPathString()}/${UI_DIR_AI_PROMPT_SCREENSHOT}/${item}'`).join('\n')
 
-      return `## Project screenshots: Visual reference
-The project includes the following screenshots that provide a visual reference for the project's design and functionality:
+      return `## Component Visual References (Screenshots)
 ${screenshot}
       `.trim()
     }

package/src/config.ts

@@ -120,6 +120,8 @@ export const UI_FILE_INDEX = 'index.ts'
 export const UI_FILE_AI_TYPES = 'ai-types.md'
 /** AI description file name / Название файла с описанием AI */
 export const UI_FILE_AI_DESCRIPTION = 'ai-description.md'
+/** AI MCP resources file name / Название файла с ресурсами MCP AI */
+export const UI_FILE_AI_MCP = 'ai-mcp.json'
 /** Style SCSS file name / Название файла стилей SCSS */
 export const UI_FILE_STYLE_SCSS = 'style.scss'
 /** UI properties SCSS file name / Название файла свойств UI в SCSS */

package/src/media/templates/packages/library/package.json

@@ -17,9 +17,12 @@
     "publish-to-npm": "npm publish --access public"
   },
   "files": [
+    "ai-prompts/",
+    "ai-screenshot/",
     "dist",
     "ai-description.md",
     "ai-doc.md",
+    "ai-mcp.json",
     "ai-types.md",
     "CHANGELOG.md",
     "LICENSE",

package/src/media/templates/prompts/aiCodeGlobalPrompt.en.md

@@ -5,8 +5,8 @@ Strictly follow these rules for flawless dxt-ui code:
 0. **Mandatory Deep Study (CHRONOLOGICAL GUARD)**:
    - **Step 1**: Read/create local `ai-memory.md` strictly in the current package root (e.g., `packages/constructor/`). Using repository root `ai-memory.md` for package files is FORBIDDEN.
    - **Step 2**: Read root `ai-prompt.md` and study descriptions of all mentioned libraries.
-   - **Step 3**: Read all linked `ai-types.md` and `ai-developer.md` BEFORE proposing plans, calling `list_dir`, or writing code. If a package is in `node_modules/` but exists locally (e.g., `packages/`), resolve and study the local source instead.
-   - Fully read files via `view_file` before modifying. Superficial scans (grep only) are strictly forbidden. Always check existing infrastructure before writing custom logic.
+   - **Step 3**: Read all linked `ai-types.md` and `ai-developer.md` BEFORE proposing plans, inspecting directory structures, or writing code. If a package is in `node_modules/` but exists locally (e.g., `packages/`), resolve and study the local source instead.
+   - Fully read file contents before modifying them. Superficial scans (text search only) are strictly forbidden. Always check existing infrastructure before writing custom logic.
 
 1. **"Copy-Paste Ready"**: Generate complete, runnable files with correct imports. No placeholders (e.g., `// rest of code`).
 2. **Zero Hallucinations**: Strictly use `package.json` dependencies. No invented APIs. Ask if unsure.
@@ -17,5 +17,5 @@ Strictly follow these rules for flawless dxt-ui code:
 7. **Security & Performance**: Error-proof code (`?.`, `??`, guard clauses). Use explicit `try-catch` for async. Never swallow errors. Avoid heavy ops in loops/reactivity.
 8. **Aesthetics & Conciseness**: Group logically. Save tokens by avoiding redundant comments if code is self-explanatory.
 9. **Strict Adherence & Optimization**: Follow instructions precisely without guessing. Propose relevant technical optimizations while strictly adhering to plans.
-10. **AI Workspace Memory (`ai-memory.md`)**: Actively APPLY its rules (highest priority). Update it on developer feedback. Do NOT store change logs or absolute paths (use relative). Keep it focused strictly on architectural constraints.
+10. **AI Workspace Memory (`ai-memory.md`)**: Actively APPLY its rules (highest priority). Update it on developer feedback. **CRITICAL**: Any remark from the developer that has value for the future (e.g., code style, dos and don'ts) MUST be saved here. If the developer explicitly asks to save or remember something, you MUST save it. Do NOT store change logs or absolute paths (use relative). Keep it focused strictly on architectural constraints and developer preferences.
 11. **Mandatory Full-File Self-Audit**: When creating new entities, you MUST audit the ENTIRE file (not just modified parts) to ensure no logic duplication (DRY) and full compliance with project rules. *Exception: minor bug fixes to existing code do not require a full audit.*

package/src/media/templates/prompts/aiCodeGlobalPrompt.ru.md

@@ -5,8 +5,8 @@
 0. **Обязательное глубокое изучение (БЛОКИРУЮЩИЙ КОНТРОЛЬ)**:
    - **Шаг 1**: Читай/создавай локальный `ai-memory.md` СТРОГО в корне текущего пакета (напр., `packages/constructor/`). Использовать корневой `ai-memory.md` репозитория для файлов пакета ЗАПРЕЩЕНО.
    - **Шаг 2**: Прочитай корневой `ai-prompt.md` и изучи описания всех упомянутых библиотек.
-   - **Шаг 3**: Прочитай все связанные `ai-types.md` и `ai-developer.md` ДО вызова `list_dir`, планирования или написания кода. Если пакет в `node_modules/` существует локально (в `packages/`), изучай/изменяй локальные исходники.
-   - Полностью читай файлы через `view_file` перед изменением. Поверхностное изучение (только grep) запрещено. Всегда проверяй существующую инфраструктуру перед написанием кастомной логики.
+   - **Шаг 3**: Прочитай все связанные `ai-types.md` и `ai-developer.md` ДО планирования, исследования структуры директорий или написания кода. Если пакет в `node_modules/` существует локально (в `packages/`), изучай/изменяй локальные исходники.
+   - Полностью читай содержимое файлов перед изменением. Поверхностное изучение (только через поиск текста) запрещено. Всегда проверяй существующую инфраструктуру перед написанием кастомной логики.
 
 1. **Готовность к использованию (Copy-Paste Ready)**: Генерируй полные, рабочие файлы с правильными импортами. Никаких заглушек (напр., `// остальной код`).
 2. **Нулевая толерантность к галлюцинациям**: Используй только зависимости из `package.json`. Не выдумывай API. Не знаешь — спроси.
@@ -17,5 +17,5 @@
 7. **Безопасность и Производительность**: Защищенный код (`?.`, `??`, guard clauses). Явный `try-catch` для асинхронности. Не скрывай ошибки. Избегай тяжелых операций в циклах/реактивности.
 8. **Эстетика и Лаконичность**: Логическая группировка. Экономь токены, избегая избыточных комментариев, если код очевиден.
 9. **Строгое следование инструкциям**: Выполняй команды без додумывания, но предлагай уместные технические оптимизации, придерживаясь плана.
-10. **Память ИИ (`ai-memory.md`)**: Активно ПРИМЕНЯЙ ее правила (высший приоритет). Обновляй при правках от разработчика. ЗАПРЕЩЕНО хранить историю изменений (changelogs) и абсолютные пути (только относительные). Только актуальные стандарты.
+10. **Память ИИ (`ai-memory.md`)**: Активно ПРИМЕНЯЙ ее правила (высший приоритет). Обновляй при правках от разработчика. **ВАЖНО**: Любое замечание от разработчика, которое имеет ценность для будущего (например, стиль кода, что надо делать, а что нет), ДОЛЖНО быть сохранено здесь. Также, если разработчик просит сохранить или запомнить какую-либо информацию, ты ОБЯЗАН это сделать. ЗАПРЕЩЕНО хранить историю изменений (changelogs) и абсолютные пути (только относительные). Только актуальные стандарты и предпочтения разработчика.
 11. **Обязательный полный самоаудит**: При создании новых сущностей ОБЯЗАТЕЛЬНО проверяй ВЕСЬ файл целиком. Строго контролируй отсутствие дублирования (DRY) и соблюдение всех правил проекта. *Исключение: мелкие правки существующего кода не требуют полного аудита.*

package/src/types/designTypes.ts

@@ -113,3 +113,18 @@ export type DesignTypesItem = {
 }
 
 export type DesignTypesList = DesignTypesItem[]
+
+/** Design MCP resource item / Элемент ресурса MCP дизайна */
+export type DesignMcpResourceItem = {
+  /** Resource URI / URI ресурса */
+  uri: string
+  /** Resource name / Название ресурса */
+  name: string
+  /** Resource MIME type / MIME-тип ресурса */
+  mimeType: string
+  /** Resource description / Описание ресурса */
+  description: string
+}
+
+/** Design MCP resources container / Контейнер ресурсов MCP дизайна */
+export type DesignMcpResources = DesignMcpResourceItem[]