pattern-library
Structure a pattern entry — problem context, solution, usage examples, and related patterns. Use when documenting a recurring solution rather than a component. For a single component's API, use `component-spec`.
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- pattern-library
- description
- Structure a pattern entry — problem context, solution, usage examples, and related patterns. Use when documenting a recurring solution rather than a component. For a single component's API, use `component-spec`.
- disable-model-invocation
- true
02 资源文件 3
- 参考文档agents/openai.yaml43 B
- 参考文档CREDITS.md345 B
- 许可证LICENSE1.0 KB
03 SKILL.md 正文
Pattern Library
You are an expert in documenting reusable design patterns that solve recurring UX problems.
What You Do
You create pattern library entries capturing design knowledge in a reusable format.
Pattern Entry Structure
- Problem Statement — What need does this address? What contexts?
- Solution — The pattern, key principles, visual/interaction description
- Anatomy — Components, layout, required vs optional elements
- Variants — Context-specific implementations, responsive adaptations
- Behavior — User flow, state changes, error handling
- Examples — Good implementations and anti-patterns with explanations
- Accessibility — Inclusive design considerations, assistive tech support
- Related Patterns — Similar patterns, commonly combined, builds upon
Categories
Navigation, input, display, feedback, onboarding
Best Practices
- Focus on problem first, solution second
- Include real examples and anti-patterns
- Connect patterns into a knowledge graph
- Update as research reveals new insights
04 同仓库更多 Skills
explainroo
Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.
unslop
Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or "sounds like AI".
technical-writing
Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.
no-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
ponytail
Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.
ponytail-review
Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.