AgentSkillsCN

open-headers-guidelines

针对Open Headers仓库制定的项目专属指南。在该项目中进行文案撰写、翻译与本地化、文档编写或UI字符串开发时使用，以确保保留网络术语（如header、request、value、host、url、path等），并严格遵循项目术语规范。

SKILL.md
--- frontmatter
name: open-headers-guidelines
description: Project-specific guidelines for the Open Headers repo. Use when working on copy, translations/localization, docs, or UI strings in this project to preserve networking terms (header, request, value, host, url, path, etc.) and apply project terminology rules.

Open Headers Guidelines

Overview

Follow these rules whenever generating or editing language content in this repo, especially translations. Keep networking terms in English unless explicitly told otherwise.

Terminology Rules

  • •Do not translate "header" to Swedish "Rubriker". Use "header" (or "headers") as the canonical term.
  • •Keep these networking terms unchanged across languages: header, request, value, host, url, path.
  • •For related networking terms not listed, default to leaving them in English and ask if a translation is desired.
  • •Preserve original casing (for example, Header, URL) when matching surrounding text.

Commit Messages

Follow the Conventional Commits format. This is required because the release workflow generates changelogs from commit messages.

Format: <type>(<optional scope>): <description>

Types:

  • •feat: — new feature
  • •fix: — bug fix
  • •style: — visual/UI changes (not code style)
  • •refactor: — code restructuring without behavior change
  • •docs: — documentation only
  • •chore: — maintenance tasks (deps, CI, config)
  • •test: — adding or updating tests

Examples:

  • •feat: add localhost and path URL filters
  • •fix: keep action sync without Windows API listener
  • •style: dim action icon when native badge count is zero
  • •chore: bump version to 0.2.0

Keep descriptions lowercase, imperative, and concise. No trailing period.

Future Behavior

  • •A future feature will handle some of these fixes automatically; until then, apply these rules manually.