协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
ponytail-audit【开发与工程】Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/ponytai…
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
ponytail-review, repo-wide. Scan the whole tree instead of a diff. Rank findings biggest cut first.
Same as ponytail-review:
delete: dead code, unused flexibility, speculative feature. Replacement: nothing.stdlib: hand-rolled thing the standard library ships. Name the function.native: dependency or code doing what the platform already does. Name the feature.reuse: equivalent helper, util, or pattern already in this repo. Name the path.yagni: abstraction with one implementation, config nobody sets, layer with one caller.shrink: same logic, fewer lines. Show the shorter form.Deps the stdlib or platform already ships, single-implementation interfaces,
factories with one product, wrappers that only delegate, files exporting one
thing, dead flags and config, hand-rolled stdlib, helpers duplicating an
equivalent that already lives in this repo.
Before emitting delete:, grep the whole tree for the symbol, including tests,
fixtures and string or dynamic references.
One line per finding, numbered and ranked: <N>. <tag> <what to cut>. <replacement>. [path],
so the user can say "fix 2 and 5".
End with net: -<N> lines, -<M> deps possible. Nothing to cut: Lean already. Ship.
Scope: over-engineering and complexity only. Correctness bugs, security holes, and performance are explicitly out of scope. Route them to a normal review pass. Lists findings, applies nothing. One-shot. "stop ponytail-audit" or "normal mode" to revert.