recap-integration — community recap-integration, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

このスキルについて

iOS エージェントが高度な Recap ライブラリ統合と Swift 開発機能を必要とする場合に最適です。 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]
Updated: 3/10/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/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
7/11
Quality Score
39
Canonical Locale
en
Detected Body Locale
en

iOS エージェントが高度な Recap ライブラリ統合と Swift 開発機能を必要とする場合に最適です。 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 を使用してシームレスに統合し、ユーザー エクスペリエンスを向上させるための新機能画面を提供します。

おすすめ

iOS エージェントが高度な Recap ライブラリ統合と Swift 開発機能を必要とする場合に最適です。

↓ 実現可能なユースケース for 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 supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Labs 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 & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is recap-integration?

iOS エージェントが高度な Recap ライブラリ統合と Swift 開発機能を必要とする場合に最適です。 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.

How do I install recap-integration?

Run the command: npx killer-skills add mergesort/Recap/recap-integration. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for recap-integration?

Key use cases include: カスタム表示トリガーを実現するために RecapDisplayPolicy を構成する, Swift を使用して Recap ライブラリを iOS アプリケーションに統合する, ユーザー エンゲージメントとフィードバックを向上させるための新機能画面を生成する.

Which IDEs are compatible with recap-integration?

This skill is compatible with 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. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for recap-integration?

Swift プログラミング言語が必要. Recap ライブラリと RecapDisplayPolicy に特有. iOS 開発環境に限定.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add mergesort/Recap/recap-integration. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use recap-integration immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Imported Repository Instructions

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Supporting Evidence

recap-integration

Install recap-integration, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly
Imported Repository Instructions
The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.
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.

関連スキル

Looking for an alternative to recap-integration or another community skill for your workflow? Explore these related open-source skills.

すべて表示

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
開発者