[pull] master from jaywcjlove:master

.codex/skills/awesome-mac-maintainer/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: awesome-mac-maintainer
+description: Maintain the Awesome Mac repository when adding, updating, or relocating app entries across README.md, README-zh.md, README-ja.md, and README-ko.md. Use this when the task requires category selection, multilingual sync, concise listing copy, ordering consistency, or repository-specific curation rules.
+---
+
+# Awesome Mac Maintainer
+
+Use this skill for repository curation tasks that touch app listings, especially when the user wants to add, update, or reclassify an app across the English, Chinese, Japanese, and Korean READMEs.
+
+## Use this skill for
+
+- Add a new app entry to the right category in `README.md`.
+- Sync the same app into `README-zh.md`, `README-ja.md`, and `README-ko.md`.
+- Update or shorten an existing listing without drifting from repository style.
+- Move an entry to a better category while preserving local document structure.
+
+For supported repository files and scope boundaries, see [references/supported-files.md](references/supported-files.md).
+
+## Core workflow
+
+1. Identify the most appropriate category by searching the existing README files for similar apps or keywords.
+2. Read the local context around the target section in each language before editing.
+3. Add or update the entry in all required language files.
+4. Keep the description to one sentence.
+5. Verify placement, wording, and formatting with `rg` and `git diff`.
+
+## Curation rules
+
+- Match the local section used by each document instead of assuming all four files have identical structure.
+- Preserve existing ordering within a section. In practice this is usually alphabetical by app name.
+- Do not rewrite neighboring entries unless needed for the requested task.
+- Keep edits narrowly scoped to the requested listing work.
+
+## Description style
+
+- Explain what the app is in one sentence.
+- Keep it brief and concrete.
+- Prefer product identity over feature lists.
+- Do not emphasize that the app is a macOS app unless that detail is necessary.
+- Avoid marketing phrasing unless the repository already uses it for that exact product.
+
+Preferred patterns:
+
+- "Open-source HTTP(S) debugging proxy for intercepting, inspecting, modifying, and replaying requests."
+- "Open-source screen recorder and editor for polished demos, tutorials, and product videos."
+- "Open-source tool for switching Git identities and managing SSH keys."
+
+## Icons and links
+
+- Use the product site or primary project URL for the main link when that matches surrounding entries.
+- If the project is open source and the repository URL is known, add the OSS icon linking to the repository.
+- If the project is presented as free/open source and nearby entries use the freeware marker, add `![Freeware][Freeware Icon]`.
+- Follow the exact icon formatting already used in the target section.
+
+## Category selection guidance
+
+- Prefer the category that contains the closest comparable apps already in the repo.
+- For developer tools, distinguish between:
+  - API clients / API development
+  - Network analysis / debugging proxies
+  - Version control
+- For media apps, check whether the document uses a broad audio/video section or a dedicated streaming music subsection.
+- If Chinese uses a more specific subsection than the other languages, follow that document's local structure rather than forcing uniform placement.
+
+## Validation
+
+- Search for the app name in all target files.
+- Review `git diff` for only the intended changes.
+- Confirm the entry appears once per intended file.
+- Confirm the wording remains one sentence in each language.
+
+## Scope boundary
+
+- This skill is for repository curation, not for rewriting the repository structure or reformatting unrelated content.
+- If the user asks for a broader taxonomy change, inspect the surrounding sections first and then make the smallest consistent change.

.codex/skills/awesome-mac-maintainer/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Awesome Mac Maintainer"
+  short_description: "Maintain multilingual Awesome Mac listings"
+  default_prompt: "Use $awesome-mac-maintainer to add or update app entries across README.md, README-zh.md, README-ja.md, and README-ko.md while preserving style and ordering."

.codex/skills/awesome-mac-maintainer/references/supported-files.md

@@ -0,0 +1,41 @@
+# Supported Files
+
+This skill is primarily for the repository's multilingual app listings.
+
+## Default targets
+
+- `README.md`
+- `README-zh.md`
+- `README-ja.md`
+- `README-ko.md`
+
+These are the default files for app additions, removals, description updates, and category moves unless the user explicitly asks to touch a different document set.
+
+## Working assumptions
+
+- The four README files are related, but their local section structure may differ.
+- English placement does not guarantee identical placement in Chinese, Japanese, or Korean.
+- When local structure differs, preserve the established structure in each file.
+
+## Included work
+
+- Add a new app listing.
+- Update an existing listing description.
+- Reclassify an app into a better category.
+- Normalize link and icon formatting for the touched entry.
+
+## Excluded by default
+
+- `command-line-apps.md`
+- `command-line-apps-zh.md`
+- `command-line-apps-ja.md`
+- `command-line-apps-ko.md`
+- `editor-plugin.md`
+- `editor-plugin-zh.md`
+- `editor-plugin-ja.md`
+
+Do not touch these files unless the user explicitly asks for them.
+
+## Placement rule
+
+Use the closest comparable apps already present in the target section as the primary signal for where a new entry belongs.

.gitattributes

@@ -0,0 +1 @@
+*.mjs linguist-language=Swift

.github/FUNDING.yml

@@ -1,9 +1,4 @@
-# These are supported funding model platforms
-
-github: [jaywcjlove]
-patreon: # Replace with a single Patreon username
-open_collective: jaywcjlove # Replace with a single Open Collective username
-ko_fi: # Replace with a single Ko-fi username
-tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
-community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
-custom: https://jaywcjlove.github.io/sponsor.html
+github: jaywcjlove
+# ko_fi: jaywcjlove
+# buy_me_a_coffee: jaywcjlove
+# custom: ["https://www.paypal.me/kennyiseeyou", "https://jaywcjlove.github.io/#/sponsor"]

.github/ISSUE_TEMPLATE/NEW_ADDITION_TO_LIST.yml

@@ -0,0 +1,46 @@
+name: 🎉 Addition to list
+description: Suggest an addition to this list.
+title: '🎉 Add <App Name>'
+labels: ['addition']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        NOTE: Each discrete (stand-alone) request should be in its own issue.
+
+        If you plan to open a PR with AI assistance, prefer the repository skill `.codex/skills/awesome-mac-maintainer` to keep category selection, ordering, and multilingual updates consistent.
+
+  - type: textarea
+    attributes:
+      label: 🪩 Provide a link to the proposed addition
+      description: Place link here.
+      placeholder: | 
+        https://github.com/jaywcjlove/awesome-mac
+        https://github.com/jaywcjlove/awesome-mac
+        https://github.com/jaywcjlove/awesome-mac
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: 😳 Explain why it should be added
+      description: A clear and concise description of why it should be added to this list.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: 📖 Additional context
+      description: Add any other context or screenshots about the feature request here.
+
+
+  - type: checkboxes
+    attributes:
+      label: 🧨 Issue Checklist
+      description: Put an x in the boxes once you've completed each step. You can also fill these out after creating the issue. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before responding to the issue.
+      options:
+        - label: I have checked for other similar issues
+        - label: I have explained why this change is important
+        - label: I have added necessary documentation (if appropriate)
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/REMOVE_ITEM_FROM_LIST.yml

@@ -0,0 +1,21 @@
+name: 🗑 Removal from list
+description: Suggest a removal from this list.
+title: '🗑 Remove <App Name>'
+labels: ['removal']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        NOTE: Each discrete (stand-alone) request should be in its own issue.
+
+  - type: textarea
+    attributes:
+      label: 😳 Explain why it should be removed
+      description: A clear and concise description of why it should be removed from this list.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: 📖 Additional context
+      description: Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,48 @@
+name: 🐞 Bug Report
+description: File a report when something goes wrong so it can get fixed!
+title: '🐞 Bug Report: xxx.md'
+labels: ['bug']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        NOTE: Each discrete (stand-alone) request should be in its own issue.  
+
+  - type: textarea
+    attributes:
+      label: 🐞 Describe the bug
+      description: A clear and concise description of what the bug is.
+      placeholder: ex. xxxx
+    validations:
+      required: true
+
+  - type: markdown
+    attributes:
+      value: |
+        **To Reproduce**
+        Steps to reproduce the behavior:
+        1. Go to '...'
+        2. Click on '....'
+        3. Scroll down to '....'
+        4. See error
+
+  - type: textarea
+    attributes:
+      label: 📖 Expected behavior
+      description: A clear and concise description of what you expected to happen.
+      placeholder: ex. xxxx
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: 🌅 Screenshots
+      description: If applicable, add screenshots to help explain your problem.
+      placeholder: ex. xxxx
+    validations:
+      required: true
+
+  - type: input
+    attributes:
+      label: "💻 Desktop"
+      placeholder: ex. `MacOS 13.0.1`