benchpress-docs
Read and search the BenchPress documentation. Use when working with BenchPress — its setup, configuration, API, and behavior.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-09
- Stars
- ★ 6
- Forks
- 1
01 前言 Front Matter
- name
- benchpress-docs
- metadata
- { "source": "leadtype" }
- description
- Read and search the BenchPress documentation. Use when working with BenchPress — its setup, configuration, API, and behavior.
03 SKILL.md 正文
BenchPress documentation
Press a button. Get a Frappe bench.
To work with BenchPress, read its documentation:
- Start at
/llms.txt(task-routed index) or/llms-full.txt(full context). - Every page is also available as Markdown at its
.mdURL.
04 同仓库更多 Skills
benchpress-docs
Read and search the benchpress documentation. Use when working with benchpress — its setup, configuration, API, and behavior.
ui-design
General UI/UX judgment for layout, polish, visual hierarchy, spacing, typography, color, and accessibility. Use when no product-specific or Frappe-specific design system skill applies.
technical-writing
Write prose in "Simplified Technical English". This applies to documentation, READMEs, commits, pull request, plans and release notes. It does not apply to code, identifiers, marketing copy, essays, or anything that needs a voice.
resolve-backport-conflicts
Resolve merge conflicts in a Mergify backport pull request. When a cherry-pick fails, Mergify commits the conflict markers as they are. This skill takes a pull request link or number as an argument.
quality-code-review
Review code for any Frappe application — a checklist distilled from years of engineering practice on correctness, security, performance, concurrency, readability, API design, and testing. Use this when reviewing a diff, a PR, or a piece of code for quality and security, or when you want a reviewer's checklist grounded in hard-won Frappe/ERPNext lessons.
issue-to-phases
Decompose a planning document (plan.md, a spec, or a GitHub issue) into incremental, independently-shippable "tracer bullet" phases, write them as phase specs under specs/, and optionally generate a Ralph loop (ralph.sh + prompt.md) that implements them unattended. Use this whenever the user hands you a plan and wants it broken into phases, mentions "tracer bullets", "phase 0/1/2", "build this in phases", "thin end-to-end slice first", "ralph loop", or wants phased specs in the specs/ folder — even if they never say the word "phase". Also use it when the user asks to "implement / work on phase N" of an existing spec folder, so the branch, the PR and the spec's status all move the way every earlier phase did.