recap-integration — community recap-integration, community, ide skills

v1.0.0
GitHub

关于此技能

非常适合需要高级 Recap 库集成和 Swift 开发能力的 iOS 代理。 Integrates the Recap Swift package into SwiftUI apps, authors Recap-compatible releases markdown, and configures RecapDisplayPolicy and RecapScreen customization. Use when adding Recap into an app, updating Releases.md, or customizing the behavior of a Recap screen.

mergesort mergesort
[255]
[11]
更新于: 3/10/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 6/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
6/11
Quality Score
39
Canonical Locale
en
Detected Body Locale
en

非常适合需要高级 Recap 库集成和 Swift 开发能力的 iOS 代理。 Integrates the Recap Swift package into SwiftUI apps, authors Recap-compatible releases markdown, and configures RecapDisplayPolicy and RecapScreen customization. Use when adding Recap into an app, updating Releases.md, or customizing the behavior of a Recap screen.

核心价值

赋予代理配置和利用 Recap 库的 RecapDisplayPolicy 的能力，利用 Swift 和 RecapScreen 实现无缝集成，并提供一个新增功能屏幕以增强用户体验。

适用 Agent 类型

非常适合需要高级 Recap 库集成和 Swift 开发能力的 iOS 代理。

↓ 赋予的主要能力 · recap-integration

配置 RecapDisplayPolicy 以实现自定义显示触发器
使用 Swift 将 Recap 库集成到 iOS 应用程序中
生成新增功能屏幕以提高用户参与度和反馈

! 使用限制与门槛

  • 需要 Swift 编程语言
  • 特定于 Recap 库和 RecapDisplayPolicy
  • 仅限于 iOS 开发环境

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

评审后的下一步

先决定动作，再继续看上游仓库材料

Killer-Skills 的主价值不应该停在“帮你打开仓库说明”，而是先帮你判断这项技能是否值得安装、是否应该回到可信集合复核，以及是否已经进入工作流落地阶段。

安装路径

先进入安装与验证

如果这项技能值得继续，下一步应该先确认安装命令、CLI 写入路径与环境验证。
可信复核

回到可信合集再做一次复核

如果你还在比较不同技能或供应方，先回到可信合集做二次判断，而不是继续放大仓库噪音。
工作流

如果要进团队流转，转到工作流集合

当你的目标已经不是单个技能，而是团队协作、审批和交接，就应该转到工作流合集继续决策。
实验室 Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

常见问题与安装步骤

以下问题与步骤与页面结构化数据保持一致，便于搜索引擎理解页面内容。

? FAQ

recap-integration 是什么？

非常适合需要高级 Recap 库集成和 Swift 开发能力的 iOS 代理。 Integrates the Recap Swift package into SwiftUI apps, authors Recap-compatible releases markdown, and configures RecapDisplayPolicy and RecapScreen customization. Use when adding Recap into an app, updating Releases.md, or customizing the behavior of a Recap screen.

如何安装 recap-integration？

运行命令：npx killer-skills add mergesort/Recap/recap-integration。支持 Cursor、Windsurf、VS Code、Claude Code 等 19+ IDE/Agent。

recap-integration 适用于哪些场景？

典型场景包括：配置 RecapDisplayPolicy 以实现自定义显示触发器、使用 Swift 将 Recap 库集成到 iOS 应用程序中、生成新增功能屏幕以提高用户参与度和反馈。

recap-integration 支持哪些 IDE 或 Agent？

该技能兼容 Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer。可使用 Killer-Skills CLI 一条命令通用安装。

recap-integration 有哪些限制？

需要 Swift 编程语言；特定于 Recap 库和 RecapDisplayPolicy；仅限于 iOS 开发环境。

↓ 安装步骤

  1. 1. 打开终端

    在你的项目目录中打开终端或命令行。

  2. 2. 执行安装命令

    运行：npx killer-skills add mergesort/Recap/recap-integration。CLI 会自动识别 IDE 或 AI Agent 并完成配置。

  3. 3. 开始使用技能

    recap-integration 已启用，可立即在当前项目中调用。

! 参考页模式

此页面仍可作为安装与查阅参考，但 Killer-Skills 不再把它视为主要可索引落地页。请优先阅读上方评审结论，再决定是否继续查看上游仓库说明。

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

recap-integration

安装 recap-integration，这是一款面向AI agent workflows and automation的 AI Agent Skill。查看评审结论、使用场景与安装路径。

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Recap Integration

Use this skill when integrating, configuring, or using the Recap library.

What to read first

Start with these files:

  • README.md
  • Sources/Recap/Public/RecapScreen.swift
  • Sources/Recap/Public/View+Recap.swift
  • Sources/Recap/Public/RecapDisplayPolicy.swift
  • Sources/Recap/Public/RecapDisplayPolicy.Trigger.swift
  • Demo/Demo/Assets/Releases.md
  • Demo/Demo/DemoRecapScreen.swift

Read additional public API files in Sources/Recap/Public/ only if the task touches a specific type.

Core workflow

  1. Identify whether the task is about integration, release authoring, display policy, or screen customization.
  2. Prefer Recap's public APIs over custom implementations.
  3. Match existing Recap naming and examples from the README and demo app.
  4. Keep examples and release content user-facing and concise.

Integration rules

  • Prefer ReleasesParser(fileName:) for bundled release markdown.
  • Prefer RecapScreen(releases:) as the entry point for presentation.
  • Prefer RecapDisplayPolicy and RecapDisplayPolicy.Trigger over hand-rolled version gating.
  • Prefer .recapScreenPaginationStyle(.automatic) unless the user explicitly wants forced .labeled or .compact.
  • When customizing behavior, use View+Recap modifiers instead of editing internal implementation unless the task is explicitly a library change.

Release markdown rules

When creating or editing a Recap releases markdown file:

  • Keep the newest release first.
  • Follow the schema documented in README.md.
  • Use one release section per app version.
  • Use user-facing feature titles and descriptions, not commit-style summaries.
  • Choose the semantic change type (Major, Minor, Patch) based on product impact, not commit count.
  • Reuse the style and structure of Demo/Demo/Assets/Releases.md.

Mac Catalyst guidance

If the task touches Mac Catalyst:

  • Preserve the distinction between automatic pagination, labeled buttons, and compact buttons.
  • Be careful not to regress iPhone or iPad behavior while changing Catalyst presentation.

Avoid

  • Do not invent a different release markdown format.
  • Do not parse releases manually if ReleasesParser is sufficient.
  • Do not replace RecapDisplayPolicy with custom version-comparison logic unless the user explicitly needs behavior outside the public API.

相关技能

寻找 recap-integration 的替代方案 (Alternative) 或可搭配使用的同类 community Skill？探索以下相关开源技能。

查看全部

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

为prompts.chat的信息反馈系统生成可定制的插件小部件

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

React 框架

★ 138.4k
⑂ 0
浏览器

pr-review

Logo of pytorch
pytorch

Python中具有强大GPU加速的张量和动态神经网络

★ 98.6k
⑂ 0
开发者工具