Translate logo

Translate

Organization
ai-driven-dev
translate

Builds the canonical-source-to-target-native translation pipeline under src/contexts/translate/ — target-aware content transforms, the plugin content translator, and the build strategies behind `aidd translate` and `aidd sync`. Use when adding a target-aware transform, changing `PluginContentTranslator`, adding a build strategy, or wiring a new tool into the build registry. Do NOT use for a tool's own profile, capability classes, or build contract — use `tools`. Do NOT use for where content is fetched from — use `distribution`. Do NOT use for manifest/install orchestration — use `framework`.

Overview

Publisherai-driven-dev
Repositoryframework
Skill nametranslate
Stars
515
Forks
54
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by ai-driven-dev on GitHub. Read the source before you install it.

Installation

Install the Translate AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/ai-driven-dev/framework/tree/main/cli/.claude/skills/translate
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/ai-driven-dev/framework.git /tmp/framework
mkdir -p .claude/skills
cp -r /tmp/framework/cli/.claude/skills/translate .claude/skills/translate
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Translate in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Translate on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Translate is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Translate

translate is the core: it turns the canonical, Claude-format framework source into target-native content for every tool at once. It reaches two places and no others: tools, its one outbound context edge, and kernel. Everything it reaches in tools is that context's declared public surface (contracts.ts, registry.ts, build-contract.ts, and the handful of capability and port modules listed as public), never an internal file. The whole graph is in .claude/rules/00-architecture/0-contexts.md.

What goes in

ConceptLocation
A transform whose behavior differs by target tooldomain/formats/
The plugin-files-to-installed-files translatordomain/content-translator.ts (PluginContentTranslator)
The canonical framework-doc shapedomain/canon.ts
The canonical single-plugin shapedomain/plugin-distribution.ts
Build targets and modesdomain/build-target.ts
The aidd translate use-caseapplication/translate-source.ts (FrameworkBuildUseCase)
A build orchestrator (one per mode, never per tool)application/strategies/
Schema validation for marketplace/plugin manifestsinfrastructure/schema-validator.ts

A transform used by exactly one tool profile does not belong here — it lives in that profile's own directory. A transform shared by ≥2 profiles but identical regardless of target lives in contexts/tools/domain/formats/ instead. What belongs in translate/domain/formats/ is a transform that is aware of which target it is producing for.

How

  • PluginContentTranslator takes one plugin's canonical files and one tool's AiTool<C>, and calls the tool's own rewriteContent — it does not reimplement a tool's rewrite logic, it invokes what tools declared. That function is one-way and has no inverse; the tools skill's references/content-rewrite.md says why, and names the trap an identity rewrite sets.
  • FrameworkBuildUseCase (aidd translate) reads a ToolBuildContract per target and mode from tools, and dispatches to MarketplaceBuildStrategy or FlatBuildStrategy — both implement BuildOutputStrategy and iterate the six artifact kinds generically, with zero per-tool or per-kind branching. Adding a build target means the target tool declares a contract in tools; it never means adding a case here. See the tools skill's references/build-contract.md.
  • runtime/wiring/translate.ts derives the "<target>:<mode>" build registry by iterating every registered tool and reading its contract — there is no hand-maintained per-tool row.
  • Follow the use-case and orchestration rules in .claude/rules/00-architecture/ for the application layer's shape, and the shared-module rule there before promoting a helper used by only one strategy into shared-plugin-helpers.ts.

Public surface

Nothing outside contexts/translate/ may import a module this context has not declared public — tests/architecture/context-boundary.arch.test.ts holds the list (PUBLIC_MODULES.translate). framework is the only context that imports from here (framework → translate); a module used by framework must be on that list.

How it's tested

  • tests/contexts/translate/ mirrors src/contexts/translate/ — formats, content-translator, canon, and the two build strategies each have unit or integration coverage.
  • tests/golden/framework-build-golden.e2e.test.ts snapshots a full build across every target — see test skill's golden/machine-independence rules before touching a snapshot.
  • A new target-aware transform gets a unit test over a representative input carrying the marker it is meant to rewrite. A transform that is the identity for the fixture it was given is indistinguishable from one that never ran.

Frequently asked questions

What does the Translate AI skill do?

Builds the canonical-source-to-target-native translation pipeline under src/contexts/translate/ — target-aware content transforms, the plugin content translator, and the build strategies behind `aidd translate` and `aidd sync`. Use when adding a target-aware transform, changing `PluginContentTranslator`, adding a build strategy, or wiring a new tool into the build registry. Do NOT use for a tool's own profile, capability classes, or build contract — use `tools`. Do NOT use for where content is fetched from — use `distribution`. Do NOT use for manifest/install orchestration — use `framework`.

Why use Translate on TypingMind?

Because you install it once and use it with any model. Translate is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Translate in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ai-driven-dev/framework/tree/main/cli/.claude/skills/translate. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Translate?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Translate?

As many as you like. As long as a model supports skills, you can use Translate with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Translate AI skill free?

Yes. It is published on GitHub by ai-driven-dev under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇