Refactor code structure for improved readability and maintainability
This commit is contained in:
Zied
89
SKILLS_UPDATE_GUIDE.md
Normal file
89
SKILLS_UPDATE_GUIDE.md
Normal file
@@ -0,0 +1,89 @@
|
||||
# Skills Update Guide
|
||||
|
||||
This guide explains how to update the skills in the Antigravity Awesome Skills web application.
|
||||
|
||||
## Automatic Updates (Recommended)
|
||||
|
||||
The `START_APP.bat` file automatically checks for and updates skills when you run it. It uses multiple methods:
|
||||
|
||||
1. **Git method** (if Git is installed): Fast and efficient
|
||||
2. **PowerShell download** (fallback): Works without Git
|
||||
|
||||
## Manual Update Options
|
||||
|
||||
### Option 1: Using npm script (Recommended for manual updates)
|
||||
```bash
|
||||
npm run update:skills
|
||||
```
|
||||
|
||||
This command:
|
||||
- Generates the latest skills index from the skills directory
|
||||
- Copies it to the web app's public directory
|
||||
- Requires Python and PyYAML to be installed
|
||||
|
||||
### Option 2: Using START_APP.bat (Integrated solution)
|
||||
```bash
|
||||
START_APP.bat
|
||||
```
|
||||
|
||||
The START_APP.bat file includes integrated update functionality that:
|
||||
- Automatically checks for updates on startup
|
||||
- Uses Git if available (fast method)
|
||||
- Falls back to HTTPS download if Git is not installed
|
||||
- Handles all dependencies automatically
|
||||
- Provides clear status messages
|
||||
- Works without any additional setup
|
||||
|
||||
### Option 3: Manual steps
|
||||
```bash
|
||||
# 1. Generate skills index
|
||||
python scripts/generate_index.py
|
||||
|
||||
# 2. Copy to web app
|
||||
copy skills_index.json web-app\public\skills.json
|
||||
```
|
||||
|
||||
## Prerequisites
|
||||
|
||||
For manual updates, you need:
|
||||
|
||||
- **Python 3.x**: Download from [python.org](https://python.org/)
|
||||
- **PyYAML**: Install with `pip install PyYAML`
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### "Python is not recognized"
|
||||
- Install Python from [python.org](https://python.org/)
|
||||
- Make sure to check "Add Python to PATH" during installation
|
||||
|
||||
### "PyYAML not found"
|
||||
- Install with: `pip install PyYAML`
|
||||
- Or run the update script which will install it automatically
|
||||
|
||||
### "Failed to copy skills"
|
||||
- Make sure the `web-app\public\` directory exists
|
||||
- Check file permissions
|
||||
|
||||
## What Gets Updated
|
||||
|
||||
The update process refreshes:
|
||||
- Skills index (`skills_index.json`)
|
||||
- Web app skills data (`web-app\public\skills.json`)
|
||||
- All 900+ skills from the skills directory
|
||||
|
||||
## When to Update
|
||||
|
||||
Update skills when:
|
||||
- New skills are added to the repository
|
||||
- You want the latest skill descriptions
|
||||
- Skills appear missing or outdated in the web app
|
||||
|
||||
## Git Users
|
||||
|
||||
If you have Git installed and want to update the entire repository:
|
||||
```bash
|
||||
git pull origin main
|
||||
npm run update:skills
|
||||
```
|
||||
|
||||
This pulls the latest code and updates the skills data.
|
||||
@@ -15,15 +15,17 @@ IF %ERRORLEVEL% NEQ 0 (
|
||||
)
|
||||
|
||||
:: ===== Auto-Update Skills from GitHub =====
|
||||
echo [INFO] Checking for skill updates...
|
||||
|
||||
:: Method 1: Try Git first (if available)
|
||||
WHERE git >nul 2>nul
|
||||
IF %ERRORLEVEL% NEQ 0 goto :NO_GIT
|
||||
goto :HAS_GIT
|
||||
IF %ERRORLEVEL% EQU 0 goto :USE_GIT
|
||||
|
||||
:NO_GIT
|
||||
echo [WARN] Git is not installed. Skipping auto-update.
|
||||
goto :SKIP_UPDATE
|
||||
:: Method 2: Try PowerShell download (fallback)
|
||||
echo [INFO] Git not found. Using alternative download method...
|
||||
goto :USE_POWERSHELL
|
||||
|
||||
:HAS_GIT
|
||||
:USE_GIT
|
||||
:: Add upstream remote if not already set
|
||||
git remote get-url upstream >nul 2>nul
|
||||
IF %ERRORLEVEL% EQU 0 goto :DO_FETCH
|
||||
@@ -31,23 +33,69 @@ echo [INFO] Adding upstream remote...
|
||||
git remote add upstream https://github.com/sickn33/antigravity-awesome-skills.git
|
||||
|
||||
:DO_FETCH
|
||||
echo [INFO] Checking for skill updates from original repo...
|
||||
echo [INFO] Fetching latest skills from original repo...
|
||||
git fetch upstream >nul 2>nul
|
||||
IF %ERRORLEVEL% NEQ 0 goto :FETCH_FAIL
|
||||
goto :DO_MERGE
|
||||
|
||||
:FETCH_FAIL
|
||||
echo [WARN] Could not fetch updates. Continuing with local version...
|
||||
goto :SKIP_UPDATE
|
||||
echo [WARN] Could not fetch updates via Git. Trying alternative method...
|
||||
goto :USE_POWERSHELL
|
||||
|
||||
:DO_MERGE
|
||||
git merge upstream/main --ff-only >nul 2>nul
|
||||
:: Surgically extract ONLY the /skills/ folder from upstream to avoid all merge conflicts
|
||||
git checkout upstream/main -- skills >nul 2>nul
|
||||
IF %ERRORLEVEL% NEQ 0 goto :MERGE_FAIL
|
||||
|
||||
:: Save the updated skills to local history silently
|
||||
git commit -m "auto-update: sync latest skills from upstream" >nul 2>nul
|
||||
echo [INFO] Skills updated successfully from original repo!
|
||||
goto :SKIP_UPDATE
|
||||
|
||||
:MERGE_FAIL
|
||||
echo [WARN] Could not merge updates. Continuing with local version...
|
||||
echo [WARN] Could not update skills via Git. Trying alternative method...
|
||||
goto :USE_POWERSHELL
|
||||
|
||||
:USE_POWERSHELL
|
||||
echo [INFO] Downloading latest skills via HTTPS...
|
||||
if exist "update_temp" rmdir /S /Q "update_temp" >nul 2>nul
|
||||
if exist "update.zip" del "update.zip" >nul 2>nul
|
||||
|
||||
:: Download the latest repository as ZIP
|
||||
powershell -Command "Invoke-WebRequest -Uri 'https://github.com/sickn33/antigravity-awesome-skills/archive/refs/heads/main.zip' -OutFile 'update.zip' -UseBasicParsing" >nul 2>nul
|
||||
IF %ERRORLEVEL% NEQ 0 goto :DOWNLOAD_FAIL
|
||||
|
||||
:: Extract and update skills
|
||||
echo [INFO] Extracting latest skills...
|
||||
powershell -Command "Expand-Archive -Path 'update.zip' -DestinationPath 'update_temp' -Force" >nul 2>nul
|
||||
IF %ERRORLEVEL% NEQ 0 goto :EXTRACT_FAIL
|
||||
|
||||
:: Copy only the skills folder
|
||||
if exist "update_temp\antigravity-awesome-skills-main\skills" (
|
||||
echo [INFO] Updating skills directory...
|
||||
xcopy /E /Y /I "update_temp\antigravity-awesome-skills-main\skills" "skills" >nul 2>nul
|
||||
echo [INFO] Skills updated successfully without Git!
|
||||
) else (
|
||||
echo [WARN] Could not find skills folder in downloaded archive.
|
||||
goto :UPDATE_FAIL
|
||||
)
|
||||
|
||||
:: Cleanup
|
||||
del "update.zip" >nul 2>nul
|
||||
rmdir /S /Q "update_temp" >nul 2>nul
|
||||
goto :SKIP_UPDATE
|
||||
|
||||
:DOWNLOAD_FAIL
|
||||
echo [WARN] Failed to download skills update (network issue or no internet).
|
||||
goto :UPDATE_FAIL
|
||||
|
||||
:EXTRACT_FAIL
|
||||
echo [WARN] Failed to extract downloaded skills archive.
|
||||
goto :UPDATE_FAIL
|
||||
|
||||
:UPDATE_FAIL
|
||||
echo [INFO] Continuing with local skills version...
|
||||
echo [INFO] To manually update skills later, run: npm run update:skills
|
||||
|
||||
:SKIP_UPDATE
|
||||
|
||||
|
||||
@@ -14,6 +14,7 @@
|
||||
"test": "node scripts/tests/validate_skills_headings.test.js && python3 scripts/tests/test_validate_skills_headings.py && python3 scripts/tests/inspect_microsoft_repo.py && python3 scripts/tests/test_comprehensive_coverage.py",
|
||||
"sync:microsoft": "python3 scripts/sync_microsoft_skills.py",
|
||||
"sync:all-official": "npm run sync:microsoft && npm run chain",
|
||||
"update:skills": "python3 scripts/generate_index.py && copy skills_index.json web-app/public/skills.json",
|
||||
"app:setup": "node scripts/setup_web.js",
|
||||
"app:install": "cd web-app && npm install",
|
||||
"app:dev": "npm run app:setup && cd web-app && npm run dev",
|
||||
|
||||
4406
skills_index.json
4406
skills_index.json
File diff suppressed because it is too large
Load Diff
11
web-app/package-lock.json
generated
11
web-app/package-lock.json
generated
@@ -79,6 +79,7 @@
|
||||
"integrity": "sha512-CGOfOJqWjg2qW/Mb6zNsDm+u5vFQ8DxXfbM09z69p5Z6+mE1ikP2jUXw+j42Pf1XTYED2Rni5f95npYeuwMDQA==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"@babel/code-frame": "^7.29.0",
|
||||
"@babel/generator": "^7.29.0",
|
||||
@@ -1859,6 +1860,7 @@
|
||||
"resolved": "https://registry.npmjs.org/@types/react/-/react-19.2.14.tgz",
|
||||
"integrity": "sha512-ilcTH/UniCkMdtexkoCN0bI7pMcJDvmQFPvuPvmEaYA/NSfFTAgdUSLAoVjaRJm7+6PvcM+q1zYOwS4wTYMF9w==",
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"csstype": "^3.2.2"
|
||||
}
|
||||
@@ -1921,6 +1923,7 @@
|
||||
"integrity": "sha512-NZyJarBfL7nWwIq+FDL6Zp/yHEhePMNnnJ0y3qfieCrmNvYct8uvtiV41UvlSe6apAfk0fY1FbWx+NwfmpvtTg==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"bin": {
|
||||
"acorn": "bin/acorn"
|
||||
},
|
||||
@@ -2073,6 +2076,7 @@
|
||||
}
|
||||
],
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"baseline-browser-mapping": "^2.9.0",
|
||||
"caniuse-lite": "^1.0.30001759",
|
||||
@@ -2433,6 +2437,7 @@
|
||||
"integrity": "sha512-LEyamqS7W5HB3ujJyvi0HQK/dtVINZvd5mAAp9eT5S/ujByGjiZLCzPcHVzuXbpJDJF/cxwHlfceVUDZ2lnSTw==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"@eslint-community/eslint-utils": "^4.8.0",
|
||||
"@eslint-community/regexpp": "^4.12.1",
|
||||
@@ -4250,6 +4255,7 @@
|
||||
"integrity": "sha512-5gTmgEY/sqK6gFXLIsQNH19lWb4ebPDLA4SdLP7dsWkIXHWlG66oPuVvXSGFPppYZz8ZDZq0dYYrbHfBCVUb1Q==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"engines": {
|
||||
"node": ">=12"
|
||||
},
|
||||
@@ -4277,6 +4283,7 @@
|
||||
}
|
||||
],
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"nanoid": "^3.3.11",
|
||||
"picocolors": "^1.1.1",
|
||||
@@ -4328,6 +4335,7 @@
|
||||
"resolved": "https://registry.npmjs.org/react/-/react-19.2.4.tgz",
|
||||
"integrity": "sha512-9nfp2hYpCwOjAN+8TZFGhtWEwgvWHXqESH8qT89AT/lWklpLON22Lc8pEtnpsZz7VmawabSU0gCjnj8aC0euHQ==",
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"engines": {
|
||||
"node": ">=0.10.0"
|
||||
}
|
||||
@@ -4337,6 +4345,7 @@
|
||||
"resolved": "https://registry.npmjs.org/react-dom/-/react-dom-19.2.4.tgz",
|
||||
"integrity": "sha512-AXJdLo8kgMbimY95O2aKQqsz2iWi9jMgKJhRBAxECE4IFxfcazB2LmzloIoibJI3C12IlY20+KFaLv+71bUJeQ==",
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"scheduler": "^0.27.0"
|
||||
},
|
||||
@@ -4885,6 +4894,7 @@
|
||||
"integrity": "sha512-w+N7Hifpc3gRjZ63vYBXA56dvvRlNWRczTdmCBBa+CotUzAPf5b7YMdMR/8CQoeYE5LX3W4wj6RYTgonm1b9DA==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"dependencies": {
|
||||
"esbuild": "^0.27.0",
|
||||
"fdir": "^6.5.0",
|
||||
@@ -5027,6 +5037,7 @@
|
||||
"integrity": "sha512-rftlrkhHZOcjDwkGlnUtZZkvaPHCsDATp4pGpuOOMDaTdDDXF91wuVDJoWoPsKX/3YPQ5fHuF3STjcYyKr+Qhg==",
|
||||
"dev": true,
|
||||
"license": "MIT",
|
||||
"peer": true,
|
||||
"funding": {
|
||||
"url": "https://github.com/sponsors/colinhacks"
|
||||
}
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
60
web-app/public/skills/00-andruia-consultant/SKILL.md
Normal file
60
web-app/public/skills/00-andruia-consultant/SKILL.md
Normal file
@@ -0,0 +1,60 @@
|
||||
---
|
||||
id: 00-andruia-consultant
|
||||
name: 00-andruia-consultant
|
||||
description: "Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español."
|
||||
category: andruia
|
||||
risk: safe
|
||||
source: personal
|
||||
---
|
||||
|
||||
## When to Use
|
||||
|
||||
Use this skill at the very beginning of a project to diagnose the workspace, determine whether it's a "Pure Engine" (new) or "Evolution" (existing) project, and to set the initial technical roadmap and expert squad.
|
||||
|
||||
# 🤖 Andru.ia Solutions Architect - Hybrid Engine (v2.0)
|
||||
|
||||
## Description
|
||||
|
||||
Soy el Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Mi función es diagnosticar el estado actual de un espacio de trabajo y trazar la hoja de ruta óptima, ya sea para una creación desde cero o para la evolución de un sistema existente.
|
||||
|
||||
## 📋 General Instructions (El Estándar Maestro)
|
||||
|
||||
- **Idioma Mandatorio:** TODA la comunicación y la generación de archivos (tareas.md, plan_implementacion.md) DEBEN ser en **ESPAÑOL**.
|
||||
- **Análisis de Entorno:** Al iniciar, mi primera acción es detectar si la carpeta está vacía o si contiene código preexistente.
|
||||
- **Persistencia:** Siempre materializo el diagnóstico en archivos .md locales.
|
||||
|
||||
## 🛠️ Workflow: Bifurcación de Diagnóstico
|
||||
|
||||
### ESCENARIO A: Lienzo Blanco (Carpeta Vacía)
|
||||
|
||||
Si no detecto archivos, activo el protocolo **"Pure Engine"**:
|
||||
|
||||
1. **Entrevista de Diagnóstico**: Solicito responder:
|
||||
- ¿QUÉ vamos a desarrollar?
|
||||
- ¿PARA QUIÉN es?
|
||||
- ¿QUÉ RESULTADO esperas? (Objetivo y estética premium).
|
||||
|
||||
### ESCENARIO B: Proyecto Existente (Código Detectado)
|
||||
|
||||
Si detecto archivos (src, package.json, etc.), actúo como **Consultor de Evolución**:
|
||||
|
||||
1. **Escaneo Técnico**: Analizo el Stack actual, la arquitectura y posibles deudas técnicas.
|
||||
2. **Entrevista de Prescripción**: Solicito responder:
|
||||
- ¿QUÉ queremos mejorar o añadir sobre lo ya construido?
|
||||
- ¿CUÁL es el mayor punto de dolor o limitación técnica actual?
|
||||
- ¿A QUÉ estándar de calidad queremos elevar el proyecto?
|
||||
3. **Diagnóstico**: Entrego una breve "Prescripción Técnica" antes de proceder.
|
||||
|
||||
## 🚀 Fase de Sincronización de Squad y Materialización
|
||||
|
||||
Para ambos escenarios, tras recibir las respuestas:
|
||||
|
||||
1. **Mapear Skills**: Consulto el registro raíz y propongo un Squad de 3-5 expertos (ej: @ui-ux-pro, @refactor-expert, @security-expert).
|
||||
2. **Generar Artefactos (En Español)**:
|
||||
- `tareas.md`: Backlog detallado (de creación o de refactorización).
|
||||
- `plan_implementacion.md`: Hoja de ruta técnica con el estándar de diamante.
|
||||
|
||||
## ⚠️ Reglas de Oro
|
||||
|
||||
1. **Contexto Inteligente**: No mezcles datos de proyectos anteriores. Cada carpeta es una entidad única.
|
||||
2. **Estándar de Diamante**: Prioriza siempre soluciones escalables, seguras y estéticamente superiores.
|
||||
41
web-app/public/skills/10-andruia-skill-smith/SKILL.MD
Normal file
41
web-app/public/skills/10-andruia-skill-smith/SKILL.MD
Normal file
@@ -0,0 +1,41 @@
|
||||
---
|
||||
id: 10-andruia-skill-smith
|
||||
name: 10-andruia-skill-smith
|
||||
description: "Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante."
|
||||
category: andruia
|
||||
risk: official
|
||||
source: personal
|
||||
---
|
||||
|
||||
# 🔨 Andru.ia Skill-Smith (The Forge)
|
||||
|
||||
|
||||
## 📝 Descripción
|
||||
Soy el Ingeniero de Sistemas de Andru.ia. Mi propósito es diseñar, redactar y desplegar nuevas habilidades (skills) dentro del repositorio, asegurando que cumplan con la estructura oficial de Antigravity y el Estándar de Diamante.
|
||||
|
||||
## 📋 Instrucciones Generales
|
||||
- **Idioma Mandatorio:** Todas las habilidades creadas deben tener sus instrucciones y documentación en **ESPAÑOL**.
|
||||
- **Estructura Formal:** Debo seguir la anatomía de carpeta -> README.md -> Registro.
|
||||
- **Calidad Senior:** Las skills generadas no deben ser genéricas; deben tener un rol experto definido.
|
||||
|
||||
## 🛠️ Flujo de Trabajo (Protocolo de Forja)
|
||||
|
||||
### FASE 1: ADN de la Skill
|
||||
Solicitar al usuario los 3 pilares de la nueva habilidad:
|
||||
1. **Nombre Técnico:** (Ej: @cyber-sec, @data-visualizer).
|
||||
2. **Rol Experto:** (¿Quién es esta IA? Ej: "Un experto en auditoría de seguridad").
|
||||
3. **Outputs Clave:** (¿Qué archivos o acciones específicas debe realizar?).
|
||||
|
||||
### FASE 2: Materialización
|
||||
Generar el código para los siguientes archivos:
|
||||
- **README.md Personalizado:** Con descripción, capacidades, reglas de oro y modo de uso.
|
||||
- **Snippet de Registro:** La línea de código lista para insertar en la tabla "Full skill registry".
|
||||
|
||||
### FASE 3: Despliegue e Integración
|
||||
1. Crear la carpeta física en `D:\...\antigravity-awesome-skills\skills\`.
|
||||
2. Escribir el archivo README.md en dicha carpeta.
|
||||
3. Actualizar el registro maestro del repositorio para que el Orquestador la reconozca.
|
||||
|
||||
## ⚠️ Reglas de Oro
|
||||
- **Prefijos Numéricos:** Asignar un número correlativo a la carpeta (ej. 11, 12, 13) para mantener el orden.
|
||||
- **Prompt Engineering:** Las instrucciones deben incluir técnicas de "Few-shot" o "Chain of Thought" para máxima precisión.
|
||||
62
web-app/public/skills/20-andruia-niche-intelligence/SKILL.md
Normal file
62
web-app/public/skills/20-andruia-niche-intelligence/SKILL.md
Normal file
@@ -0,0 +1,62 @@
|
||||
---
|
||||
id: 20-andruia-niche-intelligence
|
||||
name: 20-andruia-niche-intelligence
|
||||
description: "Estratega de Inteligencia de Dominio de Andru.ia. Analiza el nicho específico de un proyecto para inyectar conocimientos, regulaciones y estándares únicos del sector. Actívalo tras definir el nicho."
|
||||
category: andruia
|
||||
risk: safe
|
||||
source: personal
|
||||
---
|
||||
|
||||
## When to Use
|
||||
|
||||
Use this skill once the project's niche or industry has been identified. It is essential for injecting domain-specific intelligence, regulatory requirements, and industry-standard UX patterns into the project.
|
||||
|
||||
# 🧠 Andru.ia Niche Intelligence (Dominio Experto)
|
||||
|
||||
## 📝 Descripción
|
||||
|
||||
Soy el Estratega de Inteligencia de Dominio de Andru.ia. Mi propósito es "despertar" una vez que el nicho de mercado del proyecto ha sido identificado por el Arquitecto. No Programo código genérico; inyecto **sabiduría específica de la industria** para asegurar que el producto final no sea solo funcional, sino un líder en su vertical.
|
||||
|
||||
## 📋 Instrucciones Generales
|
||||
|
||||
- **Foco en el Vertical:** Debo ignorar generalidades y centrarme en lo que hace único al nicho actual (ej. Fintech, EdTech, HealthTech, E-commerce, etc.).
|
||||
- **Idioma Mandatorio:** Toda la inteligencia generada debe ser en **ESPAÑOL**.
|
||||
- **Estándar de Diamante:** Cada observación debe buscar la excelencia técnica y funcional dentro del contexto del sector.
|
||||
|
||||
## 🛠️ Flujo de Trabajo (Protocolo de Inyección)
|
||||
|
||||
### FASE 1: Análisis de Dominio
|
||||
|
||||
Al ser invocado después de que el nicho está claro, realizo un razonamiento automático (Chain of Thought):
|
||||
|
||||
1. **Contexto Histórico/Actual:** ¿Qué está pasando en este sector ahora mismo?
|
||||
2. **Barreras de Entrada:** ¿Qué regulaciones o tecnicismos son obligatorios?
|
||||
3. **Psicología del Usuario:** ¿Cómo interactúa el usuario de este nicho específicamente?
|
||||
|
||||
### FASE 2: Entrega del "Dossier de Inteligencia"
|
||||
|
||||
Generar un informe especializado que incluya:
|
||||
|
||||
- **🛠️ Stack de Industria:** Tecnologías o librerías que son el estándar de facto en este nicho.
|
||||
- **📜 Cumplimiento y Normativa:** Leyes o estándares necesarios (ej. RGPD, HIPAA, Facturación Electrónica DIAN, etc.).
|
||||
- **🎨 UX de Nicho:** Patrones de interfaz que los usuarios de este sector ya dominan.
|
||||
- **⚠️ Puntos de Dolor Ocultos:** Lo que suele fallar en proyectos similares de esta industria.
|
||||
|
||||
## ⚠️ Reglas de Oro
|
||||
|
||||
1. **Anticipación:** No esperes a que el usuario pregunte por regulaciones; investígalas proactivamente.
|
||||
2. **Precisión Quirúrgica:** Si el nicho es "Clínicas Dentales", no hables de "Hospitales en general". Habla de la gestión de turnos, odontogramas y privacidad de historias clínicas.
|
||||
3. **Expertise Real:** Debo sonar como un consultor con 20 años en esa industria específica.
|
||||
|
||||
## 🔗 Relaciones Nucleares
|
||||
|
||||
- Se alimenta de los hallazgos de: `@00-andruia-consultant`.
|
||||
- Proporciona las bases para: `@ui-ux-pro-max` y `@security-review`.
|
||||
|
||||
## When to Use
|
||||
|
||||
Activa este skill **después de que el nicho de mercado esté claro** y ya exista una visión inicial definida por `@00-andruia-consultant`:
|
||||
|
||||
- Cuando quieras profundizar en regulaciones, estándares y patrones UX específicos de un sector concreto (Fintech, HealthTech, logística, etc.).
|
||||
- Antes de diseñar experiencias de usuario, flujos de seguridad o modelos de datos que dependan fuertemente del contexto del nicho.
|
||||
- Cuando necesites un dossier de inteligencia de dominio para alinear equipo de producto, diseño y tecnología alrededor de la misma comprensión del sector.
|
||||
96
web-app/public/skills/agentfolio/SKILL.md
Normal file
96
web-app/public/skills/agentfolio/SKILL.md
Normal file
@@ -0,0 +1,96 @@
|
||||
---
|
||||
name: agentfolio
|
||||
description: "Skill for discovering and researching autonomous AI agents, tools, and ecosystems using the AgentFolio directory."
|
||||
source: agentfolio.io
|
||||
risk: unknown
|
||||
---
|
||||
|
||||
# AgentFolio
|
||||
|
||||
**Role**: Autonomous Agent Discovery Guide
|
||||
|
||||
Use this skill when you want to **discover, compare, and research autonomous AI agents** across ecosystems.
|
||||
AgentFolio is a curated directory at https://agentfolio.io that tracks agent frameworks, products, and tools.
|
||||
|
||||
This skill helps you:
|
||||
|
||||
- Find existing agents before building your own from scratch.
|
||||
- Map the landscape of agent frameworks and hosted products.
|
||||
- Collect concrete examples and benchmarks for agent capabilities.
|
||||
|
||||
## Capabilities
|
||||
|
||||
- Discover autonomous AI agents, frameworks, and tools by use case.
|
||||
- Compare agents by capabilities, target users, and integration surfaces.
|
||||
- Identify gaps in the market or inspiration for new skills/workflows.
|
||||
- Gather example agent behavior and UX patterns for your own designs.
|
||||
- Track emerging trends in agent architectures and deployments.
|
||||
|
||||
## How to Use AgentFolio
|
||||
|
||||
1. **Open the directory**
|
||||
- Visit `https://agentfolio.io` in your browser.
|
||||
- Optionally filter by category (e.g., Dev Tools, Ops, Marketing, Productivity).
|
||||
|
||||
2. **Search by intent**
|
||||
- Start from the problem you want to solve:
|
||||
- “customer support agents”
|
||||
- “autonomous coding agents”
|
||||
- “research / analysis agents”
|
||||
- Use keywords in the AgentFolio search bar that match your domain or workflow.
|
||||
|
||||
3. **Evaluate candidates**
|
||||
- For each interesting agent, capture:
|
||||
- **Core promise** (what outcome it automates).
|
||||
- **Input / output shape** (APIs, UI, data sources).
|
||||
- **Autonomy model** (one-shot, multi-step, tool-using, human-in-the-loop).
|
||||
- **Deployment model** (SaaS, self-hosted, browser, IDE, etc.).
|
||||
|
||||
4. **Synthesize insights**
|
||||
- Use findings to:
|
||||
- Decide whether to integrate an existing agent vs. build your own.
|
||||
- Borrow successful UX and safety patterns.
|
||||
- Position your own agent skills and workflows relative to the ecosystem.
|
||||
|
||||
## Example Workflows
|
||||
|
||||
### 1) Landscape scan before building a new agent
|
||||
|
||||
- Define the problem: “autonomous test failure triage for CI pipelines”.
|
||||
- Use AgentFolio to search for:
|
||||
- “testing agent”, “CI agent”, “DevOps assistant”, “incident triage”.
|
||||
- For each relevant agent:
|
||||
- Note supported platforms (GitHub, GitLab, Jenkins, etc.).
|
||||
- Capture how they explain autonomy and safety boundaries.
|
||||
- Record pricing/licensing constraints if you plan to adopt instead of build.
|
||||
|
||||
### 2) Competitive and inspiration research for a new skill
|
||||
|
||||
- If you plan to add a new skill (e.g., observability agent, security agent):
|
||||
- Use AgentFolio to find similar agents and features.
|
||||
- Extract 3–5 concrete patterns you want to emulate or avoid.
|
||||
- Translate those patterns into clear requirements for your own skill.
|
||||
|
||||
### 3) Vendor shortlisting
|
||||
|
||||
- When choosing between multiple agent vendors:
|
||||
- Use AgentFolio entries as a neutral directory.
|
||||
- Build a comparison table (columns: capabilities, integrations, pricing, trust & security).
|
||||
- Use that table to drive a more formal evaluation or proof-of-concept.
|
||||
|
||||
## Example Prompts
|
||||
|
||||
Use these prompts when working with this skill in an AI coding agent:
|
||||
|
||||
- “Use AgentFolio to find 3 autonomous AI agents focused on code review. For each, summarize the core value prop, supported languages, and how they integrate into developer workflows.”
|
||||
- “Scan AgentFolio for agents that help with customer support triage. List the top options, their target customer size (SMB vs. enterprise), and any notable UX patterns.”
|
||||
- “Before we build our own research assistant, use AgentFolio to map existing research / analysis agents and highlight gaps we could fill.”
|
||||
|
||||
## When to Use
|
||||
|
||||
This skill is applicable when you need to **discover or compare autonomous AI agents** instead of building in a vacuum:
|
||||
|
||||
- At the start of a new agent or workflow project.
|
||||
- When evaluating vendors or tools to integrate.
|
||||
- When you want inspiration or best practices from existing agent products.
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: ai-engineer
|
||||
description: "Build production-ready LLM applications, advanced RAG systems, and"
|
||||
description: |
|
||||
Build production-ready LLM applications, advanced RAG systems, and
|
||||
intelligent agents. Implements vector search, multimodal AI, agent
|
||||
orchestration, and enterprise AI integrations. Use PROACTIVELY for LLM
|
||||
features, chatbots, AI agents, or AI-powered applications.
|
||||
@@ -9,6 +10,7 @@ metadata:
|
||||
risk: unknown
|
||||
source: community
|
||||
---
|
||||
|
||||
You are an AI engineer specializing in production-grade LLM applications, generative AI systems, and intelligent agent architectures.
|
||||
|
||||
## Use this skill when
|
||||
@@ -37,11 +39,13 @@ You are an AI engineer specializing in production-grade LLM applications, genera
|
||||
- Add guardrails for prompt injection, PII, and policy compliance.
|
||||
|
||||
## Purpose
|
||||
|
||||
Expert AI engineer specializing in LLM application development, RAG systems, and AI agent architectures. Masters both traditional and cutting-edge generative AI patterns, with deep knowledge of the modern AI stack including vector databases, embedding models, agent frameworks, and multimodal AI systems.
|
||||
|
||||
## Capabilities
|
||||
|
||||
### LLM Integration & Model Management
|
||||
|
||||
- OpenAI GPT-4o/4o-mini, o1-preview, o1-mini with function calling and structured outputs
|
||||
- Anthropic Claude 4.5 Sonnet/Haiku, Claude 4.1 Opus with tool use and computer use
|
||||
- Open-source models: Llama 3.1/3.2, Mixtral 8x7B/8x22B, Qwen 2.5, DeepSeek-V2
|
||||
@@ -51,6 +55,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
|
||||
- Cost optimization through model selection and caching strategies
|
||||
|
||||
### Advanced RAG Systems
|
||||
|
||||
- Production RAG architectures with multi-stage retrieval pipelines
|
||||
- Vector databases: Pinecone, Qdrant, Weaviate, Chroma, Milvus, pgvector
|
||||
- Embedding models: OpenAI text-embedding-3-large/small, Cohere embed-v3, BGE-large
|
||||
@@ -62,6 +67,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
|
||||
- Advanced RAG patterns: GraphRAG, HyDE, RAG-Fusion, self-RAG
|
||||
|
||||
### Agent Frameworks & Orchestration
|
||||
|
||||
- LangChain/LangGraph for complex agent workflows and state management
|
||||
- LlamaIndex for data-centric AI applications and advanced retrieval
|
||||
- CrewAI for multi-agent collaboration and specialized agent roles
|
||||
@@ -72,6 +78,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
|
||||
- Agent evaluation and monitoring with custom metrics
|
||||
|
||||
### Vector Search & Embeddings
|
||||
|
||||
- Embedding model selection and fine-tuning for domain-specific tasks
|
||||
- Vector indexing strategies: HNSW, IVF, LSH for different scale requirements
|
||||
- Similarity metrics: cosine, dot product, Euclidean for various use cases
|
||||
@@ -80,6 +87,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
|
||||
- Vector database optimization: indexing, sharding, and caching strategies
|
||||
|
||||
### Prompt Engineering & Optimization
|
||||
|
||||
- Advanced prompting techniques: chain-of-thought, tree-of-thoughts, self-consistency
|
||||
- Few-shot and in-context learning optimization
|
||||
- Prompt templates with dynamic variable injection and conditioning
|
||||
@@ -89,6 +97,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
|
||||
- Multi-modal prompting for vision and audio models
|
||||
|
||||
### Production AI Systems
|
||||
|
||||
- LLM serving with FastAPI, async processing, and load balancing
|
||||
- Streaming responses and real-time inference optimization
|
||||
- Caching strategies: semantic caching, response memoization, embedding caching
|
||||
@@ -98,6 +107,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
|
||||
- Observability: logging, metrics, tracing with LangSmith, Phoenix, Weights & Biases
|
||||
|
||||
### Multimodal AI Integration
|
||||
|
||||
- Vision models: GPT-4V, Claude 4 Vision, LLaVA, CLIP for image understanding
|
||||
- Audio processing: Whisper for speech-to-text, ElevenLabs for text-to-speech
|
||||
- Document AI: OCR, table extraction, layout understanding with models like LayoutLM
|
||||
@@ -105,6 +115,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
|
||||
- Cross-modal embeddings and unified vector spaces
|
||||
|
||||
### AI Safety & Governance
|
||||
|
||||
- Content moderation with OpenAI Moderation API and custom classifiers
|
||||
- Prompt injection detection and prevention strategies
|
||||
- PII detection and redaction in AI workflows
|
||||
@@ -113,6 +124,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
|
||||
- Responsible AI practices and ethical considerations
|
||||
|
||||
### Data Processing & Pipeline Management
|
||||
|
||||
- Document processing: PDF extraction, web scraping, API integrations
|
||||
- Data preprocessing: cleaning, normalization, deduplication
|
||||
- Pipeline orchestration with Apache Airflow, Dagster, Prefect
|
||||
@@ -121,6 +133,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
|
||||
- ETL/ELT processes for AI data preparation
|
||||
|
||||
### Integration & API Development
|
||||
|
||||
- RESTful API design for AI services with FastAPI, Flask
|
||||
- GraphQL APIs for flexible AI data querying
|
||||
- Webhook integration and event-driven architectures
|
||||
@@ -129,6 +142,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
|
||||
- API security: OAuth, JWT, API key management
|
||||
|
||||
## Behavioral Traits
|
||||
|
||||
- Prioritizes production reliability and scalability over proof-of-concept implementations
|
||||
- Implements comprehensive error handling and graceful degradation
|
||||
- Focuses on cost optimization and efficient resource utilization
|
||||
@@ -141,6 +155,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
|
||||
- Balances cutting-edge techniques with proven, stable solutions
|
||||
|
||||
## Knowledge Base
|
||||
|
||||
- Latest LLM developments and model capabilities (GPT-4o, Claude 4.5, Llama 3.2)
|
||||
- Modern vector database architectures and optimization techniques
|
||||
- Production AI system design patterns and best practices
|
||||
@@ -153,6 +168,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
|
||||
- Prompt engineering and optimization methodologies
|
||||
|
||||
## Response Approach
|
||||
|
||||
1. **Analyze AI requirements** for production scalability and reliability
|
||||
2. **Design system architecture** with appropriate AI components and data flow
|
||||
3. **Implement production-ready code** with comprehensive error handling
|
||||
@@ -163,6 +179,7 @@ Expert AI engineer specializing in LLM application development, RAG systems, and
|
||||
8. **Provide testing strategies** including adversarial and edge cases
|
||||
|
||||
## Example Interactions
|
||||
|
||||
- "Build a production RAG system for enterprise knowledge base with hybrid search"
|
||||
- "Implement a multi-agent customer service system with escalation workflows"
|
||||
- "Design a cost-optimized LLM inference pipeline with caching and load balancing"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: analytics-tracking
|
||||
description: ">"
|
||||
description: >
|
||||
Design, audit, and improve analytics tracking systems that produce reliable,
|
||||
decision-ready data. Use when the user wants to set up, fix, or evaluate
|
||||
analytics tracking (GA4, GTM, product analytics, events, conversions, UTMs).
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: angular
|
||||
description: ">-"
|
||||
description: >-
|
||||
Modern Angular (v20+) expert with deep knowledge of Signals, Standalone
|
||||
Components, Zoneless applications, SSR/Hydration, and reactive patterns.
|
||||
Use PROACTIVELY for Angular development, component architecture, state
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: api-documenter
|
||||
description: "Master API documentation with OpenAPI 3.1, AI-powered tools, and"
|
||||
description: |
|
||||
Master API documentation with OpenAPI 3.1, AI-powered tools, and
|
||||
modern developer experience practices. Create interactive docs, generate SDKs,
|
||||
and build comprehensive developer portals. Use PROACTIVELY for API
|
||||
documentation or developer portal creation.
|
||||
|
||||
209
web-app/public/skills/appdeploy/SKILL.md
Normal file
209
web-app/public/skills/appdeploy/SKILL.md
Normal file
@@ -0,0 +1,209 @@
|
||||
---
|
||||
name: appdeploy
|
||||
description: Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl.
|
||||
allowed-tools:
|
||||
- Bash
|
||||
risk: safe
|
||||
source: AppDeploy (MIT)
|
||||
metadata:
|
||||
author: appdeploy
|
||||
version: "1.0.5"
|
||||
---
|
||||
|
||||
# AppDeploy Skill
|
||||
|
||||
Deploy web apps to AppDeploy via HTTP API.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
- Use when planning or building apps and web apps
|
||||
- Use when deploying an app to a public URL
|
||||
- Use when publishing a website or web app
|
||||
- Use when the user says "deploy this", "make this live", or "give me a URL"
|
||||
- Use when updating an already-deployed app
|
||||
|
||||
## Setup (First Time Only)
|
||||
|
||||
1. **Check for existing API key:**
|
||||
- Look for a `.appdeploy` file in the project root
|
||||
- If it exists and contains a valid `api_key`, skip to Usage
|
||||
|
||||
2. **If no API key exists, register and get one:**
|
||||
```bash
|
||||
curl -X POST https://api-v2.appdeploy.ai/mcp/api-key \
|
||||
-H "Content-Type: application/json" \
|
||||
-d '{"client_name": "claude-code"}'
|
||||
```
|
||||
|
||||
Response:
|
||||
```json
|
||||
{
|
||||
"api_key": "ak_...",
|
||||
"user_id": "agent-claude-code-a1b2c3d4",
|
||||
"created_at": 1234567890,
|
||||
"message": "Save this key securely - it cannot be retrieved later"
|
||||
}
|
||||
```
|
||||
|
||||
3. **Save credentials to `.appdeploy`:**
|
||||
```json
|
||||
{
|
||||
"api_key": "ak_...",
|
||||
"endpoint": "https://api-v2.appdeploy.ai/mcp"
|
||||
}
|
||||
```
|
||||
|
||||
Add `.appdeploy` to `.gitignore` if not already present.
|
||||
|
||||
## Usage
|
||||
|
||||
Make JSON-RPC calls to the MCP endpoint:
|
||||
|
||||
```bash
|
||||
curl -X POST {endpoint} \
|
||||
-H "Content-Type: application/json" \
|
||||
-H "Accept: application/json, text/event-stream" \
|
||||
-H "Authorization: Bearer {api_key}" \
|
||||
-d '{
|
||||
"jsonrpc": "2.0",
|
||||
"id": 1,
|
||||
"method": "tools/call",
|
||||
"params": {
|
||||
"name": "{tool_name}",
|
||||
"arguments": { ... }
|
||||
}
|
||||
}'
|
||||
```
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **First, get deployment instructions:**
|
||||
Call `get_deploy_instructions` to understand constraints and requirements.
|
||||
|
||||
2. **Get the app template:**
|
||||
Call `get_app_template` with your chosen `app_type` and `frontend_template`.
|
||||
|
||||
3. **Deploy the app:**
|
||||
Call `deploy_app` with your app files. For new apps, set `app_id` to `null`.
|
||||
|
||||
4. **Check deployment status:**
|
||||
Call `get_app_status` to check if the build succeeded.
|
||||
|
||||
5. **View/manage your apps:**
|
||||
Use `get_apps` to list your deployed apps.
|
||||
|
||||
## Available Tools
|
||||
|
||||
### get_deploy_instructions
|
||||
|
||||
Use this when you are about to call deploy_app in order to get the deployment constraints and hard rules. You must call this tool before starting to generate any code. This tool returns instructions only and does not deploy anything.
|
||||
|
||||
**Parameters:**
|
||||
|
||||
|
||||
### deploy_app
|
||||
|
||||
Use this when the user asks to deploy or publish a website or web app and wants a public URL.
|
||||
Before generating files or calling this tool, you must call get_deploy_instructions and follow its constraints.
|
||||
|
||||
**Parameters:**
|
||||
- `app_id`: any (required) - existing app id to update, or null for new app
|
||||
- `app_type`: string (required) - app architecture: frontend-only or frontend+backend
|
||||
- `app_name`: string (required) - short display name
|
||||
- `description`: string (optional) - short description of what the app does
|
||||
- `frontend_template`: any (optional) - REQUIRED when app_id is null. One of: 'html-static' (simple sites), 'react-vite' (SPAs, games), 'nextjs-static' (multi-page). Template files auto-included.
|
||||
- `files`: array (optional) - Files to write. NEW APPS: only custom files + diffs to template files. UPDATES: only changed files using diffs[]. At least one of files[] or deletePaths[] required.
|
||||
- `deletePaths`: array (optional) - Paths to delete. ONLY for updates (app_id required). Cannot delete package.json or framework entry points.
|
||||
- `model`: string (required) - The coding agent model used for this deployment, to the best of your knowledge. Examples: 'codex-5.3', 'chatgpt', 'opus 4.6', 'claude-sonnet-4-5', 'gemini-2.5-pro'
|
||||
- `intent`: string (required) - The intent of this deployment. User-initiated examples: 'initial app deploy', 'bugfix - ui is too noisy'. Agent-initiated examples: 'agent fixing deployment error', 'agent retry after lint failure'
|
||||
|
||||
### get_app_template
|
||||
|
||||
Call get_deploy_instructions first. Then call this once you've decided app_type and frontend_template. Returns base app template and SDK types. Template files auto-included in deploy_app.
|
||||
|
||||
**Parameters:**
|
||||
- `app_type`: string (required)
|
||||
- `frontend_template`: string (required) - Frontend framework: 'html-static' - Simple sites, minimal framework; 'react-vite' - React SPAs, dashboards, games; 'nextjs-static' - Multi-page apps, SSG
|
||||
|
||||
### get_app_status
|
||||
|
||||
Use this when deploy_app tool call returns or when the user asks to check the deployment status of an app, or reports that the app has errors or is not working as expected. Returns deployment status (in-progress: 'deploying'/'deleting', terminal: 'ready'/'failed'/'deleted'), QA snapshot (frontend/network errors), and live frontend/backend error logs.
|
||||
|
||||
**Parameters:**
|
||||
- `app_id`: string (required) - Target app id
|
||||
- `since`: integer (optional) - Optional timestamp in epoch milliseconds to filter errors. When provided, returns only errors since that timestamp.
|
||||
|
||||
### delete_app
|
||||
|
||||
Use this when you want to permanently delete an app. Use only on explicit user request. This is irreversible; after deletion, status checks will return not found.
|
||||
|
||||
**Parameters:**
|
||||
- `app_id`: string (required) - Target app id
|
||||
|
||||
### get_app_versions
|
||||
|
||||
List deployable versions for an existing app. Requires app_id. Returns newest-first {name, version, timestamp} items. Display 'name' to users. DO NOT display the 'version' value to users. Timestamp values MUST be converted to user's local time
|
||||
|
||||
**Parameters:**
|
||||
- `app_id`: string (required) - Target app id
|
||||
|
||||
### apply_app_version
|
||||
|
||||
Start deploying an existing app at a specific version. Use the 'version' value (not 'name') from get_app_versions. Returns true if accepted and deployment started; use get_app_status to observe completion.
|
||||
|
||||
**Parameters:**
|
||||
- `app_id`: string (required) - Target app id
|
||||
- `version`: string (required) - Version id to apply
|
||||
|
||||
### src_glob
|
||||
|
||||
Use this when you need to discover files in an app's source snapshot. Returns file paths matching a glob pattern (no content). Useful for exploring project structure before reading or searching files.
|
||||
|
||||
**Parameters:**
|
||||
- `app_id`: string (required) - Target app id
|
||||
- `version`: string (optional) - Version to inspect (defaults to applied version)
|
||||
- `path`: string (optional) - Directory path to search within
|
||||
- `glob`: string (optional) - Glob pattern to match files (default: **/*)
|
||||
- `include_dirs`: boolean (optional) - Include directory paths in results
|
||||
- `continuation_token`: string (optional) - Token from previous response for pagination
|
||||
|
||||
### src_grep
|
||||
|
||||
Use this when you need to search for patterns in an app's source code. Returns matching lines with optional context. Supports regex patterns, glob filters, and multiple output modes.
|
||||
|
||||
**Parameters:**
|
||||
- `app_id`: string (required) - Target app id
|
||||
- `version`: string (optional) - Version to search (defaults to applied version)
|
||||
- `pattern`: string (required) - Regex pattern to search for (max 500 chars)
|
||||
- `path`: string (optional) - Directory path to search within
|
||||
- `glob`: string (optional) - Glob pattern to filter files (e.g., '*.ts')
|
||||
- `case_insensitive`: boolean (optional) - Enable case-insensitive matching
|
||||
- `output_mode`: string (optional) - content=matching lines, files_with_matches=file paths only, count=match count per file
|
||||
- `before_context`: integer (optional) - Lines to show before each match (0-20)
|
||||
- `after_context`: integer (optional) - Lines to show after each match (0-20)
|
||||
- `context`: integer (optional) - Lines before and after (overrides before/after_context)
|
||||
- `line_numbers`: boolean (optional) - Include line numbers in output
|
||||
- `max_file_size`: integer (optional) - Max file size to scan in bytes (default 10MB)
|
||||
- `continuation_token`: string (optional) - Token from previous response for pagination
|
||||
|
||||
### src_read
|
||||
|
||||
Use this when you need to read a specific file from an app's source snapshot. Returns file content with line-based pagination (offset/limit). Handles both text and binary files.
|
||||
|
||||
**Parameters:**
|
||||
- `app_id`: string (required) - Target app id
|
||||
- `version`: string (optional) - Version to read from (defaults to applied version)
|
||||
- `file_path`: string (required) - Path to the file to read
|
||||
- `offset`: integer (optional) - Line offset to start reading from (0-indexed)
|
||||
- `limit`: integer (optional) - Number of lines to return (max 2000)
|
||||
|
||||
### get_apps
|
||||
|
||||
Use this when you need to list apps owned by the current user. Returns app details with display fields for user presentation and data fields for tool chaining.
|
||||
|
||||
**Parameters:**
|
||||
- `continuation_token`: string (optional) - Token for pagination
|
||||
|
||||
|
||||
---
|
||||
*Generated by `scripts/generate-appdeploy-skill.ts`*
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: arm-cortex-expert
|
||||
description: ">"
|
||||
description: >
|
||||
Senior embedded software engineer specializing in firmware and driver
|
||||
development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD).
|
||||
Decades of experience writing reliable, optimized, and maintainable embedded
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-agents-persistent-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Agents Persistent SDK for .NET. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Use for agent CRUD, conversation threads, streaming responses, function calling, file search, and code interpreter. Triggers: "PersistentAgentsClient", "persistent agents", "agent threads", "agent runs", "streaming agents", "function calling agents .NET".
|
||||
package: Azure.AI.Agents.Persistent
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-agents-persistent-java
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools.
|
||||
Triggers: "PersistentAgentsClient", "persistent agents java", "agent threads java", "agent runs java", "streaming agents java".
|
||||
package: com.azure:azure-ai-agents-persistent
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-contentsafety-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Content Safety SDK for Python. Use for detecting harmful content in text and images with multi-severity classification.
|
||||
Triggers: "azure-ai-contentsafety", "ContentSafetyClient", "content moderation", "harmful content", "text analysis", "image analysis".
|
||||
package: azure-ai-contentsafety
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-contentunderstanding-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video.
|
||||
Triggers: "azure-ai-contentunderstanding", "ContentUnderstandingClient", "multimodal analysis", "document extraction", "video analysis", "audio transcription".
|
||||
package: azure-ai-contentunderstanding
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-document-intelligence-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Document Intelligence SDK for .NET. Extract text, tables, and structured data from documents using prebuilt and custom models. Use for invoice processing, receipt extraction, ID document analysis, and custom document models. Triggers: "Document Intelligence", "DocumentIntelligenceClient", "form recognizer", "invoice extraction", "receipt OCR", "document analysis .NET".
|
||||
package: Azure.AI.DocumentIntelligence
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-ml-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Machine Learning SDK v2 for Python. Use for ML workspaces, jobs, models, datasets, compute, and pipelines.
|
||||
Triggers: "azure-ai-ml", "MLClient", "workspace", "model registry", "training jobs", "datasets".
|
||||
package: azure-ai-ml
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-openai-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure OpenAI SDK for .NET. Client library for Azure OpenAI and OpenAI services. Use for chat completions, embeddings, image generation, audio transcription, and assistants. Triggers: "Azure OpenAI", "AzureOpenAIClient", "ChatClient", "chat completions .NET", "GPT-4", "embeddings", "DALL-E", "Whisper", "OpenAI .NET".
|
||||
package: Azure.AI.OpenAI
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-projects-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Projects SDK for .NET. High-level client for Azure AI Foundry projects including agents, connections, datasets, deployments, evaluations, and indexes. Use for AI Foundry project management, versioned agents, and orchestration. Triggers: "AI Projects", "AIProjectClient", "Foundry project", "versioned agents", "evaluations", "datasets", "connections", "deployments .NET".
|
||||
package: Azure.AI.Projects
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-projects-java
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Projects SDK for Java. High-level SDK for Azure AI Foundry project management including connections, datasets, indexes, and evaluations.
|
||||
Triggers: "AIProjectClient java", "azure ai projects java", "Foundry project java", "ConnectionsClient", "DatasetsClient", "IndexesClient".
|
||||
package: com.azure:azure-ai-projects
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-textanalytics-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Text Analytics SDK for sentiment analysis, entity recognition, key phrases, language detection, PII, and healthcare NLP. Use for natural language processing on text.
|
||||
Triggers: "text analytics", "sentiment analysis", "entity recognition", "key phrase", "PII detection", "TextAnalyticsClient".
|
||||
package: azure-ai-textanalytics
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-transcription-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Transcription SDK for Python. Use for real-time and batch speech-to-text transcription with timestamps and diarization.
|
||||
Triggers: "transcription", "speech to text", "Azure AI Transcription", "TranscriptionClient".
|
||||
package: azure-ai-transcription
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-translation-document-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale.
|
||||
Triggers: "document translation", "batch translation", "translate documents", "DocumentTranslationClient".
|
||||
package: azure-ai-translation-document
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-translation-text-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications.
|
||||
Triggers: "text translation", "translator", "translate text", "transliterate", "TextTranslationClient".
|
||||
package: azure-ai-translation-text
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-vision-imageanalysis-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Vision Image Analysis SDK for captions, tags, objects, OCR, people detection, and smart cropping. Use for computer vision and image understanding tasks.
|
||||
Triggers: "image analysis", "computer vision", "OCR", "object detection", "ImageAnalysisClient", "image caption".
|
||||
package: azure-ai-vision-imageanalysis
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-voicelive-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Voice Live SDK for .NET. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots. Triggers: "voice live", "real-time voice", "VoiceLiveClient", "VoiceLiveSession", "voice assistant .NET", "bidirectional audio", "speech-to-speech".
|
||||
package: Azure.AI.VoiceLive
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-voicelive-java
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI VoiceLive SDK for Java. Real-time bidirectional voice conversations with AI assistants using WebSocket.
|
||||
Triggers: "VoiceLiveClient java", "voice assistant java", "real-time voice java", "audio streaming java", "voice activity detection java".
|
||||
package: com.azure:azure-ai-voicelive
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-ai-voicelive-ts
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Voice Live SDK for JavaScript/TypeScript. Build real-time voice AI applications with bidirectional WebSocket communication. Use for voice assistants, conversational AI, real-time speech-to-speech, and voice-enabled chatbots in Node.js or browser environments. Triggers: "voice live", "real-time voice", "VoiceLiveClient", "VoiceLiveSession", "voice assistant TypeScript", "bidirectional audio", "speech-to-speech JavaScript".
|
||||
package: "@azure/ai-voicelive"
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-appconfiguration-java
|
||||
description: "|"
|
||||
description: |
|
||||
Azure App Configuration SDK for Java. Centralized application configuration management with key-value settings, feature flags, and snapshots.
|
||||
Triggers: "ConfigurationClient java", "app configuration java", "feature flag java", "configuration setting java", "azure config java".
|
||||
package: com.azure:azure-data-appconfiguration
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-appconfiguration-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure App Configuration SDK for Python. Use for centralized configuration management, feature flags, and dynamic settings.
|
||||
Triggers: "azure-appconfiguration", "AzureAppConfigurationClient", "feature flags", "configuration", "key-value settings".
|
||||
package: azure-appconfiguration
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-compute-batch-java
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Batch SDK for Java. Run large-scale parallel and HPC batch jobs with pools, jobs, tasks, and compute nodes.
|
||||
Triggers: "BatchClient java", "azure batch java", "batch pool java", "batch job java", "HPC java", "parallel computing java".
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-containerregistry-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories.
|
||||
Triggers: "azure-containerregistry", "ContainerRegistryClient", "container images", "docker registry", "ACR".
|
||||
package: azure-containerregistry
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-cosmos-java
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Cosmos DB SDK for Java. NoSQL database operations with global distribution, multi-model support, and reactive patterns.
|
||||
Triggers: "CosmosClient java", "CosmosAsyncClient", "cosmos database java", "cosmosdb java", "document database java".
|
||||
package: azure-cosmos
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-cosmos-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Cosmos DB SDK for Python (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.
|
||||
Triggers: "cosmos db", "CosmosClient", "container", "document", "NoSQL", "partition key".
|
||||
package: azure-cosmos
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-cosmos-rust
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Cosmos DB SDK for Rust (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.
|
||||
Triggers: "cosmos db rust", "CosmosClient rust", "container", "document rust", "NoSQL rust", "partition key".
|
||||
package: azure_data_cosmos
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-cosmos-ts
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Cosmos DB JavaScript/TypeScript SDK (@azure/cosmos) for data plane operations. Use for CRUD operations on documents, queries, bulk operations, and container management. Triggers: "Cosmos DB", "@azure/cosmos", "CosmosClient", "document CRUD", "NoSQL queries", "bulk operations", "partition key", "container.items".
|
||||
package: "@azure/cosmos"
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-data-tables-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Tables SDK for Python (Storage and Cosmos DB). Use for NoSQL key-value storage, entity CRUD, and batch operations.
|
||||
Triggers: "table storage", "TableServiceClient", "TableClient", "entities", "PartitionKey", "RowKey".
|
||||
package: azure-data-tables
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-eventgrid-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents. Triggers: "Event Grid", "EventGridPublisherClient", "CloudEvent", "EventGridEvent", "publish events .NET", "event-driven", "pub/sub".
|
||||
package: Azure.Messaging.EventGrid
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-eventgrid-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Event Grid SDK for Python. Use for publishing events, handling CloudEvents, and event-driven architectures.
|
||||
Triggers: "event grid", "EventGridPublisherClient", "CloudEvent", "EventGridEvent", "publish events".
|
||||
package: azure-eventgrid
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-eventhub-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: "Event Hubs", "event streaming", "EventHubProducerClient", "EventProcessorClient", "send events", "receive events", "checkpointing", "partition".
|
||||
package: Azure.Messaging.EventHubs
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-eventhub-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Event Hubs SDK for Python streaming. Use for high-throughput event ingestion, producers, consumers, and checkpointing.
|
||||
Triggers: "event hubs", "EventHubProducerClient", "EventHubConsumerClient", "streaming", "partitions".
|
||||
package: azure-eventhub
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-eventhub-rust
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Event Hubs SDK for Rust. Use for sending and receiving events, streaming data ingestion.
|
||||
Triggers: "event hubs rust", "ProducerClient rust", "ConsumerClient rust", "send event rust", "streaming rust".
|
||||
package: azure_messaging_eventhubs
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-identity-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Identity SDK for .NET. Authentication library for Azure SDK clients using Microsoft Entra ID. Use for DefaultAzureCredential, managed identity, service principals, and developer credentials. Triggers: "Azure Identity", "DefaultAzureCredential", "ManagedIdentityCredential", "ClientSecretCredential", "authentication .NET", "Azure auth", "credential chain".
|
||||
package: Azure.Identity
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-identity-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Identity SDK for Python authentication. Use for DefaultAzureCredential, managed identity, service principals, and token caching.
|
||||
Triggers: "azure-identity", "DefaultAzureCredential", "authentication", "managed identity", "service principal", "credential".
|
||||
package: azure-identity
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-identity-rust
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Identity SDK for Rust authentication. Use for DeveloperToolsCredential, ManagedIdentityCredential, ClientSecretCredential, and token-based authentication.
|
||||
Triggers: "azure-identity", "DeveloperToolsCredential", "authentication rust", "managed identity rust", "credential rust".
|
||||
package: azure_identity
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-keyvault-certificates-rust
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Key Vault Certificates SDK for Rust. Use for creating, importing, and managing certificates.
|
||||
Triggers: "keyvault certificates rust", "CertificateClient rust", "create certificate rust", "import certificate rust".
|
||||
package: azure_security_keyvault_certificates
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-keyvault-keys-rust
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Key Vault Keys SDK for Rust. Use for creating, managing, and using cryptographic keys.
|
||||
Triggers: "keyvault keys rust", "KeyClient rust", "create key rust", "encrypt rust", "sign rust".
|
||||
package: azure_security_keyvault_keys
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-keyvault-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Key Vault SDK for Python. Use for secrets, keys, and certificates management with secure storage.
|
||||
Triggers: "key vault", "SecretClient", "KeyClient", "CertificateClient", "secrets", "encryption keys".
|
||||
package: azure-keyvault-secrets, azure-keyvault-keys, azure-keyvault-certificates
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-keyvault-secrets-rust
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Key Vault Secrets SDK for Rust. Use for storing and retrieving secrets, passwords, and API keys.
|
||||
Triggers: "keyvault secrets rust", "SecretClient rust", "get secret rust", "set secret rust".
|
||||
package: azure_security_keyvault_secrets
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-maps-search-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data. Triggers: "Azure Maps", "MapsSearchClient", "MapsRoutingClient", "MapsRenderingClient", "geocoding .NET", "route directions", "map tiles", "geolocation".
|
||||
package: Azure.Maps.Search
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-messaging-webpubsubservice-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Web PubSub Service SDK for Python. Use for real-time messaging, WebSocket connections, and pub/sub patterns.
|
||||
Triggers: "azure-messaging-webpubsubservice", "WebPubSubServiceClient", "real-time", "WebSocket", "pub/sub".
|
||||
package: azure-messaging-webpubsubservice
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-mgmt-apicenter-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: "API Center", "ApiCenterService", "ApiCenterWorkspace", "ApiCenterApi", "API inventory", "API governance", "API versioning", "API catalog", "API discovery".
|
||||
package: Azure.ResourceManager.ApiCenter
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-mgmt-apicenter-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.
|
||||
Triggers: "azure-mgmt-apicenter", "ApiCenterMgmtClient", "API Center", "API inventory", "API governance".
|
||||
package: azure-mgmt-apicenter
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-mgmt-apimanagement-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Resource Manager SDK for API Management in .NET. Use for MANAGEMENT PLANE operations: creating/managing APIM services, APIs, products, subscriptions, policies, users, groups, gateways, and backends via Azure Resource Manager. Triggers: "API Management", "APIM service", "create APIM", "manage APIs", "ApiManagementServiceResource", "API policies", "APIM products", "APIM subscriptions".
|
||||
package: Azure.ResourceManager.ApiManagement
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-mgmt-apimanagement-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure API Management SDK for Python. Use for managing APIM services, APIs, products, subscriptions, and policies.
|
||||
Triggers: "azure-mgmt-apimanagement", "ApiManagementClient", "APIM", "API gateway", "API Management".
|
||||
package: azure-mgmt-apimanagement
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-mgmt-applicationinsights-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Application Insights SDK for .NET. Application performance monitoring and observability resource management. Use for creating Application Insights components, web tests, workbooks, analytics items, and API keys. Triggers: "Application Insights", "ApplicationInsights", "App Insights", "APM", "application monitoring", "web tests", "availability tests", "workbooks".
|
||||
package: Azure.ResourceManager.ApplicationInsights
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-mgmt-arizeaiobservabilityeval-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Resource Manager SDK for Arize AI Observability and Evaluation (.NET). Use when managing Arize AI organizations
|
||||
on Azure via Azure Marketplace, creating/updating/deleting Arize resources, or integrating Arize ML observability
|
||||
into .NET applications. Triggers: "Arize AI", "ML observability", "ArizeAIObservabilityEval", "Arize organization".
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-mgmt-botservice-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
|
||||
package: Azure.ResourceManager.BotService
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-mgmt-botservice-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Bot Service Management SDK for Python. Use for creating, managing, and configuring Azure Bot Service resources.
|
||||
Triggers: "azure-mgmt-botservice", "AzureBotService", "bot management", "conversational AI", "bot channels".
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-mgmt-fabric-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager. Triggers: "Fabric capacity", "create capacity", "suspend capacity", "resume capacity", "Fabric SKU", "provision Fabric", "ARM Fabric", "FabricCapacityResource".
|
||||
package: Azure.ResourceManager.Fabric
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-mgmt-fabric-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Fabric Management SDK for Python. Use for managing Microsoft Fabric capacities and resources.
|
||||
Triggers: "azure-mgmt-fabric", "FabricMgmtClient", "Fabric capacity", "Microsoft Fabric", "Power BI capacity".
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-mgmt-weightsandbiases-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Weights & Biases SDK for .NET. ML experiment tracking and model management via Azure Marketplace. Use for creating W&B instances, managing SSO, marketplace integration, and ML observability. Triggers: "Weights and Biases", "W&B", "WeightsAndBiases", "ML experiment tracking", "model registry", "experiment management", "wandb".
|
||||
package: Azure.ResourceManager.WeightsAndBiases
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-monitor-ingestion-java
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Monitor Ingestion SDK for Java. Send custom logs to Azure Monitor via Data Collection Rules (DCR) and Data Collection Endpoints (DCE).
|
||||
Triggers: "LogsIngestionClient java", "azure monitor ingestion java", "custom logs java", "DCR java", "data collection rule java".
|
||||
package: com.azure:azure-monitor-ingestion
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-monitor-ingestion-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Monitor Ingestion SDK for Python. Use for sending custom logs to Log Analytics workspace via Logs Ingestion API.
|
||||
Triggers: "azure-monitor-ingestion", "LogsIngestionClient", "custom logs", "DCR", "data collection rule", "Log Analytics".
|
||||
package: azure-monitor-ingestion
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-monitor-opentelemetry-exporter-java
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.
|
||||
Triggers: "AzureMonitorExporter java", "opentelemetry azure java", "application insights java otel", "azure monitor tracing java".
|
||||
Note: This package is DEPRECATED. Migrate to azure-monitor-opentelemetry-autoconfigure.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-monitor-opentelemetry-exporter-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Monitor OpenTelemetry Exporter for Python. Use for low-level OpenTelemetry export to Application Insights.
|
||||
Triggers: "azure-monitor-opentelemetry-exporter", "AzureMonitorTraceExporter", "AzureMonitorMetricExporter", "AzureMonitorLogExporter".
|
||||
package: azure-monitor-opentelemetry-exporter
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-monitor-opentelemetry-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Monitor OpenTelemetry Distro for Python. Use for one-line Application Insights setup with auto-instrumentation.
|
||||
Triggers: "azure-monitor-opentelemetry", "configure_azure_monitor", "Application Insights", "OpenTelemetry distro", "auto-instrumentation".
|
||||
package: azure-monitor-opentelemetry
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-monitor-query-java
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.
|
||||
Triggers: "LogsQueryClient java", "MetricsQueryClient java", "kusto query java", "log analytics java", "azure monitor query java".
|
||||
Note: This package is deprecated. Migrate to azure-monitor-query-logs and azure-monitor-query-metrics.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-monitor-query-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Monitor Query SDK for Python. Use for querying Log Analytics workspaces and Azure Monitor metrics.
|
||||
Triggers: "azure-monitor-query", "LogsQueryClient", "MetricsQueryClient", "Log Analytics", "Kusto queries", "Azure metrics".
|
||||
package: azure-monitor-query
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-postgres-ts
|
||||
description: "|"
|
||||
description: |
|
||||
Connect to Azure Database for PostgreSQL Flexible Server from Node.js/TypeScript using the pg (node-postgres) package. Use for PostgreSQL queries, connection pooling, transactions, and Microsoft Entra ID (passwordless) authentication. Triggers: "PostgreSQL", "postgres", "pg client", "node-postgres", "Azure PostgreSQL connection", "PostgreSQL TypeScript", "pg Pool", "passwordless postgres".
|
||||
package: pg
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-resource-manager-cosmosdb-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Resource Manager SDK for Cosmos DB in .NET. Use for MANAGEMENT PLANE operations: creating/managing Cosmos DB accounts, databases, containers, throughput settings, and RBAC via Azure Resource Manager. NOT for data plane operations (CRUD on documents) - use Microsoft.Azure.Cosmos for that. Triggers: "Cosmos DB account", "create Cosmos account", "manage Cosmos resources", "ARM Cosmos", "CosmosDBAccountResource", "provision Cosmos DB".
|
||||
package: Azure.ResourceManager.CosmosDB
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-resource-manager-durabletask-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Resource Manager SDK for Durable Task Scheduler in .NET. Use for MANAGEMENT PLANE operations: creating/managing Durable Task Schedulers, Task Hubs, and retention policies via Azure Resource Manager. Triggers: "Durable Task Scheduler", "create scheduler", "task hub", "DurableTaskSchedulerResource", "provision Durable Task", "orchestration scheduler".
|
||||
package: Azure.ResourceManager.DurableTask
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-resource-manager-mysql-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "MySQL", "MySqlFlexibleServer", "MySQL Flexible Server", "Azure Database for MySQL", "MySQL database management", "MySQL firewall", "MySQL backup".
|
||||
package: Azure.ResourceManager.MySql
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-resource-manager-playwright-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Resource Manager SDK for Microsoft Playwright Testing in .NET. Use for MANAGEMENT PLANE operations: creating/managing Playwright Testing workspaces, checking name availability, and managing workspace quotas via Azure Resource Manager. NOT for running Playwright tests - use Azure.Developer.MicrosoftPlaywrightTesting.NUnit for that. Triggers: "Playwright workspace", "create Playwright Testing workspace", "manage Playwright resources", "ARM Playwright", "PlaywrightWorkspaceResource", "provision Playwright Testing".
|
||||
package: Azure.ResourceManager.Playwright
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-resource-manager-postgresql-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "PostgreSQL", "PostgreSqlFlexibleServer", "PostgreSQL Flexible Server", "Azure Database for PostgreSQL", "PostgreSQL database management", "PostgreSQL firewall", "PostgreSQL backup", "Postgres".
|
||||
package: Azure.ResourceManager.PostgreSql
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-resource-manager-redis-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) - use StackExchange.Redis for that. Triggers: "Redis cache", "create Redis", "manage Redis", "ARM Redis", "RedisResource", "provision Redis", "Azure Cache for Redis".
|
||||
package: Azure.ResourceManager.Redis
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-resource-manager-sql-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Resource Manager SDK for Azure SQL in .NET. Use for MANAGEMENT PLANE operations: creating/managing SQL servers, databases, elastic pools, firewall rules, and failover groups via Azure Resource Manager. NOT for data plane operations (executing queries) - use Microsoft.Data.SqlClient for that. Triggers: "SQL server", "create SQL database", "manage SQL resources", "ARM SQL", "SqlServerResource", "provision Azure SQL", "elastic pool", "firewall rule".
|
||||
package: Azure.ResourceManager.Sql
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-search-documents-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Search SDK for .NET (Azure.Search.Documents). Use for building search applications with full-text, vector, semantic, and hybrid search. Covers SearchClient (queries, document CRUD), SearchIndexClient (index management), and SearchIndexerClient (indexers, skillsets). Triggers: "Azure Search .NET", "SearchClient", "SearchIndexClient", "vector search C#", "semantic search .NET", "hybrid search", "Azure.Search.Documents".
|
||||
package: Azure.Search.Documents
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-search-documents-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure AI Search SDK for Python. Use for vector search, hybrid search, semantic ranking, indexing, and skillsets.
|
||||
Triggers: "azure-search-documents", "SearchClient", "SearchIndexClient", "vector search", "hybrid search", "semantic search".
|
||||
package: azure-search-documents
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-security-keyvault-keys-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Key Vault Keys SDK for .NET. Client library for managing cryptographic keys in Azure Key Vault and Managed HSM. Use for key creation, rotation, encryption, decryption, signing, and verification. Triggers: "Key Vault keys", "KeyClient", "CryptographyClient", "RSA key", "EC key", "encrypt decrypt .NET", "key rotation", "HSM".
|
||||
package: Azure.Security.KeyVault.Keys
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-servicebus-dotnet
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions. Use for reliable message delivery, pub/sub patterns, dead letter handling, and background processing. Triggers: "Service Bus", "ServiceBusClient", "ServiceBusSender", "ServiceBusReceiver", "ServiceBusProcessor", "message queue", "pub/sub .NET", "dead letter queue".
|
||||
package: Azure.Messaging.ServiceBus
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-servicebus-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Service Bus SDK for Python messaging. Use for queues, topics, subscriptions, and enterprise messaging patterns.
|
||||
Triggers: "service bus", "ServiceBusClient", "queue", "topic", "subscription", "message broker".
|
||||
package: azure-servicebus
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-speech-to-text-rest-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Speech to Text REST API for short audio (Python). Use for simple speech recognition of audio files up to 60 seconds without the Speech SDK.
|
||||
Triggers: "speech to text REST", "short audio transcription", "speech recognition REST API", "STT REST", "recognize speech REST".
|
||||
DO NOT USE FOR: Long audio (>60 seconds), real-time streaming, batch transcription, custom speech models, speech translation. Use Speech SDK or Batch Transcription API instead.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-storage-blob-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Blob Storage SDK for Python. Use for uploading, downloading, listing blobs, managing containers, and blob lifecycle.
|
||||
Triggers: "blob storage", "BlobServiceClient", "ContainerClient", "BlobClient", "upload blob", "download blob".
|
||||
package: azure-storage-blob
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-storage-blob-rust
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Blob Storage SDK for Rust. Use for uploading, downloading, and managing blobs and containers.
|
||||
Triggers: "blob storage rust", "BlobClient rust", "upload blob rust", "download blob rust", "container rust".
|
||||
package: azure_storage_blob
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-storage-blob-ts
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Blob Storage JavaScript/TypeScript SDK (@azure/storage-blob) for blob operations. Use for uploading, downloading, listing, and managing blobs and containers. Supports block blobs, append blobs, page blobs, SAS tokens, and streaming. Triggers: "blob storage", "@azure/storage-blob", "BlobServiceClient", "ContainerClient", "upload blob", "download blob", "SAS token", "block blob".
|
||||
package: "@azure/storage-blob"
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-storage-file-datalake-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Data Lake Storage Gen2 SDK for Python. Use for hierarchical file systems, big data analytics, and file/directory operations.
|
||||
Triggers: "data lake", "DataLakeServiceClient", "FileSystemClient", "ADLS Gen2", "hierarchical namespace".
|
||||
package: azure-storage-file-datalake
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-storage-file-share-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Storage File Share SDK for Python. Use for SMB file shares, directories, and file operations in the cloud.
|
||||
Triggers: "azure-storage-file-share", "ShareServiceClient", "ShareClient", "file share", "SMB".
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-storage-file-share-ts
|
||||
description: "|"
|
||||
description: |
|
||||
Azure File Share JavaScript/TypeScript SDK (@azure/storage-file-share) for SMB file share operations. Use for creating shares, managing directories, uploading/downloading files, and handling file metadata. Supports Azure Files SMB protocol scenarios. Triggers: "file share", "@azure/storage-file-share", "ShareServiceClient", "ShareClient", "SMB", "Azure Files".
|
||||
package: "@azure/storage-file-share"
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-storage-queue-py
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Queue Storage SDK for Python. Use for reliable message queuing, task distribution, and asynchronous processing.
|
||||
Triggers: "queue storage", "QueueServiceClient", "QueueClient", "message queue", "dequeue".
|
||||
package: azure-storage-queue
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: azure-storage-queue-ts
|
||||
description: "|"
|
||||
description: |
|
||||
Azure Queue Storage JavaScript/TypeScript SDK (@azure/storage-queue) for message queue operations. Use for sending, receiving, peeking, and deleting messages in queues. Supports visibility timeout, message encoding, and batch operations. Triggers: "queue storage", "@azure/storage-queue", "QueueServiceClient", "QueueClient", "send message", "receive message", "dequeue", "visibility timeout".
|
||||
package: "@azure/storage-queue"
|
||||
risk: unknown
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: backend-architect
|
||||
description: "Expert backend architect specializing in scalable API design,"
|
||||
description: |
|
||||
Expert backend architect specializing in scalable API design,
|
||||
microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC
|
||||
APIs, event-driven architectures, service mesh patterns, and modern backend
|
||||
frameworks. Handles service boundary definition, inter-service communication,
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: backend-security-coder
|
||||
description: "Expert in secure backend coding practices specializing in input"
|
||||
description: |
|
||||
Expert in secure backend coding practices specializing in input
|
||||
validation, authentication, and API security. Use PROACTIVELY for backend
|
||||
security implementations or security code reviews.
|
||||
metadata:
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: bash-pro
|
||||
description: "Master of defensive Bash scripting for production automation, CI/CD"
|
||||
description: |
|
||||
Master of defensive Bash scripting for production automation, CI/CD
|
||||
pipelines, and system utilities. Expert in safe, portable, and testable shell
|
||||
scripts.
|
||||
metadata:
|
||||
|
||||
@@ -83,25 +83,27 @@ fn main() {
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: Spawning Entities with Bundles
|
||||
### Example 1: Spawning Entities with Require Component
|
||||
|
||||
```rust
|
||||
#[derive(Bundle)]
|
||||
struct PlayerBundle {
|
||||
player: Player,
|
||||
velocity: Velocity,
|
||||
sprite: SpriteBundle,
|
||||
use bevy::prelude::*;
|
||||
|
||||
#[derive(Component, Reflect, Default)]
|
||||
#[require(Velocity, Sprite)]
|
||||
struct Player;
|
||||
|
||||
#[derive(Component, Default)]
|
||||
struct Velocity {
|
||||
x: f32,
|
||||
y: f32,
|
||||
}
|
||||
|
||||
fn setup(mut commands: Commands, asset_server: Res<AssetServer>) {
|
||||
commands.spawn(PlayerBundle {
|
||||
player: Player,
|
||||
velocity: Velocity { x: 10.0, y: 0.0 },
|
||||
sprite: SpriteBundle {
|
||||
texture: asset_server.load("player.png"),
|
||||
..default()
|
||||
},
|
||||
});
|
||||
commands.spawn((
|
||||
Player,
|
||||
Velocity { x: 10.0, y: 0.0 },
|
||||
Sprite::from_image(asset_server.load("player.png")),
|
||||
));
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user