https://www.langcapture.com/assets/page-C_C0NqVr.js

1import{w as x,u as C,L as i}from"./chunk-OE4NN4TA-DqYUKxp0.js";import{j as e}from"./index-CFGUo14Y.js";import{i as L,d as h,w as d}from"./index-Cx3_vZob.js";import{u as m}from"./route-copy-BBvEl0x4.js";import{l as w}from"./langcapture-bS0KsRYa.js";import{M as j,L as q}from"./marketing-mobile-nav-dxhbojKt.js";import{b as T}from"./seo-BCpTxPUO.js";import"./organization-BdJSRNgM-CtZF8fwV.js";import"./index-nCYghxO-.js";import{A as k}from"./arrow-right-DbfsCUAS.js";import{c as I}from"./createLucideIcon-BH03jWmn.js";import"./index-C4PTjBNg.js";import"./x-CD7cYJWY.js";import"./preload-helper-BXl3LOEh.js";const _=[["path",{d:"M8 2v4",key:"1cmpym"}],["path",{d:"M16 2v4",key:"4m81vk"}],["rect",{width:"18",height:"18",x:"3",y:"4",rx:"2",key:"1hopcy"}],["path",{d:"M3 10h18",key:"8toen8"}]],S=I("calendar",_),P=`---
2name: LangCapture
3avatar: /images/avatars/langcapture.png
4description: The LangCapture Team
5---
6`,A=`---
7name: LangCapture
8avatar: /images/avatars/langcapture.png
9description: LangCapture 团队
10---
11`,z=`---
12title: "Cómo capturar frases útiles de GitHub, Slack, Jira y el correo"
13description: "Una guía práctica para construir una biblioteca reutilizable de frases inglés-español a partir de las herramientas que tu equipo ya usa, incluyendo captura desde el navegador, traducciones, audio y tokens de API."
14image: /og.png
15date: "2026-03-14"
16published: true
17categories: [capture-workflows]
18author: langcapture
19---
20
21La forma más rápida de construir una biblioteca de lenguaje útil no es abrir una app de estudio.
22
23Es capturar frases desde las herramientas donde tu trabajo real ya ocurre.
24
25Para equipos que trabajan entre dos idiomas, eso normalmente significa GitHub, Slack o Teams, Jira o Confluence, Notion, documentación interna y correo electrónico. Estos lugares están llenos de comunicación matizada entre idiomas que de verdad vale la pena revisar después.
26

27LangCapture está diseñado exactamente para este flujo de trabajo.
28
29## ¿Qué frases vale la pena capturar?
30
31No toda línea merece un lugar en tu biblioteca de frases. Las mejores candidatas suelen compartir un rasgo: resolvieron bien un problema real de comunicación.
32
33Buenos ejemplos incluyen:
34
35- un comentario de PR que expresa desacuerdo sin sonar defensivo
36- una actualización de Jira que es clara sobre el riesgo y los siguientes pasos
37- una respuesta de Slack que equilibra rapidez con cortesía
38- una frase de correo que establece expectativas con claridad
39- una actualización de estado en otro idioma que quieres reutilizar después
40
41Si una frase te hace pensar "ojalá pudiera volver a usar esa formulación", probablemente vale la pena guardarla.
42
43## Flujo 1: pegar directamente en LangCapture
44
45El flujo más simple sigue siendo el más rápido para muchos usuarios:
46
471. Copia una frase en cualquier idioma desde tu herramienta preferida.
482. Pégala en LangCapture.
493. Guarda el texto original con la dirección de traducción correcta.
504. Repasa la traducción guardada más tarde, o reprodúcela con TTS cuando lo necesites.
51
52Esto funciona bien cuando ya estás en la app web o cuando quieres guardar una frase justo después de leerla.
53
54Puedes probar ese flujo desde la [página de captura](/sentences/capture).
55
56## Flujo 2: usar la extensión de Chrome
57
58Cuando no quieres salir de la página en la que estás, la extensión de Chrome es la mejor opción.
59
60El flujo es directo:
61
621. Resalta la frase en GitHub, Slack, Jira, Confluence, el correo u otra página.
632. Activa LangCapture desde la extensión o el menú contextual.
643. Envía la frase directamente a tu espacio de trabajo.
654. Abre la tarjeta guardada más tarde para repasar la traducción o reproducir el audio.
66
67Esto es especialmente útil para la comunicación asíncrona porque la fricción se mantiene baja. No necesitas romper tu concentración solo para preservar una buena frase.
68
69## Sesiones o tokens de API
70
71LangCapture admite dos rutas prácticas de autenticación para la captura:
72
73- mantenerte conectado con tu sesión web normal
74- usar un token de acceso personal para la extensión del navegador u otras integraciones sin interfaz
75
76Ese flujo basado en tokens importa porque la captura real no siempre ocurre dentro de la pestaña principal de la app. A veces ocurre en una extensión del navegador. A veces, en una herramienta interna. A veces quieres publicar directamente en la API de frases.
77
78Si estás configurando la extensión, visita la [configuración de tokens de API](/settings/tokens).
79
80## Qué pasa después de guardar una frase
81
82El valor no está solo en obtener una traducción instantánea una vez. El valor está en poder volver más tarde.
83
84Después de la captura, LangCapture mantiene el flujo enfocado:
85
86- la frase original permanece intacta
87- la traducción se guarda hacia tu idioma nativo
88- la frase puede reproducirse con TTS cuando quieras escucharla
89- el elemento guardado vive en tu biblioteca para repasarlo después
90
91Eso hace que el producto sea útil tanto para la comprensión inmediata como para la reutilización a largo plazo.
92
93## Por qué esto funciona mejor que las notas sueltas
94
95Mucha gente ya colecciona líneas útiles, pero su sistema es frágil:
96
97- las capturas de pantalla desaparecen
98- las estrellas y los marcadores se vuelven ruido
99- las notas dispersas pierden la frase original o la dirección de traducción
100
101LangCapture resuelve esto al convertir la captura de frases en un flujo de trabajo repetible en lugar de un hábito improvisado.
102
103También ayuda a proteger la privacidad redactando los detalles sensibles cuando es necesario, de modo que la frase que conservas trata sobre el patrón de comunicación, no sobre los datos confidenciales que la rodean.
104
105## Ejemplos por herramienta
106
107Así puede verse una captura útil en la práctica.
108
109### GitHub
110
111Guarda comentarios de revisión que modelan un buen tono de ingeniería:
112
113> I think the implementation is heading in the right direction, but I am still worried about the migration path.
114
115### Slack o Teams
116
117Conserva respuestas cortas que son calmadas y claras bajo presión de tiempo:
118
119> I can take the first pass today, but I may need help validating the edge cases.
120
121### Jira o Confluence
122
123Captura actualizaciones de estado y lenguaje de compromisos:
124
125> We can ship the smaller version first if we want to reduce risk before the full rollout.
126
127### Correo electrónico
128

129Guarda líneas que manejan bien el alineamiento:
130
131> I want to make sure we agree on the scope before we commit to the timeline externally.
132
133## Construye una biblioteca alrededor de tu trabajo real
134
135El objetivo de LangCapture no es darte más contenido para consumir. Es ayudarte a preservar el mejor lenguaje que tu trabajo ya produce.
136
137Si quieres la historia general del producto, lee [Convierte el lenguaje real de tu trabajo en tu biblioteca personal de aprendizaje](/blog/introducing-langcapture).
138
139Si quieres el argumento de aprendizaje más amplio, lee [Deja de memorizar plantillas: construye una biblioteca real de frases de trabajo](/blog/stop-memorizing-templates-build-a-real-workplace-sentence-library-instead).
140
141Luego empieza con una frase de GitHub, Slack, Jira o el correo, y guárdala mientras aún está fresca.
142
143Puedes comenzar desde la [página de captura](/sentences/capture) o volver a la [página principal](/) para ver el flujo completo.
144`,E=`---
145title: "GitHub・Slack・Jira・メールから「使える英文」をキャプチャする方法"
146description: "チームが日常的に使っているツールから英日対訳の文ライブラリを構築する実践ガイド。ブラウザでのキャプチャ、翻訳、音声再生、API トークンの設定まで解説します。"
147image: /og.png
148date: "2026-03-14"
149published: true
150categories: [capture-workflows]
151author: langcapture
152---
153
154役に立つ語学ライブラリを最速で作る方法は、学習アプリを開くことではありません。
155
156実際の仕事がすでに行われているツールの中から、文をキャプチャすることです。
157
158多言語環境で働くチームにとって、それは多くの場合 GitHub、Slack や Teams、Jira や Confluence、Notion、社内ドキュメント、そしてメールです。こうした場所には、後から見返す価値のある、ニュアンスに富んだクロスランゲージのコミュニケーションがあふれています。
159
160LangCapture は、まさにこのワークフローのために設計されています。
161
162## どんな文をキャプチャすべきか？
163
164すべての文がライブラリに入れる価値を持つわけではありません。最良の候補にはたいてい共通点があります。それは「現実のコミュニケーション課題をうまく解決した文」だということです。
165
166良い例としては、
167
168- 防御的に聞こえることなく異論を伝えた PR コメント
169- リスクと次のステップが明確な Jira の更新
170- スピードと丁寧さを両立させた Slack の返信
171- 期待値をすっきり設定したメールの一文
172- 後で再利用したい外国語のステータス報告
173
174「この言い回し、また使いたい」と思った文なら、保存する価値はほぼ間違いなくあります。
175
176## ワークフロー 1：LangCapture に直接貼り付ける
177
178最もシンプルなワークフローは、今でも多くのユーザーにとって最速の方法です。
179
1801. 任意のツールから文をコピーする。
1812. LangCapture に貼り付ける。

1823. 適切な翻訳方向を指定して原文を保存する。
1834. 保存した訳を後から復習したり、必要なときに TTS で再生したりする。
184
185すでに Web アプリを開いているときや、読んだ直後にすぐ保存したいときに便利です。
186
187このフローは[キャプチャページ](/sentences/capture)から試せます。
188
189## ワークフロー 2：Chrome 拡張機能を使う
190
191今見ているページから離れたくないときは、Chrome 拡張機能のほうが適しています。
192
193手順はシンプルです。
194
1951. GitHub、Slack、Jira、Confluence、メールなどのページ上で文をハイライトする。
1962. 拡張機能またはコンテキストメニューから LangCapture を起動する。
1973. 文を直接ワークスペースに送信する。
1984. 保存されたカードを後から開き、訳を確認したり音声を再生したりする。
199
200摩擦が少ないので、非同期コミュニケーションの場面で特に役立ちます。良い一文を残すためだけに集中を切らす必要はありません。
201
202## セッション認証か API トークンか
203
204LangCapture は、キャプチャのために 2 つの実用的な認証方式をサポートしています。
205
206- 通常の Web セッションでログインしたまま使う
207- ブラウザ拡張機能やヘッドレスな連携にはパーソナルアクセストークンを使う
208
209トークンベースのフローが重要なのは、実際のキャプチャがいつもメインのアプリのタブの中で起きるとは限らないからです。ブラウザ拡張機能の中で起きることもあれば、社内ツールの中で起きることもあります。文の API に直接 POST したいこともあるでしょう。
210
211拡張機能をセットアップするなら、[API トークン設定](/settings/tokens)にアクセスしてください。
212
213## 文を保存した後に何が起きるか
214
215価値があるのは、一度だけ即時翻訳を得られることではありません。後から戻ってこられることにこそ価値があります。
216
217キャプチャ後も、LangCapture のワークフローはぶれません。
218
219- 原文はそのまま保持される

220- 訳はあなたの母語方向で保存される
221- 音声が欲しいときは TTS で再生できる
222- 保存した項目はライブラリに残り、いつでも復習できる
223
224だからこそ、その場での理解にも、長期的な再利用にも役立つプロダクトになっています。
225
226## なぜ「バラバラのメモ」より優れているのか
227
228便利な一文を集めている人はすでに多いのですが、その仕組みはたいてい脆いものです。
229
230- スクリーンショットは行方不明になる
231- スターやブックマークはノイズだらけになる
232- 散らばったメモは原文や翻訳方向を失う
233
234LangCapture は、文のキャプチャを「その場しのぎの習慣」ではなく「繰り返せるワークフロー」にすることで、この問題を解決します。
235
236また、必要に応じて機密情報をマスキングしてプライバシーを守るので、手元に残るのは周辺の機密データではなく、コミュニケーションのパターンそのものです。
237
238## ツール別の実例
239
240実際のキャプチャがどのようなものか、ツール別に見てみましょう。
241
242### GitHub
243
244優れたエンジニアリングのトーンを体現したレビューコメントを保存します。
245
246> I think the implementation is heading in the right direction, but I am still worried about the migration path.
247
248### Slack や Teams
249
250時間に追われる中でも落ち着きと明確さを保った短い返信を残します。
251
252> I can take the first pass today, but I may need help validating the edge cases.
253
254### Jira や Confluence
255
256ステータス更新やトレードオフを語る表現をキャプチャします。
257
258> We can ship the smaller version first if we want to reduce risk before the full rollout.
259
260### メール
261
262合意形成をうまく扱う一文を保存します。
263
264> I want to make sure we agree on the scope before we commit to the timeline externally.
265
266## 実際の仕事を中心にライブラリを育てる
267
268LangCapture の目的は、消費すべきコンテンツを増やすことではありません。あなたの仕事がすでに生み出している最良の言葉を残す手助けをすることです。
269
270プロダクト全体のストーリーを知りたい方は、[職場のリアルな英語を、自分だけの学習ライブラリに変えよう](/blog/introducing-langcapture)をお読みください。
271
272学習方法そのものの議論に興味がある方は、[テンプレートの暗記はやめよう：本物の職場フレーズライブラリを作る](/blog/stop-memorizing-templates-build-a-real-workplace-sentence-library-instead)をどうぞ。
273
274そして、GitHub、Slack、Jira、メールから 1 つの文を選んで、記憶が新しいうちに保存してみてください。
275
276[キャプチャページ](/sentences/capture)から始めることも、[ホームページ](/)に戻ってワークフロー全体を確認することもできます。
277`,N=`---
278title: "GitHub, Slack, Jira, 이메일에서 쓸모 있는 문장을 캡처하는 방법"
279description: "팀이 이미 쓰고 있는 도구에서 재사용 가능한 영한 대역 문장 라이브러리를 만드는 실전 가이드. 브라우저 캡처, 번역, 오디오, API 토큰까지 다룹니다."
280image: /og.png
281date: "2026-03-14"
282published: true
283categories: [capture-workflows]
284author: langcapture
285---
286
287쓸모 있는 언어 라이브러리를 가장 빨리 만드는 방법은 학습 앱을 여는 것이 아닙니다.
288
289실제 업무가 이미 일어나고 있는 도구에서 문장을 캡처하는 것입니다.
290
291영어와 한국어를 오가며 일하는 팀이라면 보통 GitHub, Slack 또는 Teams, Jira 또는 Confluence, Notion, 사내 문서, 이메일이 그 무대입니다. 이런 곳에는 나중에 다시 꺼내 볼 가치가 있는, 뉘앙스가 살아 있는 언어 간 커뮤니케이션이 가득합니다.
292
293LangCapture는 바로 이 워크플로를 위해 설계되었습니다.
294
295## 어떤 문장을 캡처할 가치가 있을까요?
296
297모든 문장이 라이브러리에 들어갈 자격이 있는 것은 아닙니다. 좋은 후보에는 보통 한 가지 공통점이 있습니다: 실제 커뮤니케이션 문제를 잘 해결했다는 점입니다.
298
299좋은 예는 다음과 같습니다:
300
301- 방어적으로 들리지 않으면서 반대 의견을 내는 PR 코멘트
302- 리스크와 다음 단계를 명확히 밝힌 Jira 업데이트
303- 속도와 정중함의 균형을 잡은 Slack 답글
304- 기대치를 깔끔하게 정리한 이메일 문장
305- 나중에 재사용하고 싶은 다른 언어로 된 상태 업데이트
306
307"이 표현, 나도 다시 쓰고 싶다"는 생각이 드는 문장이라면 저장할 가치가 충분합니다.
308
309## 워크플로 1: LangCapture에 바로 붙여넣기
310
311가장 단순한 워크플로가 여전히 많은 사용자에게 가장 빠른 방법입니다:
312

3131. 사용 중인 도구에서 어떤 언어로든 문장을 복사합니다.
3142. LangCapture에 붙여넣습니다.
3153. 알맞은 번역 방향으로 원문을 저장합니다.
3164. 저장된 번역을 나중에 복습하거나, 필요할 때 TTS로 다시 들어 봅니다.
317
318웹 앱을 이미 열어 두었거나, 문장을 읽은 직후 바로 저장하고 싶을 때 잘 맞는 방식입니다.
319
320이 흐름은 [캡처 페이지](/sentences/capture)에서 바로 시도해 볼 수 있습니다.
321
322## 워크플로 2: Chrome 확장 프로그램 사용하기
323
324지금 보고 있는 페이지를 떠나고 싶지 않다면 Chrome 확장 프로그램이 더 나은 선택입니다.
325
326워크플로는 간단합니다:
327
3281. GitHub, Slack, Jira, Confluence, 이메일 등 어떤 페이지에서든 문장을 드래그합니다.
3292. 확장 프로그램 또는 컨텍스트 메뉴에서 LangCapture를 실행합니다.
3303. 문장을 워크스페이스로 바로 전송합니다.
3314. 나중에 저장된 카드를 열어 번역을 확인하거나 오디오를 재생합니다.
332
333마찰이 거의 없기 때문에 비동기 커뮤니케이션 환경에서 특히 유용합니다. 좋은 문장 하나를 남기려고 집중을 깰 필요가 없습니다.
334
335## 세션 또는 API 토큰
336
337LangCapture는 캡처를 위해 두 가지 실용적인 인증 방식을 지원합니다:
338
339- 평소처럼 웹 세션에 로그인한 상태 유지
340- 브라우저 확장 프로그램이나 기타 헤드리스 연동을 위한 개인 액세스 토큰 사용
341
342토큰 기반 흐름이 중요한 이유는, 실제 캡처가 항상 메인 앱 탭 안에서만 일어나지는 않기 때문입니다. 때로는 브라우저 확장 프로그램에서, 때로는 사내 도구에서 일어납니다. 문장 API로 직접 전송하고 싶을 때도 있습니다.
343
344확장 프로그램을 설정하려면 [API 토큰 설정](/settings/tokens)을 방문하세요.
345
346## 문장을 저장한 뒤에는 어떻게 되나요
347
348가치는 즉석 번역을 한 번 받는 데서 끝나지 않습니다. 나중에 다시 돌아올 수 있다는 데 진짜 가치가 있습니다.
349
350캡처 후에도 LangCapture는 워크플로를 깔끔하게 유지합니다:
351
352- 원문은 그대로 보존됩니다
353- 번역은 모국어 방향으로 저장됩니다
354- 오디오가 필요할 때 TTS로 문장을 다시 들을 수 있습니다
355- 저장된 항목은 라이브러리에 남아 언제든 복습할 수 있습니다
356
357덕분에 당장의 이해와 장기적인 재사용 모두에 유용한 제품이 됩니다.
358
359## 흩어진 메모보다 나은 이유
360
361쓸모 있는 문장을 모으는 사람은 이미 많지만, 그 시스템은 대부분 허술합니다:
362
363- 스크린샷은 사라지고
364- 별표와 북마크는 점점 소음이 되며
365- 흩어진 메모는 원문이나 번역 방향을 잃어버립니다
366
367LangCapture는 문장 캡처를 즉흥적인 습관이 아니라 반복 가능한 워크플로로 만들어 이 문제를 해결합니다.
368
369또한 필요할 때 민감한 정보를 가려 프라이버시를 보호하므로, 저장되는 것은 기밀 데이터가 아니라 커뮤니케이션 패턴 그 자체입니다.
370
371## 도구별 예시
372
373실전에서 유용한 캡처가 어떤 모습인지 보여 드리겠습니다.
374
375### GitHub
376
377탄탄한 엔지니어링 톤을 보여 주는 리뷰 코멘트를 저장하세요:
378
379> I think the implementation is heading in the right direction, but I am still worried about the migration path.
380
381### Slack 또는 Teams
382
383시간 압박 속에서도 차분하고 명확한 짧은 답글을 보관하세요:
384
385> I can take the first pass today, but I may need help validating the edge cases.
386
387### Jira 또는 Confluence
388
389상태 업데이트와 트레이드오프 표현을 캡처하세요:
390
391> We can ship the smaller version first if we want to reduce risk before the full rollout.
392
393### 이메일
394
395합의를 잘 이끌어 내는 문장을 저장하세요:
396
397> I want to make sure we agree on the scope before we commit to the timeline externally.
398
399## 실제 업무를 중심으로 라이브러리를 만드세요
400
401LangCapture의 목적은 소비할 콘텐츠를 더 늘리는 것이 아닙니다. 여러분의 업무가 이미 만들어 내고 있는 최고의 언어를 보존하도록 돕는 것입니다.
402
403제품의 큰 그림이 궁금하다면 [실제 업무 속 언어를 나만의 학습 라이브러리로](/blog/introducing-langcapture)를 읽어 보세요.
404
405더 넓은 학습 관점의 이야기가 궁금하다면 [템플릿 암기는 그만: 진

405짜 업무 문장 라이브러리를 만드세요](/blog/stop-memorizing-templates-build-a-real-workplace-sentence-library-instead)를 읽어 보세요.
406
407그리고 GitHub, Slack, Jira, 이메일에서 만난 문장 하나로 시작해, 기억이 생생할 때 바로 저장하세요.
408
409[캡처 페이지](/sentences/capture)에서 시작하거나, [홈페이지](/)로 돌아가 전체 워크플로를 살펴볼 수 있습니다.
410`,U=`---
411title: "How to Capture Useful Sentences from GitHub, Slack, Jira, and Email"
412description: "A practical guide to building a reusable bilingual sentence library from the tools your team already uses, including browser capture, translations, audio, and API tokens."
413image: /og.png
414date: "2026-03-14"
415published: true
416categories: [capture-workflows]
417author: langcapture
418---
419
420The fastest way to build a useful language library is not to open a study app.
421
422It is to capture sentences from the tools where your real work already happens.
423
424For bilingual teams, that usually means GitHub, Slack or Teams, Jira or Confluence, Notion, internal docs, and email. The

424se places are full of nuanced cross-language communication that is actually worth revisiting later.
425
426LangCapture is designed for exactly this workflow.
427
428## Which Sentences Are Worth Capturing?
429
430Not every line deserves a place in your sentence library. The best candidates usually share one trait: they solved a real communication problem well.
431
432Good examples include:
433
434- a PR comment that disagrees without sounding defensive
435- a Jira update that is clear about risk and next steps
436- a Slack reply that balances speed with politeness
437- an email sentence that sets expectations cleanly
438- a status update in another language you want to reuse later
439
440If a sentence makes you think "I wish I could use that phrasing again," it is probably worth saving.
441
442## Workflow 1: Paste Directly into LangCapture
443
444The simplest workflow is still the fastest one for many users:
445
4461. Copy a sentence in any language from your tool of choice.
4472. Paste it into LangCapture.
4483. Save the original text with the right translation direction.
4494. Review the saved translation later, or replay it with TTS when needed.
450
451This works well when you are already in the web app or when you want to save a sentence immediately after reading it.
452
453You can try that flow from the [capture page](/sentences/capture).
454
455## Workflow 2: Use the Chrome Extension
456
457When you do not want to leave the page you are on, the Chrome extension is the better option.
458
459The workflow is straightforward:
460
4611. Highlight the sentence on GitHub, Slack, Jira, Confluence, email, or another page.
4622. Trigger LangCapture from the extension or context menu.
4633. Send the sentence directly into your workspace.
4644. Open the saved card later to review the translation or play audio.
465
466This is especially useful for async communication because the friction stays low. You do not need to break focus just to preserve one good sentence.
467
468## Sessions or API Tokens
469
470LangCapture supports two practical authentication paths for capture:
471
472- stay signed in with your normal web session
473- use a personal access token for the browser extension or other headless integrations
474
475That token-based flow matters because real capture does not always happen inside the main app tab. Sometimes it happens in a browser extension. Sometimes it happens in an internal tool. Sometimes you want to post directly to the sentence API.
476
477If you are setting up the extension, visit [API token settings](/settings/tokens).
478
479## What Happens After You Save a Sentence
480
481The value is not just in getting an instant translation once. The value is in being able to come back later.
482
483After capture, LangCapture keeps the workflow focused:
484
485- the original sentence stays intact
486- the translation is saved in your native language direction
487- the sentence can be replayed with TTS when you want audio
488- the saved item lives in your library for later review
489
490That makes the product useful for both immediate understanding and long-term reuse.
491
492## Why This Works Better Than Random Notes
493
494Many people already collect useful lines, but their system is fragile:
495
496- screenshots disappear
497- stars and bookmarks become noisy
498- scattered notes lose the original sentence or translation direction
499
500LangCapture solves this by making sentence capture a repeatable workflow instead of an improvised habit.
501
502It also helps protect privacy by redacting sensitive details when needed, so the sentence you keep is about the communication pattern, not the confidential data around it.
503
504## Examples by Tool
505
506Here is what useful capture can look like in practice.
507
508### GitHub
509
510Save review comments that model strong engineering tone:
511
512> I think the implementation is heading in the right direction, but I am still worried about the migration path.
513
514### Slack or Teams
515
516Keep short replies that are calm and clear under time pressure:
517
518> I can take the first pass today, but I may need help validating the edge cases.
519
520### Jira or Confluence
521
522Capture status updates and tradeoff language:
523
524> We can ship the smaller version first if we want to reduce risk before the full rollout.
525
526### Email
527
528Save lines that handle alignment well:
529
530> I want to make sure we agree on the scope before we commit to the timeline externally.
531
532## Build a Library Around Your Real Work
533
534The point of LangCapture is not to give you more content to consume. It is to help you preserve the best language your work already produces.
535
536If you want the higher-level product story, read [Turn Real Workplace Language into Your Personal Learning Library](/blog/introducing-langcapture).
537
538If you want the broader learning argument, read [Stop Memorizing Templates: Build a Real Workplace Sentence Library Instead](/blog/stop-memorizing-templates-build-a-real-workplace-sentence-library-instead).
539
540Then start with one sentence from GitHub, Slack, Jira, or email, and save it while it is still fresh.
541
542You can begin from the [capture page](/sentences/capture) or go back to the [homepage](/) for the full workflow.
543`,W=`---
544title: "Como capturar frases úteis do GitHub, Slack, Jira e e-mail"
545description: "Um guia prático para construir uma biblioteca reutilizável de frases em inglês e português a partir das ferramentas que sua equipe já usa, incluindo captura no navegador, traduções, áudio e tokens de API."
546image: /og.png
547date: "2026-03-14"
548published: true
549categories: [capture-workflows]
550author: langcapture
551---
552
553A forma mais rápida de construir uma biblioteca de idiomas útil não é abrir um app de estudos.
554
555É capturar frases das ferramentas onde o seu trabalho de verdade já acontece.
556
557Para equipes bilíngues, isso geralmente significa GitHub, Slack ou Teams, Jira ou Confluence, Notion, documentação interna e e-mail. Esses lugares estão cheios de comunicação cheia de nuances entre idiomas que realmente vale a pena revisitar depois.
558
559O LangCapture foi projetado exatamente para esse fluxo de trabalho.
560
561## Quais frases valem a pena capturar?
562
563Nem toda linha merece um lugar na sua biblioteca de frases. As melhores candidatas costumam compartilhar uma característica: elas resolveram bem um problema real de comunicação.
564
565Bons exemplos incluem:
566

567- um comentário de PR que discorda sem soar defensivo
568- uma atualização no Jira que deixa claros o risco e os próximos passos
569- uma resposta no Slack que equilibra rapidez com educação
570- uma frase de e-mail que alinha expectativas com clareza
571- um status update em outro idioma que você quer reutilizar depois
572
573Se uma frase faz você pensar "queria poder usar essa formulação de novo", provavelmente vale a pena salvá-la.
574
575## Fluxo 1: cole diretamente no LangCapture
576
577O fluxo mais simples ainda é o mais rápido para muita gente:
578
5791. Copie uma frase em qualquer idioma da ferramenta da sua preferência.
5802. Cole no LangCapture.
5813. Salve o texto original com a direção de tradução correta.
5824. Revise a tradução salva depois, ou reproduza com TTS quando precisar.
583
584Isso funciona bem quando você já está no app web ou quando quer salvar uma frase logo depois de lê-la.
585
586Você pode experimentar esse fluxo na [página de captura](/sentences/capture).
587
588## Fluxo 2: use a extensão do Chrome
589
590Quando você não quer sair da página em que está, a extensão do Chrome é a melhor opção.
591
592O fluxo é direto:
593
5941. Selecione a frase no GitHub, Slack, Jira, Confluence, e-mail ou em outra página.
5952. Acione o LangCapture pela extensão ou pelo menu de contexto.
5963. Envie a frase diretamente para o seu workspace.
5974. Abra o card salvo depois para revisar a tradução ou ouvir o áudio.
598
599Isso é especialmente útil para comunicação assíncrona, porque o atrito continua baixo. Você não precisa quebrar o foco só para preservar uma boa frase.
600
601## Sessões ou tokens de API
602
603O LangCapture oferece dois caminhos práticos de autenticação para a captura:
604
605- continuar conectado com a sua sessão web normal
606- usar um token de acesso pessoal para a extensão do navegador ou outras integrações headless
607
608Esse fluxo baseado em token importa porque a captura real nem sempre acontece na aba principal do app. Às vezes acontece em uma extensão do navegador. Às vezes acontece em uma ferramenta interna. Às vezes você quer postar diretamente na API de frases.
609
610Se você está configurando a extensão, acesse as [configurações de token de API](/settings/tokens).
611
612## O que acontece depois que você salva uma frase
613
614O valor não está apenas em receber uma tradução instantânea uma única vez. O valor está em poder voltar depois.
615
616Após a captura, o LangCapture mantém o fluxo focado:
617
618- a frase original permanece intacta
619- a tradução é salva na direção do seu idioma nativo
620- a frase pode ser reproduzida com TTS quando você quiser ouvir
621- o item salvo fica na sua biblioteca para revisão posterior
622
623Isso torna o produto útil tanto para compreensão imediata quanto para reutilização no longo prazo.
624
625## Por que isso funciona melhor do que anotações soltas
626
627Muita gente já coleciona linhas úteis, mas o sistema é frágil:
628
629- capturas de tela somem
630- estrelas e favoritos viram ruído
631- anotações espalhadas perdem a frase original ou a direção da tradução
632
633O LangCapture resolve isso transformando a captura de frases em um fluxo repetível, em vez de um hábito improvisado.
634
635Ele também ajuda a proteger a privacidade ao ocultar detalhes sensíveis quando necessário, para que a frase que você guarda seja sobre o padrão de comunicação, e não sobre os dados confidenciais ao redor dela.
636
637## Exemplos por ferramenta
638
639Veja como uma captura útil pode ser na prática.
640
641### GitHub
642
643Salve comentários de review que modelam um bom tom de engenharia:
644
645> I think the implementation is heading in the right direction, but I am still worried about the migration path.
646
647### Slack ou Teams
648
649Guarde respostas curtas que se mantêm calmas e claras sob pressão de tempo:
650
651> I can take the first pass today, but I may need help validating the edge cases.
652
653### Jira ou Confluence
654
655Capture atualizações de status e linguagem de trade-offs:
656
657> We can ship the smaller version first if we want to reduce risk before the full rollout.
658
659### E-mail
660
661Salve linhas que lidam bem com alinhamento:
662
663> I want to make sure we agree on the scope before we commit to the timeline externally.
664
665## Construa uma biblioteca em torno do seu trabalho real
666
667O objetivo do LangCapture não é dar a você mais conteúdo para consumir. É ajudar você a preservar a melhor linguagem que o seu trabalho já produz.
668
669Se você quer a visão geral do produto, leia [Transforme a linguagem real do trabalho na sua biblioteca pessoal de aprendizado](/blog/introducing-langcapture).
670
671Se você quer o argumento mais amplo sobre aprendizado, leia [Pare de decorar templates: construa uma biblioteca real de frases do trabalho](/blog/stop-memorizing-templates-build-a-real-workplace-sentence-library-instead).
672
673Depois, comece com uma frase do GitHub, Slack, Jira ou e-mail, e salve enquanto ela ainda está fresca.
674
675Você pode começar pela [página de captura](/sentences/capture) ou voltar para a [página inicial](/) para ver o fluxo completo.
676`,H=`---

677title: "如何从 GitHub、Slack、Jira 和邮件中采集有用句子"
678description: "一篇实操指南：如何把 GitHub、Slack、Jira、邮件里的真实多语种句子沉淀成可复用的资料库，包括网页采集、浏览器插件、翻译、音频和 API Token。"
679image: /og.png
680date: "2026-03-14"
681published: true
682categories: [capture-workflows]
683author: langcapture
684---
685
686建立真正有用的语言资料库，最快的办法通常不是打开一个学习 App。
687
688而是从你已经在用的工作工具里，把那些真正发生过的句子采下来。
689
690对多语种团队来说，这些句子就分布在 GitHub、Slack 或 Teams、Jira 或 Confluence、Notion、内部文档和邮件里。里面有大量真正值得以后回看的多语种表达。
691
692LangCapture 就是围绕这个工作流设计的。
693
694## 什么样的句子值得采集？
695
696不是每一句话都值得进你的句子库。最值得保存的句子，通常有一个共同点：它很好地解决了一个真实沟通问题。
697
698例如：
699
700- 一条表达反对意见但不显得防御的 PR 评论
701- 一条把风险和下一步说清楚的 Jira 更新
702- 一句兼顾效率和礼貌的 Slack 回复
703- 一句设定预期非常清晰的邮件表达
704- 一条你以后还会想复用的跨语言状态同步
705
706如果你看到一句话时，会冒出“这句话我以后还想再用一次”，那它大概率就值得保存。
707
708## 工作流 1：直接粘贴到 LangCapture
709
710对很多用户来说，最简单的流程仍然是最有效的：
711
7121. 从你的工具里复制一句任意语言
7132. 粘贴到 LangCapture
7143. 按正确方向保存原句与翻译
7154. 之后需要时再回看翻译，或者播放 TTS
716
717如果你已经打开网页端，或者刚看到一个很值得留下来的句子，这个流程通常最快。
718
719你可以直接从[采集页面](/sentences/capture)试一下。
720
721## 工作流 2：使用 Chrome 插件
722
723如果你不想离开当前页面，Chrome 插件更顺手。
724
725实际流程很直接：
726
7271. 在 GitHub、Slack、Jira、Confluence、邮件或其他页面高亮一句话
7282. 通过插件或右键菜单触发 LangCapture
7293. 直接把句子发送到你的工作区
7304. 之后再打开句子卡片，查看翻译或播放音频
731
732这个方式特别适合异步沟通场景——阻力够低。你不用为了存一句好表达，打断正在做的事。
733
734## 登录态或 API Token 都可以
735
736LangCapture 当前支持两种实用的鉴权方式：
737
738- 保持网页登录态，直接使用会话
739- 为浏览器插件或其它无头集成使用个人访问令牌（API Token）
740
741这点重要——真实的采集动作不一定发生在主应用标签页里。它可能在浏览器插件里，可能在内部工具里，甚至可能是你直接调句子 API。
742
743如果你正在配置插件，可以前往 [API Token 设置页](/settings/tokens)。
744
745## 句子保存后，会发生什么？
746
747LangCapture 的价值不光是”当下给你翻译一次”，更在于”你之后还能回来再用”。
748
749句子保存后，整个流程依然聚焦：
750
751- 原句会保留下来
752- 翻译会按你的母语方向保存
753- 需要音频时可以再生成 TTS
754- 这条记录会一直留在你的句子库里，方便后续回看
755
756这样既适合即时理解，也适合长期复用。
757
758## 为什么这比随手记笔记更有效
759
760很多人其实已经在收集“好句子”了，只是他们的系统非常脆弱：
761
762- 截图很快就找不到了
763- 星标和收藏会越来越嘈杂
764- 零散笔记容易丢掉原句或翻译方向
765
766LangCapture 做的事，是把”句子采集”从一个临时习惯，变成一个可以反复执行的工作流。
767
768它也处理敏感信息脱敏，所以你保存下来的重点是沟通方式本身，不是周围的机密细节。
769
770## 不同工具里，哪些句子值得留？
771
772下面举几个典型例子。
773
774### GitHub
775
776保存那些语气成熟的 code review 句子：
777
778> I think the implementation is heading in the right direction, but I am still worried about the migration path.
779
780### Slack 或 Teams
781
782保留那些在时间压力下依然清晰、克制的回复：
783
784> I can take the first pass today, but I may need help validating the edge cases.
785
786### Jira 或 Confluence
787
788保存状态同步和取舍表达：
789
790> We can ship the smaller version first if we want to reduce risk before the full rollout.
791
792### 邮件
793
794收集那些处理对齐和预期管理特别好的句子：
795
796> I want to make sure we agree on the scope before we commit to the timeline externally.
797
798## 围绕真实工作，而不是额外制造学习负担
799
800LangCapture 的重点，不是再给你增加一堆要消费的内容，而是帮你把工作里已经出现的最好表达留下来。
801
802如果你想先看更完整的产品介绍：[把真实职场语言变成你的个人学习库](/blog/introducing-langcapture)。
803
804如果你想看为什么”真实句子资料库”比”模板记忆”更有效：[别再背模板了：把真实工作句子沉淀成你的语言资料库](/blog/stop-memorizing-templates-build-a-real-workplace-sentence-library-instead)。
805
806然后，从 GitHub、Slack、Jira 或邮件里今天刚看到的一句话开始，趁它还新鲜，把它存下来。
807
808直接去[采集页面](/sentences/capture)，或者先回[首页](/)看看完整流ç¨

808‹ã€‚
809`,R=`---
810title: "Convierte el lenguaje real de tu trabajo en tu biblioteca personal de aprendizaje"
811description: "Descubre cómo LangCapture te ayuda a capturar expresiones auténticas de herramientas como GitHub, Slack y Jira — y convertirlas en activos de lenguaje reutilizables."
812image: /og.png
813date: "2026-03-14"
814published: true
815categories: [product-updates]
816author: langcapture
817---
818
819La mayoría de quienes estudian un idioma memorizan frases de libro de texto que casi nunca aparecen en el trabajo real. Mientras tanto, cada revisión de pull request, cada hilo de Slack y cada comentario de Jira está lleno de lenguaje natural y profesional — expresiones que los hablantes nativos usan todos los días.
820
821**LangCapture cierra esa brecha.**
822
823## El problema del aprendizaje de idiomas tradicional
824
825Cuando te encuentras con una gran expresión en el trabajo — por ejemplo, "Let's circle back on this after the release" — ¿qué haces? Quizá la subrayas, quizá la copias en una nota. Pero sin un sistema, esos fragmentos se acumulan y nunca se convierten en una habilidad real.
826
827## Cómo funciona LangCapture
828
8291. **Captura** — Pega cualquier frase auténtica en tu idioma objetivo desde tus herramientas de todos los días
8302. **Traduce** — Obtén al instante una traducción clara a tu idioma nativo para entender el significado en contexto
8313. **Escucha** — Oye la pronunciación natural con la reproducción TTS integrada
8324. **Construye tu biblioteca** — Cada frase se guarda en tu colección personal con buscador, lista para repasar en cualquier momento
833
834Sin libros de texto, sin ejemplos inventados. Solo lenguaje real de tu trabajo diario, organizado y listo para aprender.
835
836## Extensión de navegador: captura sin salir de tu flujo de trabajo
837
838También ofrecemos una **extensión de Chrome** que hace la captura aún más rápida. Cuando veas una buena expresión en cualquier página web — un comentario de PR en GitHub, un mensaje de Slack, un correo — solo selecciona el texto y:
839
840- Haz **clic derecho** y elige "Save to LangCapture", o
841- Presiona **Cmd+Shift+S** (Mac) / **Ctrl+Shift+S** (Windows/Linux)
842
843La frase se envía al instante a tu biblioteca de LangCapture. Una pequeña notificación confirma el guardado — sin cambiar de pestaña, sin copiar y pegar. Te mantienes en tu flujo mientras tu biblioteca de lenguaje crece en segundo plano.
844
845Para configurarla, solo genera un token de API en tu configuración de LangCapture, pégalo en el popup de la extensión y listo.
846
847## Por qué importa el input auténtico
848
849La investigación muestra que la adquisición de un idioma ocurre más rápido cuando trabajas con input que es significativo, está ligeramente por encima de tu nivel actual y está conectado a contextos reales. El lenguaje del trabajo cumple las tres condiciones.
850
851En lugar de memorizar "I would like to suggest..." de un libro de texto, coleccionas expresiones como:
852
853> "Would it make sense to sync up before we cut the release?"
854
855— porque eso es lo que tus colegas escriben de verdad.
856
857## Empieza ahora
858
859Regístrate gratis y captura tu primera frase. Tu biblioteca personal de lenguaje empieza con una sola expresión real.
860`,G=`---
861title: "職場のリアルな英語を、自分だけの学習ライブラリに変えよう"
862description: "GitHub、Slack、Jira などのツールに流れる本物の英語表現を LangCapture でキャプチャし、繰り返し使える言語資産に変える方法を紹介します。"
863image: /og.png
864date: "2026-03-14"
865published: true
866categories: [product-updates]
867author: langcapture
868---
869
870多くの語学学習者は、実際の仕事ではほとんど登場しない教科書のフレーズを勉強しています。その一方で、プルリクエストのレビュー、Slack のスレッド、Jira のコメントには、ネイティブスピーカーが毎日実際に使っている自然でプロフェッショナルな英語があふれています。
871
872**LangCapture は、このギャップを埋めるためのツールです。**
873
874## 従来の語学学習の問題点
875
876仕事中に良い表現に出会ったとき — 例えば "Let's cir

876cle back on this after the release" — あなたはどうしていますか。ハイライトしたり、メモにコピーしたりするかもしれません。しかし仕組みがなければ、そうした断片はただ溜まっていくだけで、本当のスキルにはなりません。
877
878## LangCapture の仕組み
879
8801. **キャプチャ** — 日々のツールで見つけた学習対象言語の本物の文を貼り付ける
8812. **翻訳** — 文脈の中で意味を理解できるよう、母語のわかりやすい訳を即座に取得
8823. **リスニング** — 内蔵の TTS 再生で自然な発音を確認
8834. **ライブラリを育てる** — すべての文は検索可能な自分専用のコレクションに保存され、いつでも復習できる
884
885教科書も、作り物の例文も不要です。実際の仕事から生まれた本物の英語だけを、整理された形で学べます。
886
887## ブラウザ拡張機能：作業の流れを止めずにキャプチャ
888
889キャプチャをさらに速くする **Chrome ブラウザ拡張機能** も提供しています。Web ページ上で良い表現を見つけたら — GitHub の PR コメント、Slack のメッセージ、メールなど — テキストを選択して、
890
891- **右クリック** して「Save to LangCapture」を選ぶ、または
892- **Cmd+Shift+S**（Mac）/ **Ctrl+Shift+S**（Windows/Linux）を押す
893
894だけで、その文は即座に LangCapture のライブラリへ送信されます。小さなトースト通知が保存を知らせてくれるので、タブの切り替えもコピー＆ペーストも不要です。作業の流れを保ったまま、バックグラウンドで語学ライブラリが育っていきます。
895
896セットアップは簡単です。LangCapture の設定画面で API トークンを生成し、拡張機能のポップアップに貼り付けるだけで準備完了です。
897
898## なぜ「本物のインプット」が重要なのか
899
900研究によれば、言語の習得が最も速く進むのは、意味があり、今の自分のレベルより少しだけ高く、現実の文脈に結びついたインプットに触れているときです。職場の英語は、この 3 つの条件をすべて満たしています。
901
902教科書の "I would like to suggest..." を暗記する代わりに、次のような表現を集めていくのです。
903
904> "Would it make sense to sync up before we cut the release?"
905
906— これこそが、同僚たちが実際に書いている英語だからです。
907
908## さあ、始めましょう
909
910無料登録して、最初の 1 文をキャプチャしてみてください。あなた専用の語学ライブラリは、たった 1 つの本物の表現から始まります。
911`,O=`---
912title: "실제 업무 속 언어를 나만의 학습 라이브러리로"
913description: "GitHub, Slack, Jira, 이메일 같은 일상 업무 도구에서 마주치는 살아 있는 직장 영어 표현을 캡처하고, 번역과 AI 음성을 자동으로 생성해 언제든 복습할 수 있는 재사용 가능한 언어 자산으로 만드는 방법을 LangCapture와 함께 알아보세요."
914image: /og.png
915date: "2026-03-14"
916published: true
917categories: [product-updates]
918author: langcapture
919---
920
921대부분의 언어 학습자는 실제 업무에서는 거의 쓰이지 않는 교과서 표현을 공부합니다. 그런데 정작 풀 리퀘스트 리뷰, Slack 스레드, Jira 코멘트에는 원어민이 매일 실제로 사용하는 자연스럽고 프로페셔널한 표현이 가득합니다.
922
923**LangCapture는 바로 이 간극을 메워 줍니다.**
924
925## 기존 언어 학습 방식의 문제
926
927업무 중에 멋진 표현을 만나면 — 예를 들어 "Let's circle back on this after the release" 같은 문장을 보면 — 어떻게 하시나요? 하이라이트를 하거나 메모에 복사해 두실 수도 있습니다. 하지만 체계가 없으면 이런 조각들은 쌓이기만 할 뿐 실력으로 이어지지 않습니다.
928
929## LangCapture는 이렇게 동작합니다
930
9311. **캡처** — 매일 쓰는 도구에서 만난 학습 언어 문장을 그대로 붙여넣습니다
9322. **번역** — 문맥 속 의미를 바로 이해할 수 있도록 명확한 한국어 번역을 즉시 제공합니다
9333. **듣기** — 내장 TTS 재생으로 자연스러운 발음을 들어 봅니다
9344. **라이브러리 구축** — 모든 문장이 검색 가능한 개인 컬렉션에 저장되어 언제든 복습할 수 있습니다
935
936교과서도, 억지로 만든 예문도 없습니다. 실제 업무에서 나온 진짜 언어만 정리해서 바로 학습할 수 있습니다.
937
938## 브라우저 확장 프로그램: 작업 흐름을 끊지 않는 캡처
939
940캡처를 더 빠르게 해 주는 **Chrome 브라우저 확장 프로그램**도 제공합니다. GitHub PR 코멘트, Slack 메시지, 이메일 등 어떤 웹페이지에서든 좋은 표현을 발견하면 텍스트를 선택한 뒤:
941
942- **우클릭** 후 "Save to LangCapture"를 선택하거나
943- **Cmd+Shift+S** (Mac) / **Ctrl+Shift+S** (Windows/Linux)를 누르면 됩니다
944
945문장이 즉시 LangCapture 라이브러리로 전송됩니다. 작은 토스트 알림이 저장 완료를 알려 주고, 탭 전환도 복사·붙여넣기도 필요 없습니다. 작업 흐름은 그대로 유지되고, 언어 라이브러리는 뒤에서 조용히 쌓여 갑니다.
946
947설정 방법도 간단합니다. LangCapture 설정에서 API 토큰을 생성해 확장 프로그램 팝업에 붙여넣기만 하면 바로 사용할 수 있습니다.
948
949## 진짜 인풋이 중요한 이유
950
951연구에 따르면 언어 습득은 의미가 있고, 현재 수준보다 약간 높으며, 실제 맥락과 연결된 인풋을 다룰 때 가장 빠르게 일어납니다. 업무 언어는 이 세 가지 조건을 모두 충족합니다.
952
953교과서에서 "I would like to suggest..."를 외우는 대신, 이런 표현을 수집하게 됩니다:
954
955> "Would it make sense to sync up before we cut the release?"
956
957— 동료들이 실제로 이렇게 쓰기 때문입니다.
958
959## 지금 시작하세요
960

961무료로 가입하고 첫 문장을 캡처해 보세요. 나만의 언어 라이브러리는 진짜 표현 하나에서 시작됩니다.
962`,D=`---
963title: "Turn Real Workplace Language into Your Personal Learning Library"
964description: "Learn how LangCapture helps you capture authentic expressions from tools like GitHub, Slack, and Jira — and turn them into reusable language assets."
965image: /og.png
966date: "2026-03-14"
967published: true
968categories: [product-updates]
969author: langcapture
970---
971
972Most language learners study textbook phrases that rarely show up in real work. Meanwhile, every pull request review, Slack thread, and Jira comment is full of natural, professional language — expressions that native speakers actually use every day.
973
974**LangCapture bridges this gap.**
975
976## The Problem with Traditional Language Learning
977
978When you encounter a great expression at work — say, "Let's circle back on this after the release" — what do you do? Maybe you highlight it, maybe you copy it to a note. But without a system, those snippets pile up and never turn into real skill.
979
980## How LangCapture Works
981
9821. **Capture** — Paste any authentic sentence in your target language from your daily tools
9832. **Translate** — Instantly get a clear native-language translation so you understand the meaning in context
9843. **Listen** — Hear the natural pronunciation with built-in TTS playback
9854. **Build your library** — Every sentence is saved to your searchable personal collection, ready to review anytime
986
987No textbooks, no made-up examples. Just real language from your actual work, organized and ready to learn from.
988
989## Browser Extension: Capture Without Leaving Your Workflow
990
991We also provide a **Chrome browser extension** that makes capturing even faster. When you spot a great expression on any webpage — a GitHub PR comment, a Slack message, an email — just select the text and:
992
993- **Right-click** and choose "Save to LangCapture", or
994- Press **Cmd+Shift+S** (Mac) / **Ctrl+Shift+S** (Windows/Linux)
995
996The sentence is instantly sent to your LangCapture library. A small toast notification confirms the save — no tab switching, no copy-pasting. You stay in your flow and your language library grows in the background.
997
998To set it up, just generate an API token in your LangCapture settings, paste it into the extension popup, and you're ready to go.
999
1000## Why Authentic Input Matters
1001
1002Research shows that language acquisition happens fastest when you work with input that is meaningful, slightly above your current level, and tied to real contexts. Workplace language checks all three boxes.
1003
1004Instead of memorizing "I would like to suggest..." from a textbook, you collect expressions like:
1005
1006> "Would it make sense to sync up before we cut the release?"
1007
1008— because that's what your colleagues actually write.
1009
1010## Get Started
1011
1012Sign up for free and capture your first sentence. Your personal language library starts with one real expression.
1013`,M=`---
1014title: "Transforme a linguagem real do trabalho na sua biblioteca pessoal de aprendizado"
1015description: "Veja como o LangCapture ajuda você a capturar expressões autênticas de ferramentas como GitHub, Slack e Jira — e transformá-las em ativos de linguagem reutilizáveis."
1016image: /og.png
1017date: "2026-03-14"
1018published: true
1019categories: [product-updates]
1020author: langcapture
1021---
1022
1023A maioria das pessoas que estuda idiomas decora frases de livro didático que raramente aparecem no trabalho de verdade. Enquanto isso, cada review de pull request, thread no Slack e comentário no Jira está cheio de linguagem natural e profissional — expressões que falantes nativos realmente usam todos os dias.
1024
1025**O LangCapture fecha essa lacuna.**
1026
1027## O problema do aprendizado de idiomas tradicional
1028
1029Quando você encontra uma ótima expressão no trabalho — por exemplo, "Let's circle back on this after the release" — o que você faz? Talvez destaque o texto, talvez copie para uma nota. Mas, sem um sistema, esses recortes se acumulam e nunca viram habilidade de verdade.
1030
1031## Como o LangCapture funciona
1032
10331. **Capture** — Cole qualquer frase autêntica no idioma que você está aprendendo, direto das suas ferramentas do dia a dia
10342. **Traduza** — Receba na hora uma tradução clara em português para entender o significado no contexto
10353. **Ouça** — Escute a pronúncia natural com reprodução de TTS integrada

10364. **Construa sua biblioteca** — Cada frase é salva na sua coleção pessoal pesquisável, pronta para revisar a qualquer momento
1037
1038Sem livros didáticos, sem exemplos inventados. Apenas linguagem real do seu trabalho de verdade, organizada e pronta para você aprender.
1039
1040## Extensão para navegador: capture sem sair do seu fluxo de trabalho
1041
1042Também oferecemos uma **extensão para o Chrome** que torna a captura ainda mais rápida. Quando você encontrar uma boa expressão em qualquer página — um comentário de PR no GitHub, uma mensagem no Slack, um e-mail — basta selecionar o texto e:
1043
1044- **Clicar com o botão direito** e escolher "Save to LangCapture", ou
1045- Pressionar **Cmd+Shift+S** (Mac) / **Ctrl+Shift+S** (Windows/Linux)
1046
1047A frase é enviada instantaneamente para a sua biblioteca no LangCapture. Uma pequena notificação confirma o salvamento — sem trocar de aba, sem copiar e colar. Você continua no seu fluxo enquanto sua biblioteca de idiomas cresce em segundo plano.
1048
1049Para configurar, basta gerar um token de API nas configurações do LangCapture, colá-lo no popup da extensão e pronto.
1050
1051## Por que o input autêntico importa
1052
1053Pesquisas mostram que a aquisição de idiomas acontece mais rápido quando você trabalha com input que é significativo, está um pouco acima do seu nível atual e está ligado a contextos reais. A linguagem do ambiente de trabalho atende aos três critérios.
1054
1055Em vez de decorar "I would like to suggest..." de um livro didático, você coleciona expressões como:
1056
1057> "Would it make sense to sync up before we cut the release?"
1058
1059— porque é isso que seus colegas realmente escrevem.
1060
1061## Comece agora
1062
1063Cadastre-se gratuitamente e capture sua primeira frase. Sua biblioteca pessoal de idiomas começa com uma expressão real.
1064`,J=`---
1065title: "把真实职场语言变成你的个人学习库"
1066description: "了解 LangCapture 如何帮助你从 GitHub、Slack、Jira 和邮件等日常工具中捕获地道的职场外语表达，自动生成清晰翻译与 AI 音频，并把它们转化为可随时复习、真正用得上的可复用语言资产。"
1067image: /og.png
1068date: "2026-03-14"
1069published: true
1070categories: [product-updates]
1071author: langcapture
1072---
1073
1074大多数语言学习者学的是教科书里的短语，但实际工作中几乎碰不到。另一方面，每一条 Pull Request 评审、Slack 对话、Jira 评论里，到处是自然、专业的外语表达——母语者每天都在用的那种。
1075
1076**LangCapture 就是干这个的。**
1077
1078## 传统语言学习的问题
1079
1080工作中碰到一个很妙的表达——比如 "Let's circle back on this after the release"——你通常怎么做？高亮一下、复制到笔记里。但没有系统的话，这些片段只会越堆越多，永远变不成真本事。
1081
1082## LangCapture 如何运作
1083
10841. **捕获** — 粘贴你日常工具里看到的真实外语句子
10852. **翻译** — 实时拿到清晰的母语翻译，在上下文里理解意思
10863. **朗读** — 内置 TTS 播放，听到自然的发音
10874. **建立语言库** — 每句都存进可搜索的个人收藏，随时复习
1088
1089没有教科书，没有虚构例句。只把你真实工作中碰到的语言整理好，随时能学。
1090
1091## 浏览器插件：不离开工作流就能捕获
1092
1093我们还提供了一个 **Chrome 浏览器插件**，让捕获再快一点。在任何网页上看到好的表达——GitHub PR 评论、Slack 消息、邮件——选中文本，然后：
1094
1095- **右键**，选 "Save to LangCapture"，或者
1096- 按 **Cmd+Shift+S**（Mac）/ **Ctrl+Shift+S**（Windows/Linux）
1097
1098句子即时发到你的 LangCapture 语言库，弹一个小通知确认保存成功。不用切换标签页，不用复制粘贴。你保持工作节奏，语言库在后台自己长。
1099
1100设置也简单：在 LangCapture 设置里生成一个 API Token，粘贴到插件弹窗，就行了。
1101
1102## 为什么真实输入重要
1103
1104语言习得研究有一个挺扎实的结论：当学习材料有意义、略高于当前水平、且跟真实场景挂钩时，学得最快。职场外语正好三条全中。
1105
1106与其从教科书里背 "I would like to suggest..."，不如收集这样的表达：
1107
1108> "Would it make sense to sync up before we cut the release?"
1109

1110——这是你同事真的会写出来的东西。
1111
1112## 开始使用
1113
1114免费注册，捕获第一句话。你的个人语言库，从一个真实表达开始。
1115`,B=`---
1116title: "Deja de memorizar plantillas: construye una biblioteca real de frases de trabajo"
1117description: "La mayoría de los profesionales no necesita más plantillas de lenguaje de negocios. Necesita una forma de guardar frases reales de trabajo en inglés y español, con traducción y audio para repasarlas después."
1118image: /og.png
1119date: "2026-03-14"
1120published: true
1121categories: [workplace-language-learning]
1122author: langcapture
1123---
1124
1125Si trabajas en producto, ingeniería, diseño u operaciones, probablemente ves frases útiles en varios idiomas todos los días.
1126
1127Un comentario de revisión bien pensado en GitHub. Una respuesta serena en Slack. Una actualización de estado pulida. Un correo conciso para stakeholders.
1128
1129La mayoría de la gente hace lo mismo con estas frases: las copia en una nota, marca el mensaje con una estrella o se promete que recordará la formulación más tarde.
1130
1131Por lo general, no la recuerda.
1132
1133Por eso memorizar plantillas genéricas rara vez es suficiente. La comunicación real del trabajo es contextual. El tono importa. La elección de palabras importa. La diferencia entre "I disagree" y "I am not convinced this is the right tradeoff yet" importa.
1134
1135## El problema del aprendizaje basado en plantillas
1136
1137Las listas de plantillas pueden ser útiles al principio, pero se quedan cortas muy rápido en equipos reales.
1138
1139Estas son las razones:
1140
1141- Son demasiado genéricas para las situaciones que realmente enfrentas.
1142- Ignoran el tono de la comunicación asíncrona real.
1143- Son difíciles de consultar cuando las necesitas dentro de un flujo de trabajo real.
1144
1145La mayoría de los profesionales que trabajan entre dos idiomas no necesita cincuenta frases pulidas para reuniones imaginarias. Necesita una forma confiable de conservar las frases reales que ya encuentra en GitHub, Slack, Jira, Confluence, Notion o el correo.
1146
1147## Qué hace mejor una biblioteca de frases
1148
1149Una biblioteca de frases es más simple y más útil que una pila de plantillas.
1150
1151En lugar de intentar generar lenguaje desde cero, capturas una frase real que ya funcionó en contexto, y la guardas en un formato que de verdad puedes repasar después:
1152
1153- la frase original
1154- una traducción clara a tu idioma nativo
1155- reproducción opcional con TTS cuando quieras volver a escucharla
1156- un lugar estable para volver a esa línea más tarde
1157
1158Ese es el núcleo de LangCapture.
1159
1160No estás creando tarjetas de memoria para la escuela. Estás construyendo una biblioteca de referencia para la comunicación real del trabajo.
1161
1162## Cómo encaja LangCapture en este flujo de trabajo
1163
1164LangCapture está construido alrededor de una tarea concreta: convertir la comunicación real de trabajo entre dos idiomas en activos de lenguaje reutilizables.
1165
1166El flujo actual es intencionalmente simple:
1167
11681. Pega una frase que encontraste en tu día a día.
11692. Guarda el texto original con la dirección de traducción correcta.
11703. Repásala más tarde en tu biblioteca personal de frases.
11714. Genera audio solo cuando quieras volver a reproducir la frase.
1172
1173Suena básico, pero resuelve un problema real. El lenguaje útil suele desaparecer porque el paso de captura es demasiado lento, el paso de repaso es demasiado desordenado, o la nota guardada pierde el contexto de la redacción original.
1174
1175LangCapture mantiene juntas la frase original y la traducción para que puedas revisar ambos lados rápidamente cuando los necesites.
1176
1177Si primero quieres la visión general, empieza con [Convierte el lenguaje real de tu trabajo en tu biblioteca personal de aprendizaje](/blog/introducing-langcapture).
1178
1179## El lenguaje real supera a los ejemplos inventados
1180
1181Una frase real de tu flujo de trabajo suele enseñar más que un ejemplo de libro de texto, porque ya trae consigo:
1182
1183- el nivel correcto de franqueza
1184- la cantidad justa de matices
1185- la terminología que tu equipo realmente usa
1186- el estilo de comunicación de tu entorno
1187
1188Por ejemplo, estos son los tipos de frases que vale la pena guardar:
1189
1190> I am not blocking this PR, but I think we should add a test for the edge case.
1191
1192> We can ship this now, but I want to call out the risk before we commit to the timeline.
1193
1194> This makes sense for v1, though we may want to revisit the naming once the scope expands.
1195

1196Esto no es "material de estudio". Es comunicación de calidad de producción.
1197
1198## Diseñado para repasar, no solo para capturar
1199
1200Guardar una frase solo es útil si puedes encontrarla y repasarla después.
1201
1202Por eso LangCapture almacena cada línea capturada en una biblioteca de frases en lugar de tratarla como una solicitud de traducción desechable. Puedes volver al texto original, revisar la traducción guardada y reproducir la frase con TTS cuando quieras practicar pronunciación o ritmo.
1203
1204El producto también aplica redacción con enfoque en privacidad cuando es necesario, de modo que detalles sensibles como nombres de empresas, nombres de repositorios, enlaces, tickets, correos y secretos no sean el centro de lo que se preserva.
1205
1206## Para quién funciona mejor
1207
1208Este flujo de trabajo es especialmente útil para:
1209
1210- equipos de producto que trabajan en dos idiomas
1211- ingenieros que quieren mejorar su tono en revisiones y discusiones asíncronas
1212- diseñadores que necesitan seguir hilos de producto e implementación
1213- gente de operaciones y PMs que escriben actualizaciones, decisiones y respuestas a stakeholders
1214
1215Si tu trabajo ya ocurre en comunicación escrita, ya tienes la materia prima. Lo que falta es el sistema para conservarla.
1216
1217## Empieza con una frase real
1218
1219No necesitas un gran plan de estudio para sacarle valor a LangCapture.
1220
1221Empieza con una línea útil que hayas visto hoy. Guárdala. Repásala mañana. Repite cuando otra frase valga la pena.
1222
1223Así es como crece una biblioteca real de frases de trabajo.
1224
1225Puedes [capturar tu primera frase](/sentences/capture) ahora, o [volver a la página principal](/) para ver la descripción completa del producto.
1226`,F=`---
1227title: "テンプレートの暗記はやめよう：本物の職場フレーズライブラリを作る"
1228description: "多くのビジネスパーソンに必要なのは、ビジネス英語のテンプレート集ではありません。職場で出会った本物の文を訳と音声つきで保存し、後から復習できる仕組みです。"
1229image: /og.png
1230date: "2026-03-14"
1231published: true
1232categories: [workplace-language-learning]
1233author: langcapture
1234---
1235
1236プロダクト、エンジニアリング、デザイン、オペレーションの仕事をしているなら、複数の言語で「使える文」を毎日のように目にしているはずです。
1237
1238思慮深い GitHub のレビューコメント。落ち着いた Slack の返信。洗練されたステータス更新。簡潔なステークホルダー向けメール。
1239
1240こうした文に対して、ほとんどの人は同じ行動を取ります。メモにコピーする、メッセージにスターを付ける、あるいは「この言い回しは後で思い出せる」と自分に言い聞かせる。
1241
1242たいてい、思い出せません。
1243
1244だからこそ、汎用テンプレートの暗記だけでは足りないのです。実際の仕事のコミュニケーションは文脈に依存します。トーンが重要で、言葉選びが重要です。"I disagree" と "I am not convinced this is the right tradeoff yet" の違いは、決して小さくありません。
1245
1246## テンプレート先行型学習の問題点
1247
1248テンプレート集はごく初期には役立ちますが、実際のチームの中ではすぐに通用しなくなります。
1249
1250理由は次のとおりです。
1251
1252- 汎用的すぎて、実際に直面する状況に合わない。
1253- 現実の非同期コミュニケーションのトーンを無視している。
1254- 実際のワークフローの中で必要になったときに、見返しにくい。
1255
1256多言語環境で働くプロフェッショナルの多くに必要なのは、架空の会議のための洗練されたフレーズ 50 選ではありません。GitHub、Slack、Jira、Confluence、Notion、メールですでに出会っている本物の文を、確実に残しておける方法です。
1257
1258## フレーズライブラリのほうが優れている理由
1259
1260フレーズライブラリは、テンプレートの山よりもシンプルで、実用的です。
1261
1262ゼロから言葉をひねり出そうとするのではなく、すでに文脈の中で機能した本物の文をキャプチャし、後ã

1262‹ã‚‰æœ¬å½“に復習できる形で保存します。
1263
1264- 原文そのもの
1265- 母語によるわかりやすい訳
1266- 聞き直したいときの TTS 再生（任意）
1267- 後からその一文に戻れる安定した置き場所
1268
1269これが LangCapture の核心です。
1270
1271学校用の単語カードを作っているのではありません。実際の仕事のコミュニケーションのためのリファレンスライブラリを作っているのです。
1272
1273## LangCapture はこのワークフローにどうフィットするか
1274
1275LangCapture は、ある狭い役割に特化して作られています。職場で交わされる本物のバイリンガルなコミュニケーションを、再利用可能な言語資産に変えることです。
1276
1277現在のワークフローは意図的にシンプルにしてあります。
1278
12791. 現場で見つけた文を貼り付ける。
12802. 適切な翻訳方向を指定して原文を保存する。
12813. 後から自分のフレーズライブラリで復習する。
12824. 文を聞き直したいときだけ音声を生成する。
1283
1284基本的なことに聞こえますが、これが現実の問題を解決します。役立つ表現が消えてしまうのはたいてい、キャプチャが面倒だったり、復習の仕組みが散らかっていたり、保存したメモが元の言い回しの文脈を失ってしまうからです。
1285
1286LangCapture は原文と訳をセットで保持するので、必要なときに両方をすばやく見比べられます。
1287
1288まず全体像から知りたい方は、[職場のリアルな英語を、自分だけの学習ライブラリに変えよう](/blog/introducing-langcapture)からどうぞ。
1289
1290## 本物の文は、作られた例文に勝る
1291
1292自分のワークフローから生まれた本物の文は、教科書の例文よりも多くのことを教えてくれます。なぜなら、最初から次のものを備えているからです。
1293
1294- ちょうどよい率直さの度合い
1295- ちょうどよい婉曲表現の量
1296- チームが実際に使っている用語
1297- あなたの職場環境のコミュニケーションスタイル
1298
1299例えば、保存する価値があるのはこんな文です。
1300
1301> I am not blocking this PR, but I think we should add a test for the edge case.
1302
1303> We can ship this now, but I want to call out the risk before we commit to the timeline.
1304
1305> This makes sense for v1, though we may want to revisit the naming once the scope expands.
1306
1307これらは「学習教材」ではありません。実戦レベルのコミュニケーションそのものです。
1308
1309## キャプチャだけでなく、復習のために設計
1310
1311文を保存しても、後から見つけて復習できなければ意味がありません。
1312
1313だからこそ LangCapture は、キャプチャした一文を使い捨ての翻訳リクエストとして扱うのではなく、フレーズライブラリに保管します。原文に戻り、保存された訳を確認し、発音やリズムを練習したいときには TTS で再生できます。
1314
1315また、必要に応じてプライバシー優先のマスキングを適用するため、会社名、リポジトリ名、リンク、チケット、メールアドレス、シークレットといった機密情報が保存内容の中心になることはありません。
1316
1317## 特に効果を発揮するのはこんな人
1318
1319このワークフローが特に役立つのは、
1320
1321- 多言語環境で働くプロダクトチーム
1322- レビューや非同期ディスカッションのトーンを磨きたいエンジニア
1323- プロダクトや実装のスレッドを追う必要があるデザイナー
1324- 進捗報告・意思決定・ステークホルダー対応を書くオペレーターや PM
1325
1326仕事がすでに文章ベースのコミュニケーションで回っているなら、素材はもう手元にあります。足りないのは、それを残しておく仕組みだけです。
1327
1328## まずは本物の 1 文から
1329
1330LangCapture から価値を得るのに、壮大な学習計画は要りません。
1331
1332今日見かけた使える一文から始めましょう。保存する。明日見返す。また残す価値のある文に出会ったら繰り返す。
1333
1334本物の職場フレーズライブラリは、こうやって育っていきます。
1335
1336今すぐ[最初の 1 文をキャプチャ](/sentences/capture)するか、[ホームページに戻って](/)プロダクトの全体像をご覧ください。
1337`,Y=`---

1338title: "템플릿 암기는 그만: 진짜 업무 문장 라이브러리를 만드세요"
1339description: "대부분의 직장인에게 필요한 것은 비즈니스 영어 템플릿이 아닙니다. 실제 업무에서 만난 영한 대역 문장을 번역과 오디오와 함께 저장해 두고 복습할 수 있는 방법입니다."
1340image: /og.png
1341date: "2026-03-14"
1342published: true
1343categories: [workplace-language-learning]
1344author: langcapture
1345---
1346
1347프로덕트, 엔지니어링, 디자인, 운영 분야에서 일한다면 아마 매일 여러 언어로 된 쓸모 있는 문장을 보고 계실 겁니다.
1348
1349사려 깊은 GitHub 리뷰 코멘트. 차분한 Slack 답글. 잘 다듬어진 상태 업데이트. 간결한 이해관계자 이메일.
1350
1351이런 문장을 만났을 때 대부분의 사람들은 비슷하게 행동합니다. 메모에 복사해 두거나, 메시지에 별표를 달거나, 나중에 그 표현을 기억해 내겠다고 다짐합니다.
1352
1353그리고 대개는 기억하지 못합니다.
1354
1355그래서 범용 템플릿을 외우는 것만으로는 부족합니다. 실제 업무 커뮤니케이션은 맥락에 좌우됩니다. 톤이 중요하고, 단어 선택이 중요합니다. "I disagree"와 "I am not convinced this is the right tradeoff yet"의 차이가 중요합니다.
1356
1357## 템플릿 우선 학습의 문제
1358
1359템플릿 목록은 아주 초반에는 도움이 될 수 있지만, 실제 팀 환경에서는 금방 한계를 드러냅니다.
1360
1361이유는 이렇습니다:
1362
1363- 너무 범용적이어서 실제로 마주치는 상황과 맞지 않습니다.
1364- 실제 비동기 커뮤니케이션의 톤을 반영하지 못합니다.
1365- 실제 워크플로 한가운데에서 필요할 때 다시 찾아보기 어렵습니다.
1366
1367영어와 한국어를 오가며 일하는 직장인 대부분에게 필요한 것은 가상의 회의를 위한 매끈한 표현 50개가 아닙니다. GitHub, Slack, Jira, Confluence, Notion, 이메일에서 이미 만나고 있는 진짜 문장을 믿을 수 있게 보관하는 방법입니다.
1368
1369## 문장 라이브러리가 더 나은 이유
1370
1371문장 라이브러리는 템플릿 더미보다 단순하면서도 더 유용합니다.
1372
1373언어를 처음부터 지어내려 애쓰는 대신, 이미 실제 맥락에서 효과가 입증된 문장을 캡처해 나중에 실제로 복습할 수 있는 형태로 저장합니다:
1374
1375- 원문 그대로의 문장
1376- 모국어로 된 명확한 번역
1377- 다시 듣고 싶을 때 사용할 수 있는 TTS 재생
1378- 나중에 그 문장을 다시 찾을 수 있는 안정적인 공간
1379
1380이것이 LangCapture의 핵심입니다.
1381
1382학교 시험용 플래시카드를 만드는 것이 아닙니다. 실제 업무 커뮤니케이션을 위한 레퍼런스 라이브러리를 만드는 것입니다.
1383
1384## LangCapture가 이 워크플로에 들어맞는 방식
1385
1386LangCapture는 한 가지 좁은 역할에 집중합니다: 실제 이중 언어 업무 커뮤니케이션을 재사용 가능한 언어 자산으로 바꾸는 것입니다.
1387
1388현재 워크플로는 의도적으로 단순하게 유지하고 있습니다:
1389
13901. 업무 현장에서 발견한 문장을 붙여넣습니다.
13912. 알맞은 번역 방향으로 원문을 저장합니다.
13923. 나중에 개인 문장 라이브러리에서 복습합니다.
13934. 문장을 다시 듣고 싶을 때만 오디오를 생성합니다.
1394
1395단순해 보이지만 실제 문제를 해결합니다. 쓸모 있는 표현이 사라지는 이유는 보통 캡처가 너무 느리거나, 복습이 너무 번거롭거나, 저장한 메모가 원문 표현의 맥락을 잃어버리기 때문입니다.
1396
1397LangCapture는 원문과 번역을 함께 보관하므로 필요할 때 양쪽을 한눈에 빠르게 훑어볼 수 있습니다.
1398
1399전체 그림을 먼저 보고 싶다면 [실제 업무 속 언어를 나만의 학습 라이브러리로](/blog/introducing-langcapture)부터 읽어 보세요.
1400
1401## 진짜 언어가 만들어 낸 예문을 이깁니다
1402
1403업무 흐름에서 나온 진짜 문장은 교과서 예문보다 보통 더 많은 것을 가르쳐 줍니다. 이미 다음을 담고 있기 때문입니다:
1404
1405- 적절한 수준의 직설성
1406- 적절한 양의 완곡함
1407- 팀이 실제로 쓰는 용어
1408- 우리 조직 특유의 커뮤니케이션 스타일
1409
1410예를 들어, 다음은 저장할 가치가 있는 문장들입니다:
1411
1412> I am not blocking this PR, but I think we should add a test for the edge case.
1413
1414> We can ship this now, but I want to call out the risk before we commit to the timeline.
1415
1416> This makes sense for v1, though we may want to revisit the naming once the scope expands.
1417
1418이런 문장은 "학습 자료"가 아닙니다. 프로덕션급 커뮤니케이션입니다.
1419
1420## 캡처만이 아니라 복습을 위해 만들어졌습니다
1421
1422문장 저장은 나중에 찾아서 복습할 수 있어야 비로소 의미가 있습니다.
1423
1424그래서 LangCapture는 캡처된 문장을 일회용 번역 요청처럼 다루지 않고 문장 라이브러리에 저장합니다. 원문으로 돌아가 저장된 번역을 살펴보고, 발음이나 리듬을 연습하고 싶을 때 TTS로 다시 들을 수 있습니다.
1425
1426또한 필요할 때 프라이버시 우선 마스킹을 적용하여 회사명, 저장소 이름, 링크, 티켓, 이메일, 시크릿 같은 민감한 정보가 보존 대상의 중심이 되지 않도록 합니다.
1427
1428## 이런 분들께 가장 잘 맞습니다
1429
1430이 워크플로는 특히 다음과 같은 분들께 유용합니다:
1431
1432- 영어와 한국어를 오가며 일하는 프로덕트 팀
1433- 리뷰와 비동기 토론의 톤을 개선하고 싶은 엔지니어
1434- 프로덕트와 구현 논의 스레드를 따라가야 하는 디자이너
1435- 업데이트, 의사결정, 이해관계자 답신을 쓰는 운영 담당자와 PM
1436
1437이미 글로 일하고 계신다면, 원재료는 이미 갖고 계신 셈입니다. 빠진 것은 그것을 보관하는 시스템뿐입니다.
1438
1439## 진짜 문장 하나로 시작하세요
1440
1441LangCapture에서 가치를 얻는 데 거창한 학습 계획은 필요 없습니다.
1442
1443오늘 본 쓸모 있는 문장 하나로 시작하세요. 저장하고, 내일 복습하세요. 간직할 만한 문장이 또 나타나면 반복하세요.
1444
1445진짜 업무 문장 라이브러리는 그렇게 자랍니다.
1446
1447지금 [첫 문장을 캡처](/sentences/capture)하거나, [홈페이지로 돌아가](/) 전체 제품 소개를 살펴보세요.
1448`,$=`---
1449title: "Stop Memorizing Templates: Build a Real Workplace Sentence Library Instead"
1450description: "Most professionals do not need more business language templates. They need a way to save real bilingual workplace sentences with translation and audio for later review."
1451image: /og.png
1452date: "2026-03-14"
1453published: true
1454categories: [workplace-language-learning]
1455author: langcapture
1456---
1457
1458If you work in product, engineering, design, or operations, you probably see useful sentences in multiple languages every day.
1459
1460A thoughtful GitHub review comment. A calm Slack reply. A polished status update. A concise stakeholder email.
1461
1462Most people do the same thing with these sentences: they copy them into a 

1462note, star the message, or tell themselves they will remember the phrasing later.
1463
1464Usually, they do not.
1465
1466That is why memorizing generic templates is rarely enough. Real work communication is contextual. Tone matters. Word choice matters. The difference between "I disagree" and "I am not convinced this is the right tradeoff yet" matters.
1467
1468## The Problem with Template-First Learning
1469
1470Template lists can be useful at the very beginning, but they break down quickly in real teams.
1471
1472Here is why:
1473
1474- They are too generic to match the situations you actually face.
1475- They ignore the tone of real async communication.
1476- They are hard to revisit when you need them inside a real workflow.
1477
1478Most bilingual professionals do not need fifty polished phrases for imaginary meetings. They need a reliable way to keep the real sentences they already encounter in GitHub, Slack, Jira, Confluence, Notion, or email.
1479
1480## What a Sentence Library Does Better
1481
1482A sentence library is simpler and more useful than a pile of templates.
1483
1484Instead of trying to generate language from scratch, you capture a real sentence that already worked in context, then save it in a form you can actually review later:
1485
1486- the original sentence
1487- a clear translation in your native language
1488- optional TTS playback when you want to hear it again

1489- a stable place to revisit the line later
1490
1491That is the core of LangCapture.
1492
1493You are not building flashcards for school. You are building a reference library for real work communication.
1494
1495## How LangCapture Fits This Workflow
1496
1497LangCapture is built around a narrow job: turning real bilingual workplace communication into reusable language assets.
1498
1499The current workflow is intentionally simple:
1500
15011. Paste a sentence you found in the wild.
15022. Save the original text with the right translation direction.
15033. Review it later in your personal sentence library.
15044. Generate audio only when you want to replay the sentence.
1505
1506That sounds basic, but it solves a real problem. Useful language usually disappears because the capture step is too slow, the review step is too messy, or the saved note loses the context of the original wording.
1507
1508LangCapture keeps the original sentence and translation together so you can scan both sides quickly when you need them.
1509
1510If you want the broad overview first, start with [Turn Real Workplace Language into Your Personal Learning Library](/blog/introducing-langcapture).
1511
1512## Real Language Beats Invented Examples
1513
1514A real sentence from your workflow usually teaches more than a textbook example because it already carries:
1515
1516- the right level of directness
1517- the right amount of hedging
1518- the terminology your team actually uses
1519- the communication style of your environment
1520
1521For example, these are the kinds of sentences worth saving:
1522
1523> I am not blocking this PR, but I think we should add a test for the edge case.
1524
1525> We can ship this now, but I want to call out the risk before we commit to the timeline.
1526
1527> This makes sense for v1, though we may want to revisit the naming once the scope expands.
1528
1529These are not "study materials." They are production-grade communication.
1530
1531## Built for Review, Not Just Capture
1532
1533Saving a sentence is only useful if you can find and review it later.
1534
1535That is why LangCapture stores each captured line in a sentence library instead of treating it like a throwaway translation request. You can come back to the original text, inspect the saved translation, and replay the sentence with TTS when you want to practice pronunciation or rhythm.
1536
1537The product also applies privacy-first redaction when needed, so sensitive details such as company names, repo names, links, tickets, emails, and secrets are not the center of what gets preserved.
1538
1539## Who This Works Best For
1540
1541This workflow is especially useful for:
1542
1543- Bilingual product teams
1544- engineers who want to improve review and async discussion tone
1545- designers who need to follow product and implementation threads
1546- operators and PMs who write updates, decisions, and stakeholder replies
1547
1548If your work already happens in written communication, you already have the raw material. The missing part is the system for keeping it.
1549
1550## Start with One Real Sentence
1551
1552You do not need a huge study plan to get value from LangCapture.
1553
1554Start with one useful line you saw today. Save it. Review it tomorrow. Repeat when another sentence is worth keeping.
1555
1556That is how a real workplace sentence library grows.
1557
1558You can [capture your first sentence](/sentences/capture) now, or [go back to the homepage](/) for the full product overview.
1559`,K=`---
1560title: "Pare de decorar templates: construa uma biblioteca real de frases do trabalho"
1561description: "A maioria dos profissionais não precisa de mais templates de linguagem corporativa. Precisa de uma forma de salvar frases reais do trabalho, em inglês e português, com tradução e áudio para revisar depois."
1562image: /og.png
1563date: "2026-03-14"
1564published: true
1565categories: [workplace-language-learning]
1566author: langcapture
1567---
1568
1569Se você trabalha com produto, engenharia, design ou operações, provavelmente vê frases úteis em vários idiomas todos os dias.
1570
1571Um comentário de review bem pensado no GitHub. Uma resposta calma no Slack. Um status update bem escrito. Um e-mail conciso para stakeholders.
1572
1573A maioria das pessoas faz a mesma coisa com essas frases: copia para uma nota, marca a mensagem com estrela ou promete a si mesma que vai lembrar daquela formulação depois.
1574
1575Normalmente, não lembra.
1576
1577É por isso que decorar templates genéricos raramente é suficie

1577nte. A comunicação real no trabalho é contextual. O tom importa. A escolha das palavras importa. A diferença entre "I disagree" e "I am not convinced this is the right tradeoff yet" importa.
1578
1579## O problema do aprendizado baseado em templates
1580
1581Listas de templates podem ser úteis bem no começo, mas desmoronam rápido em equipes de verdade.
1582
1583Veja por quê:
1584
1585- São genéricas demais para corresponder às situações que você realmente enfrenta.
1586- Ignoram o tom da comunicação assíncrona real.
1587- São difíceis de revisitar quando você precisa delas dentro de um fluxo de trabalho real.
1588
1589A maioria dos profissionais bilíngues não precisa de cinquenta frases polidas para reuniões imaginárias. Precisa de uma forma confiável de guardar as frases reais que já encontra no GitHub, Slack, Jira, Confluence, Notion ou e-mail.
1590
1591## O que uma biblioteca de frases faz melhor
1592
1593Uma biblioteca de frases é mais simples e mais útil do que uma pilha de templates.
1594
1595Em vez de tentar gerar linguagem do zero, você captura uma frase real que já funcionou em contexto e a salva em um formato que pode de fato revisar depois:
1596
1597- a frase original
1598- uma tradução clara em português
1599- reprodução opcional de TTS quando você quiser ouvir de novo
1600- um lugar estável para revisitar a linha mais tarde
1601
1602Esse é o núcleo do LangCapture.
1603
1604Você não está montando flashcards para a escola. Está construindo uma biblioteca de referência para a comunicação real do trabalho.
1605
1606## Como o LangCapture se encaixa nesse fluxo
1607
1608O LangCapture foi construído em torno de uma tarefa bem definida: transformar a comunicação bilíngue real do trabalho em ativos de linguagem reutilizáveis.
1609
1610O fluxo atual é intencionalmente simples:
1611
16121. Cole uma frase que você encontrou por aí.
16132. Salve o texto original com a direção de tradução correta.
16143. Revise depois na sua biblioteca pessoal de frases.
16154. Gere áudio apenas quando quiser reproduzir a frase.
1616
1617Parece básico, mas resolve um problema real. Linguagem útil costuma desaparecer porque a etapa de captura é lenta demais, a etapa de revisão é bagunçada demais, ou a nota salva perde o contexto da redação original.
1618
1619O LangCapture mantém a frase original e a tradução juntas, para que você possa escanear os dois lados rapidamente quando precisar.
1620
1621Se você quer primeiro a visão geral, comece por [Transforme a linguagem real do trabalho na sua biblioteca pessoal de aprendizado](/blog/introducing-langcapture).
1622
1623## Linguagem real vale mais que exemplos inventados
1624
1625Uma frase real do seu fluxo de trabalho geralmente ensina mais do que um exemplo de livro didático, porque ela já carrega:
1626
1627- o nível certo de franqueza
1628- a dose certa de cautela
1629- a terminologia que sua equipe realmente usa
1630- o estilo de comunicação do seu ambiente
1631
1632Por exemplo, estes são os tipos de frase que valem a pena salvar:
1633
1634> I am not blocking this PR, but I think we should add a test for the edge case.
1635
1636> We can ship this now, but I want to call out the risk before we commit to the timeline.
1637
1638> This makes sense for v1, though we may want to revisit the naming once the scope expands.
1639
1640Isso não é "material de estudo". É comunicação em nível de produção.
1641
1642## Feito para revisão, não só para captura
1643
1644Salvar uma frase só é útil se você consegue encontrá-la e revisá-la depois.
1645
1646Por isso o LangCapture armazena cada linha capturada em uma biblioteca de frases, em vez de tratá-la como um pedido de tradução descartável. Você pode voltar ao texto original, inspecionar a tradução salva e reproduzir a frase com TTS quando quiser praticar pronúncia ou ritmo.
1647
1648O produto também aplica ocultação de dados com foco em privacidade quando necessário, para que detalhes sensíveis como nomes de empresas, nomes de repositórios, links, tickets, e-mails e segredos não sejam o centro do que fica preservado.
1649
1650## Para quem isso funciona melhor
1651
1652Esse fluxo é especialmente útil para:
1653
1654- equipes de produto bilíngues
1655- pessoas de engenharia que querem melhorar o tom em reviews e discussões assíncronas
1656- designers que precisam acompanhar threads de produto e implementação
1657- pessoas de operações e PMs que escrevem atualizações, decisões e respostas a stakeholders
1658
1659Se o seu trabalho já acontece em comunicação escrita, você já tem a matéria-prima. O que falta é o sistema para guardá-la.
1660
1661## Comece com uma frase real
1662
1663Você não precisa de um grande plano de estudos para extrair valor do LangCapture.
1664
1665Comece com uma linha útil que você viu hoje. Salve. Revise amanhã. Repita quando outra frase valer a pena guardar.
1666
1667É assim que uma biblioteca real de frases do trabalho cresce.
1668
1669Você pode [capturar sua primeira frase](/sentences/capture) agora, ou [voltar para a página inicial](/) para ver a visão completa do produto.
1670`,V=`---
1671title: "别再背模板了：把真实工作句子沉淀成你的语言资料库"
1672description: "大多数双语职场人并不缺商务语言模板，真正缺的是一个系统，去保存 GitHub、Slack、Jira 和邮件里真实的多语种工作句子、翻译和音频，方便之后反复回看、随时复用，逐步积累成真正用得上的语言资产。"
1673image: /og.png
1674date: "2026-03-14"
1675published: true
1676categories: [workplace-language-learning]
1677author: langcapture
1678---
1679

1680如果你在产品、工程、设计或运营团队工作，你每天都会看到很多值得留下来的多语种句子。
1681
1682可能是一条克制但坚定的 GitHub review comment，一句语气拿捏得很好的 Slack 回复，或者一封措辞成熟的邮件。
1683
1684大多数人面对这些句子时，做法都差不多：复制到笔记里、加个星标，或者心里想着“这个表达挺好，我之后记一下”。
1685
1686结果往往是，之后并不会真的再看。
1687
1688这也是为什么单纯背”商务语言模板”很难帮到你。真实工作里的语言不是填空题。语境重要，语气重要，措辞的细微差别也重要。
1689
1690\`I disagree.\` 和 \`I am not convinced this is the right tradeoff yet.\` 这两句话，传达的立场可能接近，但给人的感受完全不同。
1691
1692## 为什么”模板式学习”很快会失效
1693
1694模板在入门阶段有一点帮助，但进了真实团队协作，很快就扛不住了。
1695
1696原因不复杂：
1697
1698- 模板太泛，跟你每天面对的具体场景对不上
1699- 很少反映真实异步沟通里的语气层次
1700- 你真需要的时候，很难快速找回那个表达
1701
1702大多数双语职场人，不缺 50 句虚构会议里的”标准表达”，缺的是一个可靠的办法，把自己在 GitHub、Slack、Jira、Confluence、Notion、邮件里已经看到的真实句子留好。
1703
1704## 为什么”句子资料库”比”模板清单”更有用
1705
1706句子资料库的价值在于，它不要求你从零生成语言，而是帮你把已经在真实场景里跑通过的表达保存下来。
1707
1708一条有用的记录，至少应该包括：
1709
1710- 原句
1711- 清晰的母语翻译
1712- 需要时可回听的 TTS 音频
1713- 一个稳定、之后还能找回来的位置
1714
1715这正是 LangCapture 解决的问题。
1716
1717你不是在做考试式单词卡，而是在搭一个真实工作沟通的参考库。
1718
1719## LangCapture 在这个流程里做什么
1720
1721LangCapture 的目标很聚焦：把真实的多语种工作沟通，变成你之后还能复用的语言资产。
1722
1723当前产品工作流也保持简单：
1724
17251. 贴入你在真实工作里看到的一句话
17262. 按正确方向保存原句和翻译
17273. 之后在个人句子库里回看
17284. 想练发音或节奏时，再按需生成音频
1729
1730这看起来不复杂，但正好卡在真正有价值的位置上。很多好表达最后没沉淀下来，不是因为不重要，而是采集太慢、回看太乱，或者存的时候已经弄丢了原句。
1731
1732LangCapture 把原句和翻译保留在一起，之后需要时扫一眼，就能重新进入那种表达方式。
1733
1734如果你还没有看过产品总览，可以先读这篇：[把真实职场语言变成你的个人学习库](/blog/introducing-langcapture)。
1735
1736## 真实句子，比虚构例句更能帮你进步
1737
1738真实工作流里的句子，通常比教材例句更有学习价值，它自带这些信息：
1739
1740- 这家公司或团队实际使用的语气
1741- 这个场景下合适的委婉程度
1742- 这个领域真正会出现的术语
1743- 这个环境里的沟通节奏
1744

1745比如这些句子，就很值得留下来：
1746
1747> I am not blocking this PR, but I think we should add a test for the edge case.
1748
1749> We can ship this now, but I want to call out the risk before we commit to the timeline.
1750
1751> This makes sense for v1, though we may want to revisit the naming once the scope expands.
1752
1753这些不是”学习材料”，是真正在团队里用起来的表达。
1754
1755## 重点不只是采集，而是之后还能回看
1756
1757保存一句话，只有在你之后还能找到、还能复习时，才真正有价值。
1758
1759所以 LangCapture 不把它当一次性的翻译请求——每句话存进句子库。你之后可以回来看原句、查看保存下来的翻译，需要时播放 TTS 再听一遍这句话的发音和节奏。
1760
1761产品在需要时也会做隐私优先的脱敏处理，公司名、仓库名、链接、工单、邮箱、密钥这类敏感细节，不会成为你沉淀语言资产时的负担。
1762
1763## 最适合哪些人
1764
1765这个工作流特别适合：
1766
1767- 多语种产品团队
1768- 想提升 code review 和异步沟通语气的工程师
1769- 需要跟进讨论线程的设计师
1770- 需要频繁写同步、说明和邮件的 PM 与运营
1771
1772如果你的工作本来就有大量书面沟通，那你手里已经有最好的学习材料了。缺的只是一个把它们留下来的系统。
1773
1774## 从今天看到的一句真实表达开始
1775
1776你不需要先搞一个庞大的学习计划才能从 LangCapture 获得价值。
1777
1778从今天看到的一句有用表达开始。先存下来，明天再看一遍。下次再遇到值得留的句子，继续加进去。
1779
1780真实工作语言资料库，就是这样慢慢长出来的。
1781
1782去[采集第一句话](/sentences/capture)，或者先回[首页](/)看完整产品说明。
1783`,Q=`---
1784title: "Inglés para entrevistas técnicas de ingenieros de softw

1784are: frases útiles para algoritmos, diseño de sistemas y preguntas de comportamiento"
1785description: "Una guía práctica para ingenieros que se preparan para entrevistas técnicas en un idioma que no es el suyo (con el inglés como ejemplo), con frases útiles para algoritmos, diseño de sistemas y preguntas de comportamiento. Funciona para cualquier par de idiomas."
1786image: /og.png
1787date: "2026-03-20"
1788published: true
1789categories: [workplace-language-learning]
1790author: langcapture
1791---
1792
1793Muchos ingenieros hispanohablantes no batallan en las entrevistas técnicas por falta de capacidad técnica.
1794
1795Batallan porque, cuando necesitan pensar y explicar al mismo tiempo, no logran expresar su razonamiento con suficiente claridad en inglés.
1796
1797Eso suele aparecer en pequeños momentos:
1798
1799- sabes lo que quieres hacer, pero no puedes arrancar la explicación con fluidez
1800- te lanzas a programar demasiado pronto y olvidas aclarar el problema
1801- encuentras un bug, pero no sabes cómo decirlo con calma
1802- tienes una buena idea de diseño de sistemas, pero el lenguaje de los compromisos suena demasiado brusco o demasiado vago
1803- tu respuesta de comportamiento es técnicamente cierta, pero el inglés es demasiado plano para mostrar ownership
1804
1805Aquí es donde ayuda un buen inglés para entrevistas técnicas.
1806
1807No porque una lista de frases pueda conseguirte el empleo por arte de magia. No puede.
1808
1809Pero las frases correctas pueden ayudarte a decir lo que ya sabes de una forma más calmada, más clara y más natural.
1810
1811Por eso armamos la [colección de expresiones para entrevistas técnicas](/collections/technical-interview-expressions). Es un conjunto práctico de líneas en inglés listas para entrevistas, pensado para ingenieros de softw

1811are hispanohablantes. El objetivo es simple: ayudarte a hablar con más claridad en los momentos reales de una entrevista.
1812
1813## Qué hace realmente un buen inglés de entrevista técnica
1814
1815Un buen inglés para entrevistas técnicas no se trata de sonar sofisticado.
1816
1817Cumple tres funciones más simples:
1818
18191. Te da estructura al inicio de una respuesta.
18202. Ayuda al entrevistador a seguir tu razonamiento.
18213. Hace que tu respuesta suene calmada y profesional bajo presión.
1822
1823Si tu inglés puede hacer esas tres cosas, la entrevista normalmente se vuelve mucho más fácil.
1824
1825## 1. Empieza aclarando el problema
1826
1827Un error común es empezar a resolver demasiado rápido.
1828
1829En muchas entrevistas técnicas, la mejor jugada es bajar el ritmo unos segundos y hacer primero una o dos preguntas útiles.
1830
1831Por ejemplo:
1832
1833> "Before I jump into a solution, I'd like to clarify the scope and the main constraints."
1834
1835Esto es útil porque hace dos cosas a la vez. Demuestra que eres organizado y te da un poco de tiempo para pensar.
1836
1837Otro buen ejemplo para entrevistas de diseño de sistemas es:
1838
1839> "For this system, are we optimizing mainly for latency, throughput, or cost?"
1840
1841Es una frase simple, pero poderosa. Le dice al entrevistador que entiendes que una respuesta de diseño de sistemas depende del objetivo.
1842
1843Si quieres llevarte una sola idea de esta sección, es esta:
1844
1845No te apures por sonar rápido. Intenta sonar claro.
1846
1847## 2. En entrevistas de algoritmos, explica tu razonamiento paso a paso
1848
1849Muchos candidatos se quedan demasiado callados mientras resuelven problemas de código.
1850
1851Eso es riesgoso, porque el entrevistador no puede ver lo que pasa en tu cabeza.
1852
1853Un mejor enfoque es narrar tu pensamiento en pasos pequeños.
1854
1855Por ejemplo:
1856
1857> "My first thought is a brute-force approach, just to establish a correct baseline."
1858
1859Es una buena línea porque muestra un proceso normal de resolución de problemas. No estás fingiendo ver la mejor solución de inmediato. Estás mostrando que puedes construir a partir de un punto de partida correcto.
1860
1861Otra línea útil es:
1862
1863> "Let me dry-run this on a small example to make sure the transitions actually hold."
1864
1865Esto funciona bien cuando la lógica se está complicando. Le dice al entrevistador que estás verificando tu propio trabajo en lugar de adivinar.
1866
1867Si te atoras, no necesitas entrar en pánico ni quedarte en silencio. Puedes decir:
1868
1869> "I'm a bit stuck on the next step. Could you give me a small nudge rather than the full solution?"
1870
1871Esto suena mucho mejor que quedarte congelado, y aun así demuestra que quieres seguir resolviendo el problema por tu cuenta.
1872
1873## 3. Si encuentras un bug, dilo de forma directa y calmada
1874
1875Otra parte difícil de las entrevistas técnicas es recuperarse después de un error.
1876
1877Muchos candidatos se ponen nerviosos y empiezan a sobreexplicarse. Por lo general, eso empeora el momento.
1878
1879Una respuesta más corta y más calmada funciona mejor:
1880
1881> "I just spotted a bug in my logic. Let me fix that before I build on top of it."
1882
1883Esto funciona porque suena responsable, no defensivo.
1884
1885El entrevistador no espera perfección. Quiere ver cómo manejas los errores.
1886
1887Un lenguaje claro de depuración ayuda mucho aquí.
1888
1889## 4. En diseño de sistemas, el lenguaje de los compromisos importa
1890
1891En las entrevistas de diseño de sistemas, el problema muchas veces no es tu idea. El problema es cómo explicas el compromiso entre alternativas.
1892
1893Si tu respuesta suena demasiado absoluta, puedes parecer descuidado.
1894
1895Por ejemplo, esto es mejor que decir simplemente "we should use cache":
1896
1897> "A cache would cut read latency, but we'd need a clear invalidation strategy to keep the data trustworthy."
1898
1899Esta frase es útil porque muestra el beneficio y el costo en una sola línea.
1900
1901Otro ejemplo:
1902
1903> "I'd put a queue between these services so traffic spikes don't directly overwhelm the downstream system."
1904
1905Es una buena explicación porque se centra en la razón práctica de la cola, no solo en la palabra "asynchronous".
1906
1907Un buen inglés de diseño de sistemas suele ser simplemente causa y efecto bien explicados:
1908
1909- si agregamos esto, ¿qué mejora?
1910- ¿qué nuevo riesgo crea?
1911- ¿qué necesitamos para gestionar ese riesgo?
1912
1913Si puedes decir esas tres cosas con claridad, tu respuesta normalmente se siente mucho más sólida.
1914
1915## 5. Las preguntas de comportamiento necesitan acciones claras, no palabras grandilocuentes
1916
1917Las entrevistas de comportamiento son otro lugar donde muchos candidatos se venden por debajo de su valor en inglés.
1918
1919El problema normalmente no es falta de experiencia. El problema es que la respuesta se vuelve demasiado abstracta.
1920
1921Por ejemplo:
1922
1923> "When we had a production incident, I took ownership of the response, coordinated the fix, and wrote the follow-up."
1924
1925Esto es fuerte porque muestra acción concreta.
1926
1927Otro buen ejemplo es:
1928
1929> "Instead of debating in abstract, I built a small prototype so the team could react to something concrete."
1930
1931Esto funciona bien porque muestra iniciativa con lenguaje sencillo. No intenta sonar impresionante. Solo muestra lo que hiciste y por qué ayudó.
1932
1933Para las preguntas de comportamiento, un inglés simple suele ser mejor que un inglés pulido pero vago.
1934
1935## 6. No necesitas 500 frases. Necesitas las correctas
1936
1937La mayoría de los candidatos no necesita un guion de entrevista enorme.
1938
1939Necesita un conjunto más pequeño de líneas útiles para momentos recurrentes:
1940
1941- apertura y presentación personal
1942- aclarar el problema
1943- explicar un algoritmo en voz alta
1944- pedir una pista
1945- corregir un bug
1946- explicar un compromiso de diseño de sistemas
1947- responder preguntas de ownership o de conflicto
1948- cerrar con un resumen práctico
1949
1950Esa es la idea detrás de la [colección de expresiones para entrevistas técnicas](/collections/technical-interview-expressions).
1951
1952No es una promesa de que las frases por sí solas te harán pasar una entrevista. Es simplemente un conjunto estructurado de ejemplos para momentos que se repiten una y otra vez.
1953
1954Si quieres ver cómo está organizada la colección, puedes abrir primero la vista previa pública y leer una muestra de cada área antes de decidir si te resulta útil.
1955
1956## 7. Cómo practicar estas frases sin sonar a guion
1957
1958El objetivo no es memorizar cada línea palabra por palabra.
1959
1960Un mejor método es:
1961
19621. Elige una situación de entrevista que se te dificulte.
19632. Aprende dos o tres líneas útiles para esa situación.
19643. Practica decirlas en voz alta con tus propios ejemplos.
19654. Reutiliza la estructura, no solo la redacción exacta.
1966
1967Por ejemplo, no memorices una respuesta completa para cada pregunta de diseño de sistemas.
1968
1969En su lugar, familiarízate con patrones como:
1970
1971- "Before I jump into a solution..."
1972- "My first thought is..."
1973- "The benefit is..., but the tradeoff is..."
1974- "I just spotted a bug..."
1975- "In production, I would also add..."
1976
1977Eso normalmente sonará mucho más natural.
1978
1979## Reflexión final
1980
1981Si te estás preparando para una entrevista técnica en inglés, una buena colección de frases puede ayudar.
1982
1983No porque reemplace la capacidad técnica, el buen criterio o la experiencia real.
1984
1985Sino porque te ayuda a expresar esas cosas con más claridad cuando la presión aprieta.
1986
1987Si eso es lo que necesitas, empieza con la [colección de expresiones para entrevistas técnicas](/collections/technical-interview-expressions). Puedes ver una parte primero y luego decidir si quieres el conjunto completo.
1988`,X=`---
1989title: "ソフトウェアエンジニアのための技術面接英語：アルゴリズム・システムデザイン・行動面接で使えるフレーズ"
1990description: "母語ではない言語（ここでは英語を例に）での技術面接に備えるエンジニア向けの実践ガイド。アルゴリズム、システムデザイン、行動面接で使えるフレーズを紹介します。どの言語ペアにも応用できます。"
1991image: /og.png
1992date: "2026-03-20"
1993published: true
1994categories: [workplace-language-learning]
1995author: langcapture
1996---
1997
1998日本語を母語とするエンジニアの多くが技術面接でつまずくのは、技術力が足りないからではありません。
1999
2000考えることと説明することを同時にやらなければならない場面で、自分の思考プロセスを英語で十分明確に表現できないからです。
2001
2002それはたいてい、小さな瞬間に表れます。
2003
2004- やりたいことはわかっているのに、説明の出だしがスムーズに出てこない
2005- コーディングに飛びつくのが早すぎて、問題の確認を忘れる

2006- バグを見つけたのに、それを落ち着いて伝える言い方がわからない
2007- システムデザインのアイデアは良いのに、トレードオフの説明が断定的すぎるか曖昧すぎる
2008- 行動面接の回答は事実としては正しいのに、英語が平坦すぎてオーナーシップが伝わらない
2009
2010ここで役立つのが、技術面接で本当に使える英語表現です。
2011
2012フレーズ集を覚えれば魔法のように採用される、という話ではありません。それは無理です。
2013
2014しかし適切なフレーズがあれば、すでに自分の中にあるものを、より落ち着いて、より明確に、より自然に伝えられるようになります。
2015
2016私たちが[技術面接表現コレクション](/collections/technical-interview-expressions)をまとめたのもそのためです。これは日本語を母語とするソフトウェアエンジニアのための、面接ですぐ使える実践的な英語表現セットです。目的はシンプルで、実際の面接の場面で、より明確に話せるようになることです。
2017
2018## 良い技術面接英語が実際に果たす役割
2019
2020良い技術面接英語とは、かっこよく聞こえることではありません。
2021
2022もっとシンプルな 3 つの仕事をしてくれます。
2023
20241. 回答の冒頭で、話の構造を作る時間を稼いでくれる。
20252. 面接官があなたの思考をたどりやすくなる。
20263. プレッシャーの中でも、落ち着いたプロフェッショナルな印象を与えられる。
2027
2028英語でこの 3 つができれば、面接はたいていずっと楽になります。
2029
2030## 1. まず問題を明確にすることから始める
2031
2032よくある失敗は、解き始めるのが早すぎることです。
2033
2034多くの技術面接では、数秒だけ立ち止まって、有益な質問を 1 つか 2 つ先に投げかけるほうが得策です。
2035
2036例えば、
2037
2038> "Before I jump into a solution, I'd like to clarify the scope and the main constraints."
2039
2040この一言が有効なのは、2 つのことを同時に達成するからです。あなたが整理された思考の持ち主であることを示しつつ、考える時間を少し確保できます。
2041
2042システムデザイン面接で使えるもう 1 つの好例は、
2043
2044> "For this system, are we optimizing mainly for latency, throughput, or cost?"
2045
2046シンプルな文ですが、強力です。システムデザインの答えはゴール次第で変わる、ということを理解していると面接官に伝わります。
2047
2048このセクションから 1 つだけ持ち帰るなら、これです。
2049
2050速く見せようと焦らないこと。明確に聞こえることを目指すこと。
2051
2052## 2. アルゴリズム面接では、思考プロセスを段階的に説明する
2053
2054コーディング問題を解いている間、黙り込んでしまう候補者は少なくありません。
2055
2056これはリスクが高い行動です。あなたの頭の中で何が起きているのか、面接官には見えないからです。
2057
2058より良いアプローチは、考えていることを小さなステップで実況することです。
2059
2060例えば、
2061
2062> "My first thought is a brute-force approach, just to establish a correct baseline."
2063
2064これが良い一言なのは、自然な問題解決のプロセスを示しているからです。最適解が一瞬で見えているふりをするのではなく、正しい出発点から積み上げられることを示しています。
2065
2066もう 1 つ便利なのが、
2067
2068> "Let me dry-run this on a small example to make sure the transitions actually hold."
2069
2070ロジックが込み入ってきたときに効果的です。当てずっぽうではなく、自分の作業を自分で検証していることが面接官に伝わります。
2071
2072詰まってしまっても、パニックになったり黙り込んだりする必要はありません。こう言えばよいのです。
2073
2074> "I'm a bit stuck on the next step. Could you give me a small nudge rather than the full solution?"
2075
2076固まってしまうよりはるかに良い印象を与えますし、自力で解き続けたいという姿勢も示せます。
2077
2078## 3. バグを見つけたら、率直に、落ち着いて伝える
2079
2080技術面接でもう 1 つ難しいのが、ミスからの立て直しです。
2081
2082多くの候補者は緊張のあまり、過剰に言い訳を始めてしまいます。たいていの場合、それは状況を悪化させます。
2083
2084短く、落ち着いた対応のほうが良い結果を生みます。
2085
2086> "I just spotted a bug in my logic. Let me fix that before I build on top of it."
2087
2088この言い方が機能するのは、守りに入っているのではなく、責任感があるように聞こえるからです。
2089
2090面接官は完璧さを期待していません。見たいのは、あなたがミスにどう対処するかです。
2091
2092ここでは、明確なデバッグの言葉づかいが大きな助けになります。
2093
2094## 4. システムデザインでは、トレードオフの語り方が鍵
2095
2096システムデザイン面接で問題になるのは、多くの場合アイデアそのものではありません。トレードオフの説明の仕方です。
2097
2098回答が断定的すぎると、雑な印象を与えかねません。
2099
2100例えば、単に「キャッシュを使うべきです」と言うより、こちらのほうがずっと良い回答でã

2100™ã€‚
2101
2102> "A cache would cut read latency, but we'd need a clear invalidation strategy to keep the data trustworthy."
2103
2104この文が優れているのは、メリットとコストを一文で示しているからです。
2105
2106もう 1 つの例として、
2107
2108> "I'd put a queue between these services so traffic spikes don't directly overwhelm the downstream system."
2109
2110これが良い説明なのは、「非同期」という言葉を使うこと自体ではなく、キューを置く実務的な理由に焦点を当てているからです。
2111
2112良いシステムデザイン英語とは、多くの場合、明確な因果関係の説明にすぎません。
2113
2114- これを追加すると、何が良くなるのか？
2115- 新たにどんなリスクが生まれるのか？
2116- そのリスクを管理するために何が必要か？
2117
2118この 3 点を明確に語れれば、回答の説得力はたいてい大きく増します。
2119
2120## 5. 行動面接に必要なのは、大げさな言葉ではなく具体的な行動
2121
2122行動面接も、多くの候補者が英語で自分を安売りしてしまう場面です。
2123
2124問題はたいてい経験不足ではありません。回答が抽象的になりすぎることです。
2125
2126例えば、
2127
2128> "When we had a production incident, I took ownership of the response, coordinated the fix, and wrote the follow-up."
2129
2130具体的な行動を示しているからこそ、力強い回答になっています。
2131
2132もう 1 つの好例は、
2133
2134> "Instead of debating in abstract, I built a small prototype so the team could react to something concrete."
2135
2136平易な言葉で主体性を示しているのが効いています。印象的に聞こえようとはしていません。自分が何をして、それがなぜ役に立ったのかを、ただ示しているだけです。
2137
2138行動面接では、洗練されているけれど曖昧な英語より、シンプルな英語のほうがたいてい有効です。
2139
2140## 6. 必要なのは 500 のフレーズではなく、「正しい」フレーズ
2141
2142ほとんどの候補者に、膨大な面接用台本は必要ありません。
2143
2144繰り返し訪れる場面のための、小さな表現セットがあれば十分です。
2145
2146- オープニングと自己紹介
2147- 問題の明確化
2148- アルゴリズムの口頭説明
2149- ヒントの求め方
2150- バグの修正
2151- システムデザインのトレードオフの説明
2152- オーナーシップやコンフリクトに関する質問への回答
2153- 実務的なまとめによるクロージング
2154
2155これが[技術面接表現コレクション](/collections/technical-interview-expressions)の背後にある考え方です。
2156
2157フレーズだけで面接を突破できる、という約束ではありません。何度も訪れる場面のために構造化された例文集、それだけのことです。
2158
2159コレクションの構成を確認したい方は、まず公開プレビューを開いて各分野のサンプルを読んでから、自分に役立つかどうか判断できます。
2160
2161## 7. 台本っぽくならずにフレーズを練習する方法
2162
2163目標は、すべての文を一語一句暗記することではありません。
2164
2165より良い方法はこうです。
2166
21671. 自分が苦手な面接の場面を 1 つ選ぶ。
21682. その場面で使える表現を 2〜3 個学ぶ。
21693. 自分自身の事例を当てはめて、声に出して練習する。
21704. 正確な文言ではなく、構造を再利用する。
2171
2172例えば、システムデザインの質問ごとに完全な回答を 1 つずつ暗記するのはやめましょう。
2173
2174代わりに、次のようなパターンに慣れておくのです。
2175
2176- "Before I jump into a solution..."
2177- "My first thought is..."
2178- "The benefit is..., but the tradeoff is..."
2179- "I just spotted a bug..."
2180- "In production, I would also add..."
2181
2182そのほうが、たいていずっと自然に聞こえます。
2183
2184## 最後に
2185
2186英語での技術面接に備えているなら、使えるフレーズ集は確かに役に立ちます。
2187
2188技術力や的確な判断力、実際の経験の代わりになるからではありません。
2189
2190プレッシャーがかかる場面で、それらをより明確に表現する助けになるからです。
2191
2192それがまさに必要なものなら、[技術面接表現コレクション](/collections/technical-interview-expressions)から始めてみてください。まず一部をプレビューして、フルセットが必要かどうか判断できます。
2193`,Z=`---
2194title: "소프트웨어 엔지니어를 위한 기술 면접 영어: 알고리즘, 시스템 설계, 행동 면접에서 바로 쓰는 표현"
2195description: "모국어가 아닌 언어(영어 기준)로 기술 면접을 준비하는 엔지니어를 위한 실전 가이드. 알고리즘, 시스템 설계, 행동 면접 질문에 유용한 표현을 다룹니다. 어떤 언어 조합에도 적용할 수 있습니다."
2196image: /og.png
2197date: "2026-03-20"
2198published: true
2199categories: [workplace-language-learning]
2200author: langcapture
2201---
2202
2203한국어가 모국어인 많은 엔지니어가 기술 면접에서 고전하는 이유는 기술 역량이 부족해서가 아닙니다.
2204
2205생각과 설명을 동시에 해야 하는 순간, 자신의 사고 과정을 영어로 충분히 명확하게 표현하지 못하기 때문입니다.
2206

2207이 문제는 보통 작은 순간들에서 드러납니다:
2208
2209- 무엇을 하고 싶은지는 아는데, 설명을 매끄럽게 시작하지 못합니다
2210- 문제를 명확히 하는 단계를 건너뛰고 너무 일찍 코딩에 뛰어듭니다
2211- 버그를 발견했는데, 그것을 침착하게 말하는 방법을 모릅니다
2212- 좋은 시스템 설계 아이디어가 있는데, 트레이드오프 표현이 너무 단정적이거나 너무 모호하게 들립니다
2213- 행동 면접 답변이 사실 자체는 맞는데, 영어가 너무 밋밋해서 오너십이 드러나지 않습니다
2214
2215바로 이런 순간에 유용한 기술 면접 영어가 힘을 발휘합니다.
2216
2217표현 목록이 마법처럼 합격을 가져다주기 때문이 아닙니다. 그런 일은 일어나지 않습니다.
2218
2219하지만 적절한 표현은 이미 알고 있는 것을 더 차분하고, 더 명확하고, 더 자연스럽게 말할 수 있게 도와줍니다.
2220
2221그래서 저희가 [기술 면접 표현 컬렉션](/collections/technical-interview-expressions)을 만들었습니다. 한국어를 쓰는 소프트웨어 엔지니어를 위해 면접에서 바로 쓸 수 있는 영어 문장을 실전 중심으로 모은 자료입니다. 목표는 단순합니다: 실제 면접의 결정적인 순간에 더 명확하게 말할 수 있도록 돕는 것입니다.
2222
2223## 좋은 기술 면접 영어가 실제로 하는 일
2224
2225좋은 기술 면접 영어는 화려하게 들리기 위한 것이 아닙니다.
2226
2227훨씬 단순한 세 가지 역할을 합니다:
2228
22291. 답변 시작 부분에 구조를 만들어 줍니다.
22302. 면접관이 여러분의 사고 과정을 따라올 수 있게 해 줍니다.
22313. 압박 속에서도 답변이 차분하고 프로페셔널하게 들리도록 해 줍니다.
2232
2233여러분의 영어가 이 세 가지를 해낼 수 있다면 면접은 대개 훨씬 수월해집니다.
2234
2235## 1. 문제를 명확히 하는 것부터 시작하세요
2236
2237흔한 실수 중 하나는 너무 빨리 풀이에 들어가는 것입니다.
2238
2239많은 기술 면접에서는 몇 초만 속도를 늦추고 유용한 질문 한두 개를 먼저 던지는 것이 더 나은 선택입니다.
2240
2241예를 들어:
2242
2243> "Before I jump into a solution, I'd like to clarify the scope and the main constraints."
2244
2245이 문장이 유용한 이유는 두 가지 효과를 동시에 내기 때문입니다. 체계적인 사람이라는 인상을 주면서, 생각할 시간도 조금 벌어 줍니다.
2246
2247시스템 설계 면접에서 쓰기 좋은 또 다른 예는 이것입니다:
2248
2249> "For this system, are we optimizing mainly for latency, throughput, or cost?"
2250
2251단순한 문장이지만 강력합니다. 시스템 설계의 답이 목표에 따라 달라진다는 것을 이해하고 있음을 면접관에게 보여 줍니다.
2252
2253이 섹션에서 단 하나만 기억하신다면 이것입니다:
2254
2255빨라 보이려고 서두르지 마세요. 명확하게 들리도록 노력하세요.
2256
2257## 2. 알고리즘 면접에서는 사고 과정을 단계별로 설명하세요
2258
2259코딩 문제를 푸는 동안 너무 조용히 있는 지원자가 많습니다.
2260
2261면접관은 여러분의 머릿속에서 무슨 일이 일어나는지 볼 수 없기 때문에, 이는 위험한 선택입니다.
2262
2263더 나은 접근은 생각을 작은 단계로 나누어 소리 내어 설명하는 것입니다.
2264
2265예를 들어:
2266
2267> "My first thought is a brute-force approach, just to establish a correct baseline."
2268
2269이 문장이 좋은 이유는 자연스러운 문제 해결 과정을 보여 주기 때문입니다. 최적해를 단번에 꿰뚫어 본 척하지 않고, 올바른 출발점에서 차근차근 쌓아 올릴 수 있음을 보여 줍니다.
2270
2271또 하나 유용한 문장은 이것입니다:
2272
2273> "Let me dry-run this on a small example to make sure the transitions actually hold."
2274
2275로직이 복잡해질 때 잘 통하는 표현입니다. 추측에 의존하지 않고 자기 작업을 스스로 검증하고 있다는 것을 면접관에게 알려 줍니다.
2276
2277막혔을 때도 당황하거나 침묵할 필요가 없습니다. 이렇게 말할 수 있습니다:
2278
2279> "I'm a bit stuck on the next step. Could you give me a small nudge rather than the full solution?"
2280
2281얼어붙는 것보다 훨씬 좋은 인상을 주면서도, 문제를 스스로 끝까지 풀고 싶다는 의지를 보여 줍니다.
2282
2283## 3. 버그를 발견했다면 직접적이고 침착하게 말하세요
2284
2285기술 면접에서 또 하나 어려운 부분은 실수 후에 회복하는 것입니다.
2286
2287많은 지원자가 긴장한 나머지 과도하게 설명을 늘어놓기 시작합니다. 보통 그 순간을 더 악화시킬 뿐입니다.
2288
2289더 짧고 차분한 대응이 낫습니다:
2290
2291> "I just spotted a bug in my logic. Let me fix that before I build on top of it."
2292
2293이 표현이 효과적인 이유는 방어적이 아니라 책임감 있게 들리기 때문입니다.
2294
2295면접관은 완벽함을 기대하지 않습니다. 실수를 어떻게 다루는지 보고 싶어 합니다.
2296
2297이때 명확한 디버깅 표현이 큰 도움이 됩니다.
2298
2299## 4. 시스템 설계에서는 트레이드오프 표현이 중요합니다
2300
2301시스템 설계 면접에서 문제는 아이디어 자체가 아닌 경우가 많습니다. 트레이드오프를 설명하는 방식이 문제입니다.
2302
2303답변이 너무 단정적으로 들리면 신중하지 못한 사람으로 보일 수 있습니다.
2304
2305예를 들어, 단순히 "we should use cache"라고 말하는 것보다 이쪽이 낫습니다:
2306
2307> "A cache would cut read latency, but we'd need a clear invalidation strategy to keep the data trustworthy."
2308
2309이 문장이 유용한 이유는 이점과 비용을 한 문장에 함께 담기 때문입니다.
2310
2311또 다른 예:
2312
2313> "I'd put a queue between these services so traffic spikes don't directly overwhelm the downstream system."
2314
2315좋은 설명인 이유는 "asynchronous"라는 단어를 내세우는 대신 큐를 두는 실질적인 이유에 집중하기 때문입니다.
2316
2317좋은 시스템 설계 영어는 결국 명확한 인과관계인 경우가 많습니다:
2318
2319- 이것을 추가하면 무엇이 좋아지는가?
2320- 어떤 새로운 리스크가 생기는가?
2321- 그 리스크를 관리하려면 무엇이 필요한가?
2322
2323이 세 가지를 명확하게 말할 수 있다면 답변은 대개 훨씬 탄탄하게 느껴집니다.
2324

2325## 5. 행동 면접에 필요한 것은 거창한 단어가 아니라 명확한 행동입니다
2326
2327행동 면접 역시 많은 지원자가 영어 때문에 자신을 제대로 보여 주지 못하는 영역입니다.
2328
2329문제는 보통 경험 부족이 아닙니다. 답변이 너무 추상적으로 흘러가는 것이 문제입니다.
2330
2331예를 들어:
2332
2333> "When we had a production incident, I took ownership of the response, coordinated the fix, and wrote the follow-up."
2334
2335구체적인 행동을 보여 주기 때문에 강력한 답변입니다.
2336
2337또 다른 좋은 예는 이것입니다:
2338
2339> "Instead of debating in abstract, I built a small prototype so the team could react to something concrete."
2340
2341평이한 언어로 주도성을 보여 주기 때문에 효과적입니다. 인상적으로 들리려고 애쓰지 않고, 무엇을 했고 그것이 왜 도움이 되었는지를 그대로 보여 줍니다.
2342
2343행동 면접 질문에는 매끈하지만 모호한 영어보다 단순한 영어가 대개 더 낫습니다.
2344
2345## 6. 500개의 표현은 필요 없습니다. 꼭 맞는 표현이 필요합니다
2346
2347대부분의 지원자에게 방대한 면접 대본은 필요하지 않습니다.
2348
2349반복적으로 등장하는 순간들을 위한 작은 표현 세트가 필요합니다:
2350
2351- 오프닝과 자기소개
2352- 문제 명확화
2353- 알고리즘 풀이 과정 설명
2354- 힌트 요청
2355- 버그 수정
2356- 시스템 설계 트레이드오프 설명
2357- 오너십·갈등 관련 질문 답변
2358- 실용적인 요약으로 마무리
2359
2360이것이 [기술 면접 표현 컬렉션](/collections/technical-interview-expressions)의 기본 아이디어입니다.
2361
2362표현만으로 면접을 통과할 수 있다는 약속이 아닙니다. 거듭 등장하는 순간들을 위해 체계적으로 정리한 예문 모음일 뿐입니다.
2363
2364컬렉션이 어떻게 구성되어 있는지 보고 싶다면, 먼저 공개 미리보기를 열어 각 영역의 샘플을 읽어 본 뒤 자신에게 유용한지 판단할 수 있습니다.
2365
2366## 7. 대본처럼 들리지 않게 연습하는 방법
2367
2368목표는 모든 문장을 토씨 하나까지 외우는 것이 아닙니다.
2369
2370더 나은 방법은 이렇습니다:
2371
23721. 자신이 어려워하는 면접 상황 하나를 고릅니다.
23732. 그 상황에 유용한 표현 두세 개를 익힙니다.
23743. 자신의 사례를 넣어 소리 내어 말하는 연습을 합니다.
23754. 정확한 문구가 아니라 구조를 재사용합니다.
2376
2377예를 들어, 모든 시스템 설계 질문에 대해 완성된 답변을 통째로 외우지 마세요.
2378
2379대신 이런 패턴에 익숙해지세요:
2380
2381- "Before I jump into a solution..."
2382- "My first thought is..."
2383- "The benefit is..., but the tradeoff is..."
2384- "I just spotted a bug..."
2385- "In production, I would also add..."
2386
2387그쪽이 대개 훨씬 자연스럽게 들립니다.
2388
2389## 마치며
2390
2391영어 기술 면접을 준비하고 있다면 잘 만든 표현 컬렉션이 도움이 될 수 있습니다.
2392
2393기술 역량, 건전한 판단력, 실제 경험을 대체해 주기 때문이 아닙니다.
2394
2395압박이 거센 순간에 그것들을 더 명확하게 표현할 수 있도록 도와주기 때문입니다.
2396
2397그게 지금 필요한 것이라면 [기술 면접 표현 컬렉션](/collections/technical-interview-expressions)부터 시작해 보세요. 일부를 먼저 미리 본 뒤, 전체 세트가 필요한지 결정할 수 있습니다.
2398`,ee=`---
2399title: "Technical Interview English for Software Engineers: Useful Phrases for Algorithms, System Design, and Behavioral Questions"
2400description: "A practical guide for engineers preparing for technical interviews in a non-native language (English example), with useful phrases for algorithms, system design, and behavioral questions. Works for any target language pair."
2401image: /og.png
2402date: "2026-03-20"
2403published: true
2404categories: [workplace-language-learning]
2405author: langcapture
2406---
2407
2408Many Chinese-speaking engineers do not struggle with technical interviews because they lack technical ability.
2409
2410They struggle because, when they need to think and explain at the same time, they cannot express their reasoning clearly enough in English.
2411
2412That usually shows up in small moments:
2413

2414- you know what you want to do, but you cannot start the explanation smoothly
2415- you jump into coding too early and forget to clarify the problem
2416- you find a bug, but you do not know how to say it calmly
2417- you have a good system design idea, but the tradeoff language sounds too blunt or too vague
2418- your behavioral answer is technically true, but the English is too flat to show ownership
2419
2420This is where useful technical interview English helps.
2421
2422Not because a phrase list can magically get you hired. It cannot.
2423
2424But the right phrases can help you say what you already know in a calmer, clearer, and more natural way.
2425
2426That is also why we put together the [technical interview expressions collection](/collections/technical-interview-expressions). It is a practical set of interview-ready English lines for Chinese-speaking software engineers. The goal is simple: help you speak more clearly in real interview moments.
2427
2428## What Good Technical Interview English Actually Does
2429
2430Good technical interview English is not about sounding fancy.
2431
2432It does three simpler jobs:
2433
24341. It buys you structure at the start of an answer.
24352. It helps the interviewer follow your reasoning.
24363. It makes your answer sound calm and professional under pressure.
2437
2438If your English can do those three things, the interview usually gets much easier.
2439
2440## 1. Start by Clarifying the Problem
2441
2442One common mistake is to start solving too fast.
2443
2444In many technical interviews, the better move is to slow down for a few seconds and ask one or two useful questions first.
2445
2446For example:
2447
2448> "Before I jump into a solution, I'd like to clarify the scope and the main constraints."
2449
2450This is useful because it does two things at once. It shows that you are organized, and it gives you a little time to think.
2451
2452Another good example for system design interviews is:
2453
2454> "For this system, are we optimizing mainly for latency, throughput, or cost?"
2455
2456This is a simple sentence, but it is powerful. It tells the interviewer that you understand a system design answer depends on the goal.
2457
2458If you want one takeaway from this section, it is this:
2459
2460Do not rush to sound fast. Try to sound clear.
2461
2462## 2. In Algorithm Interviews, Explain Your Reasoning Step by Step
2463
2464A lot of candidates stay too quiet while solving coding problems.
2465
2466That is risky, because the interviewer cannot see what is happening in your head.
2467
2468A better approach is to narrate your thinking in small steps.
2469
2470For example:
2471
2472> "My first thought is a brute-force approach, just to establish a correct baseline."
2473
2474This is a good line because it shows a normal problem-solving process. You are not pretending to see the best solution immediately. You are showing that you can build from a correct starting point.
2475
2476Another useful line is:
2477
2478> "Let me dry-run this on a small example to make sure the transitions actually hold."
2479
2480This works well when the logic is getting complicated. It tells the interviewer you are checking your own work instead of guessing.
2481
2482If you get stuck, you do not need to panic or go silent. You can say:
2483
2484> "I'm a bit stuck on the next step. Could you give me a small nudge rather than the full solution?"
2485
2486This sounds much better than freezing, and it still shows that you want to keep solving the problem yourself.
2487
2488## 3. If You Find a Bug, Say It Directly and Calmly
2489
2490Another hard part of technical interviews is recovering after a mistake.
2491
2492Many candidates get nervous and start over-explaining. Usually that makes the moment worse.
2493
2494A shorter and calmer response is better:
2495
2496> "I just spotted a bug in my logic. Let me fix that before I build on top of it."
2497
2498This works because it sounds responsible, not defensive.
2499
2500The interviewer does not expect perfection. They want to see how you handle mistakes.
2501
2502Clear debugging language helps a lot here.
2503
2504## 4. In System Design, Tradeoff Language Matters
2505
2506In system design interviews, the problem is often not your idea. The problem is how you explain the tradeoff.
2507
2508If your answer sounds too absolute, it can make you seem careless.
2509
2510For example, this is better than simply saying "we should use cache":
2511
2512> "A cache would cut read latency, but we'd need a clear invalidation strategy to keep the data trustworthy."
2513
2514This sentence is useful because it shows both benefit and cost in one line.
2515
2516Another example:
2517
2518> "I'd put a queue between these services so traffic spikes don't directly overwhelm the downstream system."
2519
2520This is a good explanation because it focuses on the practical reason for the queue, not just the word "asynchronous."
2521
2522Good system design English is often just clear cause and effect:
2523
2524- if we add this, what gets better?
2525- what new risk does it create?
2526- what do we need to manage that risk?
2527
2528If you can say those three things clearly, your answer usually feels much stronger.
2529
2530## 5. Behavioral Questions Need Clear Actions, Not Big Words
2531
2532Behavioral interviews are another place where many candidates undersell themselves in English.
2533
2534The problem is usually not lack of experience. The problem is that the answer becomes too abstract.
2535
2536For example:
2537
2538> "When we had a production incident, I took ownership of the response, coordinated the fix, and wrote the follow-up."
2539
2540This is strong because it shows concrete action.
2541
2542Another good example is:
2543
2544> "Instead of debating in abstract, I built a small prototype so the team could react to something concrete."
2545
2546This works well because it shows initiative in plain language. It does not try to sound impressive. It just shows what you did and why it helped.
2547
2548For behavioral questions, simple English is usually better than polished but vague English.
2549
2550## 6. You Do Not Need 500 Phrases. You Need the Right Ones
2551
2552Most candidates do not need a huge interview script.
2553
2554They need a smaller set of useful lines for recurring moments:
2555
2556- opening and self-introduction
2557- clarifying the problem
2558- talking through an algorithm
2559- asking for a hint
2560- fixing a bug
2561- explaining a system design tradeoff
2562- answering ownership or conflict questions
2563- closing with a practical summary
2564
2565That is the idea behind the [technical interview expressions collection](/collections/technical-interview-expressions).
2566
2567It is not a promise that phrases alone will get someone through an interview. It is simply a structured set of examples for moments that come up again and again.
2568
2569If you want to see how the collection is organized, you can open the public preview first and read a sample from each area before deciding whether it is useful for you.
2570
2571## 7. How to Practice These Phrases Without Sounding Scripted
2572
2573The goal is not to memorize every line word for word.
2574
2575A better method is:
2576
25771. Pick one interview situation you struggle with.
25782. Learn two or three useful lines for that situation.
25793. Practice saying them out loud with your own examples.
25804. Reuse the structure, not just the exact wording.
2581
2582For example, do not memorize one full answer for every system design question.
2583
2584Instead, get comfortable with patterns like:
2585
2586- "Before I jump into a solution..."
2587- "My first thought is..."
2588- "The benefit is..., but the tradeoff is..."
2589- "I just spotted a bug..."
2590- "In production, I would also add..."
2591
2592That will usually sound much more natural.
2593
2594## Final Thought
2595
2596If you are preparing for an English technical interview, a useful phrase collection can help.
2597
2598Not because it replaces technical ability, sound judgment, or real experience.
2599
2600But because it helps you express those things more clearly when the pressure is on.
2601
2602If that is what you need, start with the [technical interview expressions collection](/collections/technical-interview-expressions). You can preview part of it first, then decide whether you want the full set.
2603`,ne=`---
2604title: "Inglês para entrevistas técnicas de engenharia de softw

2604are: frases úteis para algoritmos, system design e perguntas comportamentais"
2605description: "Um guia prático para engenheiros que se preparam para entrevistas técnicas em um idioma não nativo (exemplo em inglês), com frases úteis para algoritmos, system design e perguntas comportamentais. Funciona para qualquer par de idiomas."
2606image: /og.png
2607date: "2026-03-20"
2608published: true
2609categories: [workplace-language-learning]
2610author: langcapture
2611---
2612
2613Muitos engenheiros falantes de português não têm dificuldade em entrevistas técnicas por falta de capacidade técnica.
2614
2615Eles têm dificuldade porque, quando precisam pensar e explicar ao mesmo tempo, não conseguem expressar o raciocínio com clareza suficiente em inglês.
2616
2617Isso costuma aparecer em pequenos momentos:
2618
2619- você sabe o que quer fazer, mas não consegue começar a explicação com fluidez
2620- você parte para o código cedo demais e esquece de esclarecer o problema
2621- você encontra um bug, mas não sabe como falar dele com calma
2622- você tem uma boa ideia de system design, mas a linguagem de trade-offs soa brusca ou vaga demais
2623- sua resposta comportamental é tecnicamente verdadeira, mas o inglês é raso demais para demonstrar ownership
2624
2625É aí que um bom inglês de entrevista técnica ajuda.
2626
2627Não porque uma lista de frases consiga magicamente garantir sua contratação. Não consegue.
2628
2629Mas as frases certas podem ajudar você a dizer o que já sabe de um jeito mais calmo, mais claro e mais natural.
2630
2631Foi por isso que montamos a [coleção de expressões para entrevistas técnicas](/collections/technical-interview-expressions). É um conjunto prático de frases em inglês prontas para entrevista, pensado para engenheiros de software falantes de português. O objetivo é simples: ajudar você a falar com mais clareza nos momentos reais da entrevista.
2632
2633## O que um bom inglês de entrevista técnica realmente faz
2634
2635Um bom inglês de entrevista técnica não é sobre soar sofisticado.
2636
2637Ele cumpre três funções mais simples:
2638
26391. Garante estrutura no início de uma resposta.
26402. Ajuda o entrevistador a acompanhar o seu raciocínio.
26413. Faz sua resposta soar calma e profissional sob pressão.
2642
2643Se o seu inglês consegue fazer essas três coisas, a entrevista geralmente fica muito mais fácil.
2644
2645## 1. Comece esclarecendo o problema
2646
2647Um erro comum é começar a resolver rápido demais.
2648
2649Em muitas entrevistas técnicas, a melhor jogada é desacelerar por alguns segundos e fazer uma ou duas perguntas úteis primeiro.
2650
2651Por exemplo:
2652
2653> "Before I jump into a solution, I'd like to clarify the scope and the main constraints."
2654
2655Isso é útil porque faz duas coisas ao mesmo tempo. Mostra que você é organizado e dá um tempinho para pensar.
2656
2657Outro bom exemplo para entrevistas de system design:
2658
2659> "For this system, are we optimizing mainly for latency, throughput, or cost?"
2660
2661É uma frase simples, mas poderosa. Ela mostra ao entrevistador que você entende que uma resposta de system design depende do objetivo.
2662
2663Se você quer levar uma única lição desta seção, é esta:
2664
2665Não corra para parecer rápido. Tente parecer claro.
2666
2667## 2. Em entrevistas de algoritmos, explique seu raciocínio passo a passo
2668
2669Muitos candidatos ficam quietos demais enquanto resolvem problemas de código.
2670
2671Isso é arriscado, porque o entrevistador não consegue ver o que está acontecendo na sua cabeça.
2672
2673Uma abordagem melhor é narrar seu pensamento em pequenos passos.
2674
2675Por exemplo:
2676
2677> "My first thought is a brute-force approach, just to establish a correct baseline."
2678
2679Essa é uma boa frase porque mostra um processo normal de resolução de problemas. Você não está fingindo enxergar a melhor solução de imediato. Está mostrando que consegue construir a partir de um ponto de partida correto.
2680
2681Outra frase útil:
2682
2683> "Let me dry-run this on a small example to make sure the transitions actually hold."
2684
2685Ela funciona bem quando a lógica está ficando complicada. Mostra ao entrevistador que você está verificando o próprio trabalho em vez de chutar.
2686
2687Se você travar, não precisa entrar em pânico nem ficar em silêncio. Você pode dizer:
2688
2689> "I'm a bit stuck on the next step. Could you give me a small nudge rather than the full solution?"
2690
2691Isso soa muito melhor do que congelar, e ainda mostra que você quer continuar resolvend

2691o o problema por conta própria.
2692
2693## 3. Se encontrar um bug, fale de forma direta e calma
2694
2695Outra parte difícil das entrevistas técnicas é se recuperar depois de um erro.
2696
2697Muitos candidatos ficam nervosos e começam a se explicar demais. Em geral, isso só piora o momento.
2698
2699Uma resposta mais curta e mais calma é melhor:
2700
2701> "I just spotted a bug in my logic. Let me fix that before I build on top of it."
2702
2703Isso funciona porque soa responsável, não defensivo.
2704
2705O entrevistador não espera perfeição. Ele quer ver como você lida com erros.
2706
2707Uma linguagem clara de debugging ajuda muito aqui.
2708
2709## 4. Em system design, a linguagem de trade-offs importa
2710
2711Em entrevistas de system design, o problema muitas vezes não é a sua ideia. O problema é como você explica o trade-off.
2712
2713Se a sua resposta soa absoluta demais, pode passar a impressão de descuido.
2714
2715Por exemplo, isto é melhor do que simplesmente dizer "we should use cache":
2716
2717> "A cache would cut read latency, but we'd need a clear invalidation strategy to keep the data trustworthy."
2718
2719Essa frase é útil porque mostra benefício e custo em uma linha só.
2720
2721Outro exemplo:
2722
2723> "I'd put a queue between these services so traffic spikes don't directly overwhelm the downstream system."
2724
2725É uma boa explicação porque foca no motivo prático da fila, e não apenas na palavra "asynchronous".
2726
2727Um bom inglês de system design costuma ser apenas causa e efeito com clareza:
2728
2729- se adicionarmos isso, o que melhora?
2730- que novo risco isso cria?
2731- do que precisamos para gerenciar esse risco?
2732
2733Se você consegue dizer essas três coisas com clareza, sua resposta geralmente parece muito mais forte.
2734
2735## 5. Perguntas comportamentais pedem ações claras, não palavras grandiosas
2736
2737Entrevistas comportamentais são outro lugar onde muitos candidatos se vendem mal em inglês.
2738
2739O problema normalmente não é falta de experiência. O problema é que a resposta fica abstrata demais.
2740
2741Por exemplo:
2742
2743> "When we had a production incident, I took ownership of the response, coordinated the fix, and wrote the follow-up."
2744
2745Essa resposta é forte porque mostra ação concreta.
2746
2747Outro bom exemplo:
2748
2749> "Instead of debating in abstract, I built a small prototype so the team could react to something concrete."
2750
2751Ela funciona bem porque mostra iniciativa em linguagem simples. Não tenta impressionar. Apenas mostra o que você fez e por que isso ajudou.
2752
2753Para perguntas comportamentais, um inglês simples costuma ser melhor do que um inglês polido porém vago.
2754
2755## 6. Você não precisa de 500 frases. Precisa das frases certas
2756
2757A maioria dos candidatos não precisa de um roteiro gigante de entrevista.
2758
2759Precisa de um conjunto menor de frases úteis para momentos recorrentes:
2760
2761- abertura e apresentação pessoal
2762- esclarecimento do problema
2763- explicação de um algoritmo em voz alta
2764- pedido de dica
2765- correção de um bug
2766- explicação de um trade-off de system design
2767- respostas sobre ownership ou conflito
2768- fechamento com um resumo prático
2769
2770Essa é a ideia por trás da [coleção de expressões para entrevistas técnicas](/collections/technical-interview-expressions).
2771
2772Não é uma promessa de que frases sozinhas vão fazer alguém passar em uma entrevista. É simplesmente um conjunto estruturado de exemplos para momentos que aparecem de novo e de novo.
2773
2774Se você quer ver como a coleção é organizada, pode abrir primeiro a prévia pública e ler uma amostra de cada área antes de decidir se ela é útil para você.
2775
2776## 7. Como praticar essas frases sem soar decorado
2777
2778O objetivo não é memorizar cada linha palavra por palavra.
2779
2780Um método melhor é:
2781
27821. Escolha uma situação de entrevista em que você tem dificuldade.
27832. Aprenda duas ou três frases úteis para essa situação.
27843. Pratique dizê-las em voz alta com os seus próprios exemplos.
27854. Reutilize a estrutura, não apenas a redação exata.
2786
2787Por exemplo, não memorize uma resposta completa para cada pergunta de system design.
2788
2789Em vez disso, fique confortável com padrões como:
2790
2791- "Before I jump into a solution..."
2792- "My first thought is..."
2793- "The benefit is..., but the tradeoff is..."
2794- "I just spotted a bug..."
2795- "In production, I would also add..."
2796
2797Isso geralmente soa muito mais natural.
2798
2799## Pensamento final
2800
2801Se você está se preparando para uma entrevista técnica em inglês, uma boa coleção de frases pode ajudar.
2802
2803Não porque ela substitui capacidade técnica, bom senso ou experiência real.
2804
2805Mas porque ela ajuda você a expressar essas coisas com mais clareza quando a pressão aperta.
2806
2807Se é disso que você precisa, comece pela [coleção de expressões para entrevistas técnicas](/collections/technical-interview-expressions). Você pode ver uma prévia primeiro e depois decidir se quer o conjunto completo.
2808`,ae=`---
2809title: "技术面试英语怎么准备：算法题、系统设计、行为面试常用表达"
2810description: "一篇技术面试外语准备指南（英语为例）：在算法题、系统设计、行为面试里有哪些真正常用的表达。支持任意语言对，本指南以英语为目标语言。"
2811image: /og.png
2812date: "2026-03-20"
2813published: true
2814categories: [workplace-language-learning]
2815author: langcapture
2816---
2817
2818很多中文背景的工程师在英文技术面试里卡住，不是因为技术不够好。
2819
2820更多时候，是要一边分析一边表达，结果没办法把自己的æ€

2820è·¯ç”¨è‹±æ–‡è®²æ¸…楚。
2821
2822这种情况通常发生在一些很具体的时刻：
2823
2824- 明明知道自己想做什么，但开头一句说不出来
2825- 太快开始写代码，忘了先澄清题目
2826- 发现自己写错了，但不知道怎么自然地说出来
2827- 系统设计思路其实没问题，但讲 tradeoff 时要么太硬，要么太空
2828- 行为面试经历本身不错，但英文表达太平，没把你的作用讲出来
2829
2830这时候，”技术面试英语表达”就有用了。
2831
2832不是说背一份表达集合就能拿 offer。当然不能。
2833
2834但合适的表达，能帮你在压力下更稳、更清楚地把自己原本就会的东西说出来。
2835
2836所以我们整理了这份[技术面试表达合集](/collections/technical-interview-expressions)。目标很简单：帮中文背景的软件工程师，在真实面试场景里把英文说得更清楚一点。
2837
2838## 技术面试英语，真正起作用的地方在哪？
2839
2840技术面试英语不是为了让你听起来很高级。
2841
2842它更实际的作用有三点：
2843
28441. 帮你在答案开头说顺
28452. 让面试官跟上你的思路
28463. 紧张时依然显得冷静、专业
2847
2848一段英文能做到这三点，通常就够用了。
2849
2850## 1. 先澄清问题，不要急着做
2851
2852很多人一拿到题就马上开始解。
2853
2854但在很多技术面试里，更好的做法是先慢下来，用几秒钟把关键问题问清楚。
2855
2856比如这句：
2857
2858> "Before I jump into a solution, I'd like to clarify the scope and the main constraints."
2859
2860这句话的好处很直接：显得有条理，同时也给自己争取了一点思考时间。
2861
2862如果是系统设计题，这句也很常用：
2863
2864> "For this system, are we optimizing mainly for latency, throughput, or cost?"
2865
2866这类表达的价值在于，它让面试官知道你明白：系统设计没有脱离目标的标准答案。
2867
2868这一部分最重要的点其实只有一个：
2869
2870不要急着显得很快，先让自己显得很清楚。
2871
2872## 2. 算法题里，要把思路一小步一小步说出来
2873
2874很多候选人在做算法题时太安静了。
2875
2876这很吃亏——面试官根本不知道你脑子里在发生什么。
2877
2878更好的做法，是把推理过程分成几个小步骤说出来。
2879
2880例如：
2881
2882> "My first thought is a brute-force approach, just to establish a correct baseline."
2883
2884这句话很有用，因为它听起来很正常——你不是假装一上来就看到了最优解，而是先给一个正确的起点。
2885
2886还有一句也很常用：
2887
2888> "Let me dry-run this on a small example to make sure the transitions actually hold."
2889
2890当逻辑开始变复杂时，这种表达很有价值。它告诉面试官，你在主动验证自己的推导，而不是凭感觉往下写。
2891
2892如果一时卡住了，也不用硬撑着沉默。可以这样说：
2893
2894> "I'm a bit stuck on the next step. Could you give me a small nudge rather than the full solution?"
2895
2896这比完全沉默好很多，也体现了你还是想自己把题推下去。
2897
2898## 3. 发现 bug 之后，直接说，别慌
2899
2900技术面试里另一个难的点，是出错之后怎么接。
2901
2902很多人一发现自己写错了就开始紧张，然后解释越来越乱。通常这只会让场面更糟。
2903
2904更好的方式是短一点、稳一点：
2905
2906> "I just spotted a bug in my logic. Let me fix that before I build on top of it."
2907
2908这类表达好用，是因为它听起来像在负责，而不是在辩解。
2909
2910面试官通常并不要求你完全不犯错。他们更想看的是：你发现错误以后，怎么处理。
2911
2912## 4. 系统设计里，真正拉开差距的是 tradeoff 表达
2913
2914系统设计面试里，很多时候问题不在于你有没有想法，在于你怎么把权衡讲出来。
2915
2916表达太绝对，容易显得不够成熟。
2917
2918比如，比起直接说“这里加缓存”，下面这种说法会更好：
2919
2920> "A cache would cut read latency, but we'd need a clear invalidation strategy to keep the data trustworthy."
2921
2922这句话的好处在于，它一口气把好处和代价都说出来了。
2923
2924再比如：
2925
2926> "I'd put a queue between these services so traffic spikes don't directly overwhelm the downstream system."
2927
2928这句也很好，因为它解释了为什么要加队列，而不是只停留在“为了异步”这种比较空的说法上。
2929

2930系统设计英语很多时候并不复杂，本质上只是三件事：
2931
2932- 加这个东西以后，什么会变好？
2933- 它会带来什么新问题？
2934- 你打算怎么处理这个新问题？
2935
2936这三件事说清楚了，答案通常就会强很多。
2937
2938## 5. 行为面试里，不要堆大词，先把动作讲清楚
2939
2940行为面试也是很多人容易低估自己的地方。
2941
2942问题往往不在经历本身，在于英文一讲出来就变太抽象了。
2943
2944例如：
2945
2946> "When we had a production incident, I took ownership of the response, coordinated the fix, and wrote the follow-up."
2947
2948这句话强，是因为动作很具体。
2949
2950还有一句也很好：
2951
2952> "Instead of debating in abstract, I built a small prototype so the team could react to something concrete."
2953
2954它的好处在于，不夸张，也不空泛，只是很清楚地说明了你做了什么、为什么有用。
2955
2956行为面试里，简单英文往往比”听起来很厉害但很空”更好。
2957
2958## 6. 你不需要 500 句，你需要的是对的那一批
2959
2960大多数候选人其实不需要一整套庞大的面试台词。
2961
2962需要的是一小批真正会反复出现的表达，比如：
2963
2964- 开场自我介绍
2965- 澄清题目
2966- 讲算法思路
2967- 请求提示
2968- 发现 bug 之后怎么接
2969- 解释系统设计 tradeoff
2970- 回答 ownership 或冲突问题
2971- 收尾总结
2972
2973这正是[技术面试表达合集](/collections/technical-interview-expressions)在做的事情。
2974
2975它不是在承诺”看完这份集合就能过面试”。只是把那些反复出现的真实面试时刻整理出来，给你一套更容易上手的表达参考。
2976
2977如果你不确定有没有用，先看公开预览，再决定要不要继续看完整版。
2978
2979## 7. 怎么练，才不会像背模板？
2980
2981重点不是把每句都背下来。
2982
2983更好的方法通常是：
2984
29851. 先找一个你最容易卡住的面试场景
29862. 只学这个场景下两三句真正有用的表达
29873. 用你自己的例子把它们说几遍
29884. 练的是结构，不是死记原句
2989
2990比如，系统设计题不是要你为每个题目都背一份完整答案。
2991
2992你更应该熟悉的是这些“句型骨架”：
2993
2994- "Before I jump into a solution..."
2995- "My first thought is..."
2996- "The benefit is..., but the tradeoff is..."
2997- "I just spotted a bug..."
2998- "In production, I would also add..."
2999
3000这样用起来会自然得多。
3001
3002## 最后
3003
3004如果你正在准备英文技术面试，这类表达合集确实有帮助。
3005
3006不是因为它能替代你的技术能力、判断力和真实经历。
3007
3008而是它能帮你在关键时刻，把这些东西讲得更清楚。
3009
3010如果这正是你需要的，先看看这份[技术面试表达合集](/collections/technical-interview-expressions)。先看预览，再决定适不适合你。
3011`,te=`---
3012title: "Nuevo: usa skills para convertir tu trabajo como desarrollador en material de aprendizaje de idiomas"
3013description: "LangCapture ahora funciona con agentes que soportan skills, y este artículo incluye el skill completo de aprendizaje de idiomas para convertir discusiones de ingeniería en expresiones reutilizables en tu idioma objetivo."
3014image: /og.png
3015date: "2026-03-14"
3016published: true
3017categories: [product-updates]
3018author: langcapture
3019---
3020
3021Los desarrolladores ya pasan el día rodeados de lenguaje útil.
3022
3023Aparece en comentarios de pull requests, notas de depuración, hilos de issues, discusiones de releases, compromisos de arquitectura y conversaciones con agentes que ayudan con el trabajo de código. El problema no es la falta de material de aprendizaje. El problema es que ese material está disperso a lo largo de la jornada y rara vez se convierte en algo que puedas repasar después.
3024
3025## El lenguaje más útil ya está dentro de tu flujo de trabajo
3026
3027Si eres ingeniero, el lenguaje que más necesitas normalmente no viene de un libro de texto.
3028
3029Es el lenguaje que usas para explicar un bug, pedir una revisión, describir el riesgo de una migración, cuestionar el alcance o resumir resultados de pruebas. Esas son las frases que importan en el trabajo real, y también son las más difíciles de coleccionar de forma consistente porque desaparecen dentro de las herramientas y conversaciones.
3030
3031## Qué hace un skill en este flujo de trabajo
3032
3033En este contexto, un skill es un archivo de instrucciones reutilizable para un agente que soporta skills.
3034

3035En lugar de reescribir el mismo prompt cada vez, guardas el flujo una sola vez y dejas que el agente lo reutilice. Para LangCapture, eso significa que el agente puede revisar la conversación o el contexto de trabajo actual, extraer de 1 a 5 expresiones útiles en tu idioma objetivo, pedir confirmación y subir las líneas aprobadas a LangCapture.
3036
3037Precisamente por esto el flujo es especialmente amigable para desarrolladores: el material de aprendizaje sale directamente del trabajo real de ingeniería.
3038
3039## El skill \`language-learning\` completo
3040
3041Abajo está el contenido completo del skill. Guárdalo como \`language-learning/SKILL.md\` dentro del directorio de skills de cualquier sistema de agentes que los soporte, y luego reemplaza el placeholder del token con tu propio token de API de LangCapture. El paso de subida incluye patrones de comando tanto para Windows como para macOS/Linux.
3042
3043\`\`\`\`md
3044---
3045name: language-learning
3046description: |
3047  Extract 1-5 reusable workplace expressions in the target language from the current conversation, ask the user which ones to keep, and upload the approved sentences to LangCapture. Use when the user asks to "extraer expresiones", "aprender inglés", "subir a LangCapture", "organizar frases", "recopilar material de idiomas", or similar requests about reviewing the current session and turning it into language learning material.
3048---
3049
3050# Language Learning
3051
3052Extract concise, reusable workplace language from the current chat. Confirm with the user before uploading anything to LangCapture.
3053
3054## Workflow
3055
3056### 1. Review the current session
3057
3058Read the conversation history in the current session. Identify the main work topics being discussed, such as debugging, implementation, status updates, review feedback, deployment, testing, or coordination.
3059
3060Think from the perspective of explaining the same work to a coworker who speaks your target language. Prefer expressions that are likely to be reused in engineering conversations.
3061
3062### 2. Extract 1-5 useful expressions
3063
3064Select only sentences that are:
3065
3066- Natural workplace language
3067- Reusable without depending on hidden context
3068- Useful for engineers discussing progress, issues, requests, review, testing, or results
3069- Concise enough to remember and practice
3070
3071Avoid sentences that are:
3072
3073- Overly academic or textbook-like
3074- Too specific to internal file names, secrets, or one-off details
3075- Unclear without extra explanation
3076
3077For each item, output:
3078
30791. The sentence in the target language
30802. A short native-language note describing meaning or usage
3081
3082Use this format:
3083
3084~~~text
30851. "The latest change fixes the retry path, but I still need to verify the error handling."
3086   -> Sirve para reportar el avance de una corrección y señalar lo que falta por verificar
3087~~~
3088
3089If the session does not contain enough good material, say so directly instead of inventing weak examples.
3090
3091### 3. Ask for confirmation before upload
3092
3093After listing the extracted expressions, ask the user which ones to upload.
3094
3095If an interactive question tool is available, use it with these options:
3096
3097- All upload
3098- Choose specific items
3099- Skip
3100
3101If no such tool is available, ask a short plain-text question that offers the same three choices.
3102
3103Do not upload anything until the user confirms.
3104
3105If the user skips, stop immediately.
3106
3107### 4. Upload the approved expressions to LangCapture
3108
3109Upload each approved sentence individually.
3110
3111Prefer using the local shell tool. Use the command pattern that matches the current platform.
3112
3113Windows (PowerShell):
3114
3115~~~powershell
3116$body = @{ original_text = "<SENTENCE>" } | ConvertTo-Json -Compress
3117try {
3118  (Invoke-WebRequest \`
3119    -Method POST \`
3120    -Uri 'https://langcapture.com/api/sentences' \`
3121    -Headers @{
3122      Authorization = 'Bearer <YOUR_LANGCAPTURE_API_TOKEN>'
3123    } \`
3124    -ContentType 'application/json' \`
3125    -Body $body
3126  ).StatusCode
3127} catch {
3128  $_.Exception.Response.StatusCode.value__
3129}
3130~~~
3131
3132macOS/Linux (bash/zsh/sh):
3133
3134~~~sh
3135python3 -c "
3136import json, subprocess, sys
3137sentence = sys.argv[1]
3138payload = json.dumps({'original_text': sentence})
3139result = subprocess.run([
3140    'curl', '-s', '-o', '/dev/null', '-w', '%{http_code}',
3141    '-X', 'POST', 'https://langcapture.com/api/sentences',
3142    '-H', 'Content-Type: application/json',
3143    '-H', 'Authorization: Bearer <YOUR_LANGCAPTURE_API_TOKEN>',
3144    '--data', payload
3145], capture_output=True, text=True)
3146print(result.stdout.strip())
3147" "<SENTENCE>"
3148~~~
3149
3150Treat \`200\` as success.
3151
3152If one sentence fails, report it and continue with the remaining approved sentences.
3153
3154### 5. Summarize the result
3155
3156List each approved sentence with its upload result:
3157
3158- Uploaded successfully
3159- Failed with HTTP status code
3160
3161State clearly how many items were uploaded and how many failed.
3162
3163## Quality rules
3164
3165- Prefer realistic workplace language over polished textbook language.
3166- Keep the list short and high-signal.
3167- Require user confirmation before upload.
3168- Use the current session only; do not fabricate conversation context.
3169- Treat the API token as sensitive. Use it only for the LangCapture upload request and do not expose it unnecessarily in the final user-facing summary.
3170\`\`\`\`
3171
3172## Por qué esto es especialmente útil para desarrolladores
3173
3174La comunicación entre desarrolladores es altamente contextual.
3175
3176Una frase es útil no porque suene impresionante, sino porque te ayuda a hacer bien un trabajo específico. Puedes necesitar lenguaje para:
3177
3178- dar una actualización de avance clara
3179- explicar la causa raíz de un bug
3180- pedirle a alguien que revise un cambio
3181- discutir compromisos antes de un release
3182- alinearse sobre alcance, despliegue o cobertura de pruebas
3183
3184Cuando esas expresiones salen directamente de tu trabajo real de ingeniería, son más fáciles de entender, más fáciles de recordar y mucho más probables de reutilizar.
3185
3186## Cómo funciona el flujo de trabajo
3187
3188El flujo se mantiene simple:
3189
31901. Trabaja dentro de tus herramientas habituales o dentro de una conversación con un agente.
31912. Instala este skill en el agente que ya usas.
31923. Pídele al agente que extraiga expresiones útiles del contexto actual.
31934. Confirma qué líneas vale la pena guardar.
31945. Deja que el skill las suba a LangCapture.
3195
3196Eso significa que LangCapture no es solo un lugar para almacenar frases al azar. Se convierte en una biblioteca estructurada de expresiones que salieron de tu trabajo real de desarrollo.
3197
3198Si quieres la historia general del producto, empieza con [Convierte el lenguaje real de tu trabajo en tu biblioteca personal de aprendizaje](/blog/introducing-langcapture).
3199
3200Si quieres más ideas de flujos de captura, lee [Cómo capturar frases útiles de GitHub, Slack, Jira y el correo](/blog/how-to-capture-useful-chinese-english-sentences-from-github-slack-jira-and-email).
3201
3202Para probar este flujo tú mismo, genera un token en la [configuración de tokens de API](/settings/tokens), pégalo en el skill y conecta LangCapture al flujo basado en skills que ya usas.
3203`,oe=`---
3204title: "新機能：Skills で開発業務を語学学習の教材に変える"
3205description: "LangCapture が skills 対応のエージェントと連携できるようになりました。本記事では、エンジニアリングの議論を再利用可能な学習対象言語の表現に変えるための language-learning skill の全文を公開します。"
3206image: /og.png
3207date: "2026-03-14"
3208published: true
3209categories: [product-updates]
3210author: langcapture
3211---
3212
3213開発者は、すでに「使える言葉」に囲まれて毎日を過ごしています。
3214
3215プルリクエストのコメント、デバッグのメモ、Issue のスレッド、リリースに関する議論、アーキテクチャのトレードオフ、そしてコーディングを手伝うエージェントとの会話。問題は学習素材が足りないことでã

3215¯ã‚りません。その素材が一日の仕事のあちこちに散らばっていて、後から本当に復習できる形になることがほとんどない、ということです。
3216
3217## 最も役立つ言葉は、すでにワークフローの中にある
3218
3219エンジニアにとって、本当に必要な言葉はたいてい教科書の中にはありません。
3220
3221バグを説明する、レビューを依頼する、マイグレーションのリスクを述べる、スコープに反論する、テスト結果を要約する — そのために使う言葉こそが必要なのです。実際の仕事で重要なのはこうしたフレーズですが、ツールや会話の中に消えていくため、継続的に集めるのが最も難しいフレーズでもあります。
3222
3223## このワークフローにおける skill の役割
3224
3225このセットアップにおける skill とは、skills をサポートするエージェント向けの、再利用可能な指示ファイルです。
3226
3227毎回同じプロンプトを書き直す代わりに、ワークフローを一度保存してエージェントに再利用させます。LangCapture の場合、エージェントは現在の会話や作業コンテキストを振り返り、学習対象言語の有用な表現を 1〜5 個抽出し、確認を求めたうえで、承認された文を LangCapture にアップロードできます。
3228
3229学習素材が実際のエンジニアリング業務から直接生まれる — だからこそ、このワークフローは開発者にとって特に相性が良いのです。
3230
3231## \`language-learning\` skill の全文
3232
3233以下が skill の全文です。skills をサポートする任意のエージェントシステムの skill ディレクトリに \`language-learning/SKILL.md\` として保存し、トークンのプレースホルダーをご自身の LangCapture API トークンに置き換えてください。アップロードのステップには、Windows と macOS/Linux の両方のコマンドパターンが含まれています。
3234
3235\`\`\`\`md
3236---
3237name: language-learning
3238description: |
3239  Extract 1-5 reusable workplace expressions in the target language from the current conversation, ask the user which ones to keep, and upload the approved sentences to LangCapture. Use when the user asks to "提炼表达", "提取外语表达", "学习外语", "上传到 LangCapture", "整理句子", "收集语言素材", or similar requests about reviewing the current session and turning it into language learning material.
3240---
3241
3242# Language Learning
3243
3244Extract concise, reusable workplace language from the current chat. Confirm with the user before uploading anything to LangCapture.
3245
3246## Workflow
3247
3248### 1. Review the current session
3249
3250Read the conversation history in the current session. Identify the main work topics being discussed, such as debugging, implementation, status updates, review feedback, deployment, testing, or coordination.
3251
3252Think from the perspective of explaining the same work to a coworker who speaks your target language. Prefer expressions that are likely to be reused in engineering conversations.
3253
3254### 2. Extract 1-5 useful expressions
3255
3256Select only sentences that are:
3257
3258- Natural workplace language
3259- Reusable without depending on hidden context
3260- Useful for engineers discussing progress, issues, requests, review, testing, or results
3261- Concise enough to remember and practice
3262
3263Avoid sentences that are:
3264
3265- Overly academic or textbook-like
3266- Too specific to internal file names, secrets, or one-off details
3267- Unclear without extra explanation
3268
3269For each item, output:
3270
32711. The sentence in the target language
32722. A short native-language note describing meaning or usage
3273
3274Use this format:
3275
3276~~~text
32771. "The latest change fixes the retry path, but I still need to verify the error handling."
3278   -> 用于汇报修复进展，同时说明还有待验证的部分
3279~~~
3280
3281If the session does not contain enough good material, say so directly instead of inventing weak examples.
3282
3283### 3. Ask for confirmation before upload
3284
3285After listing the extracted expressions, ask the user which ones to upload.
3286
3287If an interactive question tool is available, use it with these options:
3288
3289- All upload
3290- Choose specific items
3291- Skip
3292
3293If no such tool is available, ask a short plain-text question that offers the same three choices.
3294
3295Do not upload anything until the user confirms.
3296
3297If the user skips, stop immediately.
3298
3299### 4. Upload the approved expressions to LangCapture
3300
3301Upload each approved sentence individually.
3302
3303Prefer using the local shell tool. Use the command pattern that matches the current platform.
3304
3305Windows (PowerShell):
3306
3307~~~powershell
3308$body = @{ original_text = "<SENTENCE>" } | ConvertTo-Json -Compress
3309try {
3310  (Invoke-WebRequest \`
3311    -Method POST \`
3312    -Uri 'https://langcapture.com/api/sentences' \`
3313    -Headers @{
3314      Authorization = 'Bearer <YOUR_LANGCAPTURE_API_TOKEN>'
3315    } \`
3316    -ContentType 'application/json' \`
3317    -Body $body
3318  ).StatusCode
3319} catch {
3320  $_.Exception.Response.StatusCode.value__
3321}
3322~~~
3323
3324macOS/Linux (bash/zsh/sh):
3325
3326~~~sh
3327python3 -c "
3328import json, subprocess, sys
3329sentence = sys.argv[1]
3330payload = json.dumps({'original_text': sentence})
3331result = subprocess.run([
3332    'curl', '-s', '-o', '/dev/null', '-w', '%{http_code}',
3333    '-X', 'POST', 'https://langcapture.com/api/sentences',
3334    '-H', 'Content-Type: application/json',
3335    '-H', 'Authorization: Bearer <YOUR_LANGCAPTURE_API_TOKEN>',
3336    '--data', payload
3337], capture_output=True, text=True)
3338print(result.stdout.strip())
3339" "<SENTENCE>"
3340~~~
3341
3342Treat \`200\` as success.
3343
3344If one sentence fails, report it and continue with the remaining approved sentences.
3345
3346### 5. Summarize the result
3347
3348List each approved sentence with its upload result:
3349
3350- Uploaded successfully
3351- Failed with HTTP status code
3352
3353State clearly how many items were uploaded and how many failed.
3354
3355## Quality rules
3356
3357- Prefer realistic workplace language over polished textbook language.
3358- Keep the list short and high-signal.
3359- Require user confirmation before upload.
3360- Use the current session only; do not fabricate conversation context.
3361- Treat the API token as sensitive. Use it only for the LangCapture upload request and do not expose it unnecessarily in the final user-facing summary.
3362\`\`\`\`
3363
3364## なぜ開発者にとって特に有用なのか
3365
3366開発者のコミュニケーションは、文脈への依存度が非常に高いものです。
3367
3368ある文が役立つのは、立派に聞こえるからではなく、特定の仕事をうまくこなす助けになるからです。例えば、次のような場面の言葉が必要になるでしょう。
3369
3370- わかりやすい進捗報告をする
3371- バグの根本原因を説明する
3372- 変更のレビューを依頼する
3373- リリース前にトレードオフを議論する
3374- スコープ、ロールアウト、テストカバレッジについて認識を合わせる
3375
3376こうした表現が自分の実際のエンジニアリング業務から直接得られたものであれば、理解しやすく、覚えやすく、再利用される可能性もずっと高くなります。
3377
3378## ワークフローの流れ
3379
3380フローはあくまでシンプルです。
3381
33821. いつものツールの中、あるいはエージェントとの会話の中で仕事をする。

33832. すでに使っているエージェントにこの skill をインストールする。
33843. 現在のコンテキストから有用な表現を抽出するようエージェントに頼む。
33854. 保存する価値のある文を確認する。
33865. skill に LangCapture へのアップロードを任せる。
3387
3388つまり LangCapture は、雑多な文をしまっておくだけの場所ではなくなります。あなたの実際の開発業務から生まれた表現が、構造化されたライブラリとして蓄積されていくのです。
3389
3390プロダクト全体のストーリーを知りたい方は、[職場のリアルな英語を、自分だけの学習ライブラリに変えよう](/blog/introducing-langcapture)からどうぞ。
3391
3392キャプチャワークフローのアイデアをもっと知りたい方は、[GitHub・Slack・Jira・メールから「使える英文」をキャプチャする方法](/blog/how-to-capture-useful-chinese-english-sentences-from-github-slack-jira-and-email)をお読みください。
3393
3394このワークフローを試すには、[API トークン設定](/settings/tokens)でトークンを生成して skill に貼り付け、すでにお使いの skill ベースのワークフローに LangCapture を接続してください。
3395`,se=`---
3396title: "신기능: 스킬로 개발 업무를 언어 학습 자료로 바꾸세요"
3397description: "LangCapture가 이제 스킬을 지원하는 에이전트와 함께 동작합니다. 엔지니어링 논의를 재사용 가능한 학습 언어 표현으로 바꿔 주는 언어 학습 스킬 전문을 이 글에 담았습니다."
3398image: /og.png
3399date: "2026-03-14"
3400published: true
3401categories: [product-updates]
3402author: langcapture
3403---
3404
3405개발자는 이미 하루 종일 쓸모 있는 언어에 둘러싸여 있습니다.
3406
3407풀 리퀘스트 코멘트, 디버깅 노트, 이슈 스레드, 릴리스 논의, 아키텍처 트레이드오프, 그리고 코딩 작업을 돕는 에이전트와의 대화 곳곳에 그런 언어가 등장합니다. 문제는 학습 자료가 부족한 것이 아닙니다. 이 자료가 하루 업무 곳곳에 흩어져 있어서, 나중에 실제로 복습할 수 있는 형태로 정리되는 일이 거의 없다는 것이 문제입니다.
3408
3409## 가장 쓸모 있는 언어는 이미 워크플로 안에 있습니다
3410
3411엔지니어라면, 가장 필요한 언어는 대개 교과서에서 나오지 않습니다.
3412
3413버그를 설명하고, 리뷰를 요청하고, 마이그레이션 리스크를 기술하고, 범위 확장에 반대 의견을 내고, 테스트 결과를 요약할 때 쓰는 언어입니다. 실제 업무에서 중요한 표현은 바로 이런 것들인데, 도구와 대화 속으로 사라져 버리기 때문에 꾸준히 모으기가 가장 어렵기도 합니다.
3414
3415## 이 워크플로에서 스킬이 하는 일
3416
3417여기서 스킬이란, 스킬을 지원하는 에이전트를 위한 재사용 가능한 지시 파일을 말합니다.
3418
3419매번 같은 프롬프트를 다시 쓰는 대신, 워크플로를 한 번 저장해 두고 에이전트가 재사용하게 합니다. LangCapture의 경우, 에이전트가 현재 대화나 작업 맥락을 검토해 학습 언어로 된 유용한 표현을 1~5개 추출하고, 사용자 확인을 거친 뒤 승인된 문장을 LangCapture에 업로드한다는 뜻입니다.
3420
3421학습 자료가 실제 엔지니어링 업무에서 곧바로 나오기 때문에, 이 워크플로는 특히 개발자에게 잘 맞습니다.
3422
3423## \`language-learning\` 스킬 전문
3424
3425아래는 스킬 전체 내용입니다. 스킬을 지원하는 에이전트 시스템의 스킬 디렉터리에 \`language-learning/SKILL.md\`로 저장한 뒤, 토큰 자리표시자를 본인의 LangCapture API 토큰으로 교체하세요. 업로드 단계에는 Windows와 macOS/Linux 명령 패턴이 모두 포함되어 있습니다.
3426
3427\`\`\`\`md
3428---
3429name: language-learning
3430description: |
3431  Extract 1-5 reusable workplace expressions in the target language from the current conversation, ask the user which ones to keep, and upload the approved sentences to LangCapture. Use when the user asks to "표현 추출", "외국어 표현 정리", "외국어 학습", "LangCapture에 업로드", "문장 정리", "언어 자료 수집", or similar requests about reviewing the current session and turning it into language learning material.
3432---
3433
3434# Language Learning
3435
3436Extract concise, reusable workplace language from the current chat. Confirm with the user before uploading anything to LangCapture.
3437
3438## Workflow
3439
3440### 1. Review the current session
3441
3442Read the conversation history in the current session. Identify the main work topics being discussed, such as debugging, implementation, status updates, review feedback, deployment, testing, or coordination.
3443
3444Think from the perspective of explaining the same work to a coworker who speaks your target language. Prefer expressions that are likely to be reused in engineering conversations.
3445
3446### 2. Extract 1-5 useful expressions
3447
3448Select only sentences that are:
3449
3450- Natural workplace language
3451- Reusable without depending on hidden context
3452- Useful for engineers discussing progress, issues, requests, review, testing, or results
3453- Concise enough to remember and practice
3454
3455Avoid sentences that are:
3456
3457- Overly academic or textbook-like
3458- Too specific to internal file names, secrets, or one-off details
3459- Unclear without extra explanation
3460
3461For each item, output:
3462
34631. The sentence in the target language
34642. A short native-language note describing meaning or usage
3465
3466Use this format:
3467
3468~~~text
34691. "The latest change fixes the retry path, but I still need to verify the error handling."
3470   -> 수정 진행 상황을 보고하면서 아직 검증이 남은 부분을 함께 알리는 표현
3471~~~
3472
3473If the session does not contain enough good material, say so directly instead of inventing weak examples.
3474

3475### 3. Ask for confirmation before upload
3476
3477After listing the extracted expressions, ask the user which ones to upload.
3478
3479If an interactive question tool is available, use it with these options:
3480
3481- All upload
3482- Choose specific items
3483- Skip
3484
3485If no such tool is available, ask a short plain-text question that offers the same three choices.
3486
3487Do not upload anything until the user confirms.
3488
3489If the user skips, stop immediately.
3490
3491### 4. Upload the approved expressions to LangCapture
3492
3493Upload each approved sentence individually.
3494
3495Prefer using the local shell tool. Use the command pattern that matches the current platform.
3496
3497Windows (PowerShell):
3498
3499~~~powershell
3500$body = @{ original_text = "<SENTENCE>" } | ConvertTo-Json -Compress
3501try {
3502  (Invoke-WebRequest \`
3503    -Method POST \`
3504    -Uri 'https://langcapture.com/api/sentences' \`
3505    -Headers @{
3506      Authorization = 'Bearer <YOUR_LANGCAPTURE_API_TOKEN>'
3507    } \`
3508    -ContentType 'application/json' \`
3509    -Body $body
3510  ).StatusCode
3511} catch {
3512  $_.Exception.Response.StatusCode.value__
3513}
3514~~~
3515
3516macOS/Linux (bash/zsh/sh):
3517
3518~~~sh
3519python3 -c "
3520import json, subprocess, sys
3521sentence = sys.argv[1]
3522payload = json.dumps({'original_text': sentence})
3523result = subprocess.run([
3524    'curl', '-s', '-o', '/dev/null', '-w', '%{http_code}',
3525    '-X', 'POST', 'https://langcapture.com/api/sentences',
3526    '-H', 'Content-Type: application/json',
3527    '-H', 'Authorization: Bearer <YOUR_LANGCAPTURE_API_TOKEN>',
3528    '--data', payload
3529], capture_output=True, text=True)
3530print(result.stdout.strip())
3531" "<SENTENCE>"
3532~~~
3533
3534Treat \`200\` as success.
3535
3536If one sentence fails, report it and continue with the remaining approved sentences.
3537
3538### 5. Summarize the result
3539
3540List each approved sentence with its upload result:
3541
3542- Uploaded successfully
3543- Failed with HTTP status code
3544
3545State clearly how many items were uploaded and how many failed.
3546
3547## Quality rules
3548
3549- Prefer realistic workplace language over polished textbook language.
3550- Keep the list short and high-signal.
3551- Require user confirmation before upload.
3552- Use the current session only; do not fabricate conversation context.
3553- Treat the API token as sensitive. Use it only for the LangCapture upload request and do not expose it unnecessarily in the final user-facing summary.
3554\`\`\`\`
3555
3556## 개발자에게 특히 유용한 이유
3557
3558개발자 커뮤니케이션은 맥락 의존도가 매우 높습니다.
3559
3560어떤 문장이 유용한 이유는 멋있게 들려서가 아니라, 특정한 일을 잘 해내는 데 도움이 되기 때문입니다. 이런 상황에 쓸 언어가 필요할 수 있습니다:
3561
3562- 명확한 진행 상황 공유
3563- 버그의 근본 원인 설명
3564- 변경 사항 리뷰 요청
3565- 릴리스 전 트레이드오프 논의
3566- 범위, 롤아웃, 테스트 커버리지에 대한 합의
3567
3568이런 표현이 실제 엔지니어링 업무에서 직접 나온 것이라면, 이해하기도 쉽고 기억하기도 쉬우며 다시 쓰게 될 가능성도 훨씬 높아집니다.
3569
3570## 워크플로 동작 방식
3571
3572흐름은 단순합니다:
3573
35741. 평소 쓰는 도구나 에이전트 대화 안에서 일합니다.
35752. 이미 사용 중인 에이전트에 이 스킬을 설치합니다.
35763. 현재 맥락에서 유용한 표현을 추출해 달라고 에이전트에 요청합니다.
35774. 어떤 문장을 저장할지 확인합니다.
35785. 스킬이 LangCapture에 업로드하도록 둡니다.
3579
3580이렇게 하면 LangCapture는 아무 문장이나 쌓아 두는 곳이 아니라, 실제 개발 업무에서 나온 표현들을 체계적으로 모은 라이브러리가 됩니다.
3581
3582제품의 큰 그림이 궁금하다면 [실제 업무 속 언어를 나만의 학습 라이브러리로](/blog/introducing-langcapture)부터 시작하세요.
3583
3584캡처 워크플로에 대한 아이디어가 더 필요하다면 [GitHub, Slack, Jira, 이메일에서 쓸모 있는 문장을 캡처하는 방법](/blog/how-to-capture-useful-chinese-english-sentences-from-github-slack-jira-and-email)을 읽어 보세요.
3585
3586이 워크플로를 직접 써 보려면 [API 토큰 설정](/settings/tokens)에서 토큰을 생성해 스킬에 붙여넣고, 이미 사용 중인 스킬 기반 워크플로에 LangCapture를 연결하세요.
3587`,re=`---
3588title: "New: Use Skills to Turn Developer Work into Language Learning Material"
3589description: "LangCapture now works with agents that support skills, and this post includes the full language-learning skill you can use to turn engineering discussions into reusable target-language expressions."
3590image: /og.png
3591date: "2026-03-14"
3592published: true
3593categories: [product-updates]
3594author: langcapture
3595---
3596
3597Developers already spend their day surrounded by useful language.
3598
3599It appears in pull request comments, debugging notes, issue threads, release discussions, architecture tradeoffs, and conversations with agents that help with coding work. The problem is not a lack of learning material. The problem is that this material is scattered across the workday and rarely gets turned into something you can actually review later.
3600
3601## The Most Useful Language Is Already Inside Your Workflow
3602
3603If you are an engineer, the language you need most is usually not from a textbook.
3604
3605It is the language you use to explain a bug, ask for review, describe a migration risk, push back on scope, or summarize test results. These are the phrases that matter in real work, and they are also the hardest ones to collect consistently because they disappear inside tools and conversations.
3606
3607## What a Skill Does in This Workflow
3608
3609In this setup, a skill is a reusable instruction file for an agent that supports skills.
3610
3611Instead of rewriting the same prompt every time, you save the workflow once and let the agent reuse it. For LangCapture, that means the agent can review the current conversation or work context, extract 1 to 5 useful expressions in your target language, ask for confirmation, and upload the approved lines to LangCapture.
3612
3613This is exactly why the workflow is especially friendly for developers: the learning material comes directly from real engineering work.
3614
3615## The Full \`language-learning\` Skill
3616
3617Below is the full skill content. Save it as \`language-learning/SKILL.md\` inside the skill directory of any agent system that supports skills, then replace the token placeholder with your own 

3617LangCapture API token. The upload step includes both Windows and macOS/Linux command patterns.
3618
3619\`\`\`\`md
3620---
3621name: language-learning
3622description: |
3623  Extract 1-5 reusable workplace expressions in the target language from the current conversation, ask the user which ones to keep, and upload the approved sentences to LangCapture. Use when the user asks to "提炼表达", "提取外语表达", "学习外语", "上传到 LangCapture", "整理句子", "收集语言素材", or similar requests about reviewing the current session and turning it into language learning material.
3624---
3625
3626# Language Learning
3627
3628Extract concise, reusable workplace language from the current chat. Confirm with the user before uploading anything to LangCapture.
3629
3630## Workflow
3631
3632### 1. Review the current session
3633
3634Read the conversation history in the current session. Identify the main work topics being discussed, such as debugging, implementation, status updates, review feedback, deployment, testing, or coordination.
3635
3636Think from the perspective of explaining the same work to a coworker who speaks your target language. Prefer expressions that are likely to be reused in engineering conversations.
3637
3638### 2. Extract 1-5 useful expressions
3639
3640Select only sentences that are:
3641
3642- Natural workplace language
3643- Reusable without depending on hidden context
3644- Useful for engineers discussing progress, issues, requests, review, testing, or results
3645- Concise enough to remember and practice
3646
3647Avoid sentences that are:
3648
3649- Overly academic or textbook-like
3650- Too specific to internal file names, secrets, or one-off details
3651- Unclear without extra explanation
3652
3653For each item, output:
3654
36551. The sentence in the target language
36562. A short native-language note describing meaning or usage
3657
3658Use this format:
3659
3660~~~text
36611. "The latest change fixes the retry path, but I still need to verify the error handling."
3662   -> 用于汇报修复进展，同时说明还有待验证的部分
3663~~~
3664
3665If the session does not contain enough good material, say so directly instead of inventing weak examples.
3666
3667### 3. Ask for confirmation before upload
3668
3669After listing the extracted expressions, ask the user which ones to upload.
3670
3671If an interactive question tool is available, use it with these options:
3672
3673- All upload
3674- Choose specific items
3675- Skip
3676
3677If no such tool is available, ask a short plain-text question that offers the same three choices.
3678
3679Do not upload anything until the user confirms.
3680
3681If the user skips, stop immediately.
3682
3683### 4. Upload the approved expressions to LangCapture
3684
3685Upload each approved sentence individually.
3686
3687Prefer using the local shell tool. Use the command pattern that matches the current platform.
3688
3689Windows (PowerShell):
3690
3691~~~powershell
3692$body = @{ original_text = "<SENTENCE>" } | ConvertTo-Json -Compress
3693try {
3694  (Invoke-WebRequest \`
3695    -Method POST \`
3696    -Uri 'https://langcapture.com/api/sentences' \`
3697    -Headers @{
3698      Authorization = 'Bearer <YOUR_LANGCAPTURE_API_TOKEN>'
3699    } \`
3700    -ContentType 'application/json' \`
3701    -Body $body
3702  ).StatusCode
3703} catch {
3704  $_.Exception.Response.StatusCode.value__
3705}
3706~~~
3707
3708macOS/Linux (bash/zsh/sh):
3709
3710~~~sh
3711python3 -c "
3712import json, subprocess, sys
3713sentence = sys.argv[1]
3714payload = json.dumps({'original_text': sentence})
3715result = subprocess.run([
3716    'curl', '-s', '-o', '/dev/null', '-w', '%{http_code}',
3717    '-X', 'POST', 'https://langcapture.com/api/sentences',
3718    '-H', 'Content-Type: application/json',
3719    '-H', 'Authorization: Bearer <YOUR_LANGCAPTURE_API_TOKEN>',
3720    '--data', payload
3721], capture_output=True, text=True)
3722print(result.stdout.strip())
3723" "<SENTENCE>"
3724~~~
3725
3726Treat \`200\` as success.
3727
3728If one sentence fails, report it and continue with the remaining approved sentences.
3729
3730### 5. Summarize the result
3731
3732List each approved sentence with its upload result:
3733
3734- Uploaded successfully
3735- Failed with HTTP status code
3736
3737State clearly how many items were uploaded and how many failed.
3738
3739## Quality rules
3740
3741- Prefer realistic workplace language over polished textbook language.
3742- Keep the list short and high-signal.
3743- Require user confirmation before upload.
3744- Use the current session only; do not fabricate conversation context.
3745- Treat the API token as sensitive. Use it only for the LangCapture upload request and do not expose it unnecessarily in the final user-facing summary.
3746\`\`\`\`
3747
3748## Why This Is Especially Useful for Developers
3749
3750Developer communication is highly contextual.
3751
3752A sentence is useful not because it sounds impressive, but because it helps you do a specific job well. You may need language for:
3753
3754- giving a clear progress update
3755- explaining the root cause of a bug
3756- asking someone to review a change
3757- discussing tradeoffs before a release
3758- aligning on scope, rollout, or test coverage
3759
3760When those expressions come directly from your real engineering work, they are easier to understand, easier to remember, and much more likely to be reused.
3761
3762## How the Workflow Works
3763
3764The flow stays simple:
3765
37661. Work inside your usual tools or inside an agent conversation.
37672. Install this skill in the agent you already use.
37683. Ask the agent to extract useful expressions from the current context.
37694. Confirm which lines are worth saving.
37705. Let the skill upload them to LangCapture.
3771
3772That means LangCapture is not just a place to store random sentences. It becomes a structured library of expressions that came from your actual development work.
3773
3774If you want the broader product story, start with [Turn Real Workplace Language into Your Personal Learning Library](/blog/introducing-langcapture).
3775
3776If you want more ideas for capture workflows, read [How to Capture Useful Sentences from GitHub, Slack, Jira, and Email](/blog/how-to-capture-useful-chinese-english-sentences-from-github-slack-jira-and-email).
3777
3778To try this workflow yourself, generate a token in [API token settings](/settings/tokens), paste it into the skill, and connect LangCapture to the skill-based workflow you already use.
3779`,ie=`---
3780title: "Novidade: use skills para transformar o trabalho de desenvolvimento em material de aprendizado de idiomas"
3781description: "O LangCapture agora funciona com agentes que suportam skills, e este post inclui a skill completa de aprendizado de idiomas que você pode usar para transformar discussões de engenharia em expressões reutilizáveis no idioma que está aprendendo."
3782image: /og.png
3783date: "2026-03-14"
3784published: true
3785categories: [product-updates]
3786author: langcapture
3787---
3788
3789Desenvolvedores já passam o dia cercados de linguagem útil.
3790
3791Ela aparece em comentários de pull request, notas de debugging, threads de issues, discussões de release, trade-offs de arquitetura e conversas com agentes que ajudam no trabalho de programação. O problema não é falta de material de aprendizado. O problema é que esse material fica espalhado pelo dia de trabalho e raramente vira algo que você consiga revisar depois.
3792
3793## A linguagem mais útil já está dentro do seu fluxo de trabalho
3794
3795Se você é engenheiro, a linguagem de que mais precisa geralmente não vem de um livro didático.
3796
3797É a linguagem que você usa para explicar um bug, pedir review, descrever um risco de migração, contestar o escopo ou resumir resultados de testes. Essas são as frases que importam no trabalho de verdade, e também são as mais difíceis de colecionar com consistência, porque desaparecem dentro de ferramentas e conversas.
3798
3799## O que uma skill faz nesse fluxo
3800
3801Nesse cenário, uma skill é um arquivo de instruções reutilizável para um agente que suporta skills.
3802
3803Em vez de reescrever o mesmo prompt toda vez, você salva o fluxo uma única vez e deixa o agente reutilizá-lo. Para o LangCapture, isso significa que o agente pode revisar a conversa ou o contexto de trabalho atual, extrair de 1 a 5 expressões úteis no idioma que você está aprendendo, pedir c

3803onfirmação e enviar as linhas aprovadas para o LangCapture.
3804
3805É exatamente por isso que esse fluxo é especialmente amigável para desenvolvedores: o material de aprendizado vem diretamente do trabalho real de engenharia.
3806
3807## A skill \`language-learning\` completa
3808
3809Abaixo está o conteúdo completo da skill. Salve como \`language-learning/SKILL.md\` no diretório de skills de qualquer sistema de agentes que suporte skills, e depois substitua o placeholder do token pelo seu próprio token de API do LangCapture. A etapa de upload inclui padrões de comando para Windows e para macOS/Linux.
3810
3811\`\`\`\`md
3812---
3813name: language-learning
3814description: |
3815  Extract 1-5 reusable workplace expressions in the target language from the current conversation, ask the user which ones to keep, and upload the approved sentences to LangCapture. Use when the user asks to "extrair expressões", "extrair frases em inglês", "aprender inglês", "enviar para o LangCapture", "organizar frases", "coletar material de idioma", or similar requests about reviewing the current session and turning it into language learning material.
3816---
3817
3818# Language Learning
3819
3820Extract concise, reusable workplace language from the current chat. Confirm with the user before uploading anything to LangCapture.
3821
3822## Workflow
3823
3824### 1. Review the current session
3825
3826Read the conversation history in the current session. Identify the main work topics being discussed, such as debugging, implementation, status updates, review feedback, deployment, testing, or coordination.
3827
3828Think from the perspective of explaining the same work to a coworker who speaks your target language. Prefer expressions that are likely to be reused in engineering conversations.
3829
3830### 2. Extract 1-5 useful expressions
3831
3832Select only sentences that are:
3833
3834- Natural workplace language
3835- Reusable without depending on hidden context
3836- Useful for engineers discussing progress, issues, requests, review, testing, or results
3837- Concise enough to remember and practice
3838
3839Avoid sentences that are:
3840
3841- Overly academic or textbook-like
3842- Too specific to internal file names, secrets, or one-off details
3843- Unclear without extra explanation
3844
3845For each item, output:
3846
38471. The sentence in the target language
38482. A short native-language note describing meaning or usage
3849
3850Use this format:
3851
3852~~~text
38531. "The latest change fixes the retry path, but I still need to verify the error handling."
3854   -> Usada para relatar o progresso de uma correção, indicando que ainda há partes a verificar
3855~~~
3856
3857If the session does not contain enough good material, say so directly instead of inventing weak examples.
3858
3859### 3. Ask for confirmation before upload
3860
3861After listing the extracted expressions, ask the user which ones to upload.
3862
3863If an interactive question tool is available, use it with these options:
3864
3865- All upload
3866- Choose specific items
3867- Skip
3868
3869If no such tool is available, ask a short plain-text question that offers the same three choices.
3870
3871Do not upload anything until the user confirms.
3872
3873If the user skips, stop immediately.
3874
3875### 4. Upload the approved expressions to LangCapture
3876
3877Upload each approved sentence individually.
3878
3879Prefer using the local shell tool. Use the command pattern that matches the current platform.
3880
3881Windows (PowerShell):
3882
3883~~~powershell
3884$body = @{ original_text = "<SENTENCE>" } | ConvertTo-Json -Compress
3885try {
3886  (Invoke-WebRequest \`
3887    -Method POST \`
3888    -Uri 'https://langcapture.com/api/sentences' \`
3889    -Headers @{
3890      Authorization = 'Bearer <YOUR_LANGCAPTURE_API_TOKEN>'
3891    } \`
3892    -ContentType 'application/json' \`
3893    -Body $body
3894  ).StatusCode
3895} catch {
3896  $_.Exception.Response.StatusCode.value__
3897}
3898~~~
3899
3900macOS/Linux (bash/zsh/sh):
3901
3902~~~sh
3903python3 -c "
3904import json, subprocess, sys
3905sentence = sys.argv[1]
3906payload = json.dumps({'original_text': sentence})
3907result = subprocess.run([
3908    'curl', '-s', '-o', '/dev/null', '-w', '%{http_code}',
3909    '-X', 'POST', 'https://langcapture.com/api/sentences',
3910    '-H', 'Content-Type: application/json',
3911    '-H', 'Authorization: Bearer <YOUR_LANGCAPTURE_API_TOKEN>',
3912    '--data', payload
3913], capture_output=True, text=True)
3914print(result.stdout.strip())
3915" "<SENTENCE>"
3916~~~
3917
3918Treat \`200\` as success.
3919
3920If one sentence fails, report it and continue with the remaining approved sentences.
3921
3922### 5. Summarize the result
3923
3924List each approved sentence with its upload result:
3925
3926- Uploaded successfully
3927- Failed with HTTP status code
3928
3929State clearly how many items were uploaded and how many failed.
3930
3931## Quality rules
3932
3933- Prefer realistic workplace language over polished textbook language.
3934- Keep the list short and high-signal.
3935- Require user confirmation before upload.
3936- Use the current session only; do not fabricate conversation context.
3937- Treat the API token as sensitive. Use it only for the LangCapture upload request and do not expose it unnecessarily in the final user-facing summary.
3938\`\`\`\`
3939
3940## Por que isso é especialmente útil para desenvolvedores
3941
3942A comunicação de desenvolvedores é altamente contextual.
3943
3944Uma frase é útil não porque soa impressionante, mas porque ajuda você a fazer bem um trabalho específico. Você pode precisar de linguagem para:
3945
3946- dar uma atualização de progresso clara
3947- explicar a causa raiz de um bug
3948- pedir que alguém revise uma mudança
3949- discutir trade-offs antes de um release
3950- alinhar escopo, rollout ou cobertura de testes
3951
3952Quando essas expressões vêm diretamente do seu trabalho real de engenharia, elas são mais fáceis de entender, mais fáceis de lembrar e muito mais prováveis de serem reutilizadas.
3953
3954## Como o fluxo funciona
3955
3956O fluxo continua simples:
3957
39581. Trabalhe nas suas ferramentas habituais ou dentro de uma conversa com um agente.
39592. Instale esta skill no agente que você já usa.
39603. Peça ao agente para extrair expressões úteis do contexto atual.
39614. Confirme quais linhas valem a pena salvar.
39625. Deixe a skill enviá-las para o LangCapture.
3963
3964Isso significa que o LangCapture não é só um lugar para guardar frases aleatórias. Ele se torna uma biblioteca estruturada de expressões que vieram do seu trabalho real de desenvolvimento.
3965

3966Se você quer a visão geral do produto, comece por [Transforme a linguagem real do trabalho na sua biblioteca pessoal de aprendizado](/blog/introducing-langcapture).
3967
3968Se você quer mais ideias de fluxos de captura, leia [Como capturar frases úteis do GitHub, Slack, Jira e e-mail](/blog/how-to-capture-useful-chinese-english-sentences-from-github-slack-jira-and-email).
3969
3970Para experimentar esse fluxo, gere um token nas [configurações de token de API](/settings/tokens), cole na skill e conecte o LangCapture ao fluxo baseado em skills que você já usa.
3971`,le=`---
3972title: “新功能：用 Skills 把开发工作整理成可学习的外语表达”
3973description: “LangCapture 现在可以配合支持 skills 的 agent 使用，本文也附上完整的 language-learning skill 内容，方便你直接把开发讨论整理成可学习的外语表达。”
3974image: /og.png
3975date: “2026-03-14”
3976published: true
3977categories: [product-updates]
3978author: langcapture
3979---
3980
3981程序员每天其实都在接触大量值得学的外语表达。
3982
3983Pull Request 评论、排查 bug 的讨论、issue 线程、发布同步、架构取舍，以及各种帮你完成开发工作的 agent 对话——到处都是。真正的问题不是没有素材，而是这些素材散落在工作流里，最后没被整理成能反复学习的内容。
3984
3985## 最值得学的外语，本来就在你的开发流程里
3986
3987对程序员来说，最有价值的外语往往不是教科书里的句子。
3988
3989真正重要的是你在工作里反复会用到的表达——解释一个 bug 的原因、请求同事 review、说明迁移风险、讨论 scope、同步测试结果。这些最贴近真实工作，也最容易在实际沟通中复用，但平时很难系统地收集起来。
3990
3991## Skill 在这个工作流里到底是什么
3992
3993这里说的 skill，是一份可以复用的 agent 指令文件。
3994
3995与其每次都手动敲一大段 prompt，不如把流程固定下来，交给支持 skills 的 agent 反复跑。对 LangCapture 来说，这份 skill 做的事是：回顾当前对话或工作上下文，提炼 1 到 5 条值得学的外语表达，先跟你确认，再把确认后的句子上传到 LangCapture。
3996

3997这也是它对程序员特别友好的原因——素材本来就来自你的真实开发工作。
3998
3999## 完整的 \`language-learning\` Skill 内容
4000
4001下面就是这篇文章对应的完整 skill 内容。你可以把它保存为某个支持 skills 的 agent 系统里的 \`language-learning/SKILL.md\`，然后把其中的 token 占位符替换成你自己的 LangCapture API token。上传步骤里同时给出了 Windows 和 macOS/Linux 两种命令写法。
4002
4003\`\`\`\`md
4004---
4005name: language-learning
4006description: |
4007  Extract 1-5 reusable workplace expressions in the target language from the current conversation, ask the user which ones to keep, and upload the approved sentences to LangCapture. Use when the user asks to “提炼表达”, “提取外语表达”, “学习外语”, “上传到 LangCapture”, “整理句子”, “收集语言素材”, or similar requests about reviewing the current session and turning it into language learning material.
4008---
4009
4010# Language Learning
4011
4012Extract concise, reusable workplace language from the current chat. Confirm with the user before uploading anything to LangCapture.
4013
4014## Workflow
4015
4016### 1. Review the current session
4017
4018Read the conversation history in the current session. Identify the main work topics being discussed, such as debugging, implementation, status updates, review feedback, deployment, testing, or coordination.
4019
4020Think from the perspective of explaining the same work to a coworker who speaks your target language. Prefer expressions that are likely to be reused in engineering conversations.
4021
4022### 2. Extract 1-5 useful expressions
4023
4024Select only sentences that are:
4025
4026- Natural workplace language
4027- Reusable without depending on hidden context
4028- Useful for engineers discussing progress, issues, requests, review, testing, or results
4029- Concise enough to remember and practice
4030
4031Avoid sentences that are:
4032
4033- Overly academic or textbook-like
4034- Too specific to internal file names, secrets, or one-off details
4035- Unclear without extra explanation
4036
4037For each item, output:
4038
40391. The sentence in the target language
40402. A short native-language note describing meaning or usage
4041
4042Use this format:
4043
4044~~~text
40451. “The latest change fixes the retry path, but I still need to verify the error handling.”
4046   -> 用于汇报修复进展，同时说明还有待验证的部分
4047~~~
4048
4049If the session does not contain enough good material, say so directly instead of inventing weak examples.
4050
4051### 3. Ask for confirmation before upload
4052
4053After listing the extracted expressions, ask the user which ones to upload.
4054
4055If an interactive question tool is available, use it with these options:
4056
4057- All upload
4058- Choose specific items
4059- Skip
4060
4061If no such tool is available, ask a short plain-text question that offers the same three choices.
4062
4063Do not upload anything until the user confirms.
4064
4065If the user skips, stop immediately.
4066
4067### 4. Upload the approved expressions to LangCapture
4068
4069Upload each approved sentence individually.
4070
4071Prefer using the local shell tool. Use the command pattern that matches the current platform.
4072
4073Windows (PowerShell):
4074
4075~~~powershell
4076$body = @{ original_text = “<SENTENCE>” } | ConvertTo-Json -Compress
4077try {
4078  (Invoke-WebRequest \`
4079    -Method POST \`
4080    -Uri 'https://langcapture.com/api/sentences' \`
4081    -Headers @{
4082      Authorization = 'Bearer <YOUR_LANGCAPTURE_API_TOKEN>'
4083    } \`
4084    -ContentType 'application/json' \`
4085    -Body $body
4086  ).StatusCode
4087} catch {
4088  $_.Exception.Response.StatusCode.value__
4089}
4090~~~
4091
4092macOS/Linux (bash/zsh/sh):
4093
4094~~~sh
4095python3 -c “
4096import json, subprocess, sys
4097sentence = sys.argv[1]
4098payload = json.dumps({'original_text': sentence})
4099result = subprocess.run([
4100    'curl', '-s', '-o', '/dev/null', '-w', '%{http_code}',
4101    '-X', 'POST', 'https://langcapture.com/api/sentences',
4102    '-H', 'Content-Type: application/json',
4103    '-H', 'Authorization: Bearer <YOUR_LANGCAPTURE_API_TOKEN>',
4104    '--data', payload
4105], capture_output=True, text=True)
4106print(result.stdout.strip())
4107“ “<SENTENCE>”
4108~~~
4109
4110Treat \`200\` as success.
4111
4112If one sentence fails, report it and continue with the remaining approved sentences.
4113
4114### 5. Summarize the result
4115
4116List each approved sentence with its upload result:
4117
4118- Uploaded successfully
4119- Failed with HTTP status code
4120
4121State clearly how many items were uploaded and how many failed.
4122
4123## Quality rules
4124
4125- Prefer realistic workplace language over polished textbook language.
4126- Keep the list short and high-signal.
4127- Require user confirmation before upload.
4128- Use the current session only; do not fabricate conversation context.
4129- Treat the API token as sensitive. Use it only for the LangCapture upload request and do not expose it unnecessarily in the final user-facing summary.
4130\`\`\`\`
4131
4132## 为什么对程序员尤其友好
4133
4134程序员的跨语言沟通，本来就高度依赖上下文。
4135
4136一个句子有用，不是因为它”高级”，而是因为它能帮你更好地完成一个具体任务。比如你可能需要表达这些：
4137
4138- 汇报当前进度
4139- 解释一个 bug 的 root cause
4140- 请别人帮你 review
4141- 在发布前讨论 tradeoff
4142- 对齐 scope、rollout 或 testing plan
4143
4144当这些表达直接来自你的真实开发工作，它们更容易理解、更容易记ä

4144½ï¼Œä¹Ÿæ›´å®¹æ˜“在下一次沟通时真正用出来。
4145
4146## 这个工作流怎么用
4147
4148整个流程很简单：
4149
41501. 先在你原本的工具里工作，或者直接在 agent 对话里推进任务。
41512. 把这份 skill 安装到你正在使用的 agent 里。
41523. 让 agent 从当前上下文中提炼值得学习的外语表达。
41534. 你确认哪些内容值得保留。
41545. 再由 skill 上传到 LangCapture。
4155
4156这样一来，LangCapture 就不只是一个保存零散句子的地方了——它会变成一个真正来自你日常开发工作的外语资料库。
4157
4158如果想先看更完整的产品介绍：[把真实职场语言变成你的个人学习库](/blog/introducing-langcapture)。
4159
4160想看更多关于捕获工作流的内容：[如何从 GitHub、Slack、Jira 和邮件中捕获有用的句子](/blog/how-to-capture-useful-chinese-english-sentences-from-github-slack-jira-and-email)。
4161
4162想马上试的话，去 [API Token 设置页](/settings/tokens) 生成 token，填进这份 skill，然后把 LangCapture 接进你已经在用的 skill 工作流。
4163`,ue=`---
4164name: Flujos de captura
4165description: Formas prácticas de capturar, guardar y repasar frases útiles del trabajo
4166seoTitle: Flujos de captura para frases de inglés laboral
4167seoDescription: Aprende a capturar inglés útil de GitHub, Slack, Jira y correo, guardarlo en LangCapture y repasarlo con traducciones y audio.
4168---
4169`,ce=`---
4170name: キャプチャワークフロー
4171description: 職場で出会った使える文をキャプチャ・保存・復習するための実践的な方法
4172seoTitle: 職場英語フレーズのキャプチャワークフロー
4173seoDescription: GitHub、Slack、Jira、メールで見つけた実用的な職場英語をキャプチャし、LangCaptureのライブラリに保存して翻訳と音声で復習する方法。
4174---
4175`,de=`---
4176name: 캡처 워크플로
4177description: 쓸모 있는 업무 문장을 캡처하고 저장하고 복습하는 실전 방법
4178seoTitle: 업무 영어 문장을 위한 캡처 워크플로
4179seoDescription: GitHub, Slack, Jira, 이메일에서 유용한 업무 영어 문장을 캡처하고 LangCapture 라이브러리에 저장한 뒤 번역과 오디오로 복습하는 방법입니다.
4180---
4181`,pe=`---
4182name: Capture Workflows
4183description: Practical ways to capture, save, and review useful workplace sentences
4184seoTitle: Capture Workflows for Workplace English Sentences
4185seoDescription: Practical workflows for capturing useful workplace English from GitHub, Slack, Jira, and email, then saving it to a reviewable LangCapture library.
4186---
4187`,me=`---
4188name: Fluxos de captura
4189description: Formas práticas de capturar, salvar e revisar frases úteis do ambiente de trabalho
4190seoTitle: Fluxos de captura para frases de inglês no trabalho
4191seoDescription: Aprenda a capturar inglês útil do GitHub, Slack, Jira e email, salvar no LangCapture e revisar com traduções e áudio.
4192---
4193`,ge=`---
4194name: 采集工作流
4195description: 围绕真实工作句子的采集、保存与回看方法
4196seoTitle: 职场英语句子采集工作流：从 GitHub、Slack、Jira 到个人句库

4197seoDescription: 学习如何从 GitHub、Slack、Jira 和邮件中采集有用的职场英语句子，保存到 LangCapture 句库，并结合翻译与音频持续复习。
4198---
4199`,he=`---
4200name: Novedades del producto
4201description: Sigue las novedades de LangCapture: nuevos flujos de captura, mejoras de traducción y audio, colecciones de expresiones y cambios que facilitan crear y repasar tu biblioteca de frases de trabajo.
4202seoTitle: Novedades de LangCapture: captura, traducción y audio
4203seoDescription: Sigue las mejoras de LangCapture para captura de frases, traducción, repaso con audio, colecciones de expresiones y aprendizaje de inglés laboral.
4204---
4205`,fe=`---
4206name: プロダクトアップデート
4207description: LangCapture のプロダクト更新情報です。新しいキャプチャワークフロー、翻訳と音声の改善、表現コレクション、職場の文例ライブラリを作りやすくする変更をまとめます。
4208seoTitle: LangCapture製品アップデート：キャプチャ、翻訳、音声
4209seoDescription: LangCaptureの製品アップデートを確認できます。文のキャプチャ、翻訳、音声復習、表現コレクション、職場英語ライブラリの改善をまとめています。
4210---
4211`,be=`---
4212name: 제품 업데이트
4213description: LangCapture 제품 업데이트를 확인하세요. 새로운 문장 캡처 흐름, 번역과 오디오 개선, 표현 컬렉션, 직장 문장 라이브러리를 더 쉽게 만들고 복습하도록 돕는 변경 사항을 다룹니다.
4214seoTitle: LangCapture 제품 업데이트: 캡처, 번역, 오디오
4215seoDescription: LangCapture의 문장 캡처, 번역, 오디오 복습, 표현 컬렉션, 업무 영어 문장 라이브러리 개선 사항을 확인하세요.
4216---
4217`,ve=`---
4218name: Product Updates
4219description: Follow LangCapture product updates, including new capture workflows, translation and audio improvements, collection packs, and changes that make your workplace sentence library easier to build and review.
4220seoTitle: LangCapture Product Updates for Capture, Translation, and Audio
4221seoDescription: Follow LangCapture product updates for sentence capture, translation, audio review, expression collections, and workplace English learning workflows.
4222---
4223`,ye=`---
4224name: Novidades do produto
4225description: Acompanhe as novidades do LangCapture, incluindo novos fluxos de captura, melhorias de tradução e áudio, coleções de expressões e mudanças que ajudam você a criar e revisar sua biblioteca de frases de trabalho.
4226seoTitle: Novidades do LangCapture: captura, tradução e áudio
4227seoDescription: Acompanhe melhorias do LangCapture para captura de frases, tradução, revisão com áudio, coleções de expressões e aprendizado de inglês no trabalho.
4228---
4229`,we=`---
4230name: 产品更新
4231description: 查看 LangCapture 的产品更新，包括新的句子采集流程、翻译与音频体验改进、表达合集上线，以及让你的职场双语句子库更容易积累和复习的功能变化。
4232seoTitle: LangCapture 产品更新：采集、翻译、音频与表达合集
4233seoDescription: 查看 LangCapture 的产品更新，包括句子采集流程、翻译与音频体验、表达合集，以及让工程师职场英语句子库更容易积累和复习的功能变化。
4234---
4235`,ke=`---
4236name: Aprendizaje de idiomas en el trabajo
4237description: Aprende de comunicación bilingüe real en lugar de plantillas genéricas
4238seoTitle: Aprendizaje de inglés laboral con comunicación real
4239seoDescription: Aprende inglés laboral desde mensajes reales de GitHub, Slack, Jira y correo, en vez de memorizar plantillas genéricas de business English.
4240---
4241`,xe=`---
4242name: 職場の語学学習
4243description: 汎用テンプレートではなく、職場の本物の多言語コミュニケーションから学ぶ
4244seoTitle: 本物のチームコミュニケーションで学ぶ職場英語
4245seoDescription: 汎用的なビジネス英語テンプレートではなく、GitHub、Slack、Jira、メールで実際に使われる表現から職場英語を学ぶ方法。
4246---
4247`,Ce=`---
4248name: 직장 언어 학습
4249description: 범용 템플릿 대신 실제 이중 언어 커뮤니케이션에서 배우기
4250seoTitle: 실제 팀 커뮤니케이션으로 배우는 업무 영어
4251seoDescription: 일반적인 비즈니스 영어 템플릿 대신 GitHub, Slack, Jira, 이메일에서 실제로 쓰이는 표현을 저장하고 복습하며 업무 영어를 학습하세요.
4252---
4253`,Le=`---
4254name: Workplace Language Learning
4255description: Learn from real bilingual communication instead of generic templates
4256seoTitle: Workplace Language Learning with Real Team Communication
4257seoDescription: Learn workplace English from real GitHub, Slack, Jira, and email communication instead of memorizing generic business English templates.
4258---
4259`,je=`---
4260name: Aprendizado de idiomas no trabalho
4261description: Aprenda com comunicação bilíngue real em vez de templates genéricos
4262seoTitle: Aprendizado de inglês no trabalho com comunicação real
4263seoDescription: Aprenda inglês do trabalho a partir de mensagens reais do GitHub, Slack, Jira e email, em vez de memorizar templates genéricos de business English.
4264---
4265`,qe=`---
4266name: 工作场景语言学习
4267description: 从真实多语种工作沟通中学习，而不是背通用模板
4268seoTitle: 工作场景语言学习：用真实沟通积累职场英语表达
4269seoDescription: 用真实工作沟通学习职场英语，而不是背通用模板。把 GitHub、Slack、Jira 和邮件里的表达保存成可复习的双语句子库。
4270---
4271`,Te=`---
4272title: "MVP Preview"

4273description: "Early preview of LangCapture"
4274seoTitle: "LangCapture MVP Preview Release Notes"
4275seoDescription: "See the first LangCapture preview release: sentence capture, translation, on-demand audio, collections, and the core bilingual library workflow."
4276date: "2025-12-18"
4277version: "v0.0.1"
4278published: true
4279---
4280
4281### Highlights
4282
4283This is the MVP (early preview) release of LangCapture.
4284
4285- Capture sentences in any language and store them in a personal library.
4286- AI structuring for patterns, variants, and native-language explanations.
4287- Text-to-speech playback for saved sentences.
4288- Basic authentication, dashboard, and API access.
4289
4290### Notes
4291
4292Expect rapid iteration and breaking changes as we gather feedback.
4293`,Ie=`---
4294title: "MVP 预览"
4295description: "LangCapture 早期预览版本"
4296seoTitle: "LangCapture MVP 预览版发布记录"
4297seoDescription: "查看 LangCapture 第一个预览版本：句子采集、翻译、按需音频、表达合集，以及双语职场句子库的核心工作流。"
4298date: "2025-12-18"
4299version: "v0.0.1"
4300published: true
4301---
4302
4303### 主要更新
4304
4305这是 LangCapture 的 MVP（早期预览）版本。
4306
4307- 捕捉职场外语表达并保存到个人库。
4308- AI 结构化输出：模板、变体与母语解释。
4309- 语音合成播放已保存的句子。
4310- 基础的登录注册、仪表盘与 API 能力。
4311
4312### 说明
4313
4314我们会快速迭代，功能和接口可能会有调整。
4315`,_e=`---
4316title: Cookie Policy
4317description: How LangCapture uses cookies and similar technologies
4318seoTitle: LangCapture Cookie Policy for Website and App Cookies
4319seoDescription: Learn how LangCapture uses essential cookies, preferences, analytics, and similar technologies across the website and app.
4320date: "2025-12-18"
4321published: true
4322---
4323
4324## Introduction
4325
4326This Cookie Policy explains how LangCapture uses cookies and similar technologies on our website and app. By using LangCapture, you consent to the use of cookies as described here.
4327
4328## What Are Cookies
4329
4330Cookies are small text files stored on your device that help websites function and remember information about your visit.
4331
4332## Cookies We Use
4333
4334We use the following categories of cookies:
4335
4336- **Essential Cookies**: Required for authentication, security, and core functionality.
4337- **Preference Cookies**: Remember settings such as language and UI preferences.
4338- **Analytics Cookies**: Help us understand usage and improve the service when analytics are enabled.
4339- **Attribution Cookies**: Track checkout attribution when revenue tracking is enabled.
4340
4341### Examples of Cookies
4342
4343- **Session and security**: authentication cookies that keep you signed in.
4344- **Locale**: \`NEXT_LOCALE\` stores your language preference.
4345- **UI state**: \`sidebar_state\` stores your sidebar open/closed setting.
4346- **Attribution (optional)**: \`datafast_visitor_id\` and \`datafast_session_id\` when DataFast is enabled.
4347
4348Third-party analytics providers may also set their own cookies if enabled (for example, Google Analytics, Plausible, Umami, PostHog, OpenPanel, Seline, Clarity, Ahrefs, or DataFast).
4349
4350## Managing Cookies
4351
4352Most browsers allow you to control cookies through settings. You can delete existing cookies, block new cookies, or receive notifications when cookies are set. Please note that disabling essential cookies may affect your ability to use LangCapture.
4353
4354## Changes to This Cookie Policy
4355
4356We may update this Cookie Policy from time to time. We will post the updated policy on this page and update the effective date above.
4357
4358## Contact Us
4359
4360If you have any questions about this Cookie Policy, please [contact us](/contact).
4361`,Se=`---
4362title: Cookie 政策
4363description: LangCapture 如何使用 Cookie 与类似技术
4364seoTitle: LangCapture Cookie 政策：网站与应用 Cookie 使用说明
4365seoDescription: 了解 LangCapture 如何在网站和应用中使用必要 Cookie、偏好设置、分析标识和类似技术，并说明你可以如何管理浏览器 Cookie。
4366date: "2025-12-18"
4367published: true
4368---
4369
4370## 引言
4371
4372本 Cookie 政策说明 LangCapture 在网站与应用中如何使用 Cookie 与类似技术。使用 LangCapture 即表示你同意本政策。
4373
4374## 什么是 Cookie
4375
4376Cookie 是存储在你设备上的小型文本文件，用于帮助网站正常运行并记住你的访问信息。
4377
4378## 我们使用的 Cookie 类型
4379
4380我们使用以下类别的 Cookie：
4381
4382- **必要 Cookie**：用于身份验证、安全与核心功能。
4383- **偏好 Cookie**：用于记住语言与界面设置。
4384- **分析 Cookie**：在启用分析时帮助我们了解使用情况并改进服务。
4385- **归因 Cookie**：在启用收入归因时用于结账归因追踪。
4386
4387### Cookie 示例
4388
4389- **会话与安全**：用于保持登录状态的认证 Cookie。
4390- **语言偏好**：\`NEXT_LOCALE\` 用于保存语言设置。
4391- **界面状态**：\`sidebar_state\` 用于保存侧边栏开合状态。
4392- **归因（可选）**：启用 DataFast 时的 \`datafast_visitor_id\` 与 \`datafast_session_id\`。
4393
4394若启用第三方分析服务，其也可能设置自己的 Cookie（例如 Google Analytics、Plausible、Umami、PostHog、OpenPanel、Seline、Clarity、Ahrefs 或 DataFast）。
4395
4396## 管理 Cookie
4397
4398大多数浏览器允许你通过设置管理 Cookie。你可以删除现有 Cookie、阻止新 Cookie，或在设置 Cookie 时收到通知。请注意，禁用必要 Cookie 可能影响 LangCapture 的正常使用。
4399
4400## 本 Cookie 政策的变更
4401
4402我们可能会不时更新本 Cookie 政策，并在此页面发布更新版本与最新生效日期。
4403
4404## 联系我们
4405
4406如果你对本 Cookie 政策有任何疑问，请[联系我们](/contact)。
4407`,Pe=`---
4408title: Privacy Policy
4409description: How LangCapture collects, uses, and protects personal data
4410seoTitle: LangCapture Privacy Policy for Sentence Capture and Audio
4411seoDescription: Understand how LangCapture collects and protects account data, captured sentences, translations, audio files, cookies, and billing records.
4412date: "2025-12-18"
4413published: true
4414---
4415
4416## Introduction
4417
4418LangCapture helps you capture sentences in any language, generate translations, and store them in your library. This Privacy Policy explains how we 

4418collect, use, and protect your personal data when you use our website, app, and APIs.
4419
4420## Information We Collect
4421
4422We may collect the following categories of information:
4423
4424- **Account Information**: Name, email address, profile image, and authentication provider identifiers (for example, Google or GitHub) when you sign up or log in.
4425- **User Content**: Chinese or English sentences and passages you submit, generated translations, status/error metadata, and any related audio you request through text-to-speech.
4426- **Usage and Device Data**: IP address, browser type, device identifiers, pages viewed, actions taken, and timestamps.
4427- **Cookies and Identifiers**: Session cookies, locale preferences, UI settings, and analytics or attribution identifiers where enabled.
4428- **Billing and Transaction Data**: Payment processing is handled by Creem. We store billing customer IDs, subscription status, orders, and related metadata.
4429- **Support Communications**: Messages and attachments you send to support.
4430
4431## How We Use Your Information
4432
4433We use your information to:
4434
4435- Provide, operate, and maintain LangCapture features, including sentence translation and text-to-speech.
4436- Authenticate users, secure accounts, and prevent fraud or abuse.
4437- Improve performance, reliability, and user experience.
4438- Process billing, subscriptions, and customer support requests.
4439- Communicate service updates, product changes, and important notices.
4440
4441## How We Share Information
4442
4443We may share information with service providers that help us deliver the service:
4444
4445- **AI Processing**: OpenRouter (LLM inference, currently DeepSeek V4 Flash) for sentence translation and immersive translation.
4446- **Text-to-Speech**: Minimax for speech synthesis.
4447- **Storage**: S3-compatible object storage for audio assets.
4448- **Payments**: Creem for payment processing and billing.
4449- **Email**: Resend for transactional emails.
4450- **Analytics (optional)**: Google Analytics, Plausible, Umami, PostHog, OpenPanel, Seline, Clarity, Ahrefs, or DataFast when configured.
4451- **Auth Providers**: Google and GitHub for social login when enabled.
4452
4453We may also disclose information to comply with legal obligations, enforce our terms, or protect our users and systems.
4454
4455## Data Retention
4456
4457We retain account and user content for as long as your account is active. You can request deletion of your account and data; some information may be retained to comply with legal, accounting, or security requirements. Backups may persist for a limited period.
4458
4459## Security
4460
4461We use reasonable technical and organizational measures to protect your data. No method of transmission or storage is 100% secure, so we cannot guarantee absolute security.
4462
4463## Your Choices and Rights
4464
4465Depending on your location, you may have rights to access, correct, delete, or export your data. You can also opt out of marketing emails and manage cookie preferences through your browser settings. To make a request, contact us at [[email protected]](mailto:[email protected]) or via [/contact](/contact).
4466
4467## International Transfers
4468
4469Our service providers may process data in countries other than your own. We take steps to ensure appropriate safeguards are in place where required by law.
4470
4471## Changes to This Privacy Policy
4472
4473We may update this Privacy Policy from time to time. We will post the updated policy on this page and update the effective date above.
4474
4475## Contact Us
4476
4477If you have any questions about this Privacy Policy, please [contact us](/contact).
4478`,Ae=`---
4479title: 隐私政策
4480description: LangCapture 如何收集、使用和保护个人数据
4481seoTitle: LangCapture 隐私政策：句子采集、翻译与音频数据
4482seoDescription: 了解 LangCapture 如何收集和保护账户资料、采集句子、翻译结果、音频文件、Cookie、账单记录，以及你可以如何管理个人数据。
4483date: "2025-12-18"
4484published: true
4485---
4486
4487## 引言
4488
4489LangCapture 帮助你捕捉多语种表达、翻译为母语，并将内容存入你的个人库。本隐私政策说明我们在你使用网站、应用与 API 时如何收集、使用和保护你的个人数据。
4490
4491## 我们收集的信息
4492
4493我们可能会收集以下类别的信息：
4494
4495- **账户信息**：注册或登录时提供的姓名、邮箱、头像，以及认证提供方标识（例如 Google 或 GitHub）。
4496- **用户内容**：你提交的句子或段落、翻译，以及你请求的语音合成音频。

4497- **使用与设备数据**：IP 地址、浏览器类型、设备标识、访问页面、操作记录与时间戳。
4498- **Cookie 与标识符**：会话 Cookie、语言偏好、界面设置，以及在启用时的分析或归因标识符。
4499- **计费与交易数据**：支付由 Creem 处理；我们保存账单客户编号、订阅状态、订单与相关元数据。
4500- **支持沟通**：你发送给客服的消息与附件。
4501
4502## 我们如何使用你的信息
4503
4504我们会将你的信息用于：
4505
4506- 提供与维护 LangCapture 功能，包括句子翻译与语音合成。
4507- 身份验证、账户安全、反欺诈与滥用防护。
4508- 性能优化、问题排查与体验改进。
4509- 计费、订阅管理与客户支持。
4510- 发送服务更新、产品变更与重要通知。
4511
4512## 我们如何共享信息
4513
4514我们可能与以下服务提供商共享信息以交付服务：
4515
4516- **AI 处理**：OpenRouter（模型推理，当前使用 DeepSeek V4 Flash，用于句子翻译与沉浸式翻译）。
4517- **语音合成**：Minimax。
4518- **存储**：兼容 S3 的对象存储，用于保存音频资产。
4519- **支付**：Creem。
4520- **邮件**：Resend（用于发送事务性邮件）。
4521- **分析（可选）**：在配置启用时，可能使用 Google Analytics、Plausible、Umami、PostHog、OpenPanel、Seline、Clarity、Ahrefs 或 DataFast。
4522- **身份认证**：在启用社交登录时使用 Google 与 GitHub。
4523
4524在法律要求或为保护用户与系统安全时，我们也可能披露必要信息。
4525
4526## 数据保留
4527
4528我们在账户有效期间保留账户与用户内容。你可以请求删除账户与数据；为满足法律、财务或安全要求，部分信息可能会保留。备份数据可能会在有限期限内继续存在。
4529
4530## 数据安全
4531
4532我们采取合理的技术与组织措施来保护你的数据。但任何传输或存储方式都无法保证绝对安全。
4533
4534## 你的选择与权利
4535
4536根据你所在地区的法律，你可能拥有访问、更正、删除或导出数据的权利。你也可以通过浏览器设置管理 Cookie，或退订营销邮件。如需提出请求，请联系 [[email protected]](mailto:[email protected]) 或访问 [/contact](/contact)。
4537
4538## 跨境传输
4539
4540我们的服务提供商可能在你所在国家/地区之外处理数据。我们会在法律要求范围内采取相应保障措施。
4541
4542## 本隐私政策的变更
4543
4544我们可能会不时更新本隐私政策，并在此页面发布更新版本与最新生效日期。
4545
4546## 联系我们
4547
4548如果你对本隐私政策有任何疑问，请[联系我们](/contact)。
4549`,ze=`---
4550title: Terms of Service
4551description: "The Terms of Service that govern your access to and use of LangCapture, including our website, application, and APIs, covering accounts, acceptable use, billing, and liability."
4552seoTitle: LangCapture Terms of Service for Website, App, and APIs
4553seoDescription: Review the terms that govern LangCapture accounts, sentence capture, translation, audio, APIs, billing, acceptable use, and liability.
4554date: "2025-12-18"
4555published: true
4556---
4557
4558## Introduction
4559
4560These Terms of Service ("Terms") govern your access to and use of LangCapture, including our website, application, and APIs. By using LangCapture, you agree to these Terms.
4561
4562## The Service
4563
4564LangCapture helps users capture sentences in any language, generate translations, and store them in a personal library. We may offer features such as text-to-speech and API access.
4565
4566## Eligibility
4567
4568You must be able to form a binding contract in your jurisdiction to use LangCapture. If you use LangCapture on behalf of an organization, you represent that you have authority to bind that organization.
4569
4570## Accounts and Security
4571
4572You are responsible for maintaining the confidentiality of your account credentials and API tokens. You are also responsible for all activities that occur under your account.
4573
4574## Acceptable Use
4575
4576You agree not to:
4577
4578- Use LangCapture in violation of applicable laws or regulations.
4579- Submit content that you do not have the right to use or share.
4580- Interfere with or disrupt our services, systems, or security.
4581- Attempt to gain unauthorized access to our systems or data.
4582- Use LangCapture to distribute malware, spam, or abusive content.
4583
4584## User Content
4585
4586You retain ownership of the content you submit to LangCapture. You grant us a worldwide, non-exclusive, royalty-free license to host, store, process, and display your content solely to provide and improve the service. You are responsible for ensuring you have the necessary rights and permissions to submit the content.
4587
4588## AI and Generated Output
4589
4590LangCapture uses AI services to generate translations and speech for language learning workflows. AI output may be inaccurate or incomplete, and you are responsible for verifying results before relying on them.
4591
4592## Payments and Subscriptions
4593
4594Paid plans and purchases are processed by Creem. Subscriptions may renew automatically until canceled. Prices, taxes, and billing cycles will be shown at checkout. Except where required by law, fees are non-refundable.
4595
4596## Intellectual Property
4597
4598LangCapture and its original content, features, and branding are owned by us and protected by intellectual property laws. These Terms do not grant you any rights to our trademarks or brand assets.
4599
4600## Termination
4601
4602We may suspend or terminate access to LangCapture at any time if we believe you have violated these Terms or if necessary to protect our services and users. You may stop using LangCapture at any time.
4603
4604## Disclaimer of Warranties
4605
4606LangCapture is provided "as is" and "as available" without warranties of any kind. We do not guarantee that the service will be uninterrupted, secure, or error-free.
4607
4608## Limitation of Liability
4609
4610To the maximum extent permitted by law, we are not liable for indirect, incidental, special, consequential, or punitive damages arising from your use of LangCapture.
4611
4612## Changes to Terms
4613
4614We may update these Terms from time to time. We will post the updated Terms on this page and update the effective date above.
4615
4616## Contact Us
4617
4618If you have any questions about these Terms, please [contact us](/contact).
4619`,Ee=`---
4620title: 服务条款

4621description: 规范 LangCapture 使用的条款与条件
4622seoTitle: LangCapture 服务条款：网站、应用与 API 使用规则
4623seoDescription: 查看 LangCapture 账户、句子采集、翻译、音频、API、订阅账单、可接受使用范围和责任限制相关的服务条款。
4624date: "2025-12-18"
4625published: true
4626---
4627
4628## 引言
4629
4630本服务条款（“条款”）适用于你对 LangCapture（包括网站、应用与 API）的访问与使用。使用 LangCapture 即表示你同意这些条款。
4631
4632## 服务内容
4633
4634LangCapture 帮助用户捕捉多语种表达、翻译为母语，并将内容存入个人库。我们可能提供语音合成与 API 等功能。
4635
4636## 使用资格
4637
4638你必须具备在所在司法辖区签订具有约束力合同的资格。如你代表组织使用 LangCapture，即表示你有权代表该组织接受这些条款。
4639
4640## 账户与安全
4641
4642你需要妥善保管账户凭证与 API Token，并对账户下的所有活动负责。
4643
4644## 可接受使用
4645
4646你同意不会：
4647
4648- 违反任何适用法律或法规使用 LangCapture。
4649- 提交你无权使用或分享的内容。
4650- 干扰或破坏我们的服务、系统或安全。
4651- 试图未经授权访问我们的系统或数据。
4652- 利用 LangCapture 传播恶意软件、垃圾信息或滥用性内容。
4653
4654## 用户内容
4655
4656你保留你提交内容的所有权。你授予我们全球范围内、非独占、免版税的许可，仅用于提供与改进服务所需的托管、存储、处理与展示。你应确保提交内容具备必要的权利与授权。
4657
4658## AI 与生成内容
4659
4660LangCapture 使用 AI 服务生成翻译与语音。AI 输出可能不准确或不完整，你需自行核对后再使用。
4661
4662## 付费与订阅
4663
4664付费计划与购买由 Creem 处理。订阅可能会自动续费，除非你主动取消。价格、税费与计费周期会在结账时展示。法律另有规定的除外，费用不予退还。
4665
4666## 知识产权
4667
4668LangCapture 及其原创内容、功能与品牌资产归我们所有，并受知识产权法律保护。本条款不授予你使用我们的商标或品牌资产的权利。
4669
4670## 终止
4671
4672如你违反本条款或为保护服务与用户安全，我们可随时暂停或终止你的使用权限。你也可以随时停止使用 LangCapture。
4673
4674## 免责声明
4675
4676LangCapture 按“现状”和“可用性”提供，不做任何明示或暗示保证。我们不保证服务持续可用、完全安全或无错误。
4677
4678## 责任限制
4679
4680在法律允许的最大范围内，我们不对因使用 LangCapture 而产生的间接、附带、特殊、后果性或惩罚性损害承担责任。
4681
4682## 条款变更
4683
4684我们可能会不时更新这些条款，并在本页面发布更新版本与最新生效日期。
4685
4686## 联系我们
4687
4688如对本条款有任何疑问，请[联系我们](/contact)。
4689`,Ne=Object.assign({"../../content/author/langcapture.mdx":P,"../../content/author/langcapture.zh.mdx":A,"../../content/blog/how-to-capture-useful-chinese-english-sentences-from-github-slack-jira-and-email.es.mdx":z,"../../content/blog/how-to-capture-useful-chinese-english-sentences-from-github-slack-jira-and-email.ja.mdx":E,"../../content/blog/how-to-capture-useful-chinese-english-sentences-from-github-slack-jira-and-email.ko.mdx":N,"../../content/blog/how-to-capture-useful-chinese-english-sentences-from-github-slack-jira-and-email.mdx":U,"../../content/blog/how-to-capture-useful-chinese-english-sentences-from-github-slack-jira-and-email.pt.mdx":W,"../../content/blog/how-to-capture-useful-chinese-english-sentences-from-github-slack-jira-and-email.zh.mdx":H,"../../content/blog/introducing-langcapture.es.mdx":R,"../../content/blog/introducing-langcapture.ja.mdx":G,"../../content/blog/introducing-langcapture.ko.mdx":O,"../../content/blog/introducing-langcapture.mdx":D,"../../content/blog/introducing-langcapture.pt.mdx":M,"../../content/blog/introducing-langcapture.zh.mdx":J,"../../content/blog/stop-memorizing-templates-build-a-real-workplace-sentence-library-instead.es.mdx":B,"../../content/blog/stop-memorizing-templates-build-a-real-workplace-sentence-library-instead.ja.mdx":F,"../../content/blog/stop-memorizing-templates-build-a-real-workplace-sentence-library-instead.ko.mdx":Y,"../../content/blog/stop-memorizing-templates-build-a-real-workplace-sentence-library-instead.mdx":$,"../../content/blog/stop-memorizing-templates-build-a-real-workplace-sentence-library-instead.pt.mdx":K,"../../content/blog/stop-memorizing-templates-build-a-real-workplace-sentence-library-instead.zh.mdx":V,"../../content/blog/technical-interview-english-for-software-engineers.es.mdx":Q,"../../content/blog/technical-interview-english-for-software-engineers.ja.mdx":X,"../../content/blog/technical-interview-english-for-software-engineers.ko.mdx":Z,"../../content/blog/technical-interview-english-for-software-engineers.mdx":ee,"../../content/blog/technical-interview-english-for-software-engineers.pt.mdx":ne,"../../content/blog/technical-interview-english-for-software-engineers.zh.mdx":ae,"../../content/blog/use-skills-to-turn-developer-work-into-english-learning-material.es.mdx":te,"../../content/blog/use-skills-to-turn-developer-work-into-english-learning-material.ja.mdx":oe,"../../content/blog/use-skills-to-turn-developer-work-into-english-learning-material.ko.mdx":se,"../../content/blog/use-skills-to-turn-developer-work-into-english-learning-material.mdx":re,"../../content/blog/use-skills-to-turn-developer-work-into-english-learning-material.pt.mdx":ie,"../../content/blog/use-skills-to-turn-developer-work-into-english-learning-material.zh.mdx":le,"../../content/category/capture-workflows.es.mdx":ue,"../../content/category/capture-workflows.ja.mdx":ce,"../../content/category/capture-workflows.ko.mdx":de,"../../content/category/capture-workflows.mdx":pe,"../../content/category/capture-workflows.pt.mdx":me,"../../content/category/capture-workflows.zh.mdx":ge,"../../content/category/product-updates.es.mdx":he,"../../content/category/product-updates.ja.mdx":fe,"../../content/category/product-updates.ko.mdx":be,"../../content/category/product-updates.mdx":ve,"../../content/category/product-updates.pt.mdx":ye,"../../content/category/product-updates.zh.mdx":we,"../../content/category/workplace-language-learning.es.mdx":ke,"../../content/category/workplace-language-learning.ja.mdx":xe,"../../content/category/workplace-language-learning.ko.mdx":Ce,"../../content/category/workplace-language-learning.mdx":Le,"../../content/category/workplace-language-learning.pt.mdx":je,"../../content/category/workplace-language-learning.zh.mdx":qe,"../../content/changelog/v0-0-1.mdx":Te,"../../content/changelog/v0-0-1.zh.mdx":Ie,"../../content/pages/cookie-policy.mdx":_e,"../../content/pages/cookie-policy.zh.mdx":Se,"../../content/pages/privacy-policy.mdx":Pe,"../../content/pages/privacy-policy.zh.mdx":Ae,"../../content/pages/terms-of-service.mdx":ze,"../../content/pages/terms-of-service.zh.mdx":Ee}),f=Object.entries(Ne).map(([n,t])=>Re(n,t)).filter(n=>n.published);function Ue(n,t){const o=new Map;for(const s of f)s.type===n&&s.locale===h&&o.set(s.slug,s);if(t!==h)for(const s of f)s.type===n&&s.locale===t&&o.set(s.slug,s);return[...o.values()].sort((s,a)=>(a.date??"").localeCompare(s.date??""))}function We({type:n,slug:t,locale:o}){const s=a=>f.find(r=>r.type===n&&r.slug===t&&r.locale===a)??null;return s(o)??s(h)}function He(n,t){return f.filter(o=>o.type===n&&o.slug===t).map(o=>o.locale)}function Re(n,t){const[,o="",s=t]=t.match(/^---\n([\s\S]*?)\n---\n?([\s\S]*)$/)??[t,"",t],a=Ge(o),r=n.replaceAll("\\","/"),[,u="pages",l="page.mdx"]=r.match(/content\/([^/]+)\/([^/]+)$/)??[],c=l.match(/^(.*)\.([a-z]{2})\.mdx$/),p=!!(c&&L(c[2])),v=p&&c?c[2]:h,g=p&&c?c[1]:l.replace(/\.mdx$/,"");return{type:u,slug:g,locale:v,title:a.title??a.name??g.replaceAll("-"," "),description:a.description??null,seoTitle:a.seoT

4689itle??null,seoDescription:a.seoDescription??null,date:a.date??null,image:a.image??null,author:a.author??null,published:a.published!=="false",categories:Oe(a.categories),body:s}}function Ge(n){const t={};for(const o of n.split(`
4690`)){const s=o.indexOf(":");if(s===-1)continue;const a=o.slice(0,s).trim(),r=o.slice(s+1).trim();t[a]=r.replace(/^["']|["']$/g,"")}return t}function Oe(n){return!n?.startsWith("[")||!n.endsWith("]")?[]:n.slice(1,-1).split(",").map(t=>t.trim().replace(/^["']|["']$/g,"")).filter(Boolean)}const dn=({data:n})=>n?T({title:`${n.page.seoTitle??n.page.title} | LangCapture`,description:n.page.seoDescription??n.page.description,canonicalUrl:n.seoMeta.canonicalUrl,alternateUrls:n.seoMeta.alternateUrls,imageUrl:n.seoMeta.imageUrl,jsonLd:n.jsonLd,locale:n.locale,robots:n.shouldIndex?void 0:"noindex, follow",type:n.page.kind==="document"&&n.page.section==="blog"?"article":"website",xDefaultUrl:n.seoMeta.xDefaultUrl}):[{title:"LangCapture"}],pn=x(function(){const t=C();return e.jsx(De,{isAuthenticated:t.isAuthenticated,locale:t.locale,pathname:t.pathname,children:t.page.kind==="blog-list"?e.jsx(Me,{data:t.page,locale:t.locale}):t.page.kind==="list"?e.jsx(Fe,{data:t.page,locale:t.locale}):e.jsx(Ye,{data:t.page,locale:t.locale})})});function De({children:n,isAuthenticated:t,locale:o,pathname:s}){const a=m(o),r=g=>d(o,g),u=r(t?"/sentences/capture":"/auth/register"),l=r("/dashboard"),c=r("/auth/login"),p=e.jsx(q,{label:a.nav.switchLanguage,locale:o,pathname:s}),v=t?[{label:a.nav.dashboard,to:l,variant:"button"}]:[{label:a.nav.login,to:c,variant:"plain"},{label:a.nav.signUp,to:u,variant:"button"}];return e.jsxs("div",{className:"marketing-page public-page",children:[e.jsx("header",{className:"marketing-navbar-shell public-navbar-shell",children:e.jsxs("div",{className:"marketing-container marketing-navbar",children:[e.jsxs(i,{"aria-label":"LangCapture home",className:"marketing-brand",to:r("/"),children:[e.jsx("img",{alt:"",height:"32",src:w,width:"32"}),e.jsx("span",{children:"LangCapture"})]}),e.jsxs("nav",{"aria-label":"Primary navigation",className:"marketing-nav",children:[e.jsx(i,{to:r("/pricing"),children:a.nav.pricing}),e.jsx(i,{to:r("/collections?source=navbar"),children:a.nav.collections}),e.jsx(i,{to:r("/blog"),children:a.nav.blog})]}),e.jsxs("div",{className:"marketing-actions",children:[p,t?e.jsx(i,{className:"nav-button",to:l,children:a.nav.dashboard}):e.jsxs(e.Fragment,{children:[e.jsx(i,{className:"nav-plain",to:c,children:a.nav.login}),e.jsx(i,{className:"nav-button",to:u,children:a.nav.signUp})]})]}),e.jsx(j,{links:[{label:a.nav.pricing,to:r("/pricing")},{label:a.nav.collections,to:r("/collections?source=navbar")},{label:a.nav.blog,to:r("/blog")}],actions:v,localeSwitcher:p})]})}),n,e.jsxs("footer",{className:"marketing-footer",children:[e.jsxs("div",{className:"marketing-container footer-grid",children:[e.jsxs("div",{className:"footer-brand",children:[e.jsxs("div",{children:[e.jsx("img",{alt:"",height:"32",src:w,width:"32"}),e.jsx("strong",{children:"LangCapture"})]}),e.jsx("p",{children:a.footer.tagline})]}),e.jsx(y,{links:[[a.footer.features,"/#features"],[a.footer.pricing,"/pricing"],[a.footer.faq,"/#faq"]],localized:r,title:a.footer.product}),e.jsx(y,{links:[[a.footer.collections,"/collections?source=footer"],[a.footer.blog,"/blog"],[a.footer.changelog,"/changelog"]],localized:r,title:a.footer.resources}),e.jsx(y,{links:[[a.footer.cookie,"/cookie"],[a.footer.privacy,"/privacy"],[a.footer.terms,"/terms"]],localized:r,title:a.footer.legal})]}),e.jsx("div",{className:"footer-bottom",children:e.jsx("div",{className:"marketing-container",children:e.jsxs("span",{children:["© ",new Date().getFullYear()," LangCapture"," ",a.footer.copyright]})})})]})]})}function Me({data:n,locale:t}){const o=m(t),s=a=>d(t,a);return e.jsxs("main",{children:[e.jsx("section",{className:"blog-hero-section",children:e.jsxs("div",{className:"marketing-container blog-hero-grid",children:[e.jsxs("div",{className:"blog-hero-copy",children:[e.jsxs("p",{className:"home-badge",children:[e.jsx("span",{"aria-hidden":"true",className:"badge-dot"}),o.blog.eyebrow]}),e.jsx("h1",{children:n.title}),e.jsx("p",{className:"blog-hero-description",children:n.description}),e.jsxs("div",{className:"blog-metrics","aria-label":"Blog summary",children:[e.jsxs("span",{children:[e.jsx("strong",{children:n.totalPosts}),o.blog.posts]}),e.jsxs("span",{children:[e.jsx("strong",{children:n.categories.length}),o.blog.categories]})]})]}),n.featuredDocument?e.jsxs(i,{className:"blog-featured-card",to:s(`/blog/${n.featuredDocument.slug}`),children:[e.jsx("span",{children:o.blog.latest}),e.jsx("h2",{children:n.featuredDocument.title}),n.featuredDocument.description?e.jsx("p",{children:n.featuredDocument.description}):null,e.jsxs("small",{children:[b(n.featuredDocument.date,t),e.jsx(k,{"aria-hidden":"true",size:16})]})]}):null]})}),e.jsx("section",{className:"blog-index-section",children:e.jsxs("div",{className:"marketing-container",children:[e.jsxs("nav",{"aria-label":"Blog categories",className:"blog-category-tabs",children:[e.jsx(i,{className:n.activeCategory?void 0:"active",to:s("/blog"),children:o.blog.all}),n.categories.map(a=>e.jsx(i,{className:n.activeCategory?.slug===a.slug?"active":void 0,to:s(`/blog/category/${a.slug}`),children:a.title},a.slug))]}),n.documents.length>0?e.jsx("div",{className:"blog-card-grid",children:n.documents.map(a=>e.jsx(Je,{document:a,locale:t},a.slug))}):e.jsx("p",{className:"blog-empty",children:o.blog.empty}),n.totalPages>

46901?e.jsx(Be,{basePath:n.basePath,currentPage:n.currentPage,locale:t,totalPages:n.totalPages}):null]})})]})}function Je({document:n,locale:t}){const o=m(t),s=l=>d(t,l),r=$e(t,[n]).filter(l=>n.categories.includes(l.slug))[0]??null,u=Ke(n.author,t)??"LangCapture";return e.jsxs(i,{className:"blog-card",to:s(`/blog/${n.slug}`),children:[e.jsxs("div",{className:"blog-card-visual","aria-hidden":"true",children:[e.jsx("img",{alt:"",height:"40",src:w,width:"40"}),e.jsxs("div",{children:[e.jsx("strong",{children:"LangCapture"}),e.jsx("span",{children:o.blog.visualSubtitle})]}),r?e.jsx("em",{children:r.title}):null]}),e.jsxs("div",{className:"blog-card-body",children:[e.jsx("h2",{children:n.title}),n.description?e.jsx("p",{children:n.description}):null,e.jsxs("div",{className:"blog-card-meta",children:[e.jsx("span",{children:u}),e.jsx("time",{dateTime:n.date??void 0,children:b(n.date,t)})]}),e.jsxs("span",{className:"blog-card-link",children:[o.blog.readArticle,e.jsx(k,{"aria-hidden":"true",size:15})]})]})]})}function Be({basePath:n,currentPage:t,locale:o,totalPages:s}){const a=m(o),r=l=>d(o,l),u=l=>l<=1?n:`${n}/page/${l}`;return e.jsxs("nav",{"aria-label":"Blog pagination",className:"blog-pagination",children:[e.jsx(i,{"aria-disabled":t<=1,className:t<=1?"disabled":void 0,to:r(u(Math.max(1,t-1))),children:a.blog.previous}),e.jsxs("span",{children:[t," / ",s]}),e.jsx(i,{"aria-disabled":t>=s,className:t>=s?"disabled":void 0,to:r(u(Math.min(s,t+1))),children:a.blog.next})]})}function Fe({data:n,locale:t}){return e.jsx("main",{className:"public-document-shell",children:e.jsxs("section",{className:"public-document-list",children:[e.jsxs("p",{className:"home-badge",children:[e.jsx("span",{"aria-hidden":"true",className:"badge-dot"}),"LangCapture"]}),e.jsx("h1",{children:n.title}),e.jsx("p",{className:"lede",children:n.description}),e.jsx("div",{className:"public-list",children:n.documents.map(o=>e.jsxs(i,{className:"public-list-row",to:d(t,`${n.basePath}/${o.slug}`),children:[e.jsxs("span",{children:[e.jsx("strong",{children:o.title}),o.description?e.jsx("small",{children:o.description}):null]}),e.jsx("time",{dateTime:o.date??void 0,children:b(o.date,t)})]},o.slug))})]})})}function Ye({data:n,locale:t}){const o=m(t),s=a=>d(t,a);return e.jsxs("main",{className:"public-document-shell",children:[e.jsxs("article",{className:n.section==="blog"?"public-article blog-article":"public-article",children:[n.section==="blog"?e.jsx(i,{className:"article-back-link",to:s("/blog"),children:o.blog.backToBlog}):null,e.jsxs("div",{className:"article-meta",children:[n.date?e.jsxs("span",{children:[e.jsx(S,{"aria-hidden":"true",size:15}),b(n.date,t)]}):e.jsx("span",{children:"LangCapture"}),n.author?e.jsx("span",{children:n.author}):null]}),e.jsx("h1",{children:n.title}),n.description?e.jsx("p",{className:"lede",children:n.description}):null,n.categories.length>0?e.jsx("div",{className:"article-category-row",children:n.categories.map(a=>e.jsx(i,{to:s(`/blog/category/${a.slug}`),children:a.title},a.slug))}):null,e.jsx("div",{className:"article-body",children:n.blocks.map((a,r)=>a.type==="heading"?e.jsx("h2",{children:a.text},`${a.type}-${r}`):a.type==="blockquote"?e.jsx("blockquote",{children:a.text},`${a.type}-${r}`):a.type==="list"?e.jsx("ul",{children:e.jsx("li",{children:a.text})},`${a.type}-${r}`):e.jsx("p",{children:a.text},`${a.type}-${r}`))})]}),n.section==="blog"?e.jsxs("section",{className:"article-cta",children:[e.jsxs("div",{children:[e.jsx("h2",{children:o.blog.ctaTitle}),e.jsx("p",{children:o.blog.ctaDescription})]}),e.jsxs(i,{className:"lc-button primary",to:s("/auth/register"),children:[o.blog.ctaAction,e.jsx(k,{"aria-hidden":"true",size:16})]})]}):null]})}function y({title:n,links:t,localized:o}){return e.jsxs("div",{className:"footer-column",children:[e.jsx("strong",{children:n}),e.jsx("ul",{children:t.map(([s,a])=>e.jsx("li",{children:e.jsx(i,{to:o(a),children:s})},s))})]})}function $e(n,t){const o=new Map;for(const s of t)for(const a of s.categories)o.set(a,(o.get(a)??0)+1);return Ue("category",n).filter(s=>o.has(s.slug)).map(s=>({count:o.get(s.slug)??0,description:s.description,seoTitle:s.seoTitle,seoDescription:s.seoDescription,seoLocales:He("category",s.slug),slug:s.slug,title:s.title}))}function Ke(n,t){return n?We({type:"author",slug:n,locale:t})?.title??n:null}function b(n,t){if(!n)return"";const o=new Date(n);if(Number.isNaN(o.getTime()))return n;if(t==="zh"){const s=o.getFullYear(),a=String(o.getMonth()+1).padStart(2,"0"),r=String(o.getDate()).padStart(2,"0");return`${s}/${a}/${r}`}return new Intl.DateTimeFormat(t,{month:"short",day:"numeric",year:"numeric"}

4690).format(o)}export{pn as default,dn as meta};