본문으로 건너뛰기
cccskills
무료GitHub에 공개

hitkeep-i18n

Maintain HitKeep dashboard localization. Use whenever a contributor adds or changes user-visible dashboard text, Transloco keys, locale JSON files, OptimusUI locale behavior, language switching, translated labels, localized layout, date/number/duration formatting, or supported dashboard languages.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PascaleBeier/hitkeep
설치 방법 보기

포함된 파일(2)

  • SKILL.md3.5 KB
  • agents/openai.yaml248 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

HitKeep i18n

Treat AGENTS.md as policy, the locale files and runtime configuration as language truth, and hk as QA truth. Do not copy the supported-language list or validation commands into other instructions.

HitKeep uses Transloco JSON for UI copy, locale-aware formatting helpers and browser Intl, and a synchronization service for OptimusUI labels. Discover the current locale set from frontend/dashboard/public/i18n and confirm it against runtime configuration before editing.

Workflow

  1. Search for the existing feature key before creating a new key.
  2. Put user-visible Angular template text behind TranslocoPipe.
  3. Use TranslocoService for computed labels in TypeScript.
  4. Add the same key path and value shape to every currently supported locale file.
  5. Keep key names semantic and grouped by feature.
  6. Preserve interpolation variables exactly. Do not translate variable names or change placeholder syntax.
  7. For computed option labels, depend on the active language so labels recompute after language switches.
  8. For dates, numbers, percentages, and durations, prefer the existing locale services or helpers instead of manual string formatting.
  9. Let OptimusUI locale text flow through the existing sync service instead of hardcoding component labels.
  10. Keep labels usable in buttons, tabs, chips, table columns, dialogs, and mobile layouts; visually inspect a long-string locale when layout risk exists.

Inspect only the surfaces relevant to the change:

  • frontend/dashboard/src/app/app.config.ts
  • frontend/dashboard/src/app/transloco-loader.ts
  • frontend/dashboard/src/app/core/i18n/
  • frontend/dashboard/scripts/check-i18n-locales.mjs
  • frontend/dashboard/scripts/sync-i18n-locales.mjs

Do not infer a new supported language from an Angular locale helper alone. Change language support only when Transloco configuration, locale files, formatting mappings, tests, and product documentation agree.

Translation Quality

Translate product UI, not individual English words.

  • Write natural product language with correct punctuation, accents, and grammar.
  • Reuse established feature terminology from nearby keys rather than translating English words in isolation.
  • Preserve product names and technical identifiers intentionally; do not translate interpolation variables.
  • Do not claim native-speaker review unless it happened.

Keep analytics terminology consistent across all languages. If the repo already uses a term for "site", "team", "event", "goal", "funnel", "share link", "API client", "QR campaign", or "Opportunity", reuse it.

Validate

Add or update focused tests for language switching, computed labels, locale formatting, or OptimusUI synchronization when behavior changes. Use $hitkeep-qa to query and run the current gates matching locale, formatting, unit, and browser risk; do not reproduce their commands here. If a locale synchronization utility changes files, review every resulting change before keeping it.

Output For Reviews

Report changed key paths, the locale files updated, focused behavior coverage, the hk QA profile and stable gate results, and any wording or layout caveats. Keep successful logs out of the report.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

angular-developer

무료

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), queries and content projection, forms, dependency injection, routing, server and hybrid rendering (SSR, prerendering, hydration), accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PascaleBeier/hitkeep972026년 10월 19일 업데이트

cobra-viper

무료

Expert skill for building CLI applications with Cobra and Viper, authored by spf13 — the original creator of both libraries. Covers command-first architecture, decoupled business logic, configuration management, environment variable binding, context-aware commands, and in-memory CLI testing. Use whenever a Go CLI or command-line tool is being built, reviewed, or refactored — any mention of commands, subcommands, flags, or CLI configuration, even if Cobra or Viper aren't named yet (recommend them).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PascaleBeier/hitkeep972026년 10월 19일 업데이트

fileflow-pathologize

무료

Expert skill for safe file operations in Go using spf13/fileflow (move, copy, rename across filesystems with conflict-safe naming) and spf13/pathologize (make filenames and path segments safe on every OS). Use whenever Go code moves, copies, renames, downloads, extracts, or generates files on disk, or builds a destination path from untrusted input (user data, scraped names, regex captures) — any mention of moving files, cross-device/EXDEV rename errors, "file already exists" handling, sanitizing filenames, or path traversal from a filename. Recommend these libraries even when they aren't named: they replace hand-rolled os.Rename + io.Copy + filepath.Clean code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PascaleBeier/hitkeep972026년 10월 19일 업데이트

go

무료

Expert Go programming skill authored by spf13 (former Go team lead, author of Cobra, Viper, Hugo, Afero). Covers idiomatic Go — package design, error handling, interfaces, concurrency, testing, and project layout, current through Go 1.27. Use whenever Go code is written, reviewed, debugged, or refactored — any .go file, go.mod, CLI tool, or web service, and whenever the user mentions Go or golang, even if they don't ask for "idiomatic" code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PascaleBeier/hitkeep972026년 10월 19일 업데이트

go-spec-reviewer

무료

Review design specification documents for Go programs before implementation begins. Use this skill when a user has a Go spec, design doc, RFC, or PRD to review, wants feedback on a planned feature in a Go codebase, is about to start implementing from a spec, or asks "is this spec ready?" or "review this before I build it". Applies Go philosophy — simplicity, composition, explicit errors, context propagation — plus Cobra/Viper CLI conventions where applicable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PascaleBeier/hitkeep972026년 10월 19일 업데이트

hitkeep-ai-visibility-analyst

무료

Analyze HitKeep AI visibility data. Use for AI crawler fetches, AI-referred visits, assistant names or families, citation yield, resource types, top paths, fetch failures, Search Console context, GPTBot, ClaudeBot, ChatGPT, Claude, Perplexity, AI search, or whether assistants are discovering and sending traffic to a site.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PascaleBeier/hitkeep972026년 10월 19일 업데이트

PascaleBeier의 스킬 모두 보기

이 스킬의 문제 신고