メニュー
Envilder website internationalization workflow. Use when adding, editing, or reviewing translated strings, creating localized pages, or verifying i18n completeness. Covers the full lifecycle from type definition to locale files.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Workflow for investigating and reproducing bugs before fixing via TDD. Use when a bug report or GitHub issue is received. Covers issue fetching, root cause analysis, reproduction planning, and handoff to TDD cycle.
CRAP score quality gate for code complexity and test coverage. Use when reviewing methods for complexity risk, deciding whether to split methods, or determining minimum test coverage requirements.
Code smell detection and safe incremental refactoring patterns. Use when improving code structure, reducing technical debt, or cleaning up after a TDD cycle. Covers SOLID principles, smell catalog, and the propose-apply workflow.
Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity. Use when reviewing PRs, commits, or local changes. Includes severity model and output format.
Index of Architecture Decision Records (ADRs) for cross-cutting technical decisions. Use when making design choices, reviewing proposals for consistency with prior decisions, or onboarding to understand why specific tools or patterns were chosen. Covers test tooling, SDK architecture, code quality, and acceptance test infrastructure.
Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning. Use when creating commits, pull requests, or managing Git workflow.
| name | website-i18n |
| description | Envilder website internationalization workflow. Use when adding, editing, or reviewing translated strings, creating localized pages, or verifying i18n completeness. Covers the full lifecycle from type definition to locale files. |
Every user-visible string on the Envilder website MUST go through the i18n system. Never hardcode text in components.
| What | Where |
|---|---|
| Translation types | src/website/src/i18n/types.ts |
| Locale files | src/website/src/i18n/{en,ca,es}.ts (one per locale) |
| i18n utilities | src/website/src/i18n/utils.ts |
| Astro i18n config | src/website/astro.config.mjs → i18n.locales |
| Pages (default locale) | src/website/src/pages/*.astro |
| Pages (other locales) | src/website/src/pages/<locale>/*.astro |
Add the new key structure in src/website/src/i18n/types.ts:
// In the Translations interface
section: {
title: string;
description: string;
};
Update all locale files in src/website/src/i18n/:
en.ts: English (source)ca.ts: Catalanes.ts: SpanishTypeScript will error if any locale is missing a key defined in types.ts.
Access translations via the useTranslations helper:
---
import { useTranslations } from '../i18n/utils';
const { lang = 'en' } = Astro.props;
const t = useTranslations(lang);
---
<h2>{t.section.title}</h2>
<p>{t.section.description}</p>
For new pages:
src/website/src/pages/new-page.astrosrc/website/src/pages/<locale>/new-page.astroCheck astro.config.mjs → i18n.locales to discover all active locales.
Product names, CLI flags, code tokens, and acronyms stay in English:
envilder, AWS SSM, Azure Key Vault, GitHub Action, envilder.json,
.env, --map, --envfile, --exec, --provider, --push, CI/CD, IAM,
RBAC, CLI, API, JSON, YAML, Node.js, pnpm, npx
__SDK_*_VERSION__ / __APP_VERSION__
globals from astro.config.mjsAfter adding translations:
tsc --noEmit or dev server)@i18n Reviewer for linguistic quality check