recap-integration
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.
Best use case
recap-integration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using recap-integration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/recap-integration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How recap-integration Compares
| Feature / Agent | recap-integration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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.
Related Skills
hubspot-integration
Expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects. Covers Node.js and Python SDKs.
gemini-api-integration
Use when integrating Google Gemini API into projects. Covers model selection, multimodal inputs, streaming, function calling, and production best practices.
jira-integration
Use this skill when retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues. Provides Jira API patterns via MCP or direct REST calls.
unsplash-integration
Integration skill for searching and fetching high-quality, free-to-use professional photography from Unsplash.
stripe-integration
Master Stripe payment processing integration for robust, PCI-compliant payment flows including checkout, subscriptions, webhooks, and refunds.
spline-3d-integration
Use when adding interactive 3D scenes from Spline.design to web projects, including React embedding and runtime control API.
robius-matrix-integration
CRITICAL: Use for Matrix SDK integration with Makepad. Triggers on: Matrix SDK, sliding sync, MatrixRequest, timeline, matrix-sdk, matrix client, robrix, matrix room, Matrix 集成, 聊天客户端
paypal-integration
Master PayPal payment integration including Express Checkout, IPN handling, recurring billing, and refund workflows.
payment-integration
Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when implementing payments, billing, or subscription features.
odoo-shopify-integration
Connect Odoo with Shopify: sync products, inventory, orders, and customers using the Shopify API and Odoo's external API or connector modules.
planning-oracle-to-postgres-migration-integration-testing
Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Analyzes a single project to identify repositories, DAOs, and service layers that interact with the database, then produces a structured testing plan. Use when planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation.
creating-oracle-to-postgres-migration-integration-tests
Creates integration test cases for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Generates DB-agnostic xUnit tests with deterministic seed data that validate behavior consistency across both database systems. Use when creating integration tests for a migrated project, generating test coverage for data access layers, or writing Oracle-to-PostgreSQL migration validation tests.