contextos-agents 1.6.1 → 2.0.0-beta.2

package/.agents/core/skills/ui-ux-pro/TROUBLESHOOTING.md

@@ -1,19 +0,0 @@
-# ui-ux-pro Troubleshooting & Common Mistakes
-
-## 1. Obvious AI Design Tells
-
-- **Symptom**: The interface immediately looks like a generic AI prototype.
-- **Root Cause**: Using Inter alone, pure black (#000000), purple-blue gradients, and rounded icon squares above every title.
-- **Fix**: Use tinted backgrounds (#090A0F), pair primary font with JetBrains Mono for code/numbers, use subtle border highlights.
-
-## 2. Contrast Failures in Secondary Elements
-
-- **Symptom**: Captions, timestamps, and borders are invisible or impossible to read.
-- **Root Cause**: Using flat #666 or #444 grays without testing against actual background luminance.
-- **Fix**: Always test contrast ratios (minimum 4.5:1 for body, 3:1 for graphical boundaries) using semantic theme tokens.
-
-## 3. Nesting Cards Inside Cards
-
-- **Symptom**: Visual claustrophobia and slop aesthetic.
-- **Root Cause**: Putting bordered cards inside other bordered cards.
-- **Fix**: Flatten the hierarchy. Use background surface contrast and negative space instead of border-in-border nesting.

package/.agents/core/skills/ui-ux-pro/VALIDATION.json

@@ -1,12 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "type": "object",
-  "properties": {
-    "rules_followed": {
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "rules_followed"
-  ]
-}

package/.agents/core/skills/ui-ux-pro/skill.yaml

@@ -1,13 +0,0 @@
-name: ui-ux-pro
-description: >
-  Professional UI/UX design skill with strict anti-pattern enforcement.
-  Prevents AI slop design, enforces accessibility standards, semantic
-  color palettes, proper spacing, and bans overused design clichés.
-tags:
-  - ui
-  - ux
-  - design
-  - accessibility
-  - frontend
-version: 1.0.0
-source: https://github.com/nextlevelbuilder/ui-ux-pro-max-skill

package/.agents/core/skills/ux-design/EXAMPLES.md

@@ -1,36 +0,0 @@
-# ux-design Examples — Anti-patterns vs ContextOS Standard
-
-## Example 1: Destructive Actions
-
-### Anti-pattern: Instant Deletion Without Confirmation or Recovery
-
-```tsx
-// BAD: Immediate delete on click, no confirmation, irreversible data loss
-<button onClick={() => deleteProject(project.id)}>Delete</button>
-```
-
-### Best practice: ContextOS Standard (Two-Step Confirmation or Undo Toast)
-
-```tsx
-// GOOD: Clear confirmation dialog stating exact item name and non-reversible impact
-<AlertDialog>
-  <AlertDialogTrigger asChild>
-    <Button variant="destructive">Delete Project</Button>
-  </AlertDialogTrigger>
-  <AlertDialogContent>
-    <AlertDialogHeader>
-      <AlertDialogTitle>Are you absolutely sure?</AlertDialogTitle>
-      <AlertDialogDescription>
-        This action cannot be undone. This will permanently delete <strong>{project.name}</strong>
-        and all associated API keys.
-      </AlertDialogDescription>
-    </AlertDialogHeader>
-    <AlertDialogFooter>
-      <AlertDialogCancel>Cancel</AlertDialogCancel>
-      <AlertDialogAction onClick={handleDelete} className="bg-destructive">
-        Delete permanently
-      </AlertDialogAction>
-    </AlertDialogFooter>
-  </AlertDialogContent>
-</AlertDialog>
-```

package/.agents/core/skills/ux-design/SKILL.md

@@ -1,116 +0,0 @@
----
-name: UX Design
-description: >
-  ContextOS skill for UX Design
----
-
-# UX Design
-
-## Overview
-
-User experience and interaction design standard. Enforces progressive disclosure, predictable user flows, designed empty/loading/error states, form usability, and keyboard navigation ergonomics.
-
-## When to Use
-
-Activate when designing complex multi-step workflows, onboarding funnels, form validation feedback, error recovery flows, and user journeys.
-
-## Rules & Patterns
-<!-- Source: ux.md -->
-
-## UX Design — Best Practices
-
-## Information Architecture
-
-- **Mental models** — organize content the way users think, not the way your code is structured
-- **Card sorting** — group features into logical categories
-- **Navigation structure** — no more than 3 clicks to any page
-- **Naming** — use user's language, not internal jargon
-
-## User Flows
-
-### Design every state
-
-Every screen has 5 states. Design ALL of them:
-
-1. **Empty state** — first visit, no data yet. Include CTA to get started
-2. **Loading state** — skeleton screens > spinners
-3. **Partial state** — some data, not complete
-4. **Ideal state** — normal usage with data
-5. **Error state** — what went wrong and how to fix it
-
-### Reduce cognitive load
-
-- **Progressive disclosure** — show only what's needed now
-- **Sensible defaults** — pre-fill what you can
-- **Inline help** — tooltips and contextual guidance
-- **Confirmation for destructive actions** — but NOT for every action
-
-## Forms UX
-
-- Show progress for multi-step forms
-- Validate inline (on blur), not on submit
-- Show password requirements as the user types
-- Auto-focus the first input
-- Use appropriate input types (email, tel, date)
-- Disable submit button only when form is submitting, never as "validation"
-
-## Onboarding
-
-- **Quick win** — let users see value within 30 seconds
-- **Minimal signup** — only ask for what's absolutely needed
-- **Progressive onboarding** — teach features as users encounter them
-- **Skip option** — always let users skip tutorials
-
-## Feedback
-
-- Every action needs feedback (success, error, pending)
-- Use toast notifications for non-blocking feedback
-- Use inline messages for form validation
-- Loading states should be < 300ms before showing (avoid flash)
-- Optimistic UI for fast-perceived actions
-
-## Mobile UX
-
-- Touch targets: minimum 44x44px
-- Thumb zones — place primary actions within easy reach
-- Bottom navigation for core actions
-- Pull-to-refresh for content lists
-- Haptic feedback for important actions
-
-## Psychology Principles
-
-- **Fitts's Law** — make important targets large and close
-- **Hick's Law** — reduce choices to reduce decision time
-- **Jakob's Law** — users prefer familiar patterns
-- **Peak-End Rule** — make the last interaction great
-- **Aesthetic-Usability Effect** — beautiful things are perceived as easier to use
-
-## Usability Heuristics (Nielsen)
-
-1. Visibility of system status
-2. Match between system and real world
-3. User control and freedom (undo, escape)
-4. Consistency and standards
-5. Error prevention
-6. Recognition rather than recall
-7. Flexibility and efficiency of use
-8. Aesthetic and minimalist design
-9. Help users recognize and recover from errors
-10. Help and documentation
-
-
-## Code Examples
-
-See `EXAMPLES.md` for detailed code examples.
-
-## Validation Checklist
-
-What to verify during the review phase before completing the task.
-
-## Common Mistakes
-
-Anti-patterns and things to explicitly avoid. See `TROUBLESHOOTING.md`.
-
-## Integration Notes
-
-How this skill interacts with other skills.

package/.agents/core/skills/ux-design/TROUBLESHOOTING.md

@@ -1,19 +0,0 @@
-# ux-design Troubleshooting & Common Mistakes
-
-## 1. Mystery Meat Navigation
-
-- **Symptom**: Users don't know what icons do and have to hover to guess.
-- **Root Cause**: Relying on ambiguous icons without text labels or tooltips.
-- **Fix**: Pair icons with text labels wherever space permits; always provide accessible tooltips on icon-only actions.
-
-## 2. Loss of User Input on Interruption
-
-- **Symptom**: User accidentally clicks outside a long modal form and all typed content vanishes.
-- **Root Cause**: Modals closing on backdrop click without checking form dirty state.
-- **Fix**: Prevent dismiss on outside click when form has unsaved modifications, or autosave drafts to local storage.
-
-## 3. Double-Click Submission Bugs
-
-- **Symptom**: Users double-click a submit button on slow network, resulting in duplicate charges or items.
-- **Root Cause**: Form buttons remaining active during in-flight network requests.
-- **Fix**: Disable button and show spinner state as soon as form submission begins.

package/.agents/core/skills/ux-design/VALIDATION.json

@@ -1,12 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "type": "object",
-  "properties": {
-    "rules_followed": {
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "rules_followed"
-  ]
-}

package/.agents/core/skills/ux-design/skill.yaml

@@ -1,10 +0,0 @@
-id: ux-design
-name: UX Design
-category: design
-tags: [design, ux, user-flows, usability, information-architecture]
-requires: []
-optional: [ui-design, web-accessibility]
-conflicts: []
-weight: 7
-documents:
-  - ux.md

package/.agents/core/skills/ux-design/ux.md

@@ -1,80 +0,0 @@
-# UX Design — Best Practices
-
-## Information Architecture
-
-- **Mental models** — organize content the way users think, not the way your code is structured
-- **Card sorting** — group features into logical categories
-- **Navigation structure** — no more than 3 clicks to any page
-- **Naming** — use user's language, not internal jargon
-
-## User Flows
-
-### Design every state
-
-Every screen has 5 states. Design ALL of them:
-
-1. **Empty state** — first visit, no data yet. Include CTA to get started
-2. **Loading state** — skeleton screens > spinners
-3. **Partial state** — some data, not complete
-4. **Ideal state** — normal usage with data
-5. **Error state** — what went wrong and how to fix it
-
-### Reduce cognitive load
-
-- **Progressive disclosure** — show only what's needed now
-- **Sensible defaults** — pre-fill what you can
-- **Inline help** — tooltips and contextual guidance
-- **Confirmation for destructive actions** — but NOT for every action
-
-## Forms UX
-
-- Show progress for multi-step forms
-- Validate inline (on blur), not on submit
-- Show password requirements as the user types
-- Auto-focus the first input
-- Use appropriate input types (email, tel, date)
-- Disable submit button only when form is submitting, never as "validation"
-
-## Onboarding
-
-- **Quick win** — let users see value within 30 seconds
-- **Minimal signup** — only ask for what's absolutely needed
-- **Progressive onboarding** — teach features as users encounter them
-- **Skip option** — always let users skip tutorials
-
-## Feedback
-
-- Every action needs feedback (success, error, pending)
-- Use toast notifications for non-blocking feedback
-- Use inline messages for form validation
-- Loading states should be < 300ms before showing (avoid flash)
-- Optimistic UI for fast-perceived actions
-
-## Mobile UX
-
-- Touch targets: minimum 44x44px
-- Thumb zones — place primary actions within easy reach
-- Bottom navigation for core actions
-- Pull-to-refresh for content lists
-- Haptic feedback for important actions
-
-## Psychology Principles
-
-- **Fitts's Law** — make important targets large and close
-- **Hick's Law** — reduce choices to reduce decision time
-- **Jakob's Law** — users prefer familiar patterns
-- **Peak-End Rule** — make the last interaction great
-- **Aesthetic-Usability Effect** — beautiful things are perceived as easier to use
-
-## Usability Heuristics (Nielsen)
-
-1. Visibility of system status
-2. Match between system and real world
-3. User control and freedom (undo, escape)
-4. Consistency and standards
-5. Error prevention
-6. Recognition rather than recall
-7. Flexibility and efficiency of use
-8. Aesthetic and minimalist design
-9. Help users recognize and recover from errors
-10. Help and documentation

package/.agents/core/skills/vercel-optimize/SKILL.md

@@ -1,83 +0,0 @@
----
-name: vercel-optimize
-description: "Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests."
-metadata:
-  version: "1.2.0"
----
-
-# Vercel Optimize
-
-## Overview
-
-Observability-first Vercel performance and cost reduction optimization skill. Evaluates deployed Next.js, SvelteKit, Nuxt, and Astro projects using production telemetry signals (`signals.json`), deterministic candidate gating, and code scanning to deliver ranked, verified architectural recommendations.
-
-## When to Use
-
-- When tasked with reducing Vercel bills, Function Invocations, Fast Data Transfer, or Build Minutes.
-- When diagnosing slow serverless routes, cold starts, or Edge vs Node runtime mismatches.
-- When evaluating caching opportunities (`stale-while-revalidate`, ISR, CDN edge caching) or Core Web Vitals degradation.
-
-## Rules & Patterns
-
-### 1. Prerequisites & Framework Support
-
-- Vercel CLI v53+ with `vercel metrics`, `vercel usage`, `vercel contract`, and `vercel api`.
-- Authenticated CLI session (`vercel login`) and linked app directory (`vercel link`).
-- Framework support: Next.js App Router (Full), Pages Router (Supported), SvelteKit (Supported), Nuxt (Supported), Astro (Limited).
-- Security rule: Never put auth tokens in shell commands (`VERCEL_TOKEN=...` is banned in chat/logs).
-
-### 2. Core Doctrine & Gating Pipeline
-
-- **Metrics First:** Recommendations start from Vercel production signals (14-day window), not repo-wide grep.
-- **Deterministic Gates:** `scripts/gate-investigations.mjs` selects code-scope and platform-scope candidates.
-- **Candidate-Bound Scope:** Inspect only files named by a candidate or a route-local import chain.
-- **Version-Aware Citations:** Use only verified citations matching the target framework version.
-- **Specific Cache Policies:** When recommending caching, state the exact cache policy and headers; keep auth-sensitive and error responses dynamic.
-
-### 3. Recommendation Rules
-
-- Every recommendation must trace to a launched candidate and include observed metric evidence.
-- Cite verified files with line numbers when code changes are proposed.
-- Use precise observed performance numbers; avoid customer-facing speculative `$N` savings formulas.
-- Do not recommend duration reductions for Vercel Workflow runtime endpoints (`/.well-known/workflow/v1/*`).
-
-## Code Examples
-
-```typescript
-// [GOOD] Next.js Route Segment Config for Caching & Edge Runtime
-export const dynamic = 'force-static';
-export const revalidate = 3600; // Cache at Edge for 1 hour
-
-export default async function CachedCatalogPage() {
-  const products = await getCatalogData();
-  return <CatalogGrid items={products} />;
-}
-```
-
-```bash
-# Running the signals collection and gate
-node scripts/collect-signals.mjs [projectId] > "$RUN_DIR/vercel-signals.json"
-node scripts/scan-codebase.mjs <repo-root> > "$RUN_DIR/codebase.json"
-node scripts/merge-signals.mjs "$RUN_DIR/vercel-signals.json" "$RUN_DIR/codebase.json" --out "$RUN_DIR/signals.json"
-node scripts/gate-investigations.mjs "$RUN_DIR/signals.json" > "$RUN_DIR/gate.json"
-```
-
-## Validation Checklist
-
-- [ ] Project is properly linked with valid team/personal scope (`vercel link`).
-- [ ] Production metrics signals collected across 14-day window before inspecting code.
-- [ ] No secrets or tokens passed in command line arguments.
-- [ ] Recommendations grounded in specific verified file paths and line numbers.
-- [ ] Unsafe or auth-sensitive paths kept strictly dynamic.
-
-## Common Mistakes
-
-- Inspecting repository source code before metric signals exist.
-- Hardcoding `VERCEL_TOKEN` into terminal commands or prompt logs.
-- Recommending duration reductions on long-lived streaming routes or workflow runners.
-- Applying static caching to user-specific or authenticated routes.
-
-## Integration Notes
-
-- Complements `nextjs` and `react-best-practices` for server-side optimization.
-- Pairs with `performance` and `security` skills.

package/.agents/core/skills/vercel-optimize/VALIDATION.json

@@ -1,12 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "type": "object",
-  "properties": {
-    "rules_followed": {
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "rules_followed"
-  ]
-}

package/.agents/core/skills/vercel-optimize/skill.yaml

@@ -1,10 +0,0 @@
-name: vercel-optimize
-description: Observability-first Vercel performance and cost reduction optimization skill.
-tags:
-  - vercel
-  - nextjs
-  - performance
-  - cost
-version: 1.2.0
-requires:
-  - nextjs

package/.agents/core/skills/web-accessibility/EXAMPLES.md

@@ -1,39 +0,0 @@
-# web-accessibility Examples — Anti-patterns vs ContextOS Standard
-
-## Example 1: Semantic Buttons vs Clickable Divs
-
-### Anti-pattern: Clickable Div
-
-```tsx
-// BAD: Cannot be focused with Tab, does not respond to Enter or Space, silent to screen readers
-<div className="button" onClick={handleSubmit}>Submit</div>
-```
-
-### Best practice: ContextOS Standard (Semantic Button Element)
-
-```tsx
-// GOOD: Keyboard focusable, native Enter/Space handling, properly announced by assistive tech
-<button type="button" onClick={handleSubmit} className="btn btn-primary">
-  Submit
-</button>
-```
-
----
-
-## Example 2: Icon-only Buttons
-
-### Anti-pattern: Unlabelled Icon Button
-
-```tsx
-// BAD: Screen reader announces "button", user has zero idea what it does
-<button onClick={onClose}><XIcon /></button>
-```
-
-### Best practice: ContextOS Standard (Accessible Label)
-
-```tsx
-// GOOD: Explicit aria-label and hidden decorative icon
-<button type="button" onClick={onClose} aria-label="Close modal window">
-  <XIcon aria-hidden="true" />
-</button>
-```

package/.agents/core/skills/web-accessibility/SKILL.md

@@ -1,170 +0,0 @@
----
-name: Web Accessibility
-description: >
-  ContextOS skill for Web Accessibility (WCAG 2.1 AA/AAA), ARIA dialog patterns, keyboard focus traps, and Web Interface Guidelines.
----
-
-# Web Accessibility & Interface Guidelines
-
-## Overview
-
-Enforces universal accessibility compliance (WCAG 2.1 AA / AAA), rigorous semantic markup, keyboard navigability with focus traps, screen reader live regions, and Web Interface Guidelines standards.
-
-## When to Use
-
-Activate whenever building, styling, or reviewing user interfaces, forms, modals, menus, navigation drawers, custom interactive widgets, or media elements.
-
-## Negative Constraints (What NOT to Do)
-
-1. **NEVER use `outline: none` without a custom `:focus-visible` replacement**: Keyboard users must always have a distinct, high-contrast visual focus ring.
-2. **NEVER use non-semantic elements (`<div onClick>`) for interactive triggers**: Always use native `<button>` or `<a href>`.
-3. **NEVER create modals or dialogs without keyboard focus traps**: Focus must remain trapped inside open dialogs during Tab / Shift-Tab navigation and restore to trigger on close.
-4. **NEVER rely exclusively on color to indicate state or errors**: Always pair colors with text labels, icons, or ARIA attributes (`aria-invalid="true"`).
-5. **NEVER trap screen readers with missing form labels or error associations**: Every input must link to `<label htmlFor="id">` and errors via `aria-describedby`.
-6. **NEVER play animations without honoring `prefers-reduced-motion`**: Respect user OS motion reduction preferences.
-
-## Rules & Patterns
-
-### 1. Focus Visible & High-Contrast Focus Rings
-
-```css
-button:focus-visible,
-a:focus-visible,
-input:focus-visible {
-  outline: 2px solid #6366f1;
-  outline-offset: 2px;
-  border-radius: 4px;
-}
-
-button:focus:not(:focus-visible) {
-  outline: none;
-}
-```
-
-### 2. Accessible Modal & Focus Trap Contract
-
-```tsx
-import React, { useEffect, useRef } from 'react';
-import { createPortal } from 'react-dom';
-
-interface ModalProps {
-  isOpen: boolean;
-  onClose: () => void;
-  titleId: string;
-  children: React.ReactNode;
-}
-
-export function AccessibleModal({ isOpen, onClose, titleId, children }: ModalProps) {
-  const dialogRef = useRef<HTMLDivElement>(null);
-  const triggerRef = useRef<HTMLElement | null>(null);
-
-  useEffect(() => {
-    if (!isOpen) return;
-    triggerRef.current = document.activeElement as HTMLElement;
-
-    const handleKeyDown = (e: KeyboardEvent) => {
-      if (e.key === 'Escape') {
-        e.preventDefault();
-        onClose();
-      }
-
-      if (e.key === 'Tab') {
-        const focusables = dialogRef.current?.querySelectorAll<HTMLElement>(
-          'button, [href], input, select, textarea, [tabindex]:not([tabindex="-1"])'
-        ) || [];
-        if (!focusables.length) return;
-
-        const first = focusables[0];
-        const last = focusables[focusables.length - 1];
-
-        if (e.shiftKey && document.activeElement === first) {
-          e.preventDefault();
-          last.focus();
-        } else if (!e.shiftKey && document.activeElement === last) {
-          e.preventDefault();
-          first.focus();
-        }
-      }
-    };
-
-    document.addEventListener('keydown', handleKeyDown);
-    return () => {
-      document.removeEventListener('keydown', handleKeyDown);
-      triggerRef.current?.focus();
-    };
-  }, [isOpen, onClose]);
-
-  if (!isOpen) return null;
-
-  return createPortal(
-    <div className="fixed inset-0 z-50 flex items-center justify-center bg-black/60 p-4">
-      <div 
-        ref={dialogRef}
-        role="dialog"
-        aria-modal="true"
-        aria-labelledby={titleId}
-        className="w-full max-w-lg rounded-xl bg-background p-6 shadow-2xl border"
-      >
-        {children}
-      </div>
-    </div>,
-    document.body
-  );
-}
-```
-
-### 3. Accessible Forms & Error Association
-
-```tsx
-export function EmailInput({ error, ...props }: { error?: string } & React.InputHTMLAttributes<HTMLInputElement>) {
-  const inputId = 'user-email';
-  const errorId = 'user-email-error';
-
-  return (
-    <div className="flex flex-col gap-1.5">
-      <label htmlFor={inputId} className="text-sm font-medium">
-        Email Address <span aria-hidden="true" className="text-destructive">*</span>
-      </label>
-      <input
-        id={inputId}
-        type="email"
-        autoComplete="email"
-        required
-        aria-invalid={Boolean(error)}
-        aria-describedby={error ? errorId : undefined}
-        className="rounded-md border p-2 text-sm focus-visible:ring-2"
-        {...props}
-      />
-      {error && (
-        <p id={errorId} role="alert" className="text-xs text-destructive">
-          {error}
-        </p>
-      )}
-    </div>
-  );
-}
-```
-
-## Code Examples
-
-See `EXAMPLES.md` for detailed dialog, menu, and form examples.
-
-## Validation Checklist
-
-- [ ] All interactive elements are fully operable via Keyboard (`Tab`, `Enter`, `Space`, `Escape`).
-- [ ] Visual `:focus-visible` styling is distinct and high contrast (≥ 3:1).
-- [ ] Modals use `role="dialog"`, `aria-modal="true"`, focus trap, and restore focus on close.
-- [ ] Text contrast ratios satisfy WCAG AA (≥ 4.5:1 for normal text, ≥ 3:1 for large text).
-- [ ] Forms pair inputs with `<label htmlFor>`, valid `autocomplete` tokens, and `aria-invalid`.
-- [ ] Non-text media contains descriptive `alt` attributes or `aria-hidden="true"` for decorative icons.
-
-## Common Mistakes
-
-- Hiding outline focus indicators globally without `:focus-visible` fallback.
-- Forgetting to trap focus in modal dialogs or not returning focus to trigger when modal closes.
-- Missing `aria-expanded` attributes on disclosure buttons and dropdown toggles.
-
-## Integration Notes
-
-- Pairs with `ui-ux-pro` and `impeccable-design` for visual contrast and component standards.
-- Pairs with `react` and `nextjs` for accessible dialogs and focus restoration across route transitions.

package/.agents/core/skills/web-accessibility/TROUBLESHOOTING.md

@@ -1,19 +0,0 @@
-# web-accessibility Troubleshooting & Common Mistakes
-
-## 1. Trapping Keyboard Users in Inactive Elements
-
-- **Symptom**: Tab key moves focus into invisible elements hidden offscreen.
-- **Root Cause**: Using display: none vs opacity: 0 or left: -9999px.
-- **Fix**: Always apply display: none / hidden or inert attribute to elements that are currently not visible.
-
-## 2. Color Contrast Violations
-
-- **Symptom**: Text is unreadable for users with low vision or in bright sunlight.
-- **Root Cause**: Contrast ratio between text and background color is below WCAG AA thresholds.
-- **Fix**: Ensure contrast ratio is at least 4.5:1 for body text and 3:1 for large text / graphical controls.
-
-## 3. Silent Dynamic Updates
-
-- **Symptom**: Asynchronous error messages or notifications appear on screen without screen reader announcement.
-- **Root Cause**: Missing ARIA live region.
-- **Fix**: Wrap notification banners in aria-live="polite" and role="status".

package/.agents/core/skills/web-accessibility/VALIDATION.json

@@ -1,12 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "type": "object",
-  "properties": {
-    "rules_followed": {
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "rules_followed"
-  ]
-}