@monoes/monomindcli 2.16.1 → 2.16.3

package/.claude/skills/monodesign/scripts/pin.mjs

@@ -1,221 +0,0 @@
-#!/usr/bin/env node
-/**
- * Pin/unpin sub-commands as standalone skill shortcuts.
- *
- * Usage:
- *   node <scripts_path>/pin.mjs pin <command>
- *   node <scripts_path>/pin.mjs unpin <command>
- *
- * `pin audit` creates a lightweight audit skill that redirects to Monodesign's audit workflow.
- * `unpin audit` removes that shortcut.
- *
- * The script discovers harness directories (.claude/skills, .cursor/skills, etc.)
- * in the project root and creates/removes the pin in all of them.
- */
-
-import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync } from 'node:fs';
-import { basename, join, resolve, dirname } from 'node:path';
-import { fileURLToPath } from 'node:url';
-
-const __dirname = dirname(fileURLToPath(import.meta.url));
-
-// All known harness directories
-const HARNESS_DIRS = [
-  '.claude', '.cursor', '.gemini', '.codex', '.agents',
-  '.trae', '.trae-cn', '.pi', '.opencode', '.kiro', '.rovodev',
-];
-
-const CODEX_HARNESSES = new Set(['.codex', '.agents']);
-
-// Valid sub-command names
-const VALID_COMMANDS = [
-  'craft', 'init', 'extract', 'document', 'shape',
-  'critique', 'audit',
-  'polish', 'bolder', 'quieter', 'distill', 'harden', 'onboard', 'live',
-  'animate', 'colorize', 'typeset', 'layout', 'delight', 'overdrive',
-  'clarify', 'adapt', 'optimize',
-];
-
-// Marker to identify pinned skills (so unpin doesn't delete user skills)
-const PIN_MARKER = '<!-- monodesign-pinned-skill -->';
-
-/**
- * Walk up from startDir to find a project root.
- */
-function findProjectRoot(startDir = process.cwd()) {
-  let dir = resolve(startDir);
-  while (dir !== '/') {
-    if (
-      existsSync(join(dir, 'package.json')) ||
-      existsSync(join(dir, '.git')) ||
-      existsSync(join(dir, 'skills-lock.json'))
-    ) {
-      return dir;
-    }
-    const parent = resolve(dir, '..');
-    if (parent === dir) break;
-    dir = parent;
-  }
-  return resolve(startDir);
-}
-
-/**
- * Find harness skill directories that have an monodesign skill installed.
- */
-function findHarnessDirs(projectRoot) {
-  const dirs = [];
-  for (const harness of HARNESS_DIRS) {
-    const skillsDir = join(projectRoot, harness, 'skills');
-    // Only pin in harness dirs that already have monodesign installed
-    const monodesignDir = join(skillsDir, 'monodesign');
-    if (existsSync(monodesignDir) || existsSync(join(skillsDir, 'i-monodesign'))) {
-      dirs.push(skillsDir);
-    }
-  }
-  return dirs;
-}
-
-/**
- * Load command metadata (descriptions for pinned skills).
- */
-function loadCommandMetadata() {
-  const metadataPath = join(__dirname, 'command-metadata.json');
-  if (existsSync(metadataPath)) {
-    return JSON.parse(readFileSync(metadataPath, 'utf-8'));
-  }
-  return {};
-}
-
-/**
- * Generate a pinned skill's SKILL.md content.
- */
-function commandPrefixForSkillsDir(skillsDir) {
-  return CODEX_HARNESSES.has(basename(dirname(skillsDir))) ? '$' : '/';
-}
-
-function generatePinnedSkill(command, metadata, commandPrefix) {
-  const desc = metadata[command]?.description || `Shortcut for ${commandPrefix}monodesign ${command}.`;
-  const hint = metadata[command]?.argumentHint || '[target]';
-
-  return `---
-name: ${command}
-description: "${desc}"
-argument-hint: "${hint}"
-user-invocable: true
----
-
-${PIN_MARKER}
-
-This is a pinned shortcut for \`${commandPrefix}monodesign ${command}\`.
-
-Invoke ${commandPrefix}monodesign ${command}, passing along any arguments provided here, and follow its instructions.
-`;
-}
-
-/**
- * Pin a command: create shortcut skill in all harness dirs.
- */
-function pin(command, projectRoot) {
-  const metadata = loadCommandMetadata();
-  const harnessDirs = findHarnessDirs(projectRoot);
-
-  if (harnessDirs.length === 0) {
-    console.log('No harness directories with monodesign installed found.');
-    return false;
-  }
-
-  let created = 0;
-
-  for (const skillsDir of harnessDirs) {
-    const commandPrefix = commandPrefixForSkillsDir(skillsDir);
-    const content = generatePinnedSkill(command, metadata, commandPrefix);
-    // Check if skill already exists (and isn't a pin)
-    const skillDir = join(skillsDir, command);
-    if (existsSync(skillDir)) {
-      const existingMd = join(skillDir, 'SKILL.md');
-      if (existsSync(existingMd)) {
-        const existing = readFileSync(existingMd, 'utf-8');
-        if (!existing.includes(PIN_MARKER)) {
-          console.log(`  SKIP: ${skillDir} (non-pinned skill already exists)`);
-          continue;
-        }
-      }
-    }
-
-    mkdirSync(skillDir, { recursive: true });
-    writeFileSync(join(skillDir, 'SKILL.md'), content, 'utf-8');
-    console.log(`  + ${skillDir}`);
-    created++;
-  }
-
-  if (created > 0) {
-    console.log(`\nPinned '${command}' as a standalone shortcut in ${created} location(s).`);
-    console.log('Use the pinned command directly in each harness.');
-  }
-
-  return created > 0;
-}
-
-/**
- * Unpin a command: remove shortcut skill from all harness dirs.
- */
-function unpin(command, projectRoot) {
-  const harnessDirs = findHarnessDirs(projectRoot);
-  let removed = 0;
-
-  for (const skillsDir of harnessDirs) {
-    const skillDir = join(skillsDir, command);
-    if (!existsSync(skillDir)) continue;
-
-    const skillMd = join(skillDir, 'SKILL.md');
-    if (!existsSync(skillMd)) continue;
-
-    // Safety: only remove if it's a pinned skill
-    const content = readFileSync(skillMd, 'utf-8');
-    if (!content.includes(PIN_MARKER)) {
-      console.log(`  SKIP: ${skillDir} (not a pinned skill)`);
-      continue;
-    }
-
-    rmSync(skillDir, { recursive: true, force: true });
-    console.log(`  - ${skillDir}`);
-    removed++;
-  }
-
-  if (removed > 0) {
-    console.log(`\nUnpinned '${command}' from ${removed} location(s).`);
-    console.log(`Use Monodesign's '${command}' workflow directly to access it.`);
-  } else {
-    console.log(`No pinned '${command}' shortcut found.`);
-  }
-
-  return removed > 0;
-}
-
-// --- CLI ---
-const [,, action, command] = process.argv;
-
-if (!action || !command) {
-  console.log('Usage: node pin.mjs <pin|unpin> <command>');
-  console.log(`\nAvailable commands: ${VALID_COMMANDS.join(', ')}`);
-  process.exit(1);
-}
-
-if (action !== 'pin' && action !== 'unpin') {
-  console.error(`Unknown action: ${action}. Use 'pin' or 'unpin'.`);
-  process.exit(1);
-}
-
-if (!VALID_COMMANDS.includes(command)) {
-  console.error(`Unknown command: ${command}`);
-  console.error(`Available commands: ${VALID_COMMANDS.join(', ')}`);
-  process.exit(1);
-}
-
-const root = findProjectRoot();
-
-if (action === 'pin') {
-  pin(command, root);
-} else {
-  unpin(command, root);
-}

package/.claude/skills/monodesign/shape.md

@@ -1,71 +0,0 @@
----
-name: monodesign-shape
-description: Shape the UX and UI for a feature before any code is written — produces a structured design brief through discovery, not guesswork. Design planning only; no code written. Output is a brief for monodesign:craft.
-type: design-sub-command
-argument-hint: "[feature description]"
-user-invocable: true
----
-
-# Monodesign: Shape
-
-Shape the UX and UI for a feature before any code is written. This command produces a **design brief**: a structured artifact that guides implementation through discovery.
-
-**Scope**: Design planning only. No code written. Output: a design brief for `/monodesign craft`.
-
-## Setup
-Read `PRODUCT.md` and (if present) `DESIGN.md` from the project root before starting. These are required anchors.
-
-Read `reference/shape.md` from the monodesign skill directory for the full command flow.
-
-## Phase 1: Discovery Interview
-
-Do NOT write any code or make design decisions during this phase. Ask 2–3 questions per round, then wait for answers. Have a natural dialogue; don't dump all questions at once.
-
-**Purpose & Context**
-- What is this feature for? What problem does it solve?
-- Who specifically will use it? (Role, context, frequency — not "users")
-- What's the user's state of mind when they reach this? (Rushed? Exploring? Anxious?)
-
-**Content & Data**
-- What content or data does this display or collect?
-- What are the realistic ranges? (0 items, typical, max, edge cases)
-- What are the empty state, error state, first-time use, power-user scenarios?
-
-**Design Direction** — force a visual decision on three fronts:
-- **Color strategy**: Restrained / Committed / Full palette / Drenched
-- **Theme via scene sentence**: one sentence of physical context that forces dark vs. light
-- **Two or three named anchor references** — specific products, brands, objects (not adjectives)
-
-**Scope** — always ask explicitly:
-- Fidelity: Sketch / mid-fi / high-fi / production-ready?
-- Breadth: One screen / a flow / a whole surface?
-- Time intent: Quick exploration or polish until it ships?
-
-## Phase 2: Brief Synthesis
-
-After the discovery round, synthesize and present a structured **Design Brief**:
-
-```
-## Design Brief: [Feature Name]
-
-**User**: [concrete description]
-**Problem**: [one sentence]
-**Success**: [measurable outcome]
-**User state**: [emotional/contextual state]
-
-**Content**: [what's displayed/collected + realistic ranges]
-**Edge cases**: [empty, error, overload, first-use]
-
-**Visual direction**:
-- Color strategy: [Restrained|Committed|Full palette|Drenched]
-- Theme: [dark|light] — [scene sentence]
-- References: [3 named references]
-
-**Scope**: [fidelity] / [breadth] / [time intent]
-```
-
-Stop and wait for explicit user confirmation before advancing to `/monodesign craft`. Do not start coding until the brief is approved.
-
-## Assert-then-confirm
-
-When PRODUCT.md and the prompt make one option obvious, name it and ask the user to confirm or override. Don't present four-option menus when the answer is already clear.

package/.claude/skills/monodesign/teach.md

@@ -1,18 +0,0 @@
----
-name: monodesign-teach
-description: Alias of /monodesign init — set up a project for monodesign by producing PRODUCT.md (strategic context), optionally DESIGN.md (visual system), and pre-configuring live mode.
-type: design-sub-command
-argument-hint: "[project path or description]"
-user-invocable: true
----
-
-# Monodesign: Teach (alias of Init)
-
-`teach` is the historical name for the setup command and remains fully supported; it is an alias of `init`. Both invocations behave identically.
-
-Follow `commands/init.md` and the authoritative flow in `reference/init.md` from the monodesign skill directory: one codebase crawl plus a short strategic interview produces **PRODUCT.md** (register, users, purpose, brand personality, anti-references, design principles), offers **DESIGN.md** via `/monodesign document`, and pre-configures `.monodesign/live/config.json` for `/monodesign live`.
-
-Notes preserved from the teach era:
-
-- A legacy `.monodesign.md` at the project root is auto-renamed to `PRODUCT.md` by the context loader; mention this once and merge into that content rather than starting fresh.
-- If teach was invoked as a setup blocker by another monodesign command, complete the init flow, then resume the original task with the fresh context.

package/.claude/skills/monodesign/typeset.md

@@ -1,59 +0,0 @@
----
-name: monodesign-typeset
-description: Replace generic type defaults with fonts that reflect the brand and scale with intentional contrast — font selection, hierarchy, scale, and responsive type systems.
-type: design-sub-command
-argument-hint: "[target page, component, or whole site]"
-user-invocable: true
----
-
-# Monodesign: Typeset
-
-Typography carries most of the information on the page. Replace generic defaults (Inter, Roboto, system fallback at flat scale) with type that reflects the brand and scales with intentional contrast.
-
-Read `reference/typeset.md` and `reference/typography.md` from the monodesign skill directory for the full protocol.
-
-## Register
-
-**Brand**: font selection procedure in `reference/brand.md`. Fluid `clamp()` scale, ≥1.25 ratio between steps.
-
-**Product**: system fonts and familiar sans stacks are legitimate. One well-tuned family typically carries the whole UI. Fixed `rem` scale, 1.125–1.2 ratio.
-
-## Assess Current Typography
-
-**Font choices**
-- Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults)
-- Does the font match the brand personality?
-- Are there too many families? (More than 2–3 is almost always a mess)
-
-**Hierarchy**
-- Can you tell headings from body from captions at a glance?
-- Are sizes too close together? (14px, 15px, 16px = muddy hierarchy)
-- Are weight contrasts strong enough? (Medium vs Regular is barely visible)
-
-**Sizing & scale**
-- Is there a consistent type scale, or are sizes arbitrary?
-- Body text ≥16px?
-- Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings
-
-## Typographic Rules (non-negotiable)
-
-- Cap body line length at **65–75ch**
-- Hero/display heading ceiling: `clamp()` max ≤ **6rem (~96px)**
-- Display letter-spacing floor: **≥ -0.04em** (anything tighter makes letters touch)
-- Use `text-wrap: balance` on h1–h3; `text-wrap: pretty` on long prose
-- Pair fonts on a contrast axis (serif + sans, geometric + humanist) — NOT similar families
-- Hierarchy through scale + weight contrast (≥1.25 ratio between steps)
-
-## Font Selection Process
-
-1. Load brand context from PRODUCT.md and DESIGN.md
-2. Identify brand personality from 3 words or the product description
-3. Propose 2–3 Google Fonts / variable font pairings with rationale
-4. Load one via `<link>` and demonstrate it on a real page section
-5. Iterate until the type feels native to the brand
-
-## Output
-
-- Updated CSS custom properties or tokens for `--font-heading`, `--font-body`, `--font-mono`
-- Fluid or fixed type scale as CSS custom properties
-- Applied to all heading levels and body copy on the target

package/dist/src/routing/jev-step.d.ts

@@ -1,17 +0,0 @@
-/**
- * Route-layer step 0: the Jev decision model picks among the routing package's
- * routes (keyword hit always a candidate). null = no confident decision, and
- * the existing keyword → embeddings → Haiku cascade runs unchanged.
- * Main-process safe: no transformers/onnxruntime imports.
- */
-import { type RouteLike } from '../decision/catalogs.js';
-import { type PickOptions } from '../decision/jev.js';
-export interface JevRouteResult {
-    agentSlug: string;
-    confidence: number;
-    method: 'jev';
-    routeName: string;
-    provider: string;
-}
-export declare function routeWithJev(task: string, routes: RouteLike[], keywordSlug: string | undefined, opts?: PickOptions): Promise<JevRouteResult | null>;
-//# sourceMappingURL=jev-step.d.ts.map

package/dist/src/routing/jev-step.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"jev-step.d.ts","sourceRoot":"","sources":["../../../src/routing/jev-step.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,OAAO,EAAE,KAAK,SAAS,EAAgB,MAAM,yBAAyB,CAAC;AACvE,OAAO,EAAe,KAAK,WAAW,EAAe,MAAM,oBAAoB,CAAC;AAEhF,MAAM,WAAW,cAAc;IAC7B,SAAS,EAAE,MAAM,CAAC;IAClB,UAAU,EAAE,MAAM,CAAC;IACnB,MAAM,EAAE,KAAK,CAAC;IACd,SAAS,EAAE,MAAM,CAAC;IAClB,QAAQ,EAAE,MAAM,CAAC;CAClB;AAED,wBAAsB,YAAY,CAChC,IAAI,EAAE,MAAM,EACZ,MAAM,EAAE,SAAS,EAAE,EACnB,WAAW,EAAE,MAAM,GAAG,SAAS,EAC/B,IAAI,GAAE,WAAgB,GACrB,OAAO,CAAC,cAAc,GAAG,IAAI,CAAC,CAoBhC"}

package/dist/src/routing/jev-step.js

@@ -1,27 +0,0 @@
-/**
- * Route-layer step 0: the Jev decision model picks among the routing package's
- * routes (keyword hit always a candidate). null = no confident decision, and
- * the existing keyword → embeddings → Haiku cascade runs unchanged.
- * Main-process safe: no transformers/onnxruntime imports.
- */
-import { routeCatalog } from '../decision/catalogs.js';
-import { acceptAgent, pickWithJev } from '../decision/jev.js';
-export async function routeWithJev(task, routes, keywordSlug, opts = {}) {
-    const picked = await pickWithJev(task, { agents: routeCatalog(routes) }, {
-        ...opts,
-        include: { agents: keywordSlug ? [keywordSlug] : [] },
-        agentInstructions: 'Which specialist agent should handle this software task?',
-    });
-    const slug = acceptAgent(picked?.agent, opts.env);
-    if (!picked?.agent || !slug)
-        return null;
-    const route = routes.find((r) => r.agentSlug === slug);
-    return {
-        agentSlug: slug,
-        confidence: picked.agent.confidence,
-        method: 'jev',
-        routeName: route?.name ?? slug,
-        provider: picked.provider,
-    };
-}
-//# sourceMappingURL=jev-step.js.map

package/dist/src/routing/jev-step.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"jev-step.js","sourceRoot":"","sources":["../../../src/routing/jev-step.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,OAAO,EAAkB,YAAY,EAAE,MAAM,yBAAyB,CAAC;AACvE,OAAO,EAAE,WAAW,EAAoB,WAAW,EAAE,MAAM,oBAAoB,CAAC;AAUhF,MAAM,CAAC,KAAK,UAAU,YAAY,CAChC,IAAY,EACZ,MAAmB,EACnB,WAA+B,EAC/B,IAAI,GAAgB,EAAE;IAEtB,MAAM,MAAM,GAAG,MAAM,WAAW,CAC9B,IAAI,EACJ,EAAE,MAAM,EAAE,YAAY,CAAC,MAAM,CAAC,EAAE,EAChC;QACE,GAAG,IAAI;QACP,OAAO,EAAE,EAAE,MAAM,EAAE,WAAW,CAAC,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,CAAC,EAAE,EAAE;QACrD,iBAAiB,EAAE,0DAA0D;KAC9E,CACF,CAAC;IACF,MAAM,IAAI,GAAG,WAAW,CAAC,MAAM,EAAE,KAAK,EAAE,IAAI,CAAC,GAAG,CAAC,CAAC;IAClD,IAAI,CAAC,MAAM,EAAE,KAAK,IAAI,CAAC,IAAI;QAAE,OAAO,IAAI,CAAC;IACzC,MAAM,KAAK,GAAG,MAAM,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,SAAS,KAAK,IAAI,CAAC,CAAC;IACvD,OAAO;QACL,SAAS,EAAE,IAAI;QACf,UAAU,EAAE,MAAM,CAAC,KAAK,CAAC,UAAU;QACnC,MAAM,EAAE,KAAK;QACb,SAAS,EAAE,KAAK,EAAE,IAAI,IAAI,IAAI;QAC9B,QAAQ,EAAE,MAAM,CAAC,QAAQ;KAC1B,CAAC;AACJ,CAAC"}

package/org-skills/accessibility/LICENSE.txt

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2026 Affaan Mustafa
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/org-skills/accessibility/SKILL.md

@@ -1,149 +0,0 @@
----
-name: accessibility
-description: "Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when reviewing a change for keyboard, contrast, or screen-reader support. standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS/Android)."
-tags: ["design","frontend"]
-tools: ["monodesign_detect","monodesign_fix"]
-license: MIT
-source: https://github.com/affaan-m/ECC
-source_path: "skills/accessibility"
-source_commit: bf70150eb2df8070024e5bdf08e4aa08959e2735
----
-# Accessibility (WCAG 2.2)
-
-This skill ensures that digital interfaces are Perceivable, Operable, Understandable, and Robust (POUR) for all users, including those using screen readers, switch controls, or keyboard navigation. It focuses on the technical implementation of WCAG 2.2 success criteria.
-
-## When to Use
-
-- Defining UI component specifications for Web, iOS, or Android.
-- Auditing existing code for accessibility barriers or compliance gaps.
-- Implementing new WCAG 2.2 standards like Target Size (Minimum) and Focus Appearance.
-- Mapping high-level design requirements to technical attributes (ARIA roles, traits, hints).
-
-## Core Concepts
-
-- **POUR Principles**: The foundation of WCAG (Perceivable, Operable, Understandable, Robust).
-- **Semantic Mapping**: Using native elements over generic containers to provide built-in accessibility.
-- **Accessibility Tree**: The representation of the UI that assistive technologies actually "read."
-- **Focus Management**: Controlling the order and visibility of the keyboard/screen reader cursor.
-- **Labeling & Hints**: Providing context through `aria-label`, `accessibilityLabel`, and `contentDescription`.
-
-## How It Works
-
-### Step 1: Identify the Component Role
-
-Determine the functional purpose (e.g., Is this a button, a link, or a tab?). Use the most semantic native element available before resorting to custom roles.
-
-### Step 2: Define Perceivable Attributes
-
-- Ensure text contrast meets **4.5:1** (normal) or **3:1** (large/UI).
-- Add text alternatives for non-text content (images, icons).
-- Implement responsive reflow (up to 400% zoom without loss of function).
-
-### Step 3: Implement Operable Controls
-
-- Ensure a minimum **24x24 CSS pixel** target size (WCAG 2.2 SC 2.5.8).
-- Verify all interactive elements are reachable via keyboard and have a visible focus indicator (SC 2.4.11).
-- Provide single-pointer alternatives for dragging movements.
-
-### Step 4: Ensure Understandable Logic
-
-- Use consistent navigation patterns.
-- Provide descriptive error messages and suggestions for correction (SC 3.3.3).
-- Implement "Redundant Entry" (SC 3.3.7) to prevent asking for the same data twice.
-
-### Step 5: Verify Robust Compatibility
-
-- Use correct `Name, Role, Value` patterns.
-- Implement `aria-live` or live regions for dynamic status updates.
-
-## Accessibility Architecture Diagram
-
-```mermaid
-flowchart TD
-  UI["UI Component"] --> Platform{Platform?}
-  Platform -->|Web| ARIA["WAI-ARIA + HTML5"]
-  Platform -->|iOS| SwiftUI["Accessibility Traits + Labels"]
-  Platform -->|Android| Compose["Semantics + ContentDesc"]
-
-  ARIA --> AT["Assistive Technology (Screen Readers, Switches)"]
-  SwiftUI --> AT
-  Compose --> AT
-```
-
-## Cross-Platform Mapping
-
-| Feature            | Web (HTML/ARIA)          | iOS (SwiftUI)                        | Android (Compose)                                           |
-| :----------------- | :----------------------- | :----------------------------------- | :---------------------------------------------------------- |
-| **Primary Label**  | `aria-label` / `<label>` | `.accessibilityLabel()`              | `contentDescription`                                        |
-| **Secondary Hint** | `aria-describedby`       | `.accessibilityHint()`               | `Modifier.semantics { stateDescription = ... }`             |
-| **Action Role**    | `role="button"`          | `.accessibilityAddTraits(.isButton)` | `Modifier.semantics { role = Role.Button }`                 |
-| **Live Updates**   | `aria-live="polite"`     | `.accessibilityLiveRegion(.polite)`  | `Modifier.semantics { liveRegion = LiveRegionMode.Polite }` |
-
-## Examples
-
-### Web: Accessible Search
-
-```html
-<form role="search">
-  <label for="search-input" class="sr-only">Search products</label>
-  <input type="search" id="search-input" placeholder="Search..." />
-  <button type="submit" aria-label="Submit Search">
-    <svg aria-hidden="true">...</svg>
-  </button>
-</form>
-```
-
-### iOS: Accessible Action Button
-
-```swift
-Button(action: deleteItem) {
-    Image(systemName: "trash")
-}
-.accessibilityLabel("Delete item")
-.accessibilityHint("Permanently removes this item from your list")
-.accessibilityAddTraits(.isButton)
-```
-
-### Android: Accessible Toggle
-
-```kotlin
-Switch(
-    checked = isEnabled,
-    onCheckedChange = { onToggle() },
-    modifier = Modifier.semantics {
-        contentDescription = "Enable notifications"
-    }
-)
-```
-
-## Anti-Patterns to Avoid
-
-- **Div-Buttons**: Using a `<div>` or `<span>` for a click event without adding a role and keyboard support.
-- **Color-Only Meaning**: Indicating an error or status _only_ with a color change (e.g., turning a border red).
-- **Uncontained Modal Focus**: Modals that don't trap focus, allowing keyboard users to navigate background content while the modal is open. Focus must be contained _and_ escapable via the `Escape` key or an explicit close button (WCAG SC 2.1.2).
-- **Redundant Alt Text**: Using "Image of..." or "Picture of..." in alt text (screen readers already announce the role "Image").
-
-## Best Practices Checklist
-
-- [ ] Interactive elements meet the **24x24px** (Web) or **44x44pt** (Native) target size.
-- [ ] Focus indicators are clearly visible and high-contrast.
-- [ ] Modals **contain focus** while open, and release it cleanly on close (`Escape` key or close button).
-- [ ] Dropdowns and menus restore focus to the trigger element on close.
-- [ ] Forms provide text-based error suggestions.
-- [ ] All icon-only buttons have a descriptive text label.
-- [ ] Content reflows properly when text is scaled.
-
-## References
-
-- [WCAG 2.2 Guidelines](https://www.w3.org/TR/WCAG22/)
-- [WAI-ARIA Authoring Practices](https://www.w3.org/TR/wai-aria-practices/)
-- [iOS Accessibility Programming Guide](https://developer.apple.com/documentation/accessibility)
-- [iOS Human Interface Guidelines - Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility)
-- [Android Accessibility Developer Guide](https://developer.android.com/guide/topics/ui/accessibility)
-
-## Related Skills
-
-- `frontend-patterns`
-- `design-system`
-- `liquid-glass-design`
-- `swiftui-patterns`

package/org-skills/database-migration/LICENSE.txt

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2024 Seth Hobson
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.