[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASYWA86M4FDS319M9HSH43":3,"skill-same:01M7ASYWA86M4FDS319M9HSH43":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7ASYWA86M4FDS319M9HSH43","traductor-bilingue",null,"Translates technical text between English and Spanish preserving tone and format. Keeps technical terms in English when common in Spanish dev teams (deploy, pull request, pipeline, staging). Use when translating technical documentation, code comments, or team communication.","saski\u002Farnesto","saski","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F140356?v=4","01M7ASBDSNXTRYDYB4K1PEA1RV","01M7ASBDTAKBDAAV99S1GE7HK6",6,"Unlicense","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftraductor-bilingue\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: traductor-bilingue\ndescription: Translates technical text between English and Spanish preserving tone and format. Keeps technical terms in English when common in Spanish dev teams (deploy, pull request, pipeline, staging). Use when translating technical documentation, code comments, or team communication.\nallowed-tools:\n  - Read\n  - AskUserQuestion\n---\n\nSTARTER_CHARACTER = 🌐🔄\n\n# Bilingual Technical Translator\n\nTranslates technical text between English and Spanish with high fidelity, preserving tone and format.\n\n## When to Use This Skill\n\n**Use when:**\n- Translating technical documentation between English and Spanish\n- Translating code comments or commit messages\n- Adapting team communication between languages\n- User explicitly asks to translate between these two languages\n\n**Do NOT use:**\n- For languages other than English\u002FSpanish\n- For non-technical translation\n\n---\n\n## General Behavior\n\n- Ask for source and target language if not clear.\n- Conserva el formato del texto original (listas, encabezados, código, etc.).\n- Mantén nombres propios, códigos de error, nombres de funciones, clases, APIs y rutas de archivos sin traducir.\n- No expliques la traducción; devuelve solo el texto traducido salvo que el usuario pida explicación.\n- Adapta el registro:\n  - Documentación técnica, código y comentarios: estilo neutro\u002Fprofesional.\n  - Comunicación informal (chats, email coloquial): puedes usar un tono ligeramente más cercano pero correcto.\n\n## English → Spanish guidelines\n\n- Traduce a español neutro de España, salvo que el usuario pida otro dialecto.\n- **Prioriza la naturalidad y claridad técnica**: Usa términos técnicos en inglés cuando sean más claros o estén ampliamente establecidos en la comunidad de desarrollo hispanohablante.\n- Respeta terminología técnica común en desarrollo de software que se mantiene en inglés:\n  - **Términos de control de versiones**: \"pull request\", \"commit\", \"branch\", \"merge\", \"rebase\", \"cherry-pick\", \"trunk-based development\"\n  - **CI\u002FCD y DevOps**: \"pipeline\", \"build\", \"deploy\", \"deployment\", \"release\", \"rollback\", \"staging\", \"blue-green deployment\", \"canary deployment\", \"continuous delivery\", \"continuous integration\"\n  - **Arquitectura**: \"frontend\", \"backend\", \"endpoint\", \"middleware\", \"API\", \"microservices\", \"clean code\", \"SOLID\", \"DDD\"\n  - **Testing**: \"test suite\", \"unit test\", \"integration test\", \"mock\", \"stub\", \"fixture\", \"TDD\", \"BDD\"\n  - **Metodologías y Prácticas**: \"sprint\", \"backlog\", \"daily\", \"standup\", \"retrospective\", \"XP\", \"Lean\", \"Agile\", \"pair programming\", \"DevOps\"\n  - **Conceptos técnicos**: \"issue\", \"bug\", \"feature flag\", \"feature toggle\", \"tech debt\", \"refactoring\", \"code review\"\n  - **Producto y Discovery**: \"roadmap\", \"MVP\", \"discovery\", \"product-market fit\", \"feedback loop\"\n  - **Plataforma y DevEx**: \"platform\", \"DevEx\", \"self-service\", \"dark launch\"\n  - **Gestión de Flujo**: \"WIP\", \"lead time\", \"throughput\", \"bottleneck\"\n- **Regla general**: Si un término técnico en inglés es comúnmente usado en español por profesionales (como \"deploy\" en lugar de \"desplegar\"), mantenlo en inglés.\n- Puedes combinar términos técnicos en inglés con texto en español de forma natural:\n  - ✅ \"Hacer un merge del branch\"\n  - ✅ \"Crear un pull request\"\n  - ✅ \"Ejecutar el pipeline de CI\u002FCD\"\n  - ✅ \"Actualizar el backlog del sprint\"\n- Ajusta tiempos verbales para sonar natural en contexto de ingeniería:\n  - \"You should…\" → \"Deberías…\" o \"Es recomendable que…\"\n  - \"We will…\" → \"Vamos a…\" o \"Implementaremos…\"\n- Para documentación:\n  - Usa \"usted\" implícito o formulaciones impersonales (\"se recomienda\", \"hay que\", etc.)\n- Mantén el orden de los elementos en listas y tablas.\n\n## Technical terms: When to keep English vs translate\n\n**Keep in English:**\n- Terms widely used in English by Spanish-speaking developers\n- Industry-standard concepts without a natural Spanish equivalent\n- Terms where translation would reduce clarity or sound unnatural\n\n**Examples to keep in English:**\n- \"Hacer deploy\" (better than \"desplegar\" in many contexts)\n- \"Reviewear el pull request\" (common in teams)\n- \"El bug está en el backlog\" (natural mix)\n- \"Aplicar TDD y pair programming en el equipo\"\n- \"Implementar un MVP con feedback loops rápidos\"\n- \"Reducir el WIP para mejorar el throughput\"\n- \"Feature flag\", \"tech debt\", \"refactoring\", \"clean code\"\n- \"Mejorar el DevEx de la platform\"\n\n**Translate when:**\n- A clear, widely-accepted Spanish term exists\n- The translation improves readability without losing precision\n\n**Examples to translate:**\n- \"developer\" → \"desarrollador\u002Fa\"\n- \"user\" → \"usuario\u002Fa\"\n- \"team\" → \"equipo\"\n- \"code\" → \"código\"\n- \"database\" → \"base de datos\"\n\n## Spanish → English guidelines\n\n- Traducir por defecto a inglés técnico neutro orientado a software\u002Fproduct teams.\n- Usa terminología estándar de producto y desarrollo:\n  - “historia de usuario” → “user story”\n  - “requisito” → “requirement”\n  - “caso de uso” → “use case”\n  - “despliegue” → “deployment”\n  - “entorno de preproducción” → “staging environment”\n- Prefiere:\n  - “should” para recomendaciones.\n  - “must” para requisitos estrictos.\n  - “can\u002Fmay” para opciones.\n- Para documentación o tickets:\n  - Estructura frases de manera clara y directa.\n  - Evita traducciones literales que suenen poco naturales.\n\n## Handling code and inline text\n\n- No traduzcas el contenido de bloques de código, nombres de variables, funciones o clases.\n- Comentarios dentro del código:\n  - Tradúcelos si el usuario lo pide explícitamente.\n- Textos inline tipo `this.is.code()` o `\u003CTagComponent>` deben dejarse sin traducir.\n- Mantén el idioma de mensajes de error tal como esté en el original, salvo petición explícita.\n\n## Examples\n\n### Example 1: EN → ES\n\n**User:**\n\"Translate to Spanish:\n`We will deploy the new feature to the staging environment first, and then run the regression test suite.`\"\n\n**Assistant (using this skill):**\n\"Vamos a hacer deploy de la nueva feature en el entorno de staging primero y luego ejecutaremos la suite de tests de regresión.\"\n\n_Note: This translation naturally mixes technical English terms (deploy, feature, staging, tests) with Spanish structure, which is common and preferred in Spanish-speaking dev teams._\n\n### Example 2: ES → EN\n\n**User:**\n\"Traduce a inglés:\n`Necesitamos alinear este roadmap con las dependencias de otros equipos antes del próximo release.`\"\n\n**Assistant (using this skill):**\n\"We need to align this roadmap with other teams' dependencies before the next release.\"\n\n### Example 3: EN → ES (Technical documentation)\n\n**User:**\n\"Translate to Spanish:\n`Before merging your pull request, ensure all unit tests pass and the code review is approved.`\"\n\n**Assistant (using this skill):**\n\"Antes de hacer merge de tu pull request, asegúrate de que todos los unit tests pasen y que el code review esté aprobado.\"\n\n---\n\n## Response Format\n\n**If text and language pair are clear:**\n- Return only the translation.\n\n**If source\u002Ftarget language is ambiguous:**\n- Ask: “Do you want to translate from English to Spanish or from Spanish to English?”\n\n**If user requests explanation:**\n- Add a brief explanation of key vocabulary choices after the translated text.\n","STARTER_CHARACTER = 🌐🔄\n\n# Bilingual Technical Translator\n\nTranslates technical text between English and Spanish with high fidelity, preserving tone and format.\n\n## When to Use This Skill\n\n**Use when:**\n- Translating technical documentation between English and Spanish\n- Translating code comments or commit messages\n- Adapting team communication between languages\n- User explicitly asks to translate between these two languages\n\n**Do NOT use:**\n- For languages other than English\u002FSpanish\n- For non-technical translation\n\n---\n\n## General Behavior\n\n- Ask for source and target language if not clear.\n- Conserva el formato del texto original (listas, encabezados, código, etc.).\n- Mantén nombres propios, códigos de error, nombres de funciones, clases, APIs y rutas de archivos sin traducir.\n- No expliques la traducción; devuelve solo el texto traducido salvo que el usuario pida explicación.\n- Adapta el registro:\n  - Documentación técnica, código y comentarios: estilo neutro\u002Fprofesional.\n  - Comunicación informal (chats, email coloquial): puedes usar un tono ligeramente más cercano pero correcto.\n\n## English → Spanish guidelines\n\n- Traduce a español neutro de España, salvo que el usuario pida otro dialecto.\n- **Prioriza la naturalidad y claridad técnica**: Usa términos técnicos en inglés cuando sean más claros o estén ampliamente establecidos en la comunidad de desarrollo hispanohablante.\n- Respeta terminología técnica común en desarrollo de software que se mantiene en inglés:\n  - **Términos de control de versiones**: \"pull request\", \"commit\", \"branch\", \"merge\", \"rebase\", \"cherry-pick\", \"trunk-based development\"\n  - **CI\u002FCD y DevOps**: \"pipeline\", \"build\", \"deploy\", \"deployment\", \"release\", \"rollback\", \"staging\", \"blue-green deployment\", \"canary deployment\", \"continuous delivery\", \"continuous integration\"\n  - **Arquitectura**: \"frontend\", \"backend\", \"endpoint\", \"middleware\", \"API\", \"microservices\", \"clean code\", \"SOLID\", \"DDD\"\n  - **Testing**: \"test suite\", \"unit test\", \"integration test\", \"mock\", \"stub\", \"fixture\", \"TDD\", \"BDD\"\n  - **Metodologías y Prácticas**: \"sprint\", \"backlog\", \"daily\", \"standup\", \"retrospective\", \"XP\", \"Lean\", \"Agile\", \"pair programming\", \"DevOps\"\n  - **Conceptos técnicos**: \"issue\", \"bug\", \"feature flag\", \"feature toggle\", \"tech debt\", \"refactoring\", \"code review\"\n  - **Producto y Discovery**: \"roadmap\", \"MVP\", \"discovery\", \"product-market fit\", \"feedback loop\"\n  - **Plataforma y DevEx**: \"platform\", \"DevEx\", \"self-service\", \"dark launch\"\n  - **Gestión de Flujo**: \"WIP\", \"lead time\", \"throughput\", \"bottleneck\"\n- **Regla general**: Si un término técnico en inglés es comúnmente usado en español por profesionales (como \"deploy\" en lugar de \"desplegar\"), mantenlo en inglés.\n- Puedes combinar términos técnicos en inglés con texto en español de forma natural:\n  - ✅ \"Hacer un merge del branch\"\n  - ✅ \"Crear un pull request\"\n  - ✅ \"Ejecutar el pipeline de CI\u002FCD\"\n  - ✅ \"Actualizar el backlog del sprint\"\n- Ajusta tiempos verbales para sonar natural en contexto de ingeniería:\n  - \"You should…\" → \"Deberías…\" o \"Es recomendable que…\"\n  - \"We will…\" → \"Vamos a…\" o \"Implementaremos…\"\n- Para documentación:\n  - Usa \"usted\" implícito o formulaciones impersonales (\"se recomienda\", \"hay que\", etc.)\n- Mantén el orden de los elementos en listas y tablas.\n\n## Technical terms: When to keep English vs translate\n\n**Keep in English:**\n- Terms widely used in English by Spanish-speaking developers\n- Industry-standard concepts without a natural Spanish equivalent\n- Terms where translation would reduce clarity or sound unnatural\n\n**Examples to keep in English:**\n- \"Hacer deploy\" (better than \"desplegar\" in many contexts)\n- \"Reviewear el pull request\" (common in teams)\n- \"El bug está en el backlog\" (natural mix)\n- \"Aplicar TDD y pair programming en el equipo\"\n- \"Implementar un MVP con feedback loops rápidos\"\n- \"Reducir el WIP para mejorar el throughput\"\n- \"Feature flag\", \"tech debt\", \"refactoring\", \"clean code\"\n- \"Mejorar el DevEx de la platform\"\n\n**Translate when:**\n- A clear, widely-accepted Spanish term exists\n- The translation improves readability without losing precision\n\n**Examples to translate:**\n- \"developer\" → \"desarrollador\u002Fa\"\n- \"user\" → \"usuario\u002Fa\"\n- \"team\" → \"equipo\"\n- \"code\" → \"código\"\n- \"database\" → \"base de datos\"\n\n## Spanish → English guidelines\n\n- Traducir por defecto a inglés técnico neutro orientado a software\u002Fproduct teams.\n- Usa terminología estándar de producto y desarrollo:\n  - “historia de usuario” → “user story”\n  - “requisito” → “requirement”\n  - “caso de uso” → “use case”\n  - “despliegue” → “deployment”\n  - “entorno de preproducción” → “staging environment”\n- Prefiere:\n  - “should” para recomendaciones.\n  - “must” para requisitos estrictos.\n  - “can\u002Fmay” para opciones.\n- Para documentación o tickets:\n  - Estructura frases de manera clara y directa.\n  - Evita traducciones literales que suenen poco naturales.\n\n## Handling code and inline text\n\n- No traduzcas el contenido de bloques de código, nombres de variables, funciones o clases.\n- Comentarios dentro del código:\n  - Tradúcelos si el usuario lo pide explícitamente.\n- Textos inline tipo `this.is.code()` o `\u003CTagComponent>` deben dejarse sin traducir.\n- Mantén el idioma de mensajes de error tal como esté en el original, salvo petición explícita.\n\n## Examples\n\n### Example 1: EN → ES\n\n**User:**\n\"Translate to Spanish:\n`We will deploy the new feature to the staging environment first, and then run the regression test suite.`\"\n\n**Assistant (using this skill):**\n\"Vamos a hacer deploy de la nueva feature en el entorno de staging primero y luego ejecutaremos la suite de tests de regresión.\"\n\n_Note: This translation naturally mixes technical English terms (deploy, feature, staging, tests) with Spanish structure, which is common and preferred in Spanish-speaking dev teams._\n\n### Example 2: ES → EN\n\n**User:**\n\"Traduce a inglés:\n`Necesitamos alinear este roadmap con las dependencias de otros equipos antes del próximo release.`\"\n\n**Assistant (using this skill):**\n\"We need to align this roadmap with other teams' dependencies before the next release.\"\n\n### Example 3: EN → ES (Technical documentation)\n\n**User:**\n\"Translate to Spanish:\n`Before merging your pull request, ensure all unit tests pass and the code review is approved.`\"\n\n**Assistant (using this skill):**\n\"Antes de hacer merge de tu pull request, asegúrate de que todos los unit tests pasen y que el code review esté aprobado.\"\n\n---\n\n## Response Format\n\n**If text and language pair are clear:**\n- Return only the translation.\n\n**If source\u002Ftarget language is ambiguous:**\n- Ask: “Do you want to translate from English to Spanish or from Spanish to English?”\n\n**If user requests explanation:**\n- Add a brief explanation of key vocabulary choices after the translated text.\n",{"name":5,"description":7,"allowed-tools":23},[24,25],"Read","AskUserQuestion","main","3c24fc2c035029b08c7326774bee3fef8fb95566",".agents\u002Fskills\u002Ftraductor-bilingue",0,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto","https:\u002F\u002Fgithub.com\u002Fsaski","http:\u002F\u002Fsaski.com","2026-11-12 20:09:16",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add saski\u002Farnesto --skill traductor-bilingue",{"tool":40,"command":41},"bunx","bunx skills add saski\u002Farnesto --skill traductor-bilingue",{"tool":43,"command":44},"pnpm","pnpm dlx skills add saski\u002Farnesto --skill traductor-bilingue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftraductor-bilingue\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M7AT7F5FSHNAMFMF01N0QA1X","visualize","Use \u002Fvisualize for creating compact charts, diagrams, or other visuals inline as part of the conversation itself. It chooses among Markdown tables, Mermaid, inline HTML, and other supported in-transcript forms. Use Canvas for durable artifacts outside the transcript that users may revisit, refine, or share.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fvisualize\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M7AT79MHSAR3JDDMP7DGERM9","update-cursor-settings","Modify Cursor\u002FVSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cursor-settings\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M7AT73WF3Y22E0FKYAMCCJES","update-cli-config","View and modify Cursor CLI configuration settings in ~\u002F.cursor\u002Fcli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cli-config\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7AT6F3FBP85AJJ5BJNR8B5W","statusline","Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fstatusline\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7AT6D24QFS5XRAFN8S5XJ7W","split-to-prs","Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fsplit-to-prs\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7AT69FYFN84XZKW452JV5DF","shell","Runs the rest of a \u002Fshell request as a literal shell command. Use only when the user explicitly invokes \u002Fshell and wants the following text executed directly in the terminal.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fshell\u002FSKILL.md",[],[]]