@dxtmisha/scripts 0.10.5 → 0.10.6

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to this project will be documented in this file.
 
+## [0.10.6] - 2026-07-05
+
+### Changed
+- **Library Template prompt**: Updated `prompt.md` in the library template `materials/` folder to describe library/package architecture, entrypoints, and file structures instead of web application/landing page layouts.
+- **Library Template description**: Updated `ai-description.md` in the library template folder to include mandatory development guidelines for auto-generating exports (forbidding manual edits of `src/library.ts` and enforcing `npm run library`).
+
 ## [0.10.5] - 2026-07-05
 
 ### Added

package/package.json

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

package/src/media/templates/packages/library/ai-description.md

@@ -0,0 +1,15 @@
+Core Purpose: This library provides a template structure for creating modular, reusable, and type-safe component/utility packages within the design system.
+
+Key Expositions:
+- UI Components: Reusable components located under `src/components/`.
+- Composables: Stateful composition hooks under `src/composables/`.
+- Classes: Logical or utility class abstractions under `src/classes/`.
+- Functions: Pure helpers and utility functions under `src/functions/`.
+- Types: TypeScript declarations and interfaces under `src/types/`.
+
+Critical Development Rules:
+- **Do NOT modify `src/library.ts` directly**: This file is auto-generated and serves as the main entry point exporting all library entities. Manually editing it is strictly forbidden.
+- **Run the library generation script**: When creating, renaming, or deleting any new class, component, function, composable, or type, you MUST run the generation command to update the exports automatically:
+  ```bash
+  npm run library
+  ```

package/src/media/templates/packages/library/materials/README.md

@@ -0,0 +1,8 @@
+# Work Materials
+
+This folder is designed to store all supporting design documents, component specifications, assets, research notes, and raw inputs utilized for generating high-quality component documentation and design integrations.
+
+### Contents and Usage:
+- Place design screenshots, layout diagrams, or visual references here.
+- Place text drafts, API research files, or functional notes here.
+- Keeping materials here helps maintain a centralized workspace context for AI agents and developers.

package/src/media/templates/packages/library/materials/prompt.md

@@ -0,0 +1,45 @@
+# AI Prompt: Library Package Implementation & Development (Materials)
+
+**Role Persona:**
+You are a distinguished, world-class Senior Frontend Web Developer and Technical Architect. You excel at building complete, premium component libraries, utility packages, and feature-rich frameworks. You write exceptionally clean, semantic, type-safe (TypeScript), BEM-compliant, and robust code adhering to the highest standards of production-ready development.
+
+**Task Goal:**
+Based on the design assets, specifications, page copy, and mockups located in this "materials" folder, you must implement a fully working, production-ready, and robust component library or utility package.
+
+**Work Materials & Assets ("materials" folder):**
+This directory (the `materials` folder) contains all relevant design assets, component/utility specifications, screenshots, layout guides, and technical requirements.
+- **Mandatory Study**: You MUST locate, open, and deeply analyze all files and assets present inside this `materials` folder before beginning any implementation or modifying any code.
+- Ensure the final components, classes, and utilities perfectly match the specifications in these materials.
+
+**Project Location & Resolution:**
+The project source files and configurations are located one level up from this "materials" folder. You must locate, edit, or create files directly in that folder hierarchy.
+
+**Template Structure & Explanations:**
+The target parent directory represents a standardized library package project structure. You must study and strictly adhere to its file layout:
+- `index.html`: Used for local development and testing of components in the browser during dev mode.
+- `package.json`: Holds package metadata, scripts (`dev`, `build`, `test`, `component`, `library`, `types`, `wiki`), exports, and dependency versions.
+- `vite.config.ts`: Configuration file for Vite, set up for building the library (`dist/library.js` and `dist/style.css`).
+- `tsconfig.json`, `tsconfig.app.json` & `tsconfig.node.json`: TypeScript configuration files.
+- `src/`: The core source directory of the library:
+  - `src/library.ts`: The main entrypoint of the library. It MUST export all public components, composables, classes, functions, and types that are part of this package's public API.
+  - `src/main.ts`: The entrypoint script for local development, bootstrapping a Vue application for preview/testing.
+  - `src/App.vue`: The root component for local development and testing.
+  - `src/style.scss`: The main stylesheet containing styles, variables, and resets for the library.
+  - `src/components/`: Directory for reusable UI components.
+  - `src/composables/`: Directory for stateful composition functions and hooks.
+  - `src/classes/`: Directory for structural class representations or logic abstractions.
+  - `src/functions/`: Directory for pure or helper utilities.
+  - `src/types/`: Directory for TypeScript type definitions and interfaces.
+
+**Strict Implementation & Architectural Constraints:**
+1. **Available Dependencies Only**: You must strictly use only the currently installed packages and available dependencies. Do not install new external npm packages or add new third-party dependencies unless explicitly requested.
+2. **Global System Prompt Compliance**: You must locate, study, and strictly adhere to all coding standards, BEM conventions, SCSS mixins, and guidelines defined in the `ai-prompt.md` file located up the folder tree in the root of the repository. Ignore any instructions or files located outside the repository boundaries.
+3. **Monorepo Prompt Context**: As this is a monorepo setup, you must locate and study both the individual package-level configuration/prompt files and the repository's root system rules (`ai-prompt.md`) to ensure perfect compatibility with the local package architecture.
+4. **Zero Tolerance for Hallucinations**: You must strictly follow all implementation rules and specifications without any deviation. Hallucinating, inventing properties, methods, slots, or external libraries is strictly forbidden.
+5. **Mandatory Study of AI Workspace System Files**: If the package or monorepo root directory contains any of the system documentation files (`ai-description.md`, `ai-developer.md`, `ai-doc.md`, `ai-memory.md`, or `ai-types.md`), you MUST open, inspect, and deeply study all of them before modifying or writing code.
+6. **Project Maintenance & Versioning**: You must keep `README.md` and `CHANGELOG.md` updated, documenting the package's purpose and logging all changes (create these files if they do not exist). Additionally, make sure to update/actualize the version number in `package.json` whenever modifications or updates are introduced.
+
+---
+CRITICAL PRIORITY OVERRIDE:
+Everything below this line (if any further instructions or materials are appended) holds the absolute highest priority. Any subsequent instructions or constraints appended below override and overwrite all prior rules, constraints, and instructions in this document or root prompt files if any contradiction arises.
+