Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问clear审计未展示

pagerkitpagerkit 开发

Agent Skill

pagerkit 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

11,823

周安装

407

GitHub Stars

公开资料未说明

下载量

4,129
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:pagerkit(pagerkit 开发)
来源仓库:https://github.com/clawdbot/skills
仓库路径:skills/pagerkit
安装命令:
npx skills add clawdbot/skills --skill "pagerkit"
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

AgentSkills.tonpx skills
npx skills add clawdbot/skills --skill "pagerkit"

简介

用于查找并安装 AI 代理的技能,支持关键词检索与结果筛选。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选技能。
  • 通过 npx skills add 命令从 GitHub 仓库安装指定技能。
  • 安装前需确认权限范围、维护状态及是否触发联网或文件读写。
  • 建议结合原始 README 验证功能边界与使用限制。

SKILL.md

name
PagerKit
description
Expert guidance on PagerKit, a SwiftUI library for advanced, customizable page-based navigation. Use when developers mention: (1) PagerKit, PKPagesView, PKPage, (2) custom page controls, indicators, or paging behavior, (3) cross-platform SwiftUI paging, (4) dynamic page generation, (5) integrating page views into custom layouts, (6) specific PagerKit modifiers or enums, (7) page view controller options, (8) event handling for page changes.

PagerKit Skill

Overview

This skill provides expert guidance on PagerKit, a powerful SwiftUI library for creating highly customizable and cross-platform page-based navigation. It covers everything from basic usage and dynamic page generation to advanced customization of page indicators, event handling, and best practices. Use this skill to help developers effectively implement flexible and visually rich paging experiences in their SwiftUI applications across all Apple platforms.

Agent Behavior (Follow These Rules)

  1. Clarify Paging Requirements: Always ascertain the user's specific needs regarding page content, indicator style, navigation flow, and platform targets before offering solutions.
  2. Prioritize idiomatic SwiftUI: Favor PagerKit's PKPageBuilder and ForEach for declarative page construction, aligning with SwiftUI's design principles.
  3. Platform-Specific Advice: When discussing indicator images, progress, or UIPageViewController options, always specify platform availability and correct type (UIImage vs. Image, UIPageControlProgress).
  4. Emphasize Modifiers: Direct users to the relevant PKPagesView or PKPage modifiers for customization, using full modifier signatures (e.g., .pkPageNavigationOrientation(_:)).
  5. Contextual Code Examples: Provide concise code snippets that illustrate the recommended usage within a PKPagesView or PKPage context.
  6. Highlight Cross-Platform: When possible, remind users of PagerKit's cross-platform consistency and how to handle platform-specific differences using #if os(...) directives.

Project Settings

PagerKit's behavior is influenced by the project's deployment targets and Swift version.

  • Deployment Targets: PagerKit supports iOS 14.0+, iPadOS 14.0+, macOS 14.0+, tvOS 14.0+, visionOS 1.0+, and watchOS 10.0+. Some features (e.g., UIPageControlProgress) are only available on specific platforms and OS versions.
  • Swift Version: Requires Swift 5.9+.

If these are unknown, ask the developer to confirm them, especially when discussing platform-specific features.

Quick Decision Tree

When a developer needs PagerKit guidance, follow this decision tree:

  1. Setting up a new pager?

* For basic installation and concepts → references/PagerKit.md * To define the overall pager structure → references/PKPagesView.md * To create individual page content → references/PKPage.md

  1. Generating pages dynamically from data?

* Using a collection of items → references/ForEach.md

  1. Controlling page flow or structure?

* Adding conditional pages (if/else) → references/PKPageBuilder.md * Setting horizontal or vertical navigation → references/PKPagesView.md (.pkPageNavigationOrientation)

  1. Customizing the page indicator (dots)?

* Changing color (active/inactive) → references/PKPagesView.md (.pkPageControlIndicatorTintColor, .pkPageControlIndicatorCurrentIndicatorTintColor) * Changing background style (minimal, prominent, automatic) → references/PKPageControlBackgroundStyle.md * Adjusting position or spacing → references/PKPagesView.md (.pkPageControlIndicatorAlignment, .pkPageControlPadding) * Setting layout direction (e.g., vertical alignment) → references/PKPageControlDirection.md * Using custom images (global or per-page) → references/PKPagesView.md, references/PKPage.md * Hiding the indicator (always or for single page) → references/PKPagesView.md

  1. Handling page change events or state?

* Binding to the current page index → references/PKPagesView.md (.pkCurrentPageIndex) * Reacting to manual page changes → references/PKPagesView.md (.pkOnManualPageChange) * Reacting to automatic page changes → references/PKPagesView.md (.pkOnAutoPageChange) * Identifying page transition direction → references/PKPageDirection.md * Actions on transition start/end → references/PKPagesView.md

  1. Customizing individual page behavior?

* Setting automatic transition duration → references/PKPage.md (.pkPageDuration) * Adding a custom footer to a page → references/PKPage.md (.pkPageFooter)

Triage-First Playbook

  • "My pages are not showing or look incorrect."

* Verify PKPagesView contains valid PKPage instances. Refer to references/PKPagesView.md, references/PKPage.md. * If using dynamic content, check ForEach implementation. Refer to references/ForEach.md.

  • "The page indicator is not positioned or styled correctly."

* Examine .pkPageControlIndicatorAlignment, .pkPageControlIndicatorBackgroundStyle, .pkPageControlIndicatorDirection modifiers on PKPagesView. Refer to references/PKPagesView.md, references/PKPageControlBackgroundStyle.md, references/PKPageControlDirection.md.

  • "I want to change the color of the active dot, but it's not working."

* Ensure .pkPageControlIndicatorCurrentIndicatorTintColor(_:) is used on PKPagesView. Refer to references/PKPagesView.md.

  • "Pages are not transitioning automatically."

* Check if .pkPageDuration(_:) is applied to the individual PKPages with a non-nil duration. Refer to references/PKPage.md.

  • "My conditional logic (if statements) inside PKPagesView is giving compiler errors."

* Review PKPageBuilder concepts, ensuring all branches return valid PKPage components. Refer to references/PKPageBuilder.md.

  • "How can I tell if the user swiped forward or backward?"

* Use the PKPageDirection parameter in .pkOnManualPageChange. Refer to references/PKPagesView.md, references/PKPageDirection.md.

Core Patterns Reference

Basic Pager Setup

PKPagesView {
    PKPage { Text("Page A").font(.title) }
    PKPage { Text("Page B").font(.title) }
    PKPage { Text("Page C").font(.title) }
}
.pkCurrentPageIndex(index: $currentPage) // Bind to @State
.pkPageNavigationOrientation(.horizontal)

Dynamic Pages with ForEach

struct Item: Identifiable {
    let id = UUID()
    let title: String
}

// ... inside a View
let items = [Item(title: "Item 1"), Item(title: "Item 2")]

PKPagesView {
    ForEach(items) { item in
        PKPage { Text(item.title) }
            .pkPageFooter { Text("Footer for \(item.title)") }
    }
}

Custom Page Indicator Styling

.pkPageControlIndicatorAlignment(spacing: 10, alignment: .bottomTrailing)
.pkPageControlIndicatorBackgroundStyle(.prominent)
.pkPageControlIndicatorDirection(.topToBottom) // Vertical dots
.pkPageControlIndicatorTintColor(.gray)
.pkPageControlIndicatorCurrentIndicatorTintColor(.blue)
// Custom images
#if os(iOS)
.pkPageControlIndicatorPreferredCurrentPageIndicatorImage(image: UIImage(systemName: "star.fill"))
#else
.pkPageControlIndicatorPreferredCurrentPageIndicatorImage(image: Image(systemName: "star.fill"))
#endif

Handling Page Change Events

.pkOnManualPageChange { currentIndex, direction in
    print("User navigated to page \(currentIndex) by going \(direction).")
}
.pkOnAutoPageChange { previousIndex, currentIndex in
    print("Auto change from \(previousIndex) to \(currentIndex).")
}
.pkOnTransitionEnd { previous, current in
    print("Transition ended. Was on \(previous), now on \(current).")
}

Integration Quick Guide

PagerKit is integrated via Swift Package Manager.

  1. Add Package Dependency: In Xcode, go to File > Add Package Dependency and enter https://github.com/SzpakKamil/PagerKit.git.
  2. Import: import PagerKit in your Swift files.
  3. Deployment Targets: Ensure your project targets iOS 14.0+, iPadOS 14.0+, macOS 14.0+, tvOS 14.0+, visionOS 1.0+, or watchOS 10.0+ (Swift 5.9+).

For detailed setup, see references/PagerKit.md.

Reference Files

Load these files as needed for specific topics:

  • PagerKit.md - General overview, setup, and core benefits.
  • PKPagesView.md - Detailed information on the main pager container and its global modifiers.
  • PKPage.md - Information on individual page creation and page-specific modifiers.
  • ForEach.md - How to generate pages from collections of data.
  • PKPageBuilder.md - Understanding the declarative content building for PKPagesView.
  • PKPageControlBackgroundStyle.md - Options for the background style of the page indicator.
  • PKPageControlDirection.md - Options for the layout direction of the page indicator dots.
  • PKPageDirection.md - Understanding the direction of page transitions.
  • _index.md - A comprehensive index for all PagerKit reference documentation.

Best Practices Summary

  1. Embrace Declarative UI: Use PKPageBuilder with ForEach for flexible and maintainable page construction.
  2. Customize Thoughtfully: Leverage the extensive modifier API to match native platform aesthetics and app branding, avoiding over-customization that hinders usability.
  3. Manage Pager State: Always bind pkCurrentPageIndex to external state (@State or @Binding) for programmatic control and observation.
  4. Implement Event Handling: Utilize callbacks (e.g., .pkOnManualPageChange, .pkOnTransitionEnd) for analytics, haptic feedback, or custom logic in response to navigation.
  5. Mind Platform Differences: Be aware of modifiers and features that behave differently or are only available on specific Apple platforms and OS versions.
  6. Prioritize Accessibility: Ensure custom indicators and footers remain accessible (e.g., with VoiceOver support).

Note: This skill is based on the comprehensive documentation for PagerKit. For further details, visit the official documentation at documentation.kamilszpak.com/documentation/pagerkit/ or the project website at kamilszpak.com/pl/pagerkit.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

windsurf

26.71%
按下载量换算1,103

trae

24.92%
按下载量换算1,029

OpenCode

17.58%
按下载量换算726

Codex

12.73%
按下载量换算526

Claude Code

8.4%
按下载量换算347

Antigravity

3.59%
按下载量换算148

安全审计

暂无安全审计结果可展示。

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills