@arcadialdev/arcality 2.4.30 → 2.4.32

package/.agent/skills/form-expert.md

@@ -0,0 +1,99 @@
+---
+name: form-expert
+description: Metodología experta para explorar, identificar y llenar formularios complejos en aplicaciones web.
+---
+
+# Form Expert Skill
+
+Esta habilidad define el protocolo que el agente DEBE seguir cuando la misión involucra llenar, crear o editar registros a través de formularios.
+
+## Principio Fundamental
+**NUNCA interactúes con un campo que no hayas inspeccionado primero.** Si un componente tiene un nombre genérico, un tag inferred como `[INFERRED]`, o simplemente no estás seguro de qué es, usa `inspect_element_details` ANTES de hacer click o fill.
+
+## Protocolo de Formularios (4 fases obligatorias)
+
+### Fase 1: RECONOCIMIENTO (Scan)
+Antes de llenar cualquier campo, dedica tu primer turno en el formulario a **analizar todos los componentes visibles**:
+
+1. **Lee la lista completa de CURRENT COMPONENTS** — identifica:
+   - Campos de tipo FIELD (inputs, textareas, selects)
+   - Campos con label visible (prioritarios)
+   - Campos sin label o con nombre genérico (requieren inspección)
+   - Botones de acción (GUARDAR, CANCELAR, etc.)
+   - Tabs o pestañas si el formulario tiene secciones
+
+2. **Clasifica los campos** en:
+   - ✅ **Confiables**: Tienen un nombre claro como `[input] Título del documento`
+   - ⚠️ **Sospechosos**: Tienen nombre genérico como `[input] Editar` o `[INFERRED] xxx`
+   - ❌ **Desconocidos**: Solo tienen tag genérico como `[input]`
+
+3. **Para campos sospechosos o desconocidos**: Usa `inspect_element_details` para obtener:
+   - El placeholder text
+   - El aria-label
+   - El atributo name o id
+   - Si está disabled o readonly
+
+### Fase 2: PLANIFICACIÓN (Plan)
+Con la información del reconocimiento, planifica la secuencia de acciones:
+
+1. **Prioriza los campos obligatorios** — los que tienen asterisco (*), clase "required", o están marcados en rojo.
+2. **Genera datos únicos** — Si la misión dice "genérico" o "aleatorio", genera datos que incluyan un timestamp o ID único para evitar duplicados. Ejemplo: `TEST-${timestamp}` o `Prueba QA Feb24`.
+3. **Planifica el orden**: Llena los campos de arriba a abajo, izquierda a derecha, siguiendo el orden del DOM.
+
+### Fase 3: EJECUCIÓN (Act)
+Ejecuta las acciones planificadas:
+
+1. **Llena múltiples campos por turno** — No pierdas un turno por campo. Agrupa 3-5 fills en una sola llamada a `perform_ui_actions`.
+2. **Para cada campo fill**: click + fill (en ese orden). El click asegura que el campo tiene focus.
+3. **Para dropdowns/selects**: Click para abrir → espera el siguiente turno → selecciona la opción.
+4. **Si un fill falla**: NO reintentes inmediatamente. Usa `inspect_element_details` para ver si el campo es un select, un datepicker, o tiene un overlay encima.
+
+### Fase 4: VERIFICACIÓN (Verify)
+Antes de hacer GUARDAR:
+
+1. **Usa `validate_element_state`** en el botón de GUARDAR para confirmar que está enabled.
+2. **Revisa visualmente** si hay campos en rojo o mensajes de error.
+3. **Solo entonces** haz click en GUARDAR.
+4. **Después de GUARDAR**: Espera la respuesta de la UI. Si aparece un toast de éxito o regresas a la lista, la misión fue exitosa.
+
+## Manejo de Errores en Formularios
+
+### Si un campo falla con Timeout:
+```
+1. NO reintentes el mismo click/fill inmediatamente
+2. Usa inspect_element_details en ese IDX
+3. Analiza si:
+   - El elemento está cubierto por un overlay/modal
+   - El elemento es readonly/disabled  
+   - El IDX cambió (la página se re-renderizó)
+4. Si el elemento no sirve, busca un campo alternativo con nombre similar
+```
+
+### Si aparece un error de "duplicado" o "ya existe":
+```
+1. Identifica qué campo causó el error (claves, códigos, nombres)
+2. Cambia el valor a algo único (agrega sufijo numérico o timestamp)
+3. Reintenta GUARDAR
+```
+
+### Si el formulario tiene tabs o secciones:
+```
+1. Llena los campos de la sección actual PRIMERO.
+2. Identifica el elemento de la pestaña: Busca el texto de la pestaña (ej: "CAMPOS DE LA FORMA") en componentes tipo ACTION.
+3. PRECISIÓN: Evita hacer click en contenedores grandes que agrupan varias pestañas. Prefiere el elemento más pequeño (span o label) que contenga el texto exacto.
+4. Haz click en la pestaña. Si un click simple no funciona tras 2 intentos, usa 'double_click'.
+5. Espera el siguiente turno para ver los nuevos campos.
+```
+
+## Uso de Double Click
+- Úsalo SOLO cuando:
+  - La misión lo pida explícitamente (ej: "haz doble clic en la celda").
+  - Un elemento (como una pestaña o un icono) no responda tras dos intentos de click simple.
+  - Quieras activar modos de edición en tablas o componentes complejos.
+
+## Anti-patrones (NUNCA hagas esto)
+- ❌ Hacer click en un campo `[INFERRED]` sin inspeccionarlo primero
+- ❌ Intentar llenar TODO el formulario en el primer turno sin saber qué campos hay
+- ❌ Hacer click en el botón GUARDAR sin haber verificado que los campos están llenos
+- ❌ Reintentar la misma acción fallida sin investigar la causa
+- ❌ Asumir que un componente con nombre largo (>50 chars) es un campo — probablemente es un contenedor

package/.agent/skills/investigation-protocol.md

@@ -0,0 +1,61 @@
+---
+name: investigation-protocol
+description: Protocolo obligatorio de investigación cuando una acción falla o un elemento es ambiguo.
+---
+
+# Investigation Protocol Skill
+
+## Regla de Oro
+**NUNCA reintentes una acción fallida sin investigar primero.** Si algo falla, SIEMPRE ejecuta el protocolo de investigación antes de intentar de nuevo.
+
+## Protocolo de Investigación (Obligatorio tras cualquier fallo)
+
+### Paso 1: Inspección del elemento
+```
+Usa: inspect_element_details (idx del elemento que falló)
+Objetivo: Determinar POR QUÉ falló
+```
+
+Revisa en el resultado:
+- ¿El elemento es `disabled` o `readonly`?
+- ¿El elemento está cubierto por otro (`pointer-events: none`, overlay)?
+- ¿El elemento es un `<select>` que requiere interacción diferente a fill?
+- ¿El elemento está en un iframe diferente (`frameIdx`)?
+
+### Paso 2: Auditoría de consola
+```
+Usa: capture_console_errors
+Objetivo: Buscar errores JavaScript silenciosos
+```
+
+Si la UI no responde o está congelada, puede haber un error JS no visible. Revisa:
+- Errores de red (fetch failed, 404, 500)
+- Errores de JS (TypeError, undefined)
+- Warnings de frameworks (React, Angular)
+
+### Paso 3: Captura de evidencia
+```
+Usa: create_test_evidence (type: annotated_screenshot)
+Objetivo: Documentar el estado actual para debugging
+```
+
+Si identificas un bug real de la aplicación (no un error tuyo), documéntalo con evidencia anotada.
+
+### Paso 4: Decisión
+Después de investigar, toma UNA de estas decisiones:
+1. **Reintentar con variación**: Si descubriste que el campo es un select, usa click en vez de fill.
+2. **Buscar alternativa**: Si el elemento está cubierto, busca otro camino al mismo objetivo.
+3. **Reportar bug**: Si es un bug de la aplicación, usa `report_application_bug`.
+4. **Reportar incapacidad**: Si no puedes avanzar, usa `report_inability_to_proceed`.
+
+## Cuándo usar cada herramienta de investigación
+
+| Situación | Herramienta | Obligatoria |
+|-----------|------------|-------------|
+| Acción falló con Timeout | `inspect_element_details` | ✅ SÍ |
+| Elemento con nombre [INFERRED] | `inspect_element_details` | ✅ SÍ |
+| UI no responde / congelada | `capture_console_errors` | ✅ SÍ |
+| Antes de hacer GUARDAR/SAVE | `validate_element_state` | ✅ SÍ |
+| Después de GUARDAR exitoso | `extract_table_data` | Recomendada |
+| Bug encontrado | `create_test_evidence` | ✅ SÍ |
+| Fin de misión exitosa | `create_test_evidence` | Recomendada |

package/.agent/skills/modal-master.md

@@ -0,0 +1,41 @@
+---
+name: modal-master
+description: Gestión experta de ventanas modales, diálogos y popups en pruebas de QA.
+---
+
+# Modal Master Skill
+
+Esta habilidad permite al agente detectar, navegar y cerrar ventanas modales de manera eficiente, evitando que el flujo del test se bloquee por elementos superpuestos.
+
+## Cuándo usar esta habilidad
+- Cuando el agente realiza una acción y aparece un diálogo de confirmación (ej: "¿Desea guardar los cambios?").
+- Cuando un popup de error o notificación bloquea el acceso al resto de la página.
+- Cuando la misión requiere interactuar específicamente con elementos dentro de un modal.
+
+## Instrucciones para el Agente
+
+### 1. Detección de Modales
+Antes de intentar interactuar con un elemento del fondo, verifica si hay un modal activo buscando:
+- Elementos con `role="dialog"` o `role="alertdialog"`.
+- Atributos `aria-modal="true"`.
+- Overlays oscuros que cubren la pantalla (ej: clases tipo `backdrop`, `overlay`, `modal-open`).
+- Títulos destacados que no estaban antes de la acción.
+
+### 2. Prioridad de Interacción
+Si un modal está abierto:
+- **Prioridad 1**: Si el modal es informativo (Warning/Error), léelo y repórtalo en tu pensamiento antes de cerrarlo.
+- **Prioridad 2**: Si el modal es de confirmación para la acción que acabas de realizar, haz clic en el botón afirmativo (ej: "Aceptar", "Sí", "Confirmar").
+- **Prioridad 3**: Si el modal es intrusivo y no permite seguir, busca el botón de cierre (usualmente una 'X', un botón "Cerrar" o "Cancelar").
+
+### 3. Estrategias de Cierre
+Si no encuentras un botón de cierre claro:
+- Busca botones con clases `close`, `btn-close` o que tengan un ícono dentro.
+- Usa `send_keyboard_event` con key `Escape` para intentar cerrar el modal/popup/dropdown.
+- Verifica si el modal desaparece al hacer clic en el backdrop (el área fuera del cuadro blanco).
+
+### 4. Flujo de Trabajo (Ejemplo)
+1. **Acción**: Clic en "Eliminar".
+2. **Scan**: Detecto un modal con el texto "¿Está seguro?".
+3. **Validación**: Uso `validate_element_state` para verificar que el botón "Eliminar permanentemente" es visible dentro del modal.
+4. **Ejecución**: Clic en el botón del modal.
+5. **Verificación**: Espero a que el modal desaparezca antes de realizar la siguiente acción de la misión.

package/.agent/skills/native-control-expert.md

@@ -0,0 +1,82 @@
+---
+name: native-control-expert
+description: Protocolo experto para interactuar con controles nativos del navegador (time pickers, date pickers, selects, etc.)
+---
+
+# Native Control Expert Skill
+
+Esta habilidad define el protocolo que el agente DEBE seguir cuando la misión involucra interactuar con controles nativos del navegador que **NO responden bien** a la acción estándar `fill`.
+
+## Controles Nativos que REQUIEREN esta skill
+
+| Control | Ejemplo | Acción preferida |
+|---------|---------|-----------------|
+| `<input type="time">` | Campo de hora `HH:mm` | `interact_native_control` con `control_type: "time"` |
+| `<input type="date">` | Campo de fecha `YYYY-MM-DD` | `interact_native_control` con `control_type: "date"` |
+| `<input type="datetime-local">` | Fecha y hora combinados | `interact_native_control` con `control_type: "datetime"` |
+| `<input type="color">` | Selector de color | `interact_native_control` con `control_type: "color"` |
+| `<input type="range">` | Slider numérico | `interact_native_control` con `control_type: "range"` |
+| `<select>` nativo | Dropdown estándar HTML | `interact_native_control` con `control_type: "select"` |
+| Combobox/Autocomplete | Campos con `role="combobox"` | `click` + `fill` letra + `send_keyboard_event` ArrowDown + Enter |
+| Time picker con diálogo | Campos que abren un popup al hacer click | `send_keyboard_event` con Arrow keys |
+
+## Protocolo de Interacción con Time Pickers
+
+### ❌ LO QUE NUNCA DEBES HACER:
+- Intentar `fill` repetidamente si falla la primera vez
+- Hacer click una y otra vez sin cambiar de estrategia (esto causa loop detection)
+- Asumir que un time picker funciona como un input de texto normal
+
+### ✅ LO QUE SÍ DEBES HACER:
+
+**Estrategia 1: interact_native_control (PREFERIDA)**
+```
+1. Usa inspect_element_details para confirmar que es type="time"
+2. Usa interact_native_control con control_type: "time", value: "13:05"
+3. Verifica el resultado
+```
+
+**Estrategia 2: Keyboard Navigation (FALLBACK)**
+```
+1. Haz click en el campo de hora
+2. Usa send_keyboard_event con key: "Control+a" para seleccionar todo
+3. Usa send_keyboard_event para escribir los dígitos del tiempo
+4. Ejemplo: Para "13:05", envía las teclas: "1", "3", "0", "5"
+5. Usa send_keyboard_event con key: "Tab" para navegar al siguiente campo
+```
+
+**Estrategia 3: Arrow Keys (ULTIMO RECURSO)**
+```
+1. Haz click en el segmento de horas del campo
+2. Usa send_keyboard_event con key: "ArrowUp" o "ArrowDown" para ajustar la hora
+3. Usa send_keyboard_event con key: "Tab" para mover al segmento de minutos
+4. Repite con ArrowUp/ArrowDown para los minutos
+```
+
+## Protocolo de Interacción con Date Pickers
+
+### ✅ Estrategia preferida:
+```
+1. Confirma con inspect_element_details que es type="date"
+2. Usa interact_native_control con control_type: "date", value: "2026-03-25"
+3. IMPORTANTE: El formato SIEMPRE es YYYY-MM-DD
+```
+
+## Detección: ¿Cuándo usar esta skill?
+
+Debes activar esta skill cuando:
+1. Ves un componente FIELD con nombre que incluye "HH:mm" o "hora" o "time"
+2. Un campo tiene `role="combobox"` y `aria-expanded`
+3. Un `fill()` falla en un campo de fecha/hora con Timeout o sin efecto
+4. El inspector muestra `type="time"` o `type="date"` en los atributos
+
+## Keyboard Shortcuts Útiles
+
+| Tecla | Efecto en controles nativos |
+|-------|-----------------------------|
+| `Tab` | Mover al siguiente segmento (horas → minutos → AM/PM) |
+| `ArrowUp` | Incrementar valor del segmento actual |
+| `ArrowDown` | Decrementar valor del segmento actual |
+| `Escape` | Cerrar dropdown/calendar que se abrió |
+| `Enter` | Confirmar selección en calendarios |
+| `Control+a` | Seleccionar todo el contenido del campo |

package/.agents/skills/e2e-testing-expert/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: "e2e-testing-expert"
+description: "Elite protocol for End-to-End browser testing and forensic debugging."
+---
+
+# E2E Testing Expert Protocol
+
+You are an Elite QA E2E Testing Architect. Whenever you perform E2E automation actions, you MUST follow these non-negotiable patterns:
+
+## 1. Forensic Debugging Mindset
+When a test step fails:
+- DO NOT blindly retry the same action.
+- Immediately capture the state (`capture_console_errors` or `inspect_element_details`).
+- Assume flakiness is due to state mismatch (e.g., waiting for an animation, HTTP response pending, or a Toast overlay blocking clicks).
+
+## 2. Advanced Assertion Safety
+Rely heavily on "Web-First" assertions rather than hardcoded timeouts:
+- Only act on elements once their state is truly `toBeVisible()` and `toBeEnabled()`.
+- If an element is intercepted by another (e.g., a modal overlay), target the overlay to close it before interacting.
+
+## 3. High-Quality Locators
+Prefer accessibility-first locators:
+- 1st Priority: Role-based (e.g., Button, Checkbox, Link).
+- 2nd Priority: Text content or Placeholders.
+- ALWAYS avoid brittle CSS indexes (`nth-child(5)`) or deeply nested container paths unless absolutely necessary.
+
+## 4. Human-Readable Error Reporting
+If you are completely stuck after 3 attempts, formulate your failure as a "Business Validation Error" or a clear "Technical UI Glitch" (like an element not attached to DOM). Explain to the user exactly what DOM element failed to respond.

package/.agents/skills/frontend-design/LICENSE.txt

@@ -0,0 +1,177 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

package/.agents/skills/frontend-design/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: frontend-design
+description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
+license: Complete terms in LICENSE.txt
+---
+
+This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
+
+The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
+
+## Design Thinking
+
+Before coding, understand the context and commit to a BOLD aesthetic direction:
+- **Purpose**: What problem does this interface solve? Who uses it?
+- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
+- **Constraints**: Technical requirements (framework, performance, accessibility).
+- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
+
+**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
+
+Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
+- Production-grade and functional
+- Visually striking and memorable
+- Cohesive with a clear aesthetic point-of-view
+- Meticulously refined in every detail
+
+## Frontend Aesthetics Guidelines
+
+Focus on:
+- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
+- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
+- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
+- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
+- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
+
+NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
+
+Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
+
+**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
+
+Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.