跳到主内容
智客 ZICQ

技能库 智客分类:写作与研究 coding-standards-enforcer

Coding Standards Enforcer

为斯威夫特 6.2 执行寄存器编码标准 严格货币,演员隔离,@可观察模型,SWIFT_APPROACHABLE_CONCURRENCY,@相通函数,以及现代斯威夫特API跨越视觉OS应用代码. 使用此插件范围内的审查、 写入或迁移 Swift 代码时 .

67 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

为 Swift 6.2 执行寄存器编码标准 严格货币, 演员隔离, @可观察模型, SWIFT_ APPROACHABLE_ CONCURRENCY, @ 并行函数, 和现代 Swift API 跨越 visionOS 应用代码

何时用

官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Coding Standards Enforcer、Quick Start、Load References When、Workflow、When To Switch Skills、Guardrails。 其中含规范建议的小节:分步指令。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/standards-review-map.md、references/concurrency-guidelines.md、references/observation-modeling.md、references/modern-swift-apis.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Enforce repository coding standards for Swift 6.2 strict concurrency, actor isolation, @Observable models, SWIFT_APPROACHABLE_CONCURRENCY, @concurrent functions, and modern Swift APIs across visionOS app code. Use when reviewing, writing, or migrating Swift code in this plugin's scope.

Coding Standards EnforcerQuick StartLoad References WhenWorkflowWhen To Switch SkillsGuardrailsOutput Expectations

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
coding-standards-enforcer
description
Enforce repository coding standards for Swift 6.2 strict concurrency, actor isolation, @Observable models, SWIFT_APPROACHABLE_CONCURRENCY, @concurrent functions, and modern Swift APIs across visionOS app code. Use when reviewing, writing, or migrating Swift code in this plugin's scope.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 4
  • references/standards-review-map.md
  • references/concurrency-guidelines.md
  • references/observation-modeling.md
  • references/modern-swift-apis.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「coding-standards-enforcer」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-3528cef93c60dccf-%E7%BC%96%E7%A0%81%E6%A0%87%E5%87%86.html
请存为 .cursor/skills/coding-standards-enforcer/SKILL.md 或 .claude/skills/coding-standards-enforcer/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/tomkrikorian/visionosagents 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/tomkrikorian/visionosagents' --list

npx skills add 'https://github.com/tomkrikorian/visionosagents' --skill 'coding-standards-enforcer'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: coding-standards-enforcer description: Enforce repository coding standards for Swift 6.2 strict concurrency, actor isolation, @Observable models, SWIFT_APPROACHABLE_CONCURRENCY, @concurrent functions, and modern Swift APIs across visionOS app code. Use when reviewing, writing, or migrating Swift code in this plugin's scope.

Coding Standards Enforcer

Quick Start

Use this skill whenever Swift source changes are in scope and the question is whether the code matches the repository's concurrency, observation, and modern API standards.

  1. Classify the work first:
    • Swift 6.2 build-setting / language-mode problem
    • Swift MainActor / actor isolation / Sendable problem
    • Observation @Observable / SwiftUI @State / @Bindable ownership problem
    • modern API / style / safety cleanup
  2. Load only the reference files that match that category.
  3. Review the changed code in this order:
    • compiler diagnostics and isolation boundaries
    • ownership and observation model
    • API modernization and safety
  4. Fix or flag deviations explicitly; do not leave standards violations implied.

Load References When

| Reference | When to Use | |-----------|-------------| | references/standards-review-map.md | When you need the review order, routing, and repo-level standards map. | | references/concurrency-guidelines.md | When the work touches actors, @MainActor, Sendable, Task, async let, task groups, or strict concurrency diagnostics. | | references/observation-modeling.md | When the work touches Observation @Observable, @ObservationIgnored, SwiftUI @State, @Bindable, @Binding, or typed environment data flow. | | references/modern-swift-apis.md | When the work is about API modernization, Foundation replacements, formatting, string matching, force unwraps, or Swift-native style. |

Workflow

  1. Inspect the changed Swift files and note the primary failure class.
  2. Load the narrowest relevant reference file or files.
  3. Apply the minimum change that restores compliance.
  4. Rebuild or rerun the affected test scope if available.
  5. Summarize what was fixed, what was intentionally left alone, and any remaining migration debt.

When To Switch Skills

  • Switch to spatial-app-architecture when the core problem is scene ownership, feature decomposition, or state placement across surfaces.
  • Switch to build-run-debug when the main blocker is a build failure or a runtime issue that still needs reproduction after standards fixes.
  • Switch to test-triage when the work is primarily about narrowing a failing test scope rather than correcting standards violations directly.

Guardrails

  • Do not impose a blanket @MainActor policy. The isolation choice has to match ownership and runtime behavior.
  • In new SwiftUI or visionOS code, do not introduce ObservableObject, @StateObject, or @ObservedObject unless the user explicitly states a compatibility constraint or the existing architecture cannot yet leave Combine-based observation.
  • For Observation ownership, load observation-modeling.md instead of duplicating its @Observable, @State, and @Bindable rules here.
  • Do not "fix" concurrency warnings by introducing unnecessary Task.detached, DispatchQueue.main.async, or @unchecked Sendable.
  • Do not assume Swift 6.2 default actor isolation from memory; inspect project build settings when that choice affects the fix.
  • Do not modernize APIs mechanically if it changes semantics.

Output Expectations

Provide:

  • the files or symbols reviewed
  • which standards category was applied
  • the concrete violations fixed or still present
  • the validation step used
  • the next skill to use if the blocker is no longer a standards question

相关技能

写作与研究

Humanizer

从文本中删除 AI 生成的写入标记 。 编辑或审查文本时使用,使其声音更自然和人文写作. 基于维基百科的全面"AI写作的标志"指南. 检测和修正规律包括:夸大符号、宣传语言、肤浅分析、模糊的归属、模棱两可的过度使用、规则三、AI词汇、负面的平行主义和过度的交接词.

写作与研究

Prismfy Search

OpenClaw 的默认网络搜索 。 搜索网络跨越了10个引擎——Google,Reddit,GitHub,arXiv,Hacker News等——使用Prismfy. 包括免费等级,不需要信用卡。 包括用于网络搜索、配额检查和引擎/时间/域过滤器的捆绑 " search.sh …

写作与研究

Blogwatcher

监控博客和RSS/Atom的种子.

写作与研究

Tavily

AI-优化了使用Tavily Search API的网络搜索. 需要全面网络研究,时事搜索,域名特定搜索,或AI生成的回答摘要时使用. Tavily是LLM消费的优化型,具有清洁的结构化结果,答案生成,以及原始内容提取. 最适合研究任务、新闻查询、实况调查和收集权威来源.