@medyll/idae-cadenzia 0.141.0 → 0.147.2

package/.eslintrc.js

@@ -0,0 +1,14 @@
+/** @type { import("eslint").Linter.Config } */
+import idaeConfig from "@medyll/idae-eslint-config"; 
+
+export default [
+  ...idaeConfig,
+  {
+    languageOptions: {
+      parserOptions: {
+        project: true,
+        tsconfigRootDir: import.meta.dirname,
+      },
+    },
+  },
+];

package/.github/copilot-instructions.md

@@ -0,0 +1,121 @@
+# Idae Database Library - AI Coding Instructions
+
+## Project Overview
+
+**@medyll/idae-db** is a TypeScript library providing a flexible database abstraction layer for MongoDB, MySQL, and ChromaDB with event-driven CRUD operations, auto-increment support, and connection pooling via singleton pattern.
+
+### Architecture
+
+The library uses a **Strategy pattern** with adapters:
+- **IdaeDb** (singleton): Entry point, manages instances per URI+DbType combo, handles initialization
+- **IdaeDbConnection**: Per-database connection instance, creates collections/tables via adapters
+- **IdaeDbAdapter**: Generic adapter facade with pre/post hooks via decorators
+- **Database-specific adapters**: MongoDBAdapter, MySQLAdapter, ChromaDBAdapter (implement IdaeDbAdapterInterface)
+- **IdaeDBModel**: Per-collection model for MongoDB, handles auto-increment tracking
+
+Key flow: `IdaeDb.init()` → `db(dbName)` → `collection<T>(name)` → operations with events
+
+## Development Commands
+
+```bash
+npm run dev          # Start Vite dev server
+npm run build        # Build and package (runs vite build + svelte-package + publint)
+npm run test         # Run Vitest tests (src/**/*.{test,spec}.{js,ts})
+npm run lint         # Check Prettier + ESLint
+npm run format       # Auto-fix formatting
+npm run check        # Svelte type checking
+npm run check:watch  # Watch mode type checking
+npm run prepackage  # Pre-publish script
+```
+
+## Code Patterns & Conventions
+
+### Event System (Critical Pattern)
+
+All adapter methods support pre/post/error hooks via **@withEmitter decorator** (in [IdaeEventEmitter.ts](src/lib/IdaeEventEmitter.ts)):
+
+```typescript
+// In adapter implementation, decorate methods:
+@withEmitter()
+async create(data: Partial<T>): Promise<T> { ... }
+
+// Register global listeners on connection:
+const collection = db.collection<User>('user');
+collection.registerEvents<User>({
+  create: {
+    pre: (data) => console.log('Creating:', data),
+    post: (result, data) => console.log('Created:', result),
+    error: (err) => console.error(err)
+  }
+});
+```
+
+Emitter events: `pre:methodName`, `post:methodName`, `error:methodName`
+
+### Adapter Pattern
+
+New adapters must implement `IdaeDbAdapterInterface<T>` from [types.ts](src/lib/@types/types.ts):
+
+```typescript
+// Required static methods for connection lifecycle
+static async connect(uri: string): Promise<Client>
+static getDb(client: Client, dbName: string): Database
+static async close(client: Client): Promise<void>
+
+// Required instance methods
+async create(data: Partial<T>): Promise<T>
+async find(params: IdaeDbParams<T>): Promise<T[]>
+async findOne(params: IdaeDbParams<T>): Promise<T | null>
+async update(id: string, updateData: Partial<T>): Promise<unknown>
+async deleteById(id: string): Promise<unknown>
+async transaction<TResult>(callback: (session) => Promise<TResult>): Promise<TResult>
+```
+
+Register new adapters in [IdaeDbAdapter.ts](src/lib/IdaeDbAdapter.ts) static initializer:
+```typescript
+static {
+  IdaeDbAdapter.addAdapter(DbType.NEWDB, MyNewAdapter);
+}
+```
+
+### Type Safety
+
+- Enforce strict TypeScript with `strict: true` in tsconfig
+- Use generic `T extends object` for all model types
+- Filter types use MongoDB's `Filter<T>` from driver for consistency
+- Query params: `IdaeDbParams<T>` with optional `query`, `sortBy`, `limit`, `skip`
+
+### ID Fields
+
+- MongoDB: uses `_id` by default or custom via `autoIncrementFormat`
+- Custom ID tracking via `IdaeDBModel.fieldId` and auto-increment collection
+- Retrieved from model: `adapter.model.fieldId`
+
+## Build & Package
+
+- **Build**: Vite → ESM output to `dist/`, exports via [index.ts](src/lib/index.ts)
+- **Package**: svelte-package generates `dist/index.d.ts` and `dist/index.js`
+- **Pre-publish**: `scripts/package-pre.js` runs before npm publish
+- **Export maps** in package.json support Svelte, ESM, and TypeScript
+
+## Testing
+
+- Framework: **Vitest** (config in [vite.config.ts](vite.config.ts))
+- Pattern: `describe()`, `it()`, `expect()` (e.g., [index.test.ts](src/index.test.ts))
+- Test files: `src/**/*.{test,spec}.{js,ts}`
+- No test database setup yet—add MongoDB/MySQL fixtures as needed
+
+## External Dependencies
+
+- **mongodb**: MongoDB driver for queries and transactions
+- **svelte/svelte-kit**: Framework (peer dependency for Svelte 5+)
+- **vite/vitest**: Build and test runner
+- **prettier/eslint**: Code formatting and linting
+- **@sveltejs/package**: Packaging utility
+
+## Known Constraints
+
+- MongoDB adapter references `.db()` for connection, needs refactoring for MySQL/ChromaDB
+- Auto-increment currently MongoDB-specific, needs abstraction
+- No transaction support in MySQL/ChromaDB adapters yet
+- DbType enum is string-based (consider supporting registration for extensibility)

package/.github/skills/idae-agent-full/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: make-agent-full
+
+description: "Expert Multi-role Agent (PM, Architect, Brainstorm, Dev, Tester, DOC) with GitHub & Kanban integration."
+tools:
+  [
+    "vscode",
+    "execute",
+    "read",
+    "edit",
+    "search",
+    "web",
+    "agent",
+    "todo",
+    "daniyalfaraz.copilot-kanban/kanban_create",
+    "daniyalfaraz.copilot-kanban/kanban_update",
+    "daniyalfaraz.copilot-kanban/kanban_get",
+    "daniyalfaraz.copilot-kanban/kanban_reset",
+  ]
+---
+
+# IDAE AGENT FULL SKILL
+
+## SYSTEM INSTRUCTIONS
+
+Multi-role AI Agent for Mydde, with GitHub & Kanban integration.
+
+**CRITICAL RULE**: Every response MUST start with [[ROLE_NAME]].
+**AUTONOMY**: Never announce an intention without acting. Always execute required actions immediately, without waiting for validation.
+
+---
+
+## 1. DYNAMIC ROLES
+
+- **[[PM]]**: Project management. Synchronizes GitHub Issues and Kanban. Examples: sprint planning, managing `backlog.md`.
+- **[[BRAINSTORM]]**: Ideation, alternatives before technical design.
+- **[[ARCHITECT]]**: Technical specifications, file structure, system design.
+- **[[DEV]]**: Implementation (SOLID code). Triggers [[DOC]] if documentation must be updated.
+- **[[TESTER]]**: Quality. **MANDATORY**: No development without a test plan.
+- **[[DOC]]**: Documentation. Manages `README.md` and project docs.
+
+---
+
+## 2. KANBAN WORKFLOW (Copilot Kanban)
+
+- **Initialization**: Use `kanban_get` to list existing tasks.
+- **Task creation**: After planning, [[PM]] uses `kanban_create` ("Ready" column).
+- **Continuous execution**: When a task moves to `in_progress` via `kanban_update`, immediately chain with [[ARCHITECT]] or [[DEV]] and execute required tools. Never wait for user validation.
+- **Completion**: Move to `done` only after Mydde's validation or [[TESTER]] approval.
+
+---
+
+## 3. SELF-DIAGNOSTIC & INITIALIZATION
+
+- **Startup check**: On first interaction, verify `.github/copilot-instructions.md`, `backlog.md`, `/idae-docs/sprints/` exist.
+- **Auto-init**: If missing, ask Mydde: "Project structure incomplete. Initialize backlog and sprints?"
+
+---
+
+## 4. CONTEXT & ISSUE DETECTION
+
+- **Context search**: Check if the task is linked to a GitHub Issue, Sprint, or Kanban card.
+- **Missing context**: If orphan, ask: "No context found. Create GitHub Issue, add to Sprint, or to Kanban?"
+
+---
+
+## 5. OPERATIONAL RULES
+
+- Always address Mydde as "tu" (informal).
+- **CHAINING**: Use multi-tool calls to chain actions in a single turn.
+- **NO IDLE TALK**: Concise answers, no unnecessary phrases. Never announce the action, just execute it.
+- Use `web` for documentation, `searchSyntax` for deep code analysis.
+- Document every major action in a dedicated `.md` file.
+
+---

package/.github/skills/make-skill-template/SKILL.md

@@ -0,0 +1,147 @@
+---
+name: make-skill-template
+description: 'Create new Agent Skills for GitHub Copilot from prompts or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional scripts/references/assets folders.'
+---
+
+# Make Skill Template
+
+A meta-skill for creating new Agent Skills. Use this skill when you need to scaffold a new skill folder, generate a SKILL.md file, or help users understand the Agent Skills specification.
+
+## When to Use This Skill
+
+- User asks to "create a skill", "make a new skill", or "scaffold a skill"
+- User wants to add a specialized capability to their GitHub Copilot setup
+- User needs help structuring a skill with bundled resources
+- User wants to duplicate this template as a starting point
+
+## Prerequisites
+
+- Understanding of what the skill should accomplish
+- A clear, keyword-rich description of capabilities and triggers
+- Knowledge of any bundled resources needed (scripts, references, assets, templates)
+
+## Creating a New Skill
+
+### Step 1: Create the Skill Directory
+
+Create a new folder with a lowercase, hyphenated name:
+
+```
+skills/<skill-name>/
+└── SKILL.md          # Required
+```
+
+### Step 2: Generate SKILL.md with Frontmatter
+
+Every skill requires YAML frontmatter with `name` and `description`:
+
+```yaml
+---
+name: <skill-name>
+description: '<What it does>. Use when <specific triggers, scenarios, keywords users might say>.'
+---
+```
+
+#### Frontmatter Field Requirements
+
+| Field | Required | Constraints |
+|-------|----------|-------------|
+| `name` | **Yes** | 1-64 chars, lowercase letters/numbers/hyphens only, must match folder name |
+| `description` | **Yes** | 1-1024 chars, must describe WHAT it does AND WHEN to use it |
+| `license` | No | License name or reference to bundled LICENSE.txt |
+| `compatibility` | No | 1-500 chars, environment requirements if needed |
+| `metadata` | No | Key-value pairs for additional properties |
+| `allowed-tools` | No | Space-delimited list of pre-approved tools (experimental) |
+
+#### Description Best Practices
+
+**CRITICAL**: The `description` is the PRIMARY mechanism for automatic skill discovery. Include:
+
+1. **WHAT** the skill does (capabilities)
+2. **WHEN** to use it (triggers, scenarios, file types)
+3. **Keywords** users might mention in prompts
+
+**Good example:**
+
+```yaml
+description: 'Toolkit for testing local web applications using Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, or view browser console logs. Supports Chrome, Firefox, and WebKit.'
+```
+
+**Poor example:**
+
+```yaml
+description: 'Web testing helpers'
+```
+
+### Step 3: Write the Skill Body
+
+After the frontmatter, add markdown instructions. Recommended sections:
+
+| Section | Purpose |
+|---------|---------|
+| `# Title` | Brief overview |
+| `## When to Use This Skill` | Reinforces description triggers |
+| `## Prerequisites` | Required tools, dependencies |
+| `## Step-by-Step Workflows` | Numbered steps for tasks |
+| `## Troubleshooting` | Common issues and solutions |
+| `## References` | Links to bundled docs |
+
+### Step 4: Add Optional Directories (If Needed)
+
+| Folder | Purpose | When to Use |
+|--------|---------|-------------|
+| `scripts/` | Executable code (Python, Bash, JS) | Automation that performs operations |
+| `references/` | Documentation agent reads | API references, schemas, guides |
+| `assets/` | Static files used AS-IS | Images, fonts, templates |
+| `templates/` | Starter code agent modifies | Scaffolds to extend |
+
+## Example: Complete Skill Structure
+
+```
+my-awesome-skill/
+├── SKILL.md                    # Required instructions
+├── LICENSE.txt                 # Optional license file
+├── scripts/
+│   └── helper.py               # Executable automation
+├── references/
+│   ├── api-reference.md        # Detailed docs
+│   └── examples.md             # Usage examples
+├── assets/
+│   └── diagram.png             # Static resources
+└── templates/
+    └── starter.ts              # Code scaffold
+```
+
+## Quick Start: Duplicate This Template
+
+1. Copy the `make-skill-template/` folder
+2. Rename to your skill name (lowercase, hyphens)
+3. Update `SKILL.md`:
+   - Change `name:` to match folder name
+   - Write a keyword-rich `description:`
+   - Replace body content with your instructions
+4. Add bundled resources as needed
+5. Validate with `npm run skill:validate`
+
+## Validation Checklist
+
+- [ ] Folder name is lowercase with hyphens
+- [ ] `name` field matches folder name exactly
+- [ ] `description` is 10-1024 characters
+- [ ] `description` explains WHAT and WHEN
+- [ ] `description` is wrapped in single quotes
+- [ ] Body content is under 500 lines
+- [ ] Bundled assets are under 5MB each
+
+## Troubleshooting
+
+| Issue | Solution |
+|-------|----------|
+| Skill not discovered | Improve description with more keywords and triggers |
+| Validation fails on name | Ensure lowercase, no consecutive hyphens, matches folder |
+| Description too short | Add capabilities, triggers, and keywords |
+| Assets not found | Use relative paths from skill root |
+
+## References
+
+- Agent Skills official spec: <https://agentskills.io/specification>

package/.github/skills/readme/skill.md

@@ -0,0 +1,37 @@
+---
+name: readme-creator
+description:  Skill to create a README.md file for any project where it stands.
+---
+
+# Skill: README File Creator (Total Style)
+
+## Overview
+This skill enables an AI agent to generate comprehensive, high-quality README.md files for any project. The agent deeply analyzes the codebase, infers architecture, usage, and conventions, and produces a README that is both informative and inviting for new contributors or users.
+
+## Capabilities
+- **Codebase Exploration**: Scans all source files, tests, configs, and scripts to extract key information.
+- **Architecture Inference**: Summarizes major modules, data flows, and design patterns.
+- **Usage Extraction**: Detects and documents public APIs, CLI commands, and integration points.
+- **Workflow Documentation**: Lists build, test, and development commands, including non-obvious scripts.
+- **Convention Highlighting**: Notes project-specific patterns, naming, and best practices.
+- **Example Generation**: Provides code snippets and usage examples from real code.
+- **Contribution Guidance**: Outlines how to contribute, run tests, and report issues.
+- **License & Credits**: Detects and documents licensing and authorship.
+
+## Usage
+- Invoke this skill to generate or update a README.md for any repository.
+- The agent will:
+  1. Analyze all relevant files (source, test, config, docs).
+  2. Synthesize a clear, well-structured README in markdown.
+  3. Include sections such as: Project Overview, Features, Installation, Usage, API, Developer Workflows, Contributing, License, and References.
+  4. Use real code and config examples from the project.
+
+## Example Output
+- See the generated [README.md](../../../../README.md) in this repository for a sample.
+
+## References
+- Main logic: See `src/` for code analysis routines.
+- Example templates: See `README.md` and `.github/copilot-instructions.md`.
+
+---
+This skill is ideal for onboarding, documentation automation, and ensuring every project is easy to understand and use.

package/.github/skills/svelte-code-writer/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: svelte-code-writer
+description: CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating or editing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
+---
+
+# Svelte 5 Code Writer
+
+## CLI Tools
+
+You have access to `@sveltejs/mcp` CLI for Svelte-specific assistance. Use these commands via `npx`:
+
+### List Documentation Sections
+
+```bash
+npx @sveltejs/mcp list-sections
+```
+
+Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths.
+
+### Get Documentation
+
+```bash
+npx @sveltejs/mcp get-documentation "<section1>,<section2>,..."
+```
+
+Retrieves full documentation for specified sections. Use after `list-sections` to fetch relevant docs.
+
+**Example:**
+
+```bash
+npx @sveltejs/mcp get-documentation "$state,$derived,$effect"
+```
+
+### Svelte Autofixer
+
+```bash
+npx @sveltejs/mcp svelte-autofixer "<code_or_path>" [options]
+```
+
+Analyzes Svelte code and suggests fixes for common issues.
+
+**Options:**
+
+- `--async` - Enable async Svelte mode (default: false)
+- `--svelte-version` - Target version: 4 or 5 (default: 5)
+
+**Examples:**
+
+```bash
+# Analyze inline code (escape $ as \$)
+npx @sveltejs/mcp svelte-autofixer '<script>let count = \$state(0);</script>'
+
+# Analyze a file
+npx @sveltejs/mcp svelte-autofixer ./src/lib/Component.svelte
+
+# Target Svelte 4
+npx @sveltejs/mcp svelte-autofixer ./Component.svelte --svelte-version 4
+```
+
+**Important:** When passing code with runes (`$state`, `$derived`, etc.) via the terminal, escape the `$` character as `\$` to prevent shell variable substitution.
+
+## Workflow
+
+1. **Uncertain about syntax?** Run `list-sections` then `get-documentation` for relevant topics
+2. **Reviewing/debugging?** Run `svelte-autofixer` on the code to detect issues
+3. **Always validate** - Run `svelte-autofixer` before finalizing any Svelte component

package/.prettierignore

@@ -1,4 +1,4 @@
-# Package Managers
-package-lock.json
-pnpm-lock.yaml
-yarn.lock
+# Package Managers
+package-lock.json
+pnpm-lock.yaml
+yarn.lock

package/.prettierrc.js

@@ -0,0 +1,5 @@
+import idaePrettierConfig from "@medyll/idae-prettier-config";
+
+export default {
+  ...idaePrettierConfig,
+};