Token导航 LogoToken导航

Agent Skill · 前端设计

arrange(arrange 测试)

arrange 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

arrange 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 16。

总安装 933,768周安装 39,327GitHub Stars 23,117下载 326,976核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/pbakaus/impeccable --skill arrange

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

评估和改进布局间距、视觉层次和节奏,将一般排列转变为有意的构图。

通过系统评估(包括用于识别主要和次要内容的斜视测试)来分析当前的间距一致性、视觉层次、网格结构和节奏 使用一致的尺度(框架标记、基于 rem 或自定义)建立语义间距系统并应用间隙 用于兄弟间距而不是边距 按用例推荐布局工具:用于 1D 布局和组件的 Flexbox、用于 2D 页面级结构的 Grid,以及有关重复(自动调整、minmax())等响应模式的指导 通过改变尺寸、混合卡片和非卡片内容以及使用间距和对齐方式实现自然视觉分组,打破单调的卡片网格图案 需要前端设计技能及其上下文收集协议作为先决条件;包括光学调整指导和用于深度管理的语义 z 索引刻度

来源仓库内路径:skills/arrange

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/pbakaus/impeccable --skill arrange;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

arrange 怎么安装?

在终端执行 npx skills add https://github.com/pbakaus/impeccable --skill arrange。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

arrange 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

arrange 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

arrange 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

arrange 用的人多吗?

公开数据是累计安装 933,768 次,近一周安装 39,327 次,下载 326,976 次,GitHub 23,117 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

arrange 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 来源仓库有 23,117 星,维护活跃度相对可查。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
arrange

arrange 测试 · 本页

933,76823,117只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Assess and improve layout and spacing that feels monotonous, crowded, or structurally weak — turning generic arrangements into intentional, rhythmic compositions.

MANDATORY PREPARATION

Invoke /impeccable — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /impeccable teach first.


Assess Current Layout

Analyze what's weak about the current spatial design:

  1. Spacing:

- Is spacing consistent or arbitrary? (Random padding/margin values) - Is all spacing the same? (Equal padding everywhere = no rhythm) - Are related elements grouped tightly, with generous space between groups?

  1. Visual hierarchy:

- Apply the squint test: blur your (metaphorical) eyes — can you still identify the most important element, second most important, and clear groupings? - Is hierarchy achieved effectively? (Space and weight alone can be enough — but is the current approach working?) - Does whitespace guide the eye to what matters?

  1. Grid & structure:

- Is there a clear underlying structure, or does the layout feel random? - Are identical card grids used everywhere? (Icon + heading + text, repeated endlessly) - Is everything centered? (Left-aligned with asymmetric layouts feels more designed, but not a hard and fast rule)

  1. Rhythm & variety:

- Does the layout have visual rhythm? (Alternating tight/generous spacing) - Is every section structured the same way? (Monotonous repetition) - Are there intentional moments of surprise or emphasis?

  1. Density:

- Is the layout too cramped? (Not enough breathing room) - Is the layout too sparse? (Excessive whitespace without purpose) - Does density match the content type? (Data-dense UIs need tighter spacing; marketing pages need more air)

CRITICAL: Layout problems are often the root cause of interfaces feeling "off" even when colors and fonts are fine. Space is a design material — use it with intention.

Plan Layout Improvements

Consult the spatial design reference from the impeccable skill for detailed guidance on grids, rhythm, and container queries.

Create a systematic plan:

  • Spacing system: Use a consistent scale — whether that's a framework's built-in scale (e.g., Tailwind), rem-based tokens, or a custom system. The specific values matter less than consistency.
  • Hierarchy strategy: How will space communicate importance?
  • Layout approach: What structure fits the content? Flex for 1D, Grid for 2D, named areas for complex page layouts.
  • Rhythm: Where should spacing be tight vs generous?

Improve Layout Systematically

Establish a Spacing System

  • Use a consistent spacing scale — framework scales (Tailwind, etc.), rem-based tokens, or a custom scale all work. What matters is that values come from a defined set, not arbitrary numbers.
  • Name tokens semantically if using custom properties: --space-xs through --space-xl, not --spacing-8
  • Use gap for sibling spacing instead of margins — eliminates margin collapse hacks
  • Apply clamp() for fluid spacing that breathes on larger screens

Create Visual Rhythm

  • Tight grouping for related elements (8-12px between siblings)
  • Generous separation between distinct sections (48-96px)
  • Varied spacing within sections — not every row needs the same gap
  • Asymmetric compositions — break the predictable centered-content pattern when it makes sense

Choose the Right Layout Tool

  • Use Flexbox for 1D layouts: Rows of items, nav bars, button groups, card contents, most component internals. Flex is simpler and more appropriate for the majority of layout tasks.
  • Use Grid for 2D layouts: Page-level structure, dashboards, data-dense interfaces, anything where rows AND columns need coordinated control.
  • Don't default to Grid when Flexbox with flex-wrap would be simpler and more flexible.
  • Use repeat(auto-fit, minmax(280px, 1fr)) for responsive grids without breakpoints.
  • Use named grid areas (grid-template-areas) for complex page layouts — redefine at breakpoints.

Break Card Grid Monotony

  • Don't default to card grids for everything — spacing and alignment create visual grouping naturally
  • Use cards only when content is truly distinct and actionable — never nest cards inside cards
  • Vary card sizes, span columns, or mix cards with non-card content to break repetition

Strengthen Visual Hierarchy

  • Use the fewest dimensions needed for clear hierarchy. Space alone can be enough — generous whitespace around an element draws the eye. Some of the most sophisticated designs achieve rhythm with just space and weight. Add color or size contrast only when simpler means aren't sufficient.
  • Be aware of reading flow — in LTR languages, the eye naturally scans top-left to bottom-right, but primary action placement depends on context (e.g., bottom-right in dialogs, top in navigation).
  • Create clear content groupings through proximity and separation.

Manage Depth & Elevation

  • Create a semantic z-index scale (dropdown → sticky → modal-backdrop → modal → toast → tooltip)
  • Build a consistent shadow scale (sm → md → lg → xl) — shadows should be subtle
  • Use elevation to reinforce hierarchy, not as decoration

Optical Adjustments

  • If an icon looks visually off-center despite being geometrically centered, nudge it — but only if you're confident it actually looks wrong. Don't adjust speculatively.

NEVER:

  • Use arbitrary spacing values outside your scale
  • Make all spacing equal — variety creates hierarchy
  • Wrap everything in cards — not everything needs a container
  • Nest cards inside cards — use spacing and dividers for hierarchy within
  • Use identical card grids everywhere (icon + heading + text, repeated)
  • Center everything — left-aligned with asymmetry feels more designed
  • Default to the hero metric layout (big number, small label, stats, gradient) as a template. If showing real user data, a prominent metric can work — but it should display actual data, not decorative numbers.
  • Default to CSS Grid when Flexbox would be simpler — use the simplest tool for the job
  • Use arbitrary z-index values (999, 9999) — build a semantic scale

Verify Layout Improvements

  • Squint test: Can you identify primary, secondary, and groupings with blurred vision?
  • Rhythm: Does the page have a satisfying beat of tight and generous spacing?
  • Hierarchy: Is the most important content obvious within 2 seconds?
  • Breathing room: Does the layout feel comfortable, not cramped or wasteful?
  • Consistency: Is the spacing system applied uniformly?
  • Responsiveness: Does the layout adapt gracefully across screen sizes?

Remember: Space is the most underused design tool. A layout with the right rhythm and hierarchy can make even simple content feel polished and intentional.

平台分布

Codex

36.48%
按下载量换算119,281

Claude

30.71%
按下载量换算100,414

Cursor

18.63%
按下载量换算60,916

Gemini CLI

9.42%
按下载量换算30,801

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills