← ClaudeAtlas

pick-enhancelisted

Enhance pages, a pick page that shows why an existing subject (a mechanic, design, look, UI, system) is weak, one section per problem, with fixes as takes for the author to pick. A page only; nothing is implemented. Use for /pick-enhance or when the author asks what's wrong with something and how to improve it. Argument `noxpln` leaves out each fix's Why.
SummerPain/pick-pages · ★ 2 · Web & Frontend · score 75
Install: claude install-skill SummerPain/pick-pages
# Enhance page An enhance page **improves what exists**. Each section is one problem; its takes are fixes. The author's picks end in a handoff note; the project itself stays unchanged. **Page base:** the pick-page skill (its SKILL.md, then reference/shell.md and reference/pick-line.md) and the project's profile. Visual subjects follow the profile's look rules. **Arguments:** the subject(s), the author's complaint if any, and `noxpln` (fixes without their Why). ## 1. Find the problems 1. Read the subject as it is now (pick-page A1). 2. List the problems. The author's words come first, marked "you said"; then your own findings, marked "found": numbers that don't hold up (a dead option, a must-pick, a stat that never matters, bad scaling), clashes with other parts, readability, multiplayer, cost against value, feel, and for looks the profile's look rules. 3. Back every finding with evidence: a number from the data, a line of code, a measurement, or a side-by-side with Now. Keep only what you can back. On the page the evidence is one plain line (pick-page's reference/words.md); its sources (the code line, the log, how it was measured) go in a comment beside the tab in `src/`, and into the handoff. ## 2. The page - `kind: 'enhance'`: any number of picks per section, including none. File: where the profile says. - One section per problem. Its name is the problem as a verdict («It is either fine or dead», not «Core health»); its `hook` is the label and how much it hurts («fou