tacosdedatos-seo

Translate technical content into Mexican Spanish while preserving English tool names.

5|3|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/chekos/bns-marketplace --skill tacosdedatos-seo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tacosdedatos-seo
Source: https://github.com/chekos/bns-marketplace/tree/main/tdd-growth/skills/tacosdedatos-seo
Command: npx skills add https://github.com/chekos/bns-marketplace --skill tacosdedatos-seo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps writers tailor technical content to a Mexico-first Spanish audience by preserving English tool names and aligning terminology for LATAM readers.

Core Features & Use Cases

  • Localization Guidance: Use Mexican Spanish for technical content, preserving English tool names and widely-used terms.
  • Terminology & Style Rules: Provide a Mexico-first vocabulary map and rules for when to translate vs keep English terms.
  • Hybrid Keyword Strategies: Suggest mixed-language search patterns to optimize LATAM SEO for technical topics.
  • Use Case: Craft product docs, blog posts, and tutorials for a LATAM developer audience.

Quick Start

Provide an English technical paragraph and request: Adapt this to Mexican Spanish for a LATAM developer audience, keeping tool names in English.

Frequently Asked Questions about tacosdedatos-seo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I localize technical content for Mexican Spanish without translating tool names?

To localize technical content for Mexican Spanish, you apply Mexican terminology guidelines and language tone while preserving English tool names and widely-used terms, ensuring the output reads naturally for LATAM developers.

What are hybrid keywords for LATAM SEO and when should I use them?

Hybrid keywords for LATAM SEO are mixed-language search patterns combining Spanish text with English technical terms. You use them to optimize technical content like product docs and tutorials for developers searching in both languages.

How do I write product docs and tutorials for a LATAM developer audience?

You write product docs and tutorials for a LATAM developer audience by applying a Mexico-first vocabulary map, enforcing Mexican terminology guidelines, and keeping English tool names intact to align with local developer preferences.

Does this Mexico-first Spanish localization approach work for general Latin American readers?

Yes, the Mexico-first Spanish localization approach works for general Latin American readers because it targets a broad LATAM developer audience, using Mexican terminology as a baseline while preserving English terms common across the region.

When should I keep English terms versus translating to Mexican Spanish in technical blog posts?

You keep English terms in technical blog posts when they are tool names or widely-used developer terms, and translate to Mexican Spanish for general vocabulary, following terminology rules that distinguish necessary English from translatable text.