CommunityProgramación y desarrollogithub.com

github/vscode-ext-localization

Directrices para la localización adecuada de extensiones de VS Code, siguiendo las pautas de desarrollo de extensiones de VS Code, bibliotecas y buenas prácticas.

¿Qué es vscode-ext-localization?

Esta habilidad proporciona directrices detalladas para localizar correctamente extensiones de VS Code, siguiendo las pautas oficiales de desarrollo de extensiones de VS Code, utilizando bibliotecas recomendadas y buenas prácticas. Es útil para desarrolladores que desean que sus extensiones sean accesibles en múltiples idiomas, mejorando la experiencia del usuario global. La habilidad se basa en la documentación del repositorio github/vscode-ext-localization y ofrece instrucciones claras sobre cómo implementar la internacionalización (i18n) y la localización (l10n) de manera eficiente. Incluye ejemplos de código, mejores prácticas para la gestión de cadenas de texto y recomendaciones sobre herramientas como vscode-nls o i18n de VS Code. Además, cubre aspectos como la detección del idioma del usuario, la organización de archivos de traducción y la integración con el flujo de trabajo de desarrollo de extensiones.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/github/awesome-copilot/tree/main/skills/vscode-ext-localization

Installed? Explore more Programación y desarrollo skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

¿Qué hace vscode-ext-localization?

Directrices para la localización adecuada de extensiones de VS Code, siguiendo las pautas de desarrollo de extensiones de VS Code, bibliotecas y buenas prácticas.

Introducción

La localización (l10n) de una extensión de VS Code permite que tu extensión se adapte a diferentes idiomas y regiones, mejorando la experiencia del usuario global. Esta guía proporciona las mejores prácticas y directrices para lograr una localización efectiva.

Configuración del entorno

Para empezar a localizar tu extensión, asegúrate de tener instalado Node.js y las dependencias necesarias. Recomendamos usar la biblioteca vscode-nls para la internacionalización (i18n).

npm install vscode-nls

Estructura de carpetas

Organiza tus archivos de localización de la siguiente manera:

package.json
src/
  extension.ts
  package.nls.json
  package.nls.es.json
  package.nls.fr.json

Uso de cadenas localizables

En tu código fuente, utiliza la función localize para marcar las cadenas que necesitan traducción.

import * as nls from 'vscode-nls';

const localize = nls.config({ messageFormat: nls.MessageFormat.file })();
const message = localize('hello', 'Hola');
console.log(message);

Archivos de traducción

Cada idioma tiene su propio archivo JSON de traducción. Por ejemplo:

package.nls.json (inglés, predeterminado)

{
  "extension.name": "Mi Extensión"
}

package.nls.es.json (español)

{
  "extension.name": "Mi Extensión"
}

Detección del idioma del usuario

VS Code detecta automáticamente el idioma del usuario según la configuración regional del editor. Puedes acceder a él con vscode.env.language.

const userLanguage = vscode.env.language;
console.log(`Idioma del usuario: ${userLanguage}`);

Mejores prácticas

  • Usa claves descriptivas: En lugar de cadenas literales, usa claves como extension.name.
  • Mantén las traducciones sincronizadas: Actualiza todos los archivos de idioma cuando agregues nuevas cadenas.
  • Prueba en diferentes idiomas: Cambia el idioma de VS Code para verificar que las traducciones se carguen correctamente.

Enlaces útiles

Contribuciones

Si encuentras errores o tienes sugerencias, por favor abre un issue en el repositorio github/vscode-ext-localization.


Esta guía sigue las mejores prácticas de la comunidad de VS Code.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

github/acquire-codebase-knowledge

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

github/add-educational-comments

Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.

github/agent-governance

Patterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)

github/agentic-eval

Patterns and techniques for evaluating and improving AI agent outputs. Use this skill when: - Implementing self-critique and reflection loops - Building evaluator-optimizer pipelines for quality-critical generation - Creating test-driven code refinement workflows - Designing rubric-based or LLM-as-judge evaluation systems - Adding iterative improvement to agent outputs (code, reports, analysis) - Measuring and improving agent response quality

github/agent-owasp-compliance

Check any AI agent codebase against the OWASP Agentic Security Initiative (ASI) Top 10 risks. Use this skill when: - Evaluating an agent system's security posture before production deployment - Running a compliance check against OWASP ASI 2026 standards - Mapping existing security controls to the 10 agentic risks - Generating a compliance report for security review or audit - Comparing agent framework security features against the standard - Any request like "is my agent OWASP compliant?", "check ASI compliance", or "agentic security audit"

github/ai-prompt-engineering-safety-review

Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content.

github/appinsights-instrumentation

Instrument a webapp to send useful telemetry data to Azure App Insights

github/apple-appstore-reviewer

Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons.

github/architecture-blueprint-generator

Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development.

github/arch-linux-triage

Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.

github/arize-ai-provider-integration

Creates, reads, updates, and deletes Arize AI integrations that store LLM provider credentials used by evaluators and other Arize features. Supports any LLM provider (e.g. OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Vertex AI, Gemini, NVIDIA NIM). Use when the user mentions AI integration, LLM provider credentials, create integration, list integrations, update credentials, delete integration, or connecting an LLM provider to Arize.

github/arize-annotation

Creates and manages annotation configs (categorical, continuous, freeform label schemas) and annotation queues (human review workflows) on Arize. Applies human annotations to project spans via the Python SDK. Use when the user mentions annotation config, annotation queue, label schema, human feedback, bulk annotate spans, update_annotations, labeling queue, annotate record, or human review.

github/arize-dataset

Creates, manages, and queries Arize datasets and examples. Covers dataset CRUD, appending examples, exporting data, and file-based dataset creation using the ax CLI. Use when the user needs test data, evaluation examples, or mentions create dataset, list datasets, export dataset, append examples, dataset version, golden dataset, or test set.

github/arize-evaluator

Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and continuous monitoring. Use when the user mentions create evaluator, LLM judge, hallucination, faithfulness, correctness, relevance, run eval, score spans, score experiment, trigger-run, column mapping, continuous monitoring, or improve evaluator prompt.

github/arize-experiment

Creates, runs, and analyzes Arize experiments for evaluating and comparing model performance. Covers experiment CRUD, exporting runs, comparing results, and evaluation workflows using the ax CLI. Use when the user mentions create experiment, run experiment, compare models, model performance, evaluate AI, experiment results, benchmark, A/B test models, or measure accuracy.

github/arize-instrumentation

Adds Arize AX tracing to an LLM application for the first time. Follows a two-phase agent-assisted flow to analyze the codebase then implement instrumentation after user confirmation. Use when the user wants to instrument their app, add tracing from scratch, set up LLM observability, integrate OpenTelemetry or openinference, or get started with Arize tracing.

github/arize-link

Generates deep links to the Arize UI for traces, spans, sessions, datasets, labeling queues, evaluators, and annotation configs. Produces clickable URLs for sharing Arize resources with team members. Use when the user wants to link to or open a trace, span, session, dataset, evaluator, or annotation config in the Arize UI.

github/arize-prompt-optimization

Optimizes, improves, and debugs LLM prompts using production trace data, evaluations, and annotations. Extracts prompts from spans, gathers performance signal, and runs a data-driven optimization loop using the ax CLI. Use when the user mentions optimize prompt, improve prompt, make AI respond better, improve output quality, prompt engineering, prompt tuning, or system prompt improvement.

github/arize-trace

Downloads, exports, and inspects existing Arize traces and spans to understand what an LLM app is doing or debug runtime issues. Covers exporting traces by ID, spans by ID, sessions by ID, and root-cause investigation using the ax CLI. Use when the user wants to look at existing trace data, see what their LLM app is doing, export traces, download spans, investigate errors, or analyze behavior regressions.

github/aspire

Aspire skill covering the Aspire CLI, AppHost orchestration, service discovery, integrations, MCP server, VS Code extension, Dev Containers, GitHub Codespaces, templates, dashboard, and deployment. Use when the user asks to create, run, debug, configure, deploy, or troubleshoot an Aspire distributed application.

Skills relacionados