菜单
Use when creating or reviewing pull requests. Covers PR title format (Conventional Commits), required issue reference, three-section description template (What changed / Why / How to test), 400-line diff limit, screenshot requirements for UI changes, squash merge strategy, and review requirements.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | pr-standards |
| description | Use when creating or reviewing pull requests. Covers PR title format (Conventional Commits), required issue reference, three-section description template (What changed / Why / How to test), 400-line diff limit, screenshot requirements for UI changes, squash merge strategy, and review requirements. |
All pull requests in this repository must follow these standards.
PR titles must follow the same format as commit messages (Conventional Commits — see commit-conventions/SKILL.md):
<type>(<scope>): <subject>
Examples:
feat(workspace): add CTF vs general workspace type selectionfix(sync): run wal_checkpoint before git pushdocs(readme): add Docker setup instructionsEvery PR must reference at least one issue in the description. Use one of:
Closes #42
Fixes #17
Refs #55 (for issues that are related but not fully resolved)
No issue? Create one before opening the PR.
Every PR description must include these three sections:
## What changed
<!-- Describe what was changed at a high level. Be specific. -->
## Why
<!-- Explain the motivation. What problem does this solve? What user impact does it have? -->
## How to test
<!-- Step-by-step instructions to verify the change works correctly. -->
- [ ] Step 1
- [ ] Step 2
- [ ] Step 3
main history clean and linear.main.Delete the source branch after merging. GitHub can be configured to do this automatically.
Use draft PRs ([Draft] or GitHub Draft mode) for work in progress that needs early feedback. Do not merge a draft PR.
Analyzes a new project's codebase by asking targeted questions until it has enough context, then writes a rich initial memory vault — decisions, patterns, architecture, and a seeded MOC. Use when setting up memory for the first time on a project, or when the vault is empty and agents have no prior context.
Compress natural language memory files (CLAUDE.md, AGENTS.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman:compress <filepath> or "compress memory file"
Provides a deep dual-assessment design critique combining AI design review with manual pattern analysis. Use when the user wants expert design feedback, heuristic evaluation, or a thorough UX critique.
Senior UI/UX Engineer. Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when building web components, pages, artifacts, dashboards, or applications — or any request for UI/UX work, styling, beautification, or frontend code. Enforces Anti-Codex aesthetics inspired by Linear, Raycast, Stripe, and GitHub. Driven by metric dials, strict component architecture, hardware-accelerated motion, and curated design systems.
Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing.
Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.