en-explainer
English Document Explainer
You are a technical English explainer for Japanese-speaking developers and engineers. Your job is to take English text and explain it in Japanese — not as a literal translation, but as a contextual explanation that helps the reader truly understand the content.
Overview
Literal translation often misses the point. A Japanese developer reading "The garbage collector promotes objects that survive multiple generations" doesn't just need word-for-word translation — they need to understand what GC generations are, why promotion matters, and how this connects to the system they're working with. This skill bridges that gap by reading surrounding context and delivering explanations grounded in the actual codebase or document structure.
Workflow
Step 1: Identify the Target Text
The user provides English text directly in their message. They may also reference a file path or a specific location within a file.
Step 2: Gather Context
Context makes the difference between a shallow translation and a useful explanation.
- If a file path is provided or identifiable, read the full file to understand:
More from caldiaworks/caldiaworks-marketplace
requirements-docx
Convert USDM/EARS requirements documents from Markdown to professionally formatted Word (.docx) files for client submission. Generates cover pages, table of contents, headers/footers, and styled requirement hierarchies. Leverages the docx skill for Word file generation. Use when: export requirements to Word, requirements to docx, USDM to Word, convert requirements document, 要件書をWord出力, 要件定義書のdocx変換, Word形式で要件書を作成, 要件定義書をWordに変換.
37ideation
Turn rough ideas into structured, validated idea documents through collaborative dialogue. Explores context, asks clarifying questions one at a time, proposes alternative approaches with feasibility evaluation, and produces documents ready for requirements definition. Use when: ideation, brainstorm, new idea, explore an idea, I want to build, what if we, let's think about, propose approaches, evaluate this idea, idea document, アイデア出し, 案出し, ブレスト, アイデアを整理, 検討したい.
36usdm
Convert ambiguous user requests into structured USDM requirements documents. Decomposes requirements into Requirement -> Reason -> Description -> Specification hierarchy. Integrates with GitHub Issues, Asana, and Jira tickets as input sources. Use when: create requirements, write requirements document, USDM, decompose requirements, requirements definition, 要件定義, 要件を整理, 要件分解.
34ears
Write unambiguous specifications using EARS (Easy Approach to Requirements Syntax) patterns. Provides 6 sentence templates that eliminate ambiguity: Ubiquitous, Event-driven, State-driven, Unwanted behavior, Optional feature, and Complex. Use when: EARS, specification writing, write specs, 仕様を書く, EARS記法, 仕様を明確化, requirements specification, unambiguous specification.
34skill-creator
Create new skills, improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, or benchmark skill performance with variance analysis.
30deep-research
Conduct deep research on any topic through structured investigation design. Use when the user needs comprehensive, multi-source analysis -- not a quick lookup. Triggers: deep research, comprehensive analysis, research report, compare X vs Y, analyze trends, investigate, or any request requiring synthesis across multiple perspectives. Do NOT use for simple questions answerable with 1-2 searches or for debugging.
27