Rank every live ticket into ../docs/PLAN.md and keep the shipped, canceled and on-hold folders true. Wrong today first, then dependencies, then cost; only the owner moves work on or off hold. Use when the user says "what should I build next", "rank the…
ryanallen/leaftext
SkillsMP has collected 14 skills from ryanallen/leaftext. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 14
- GitHub stars
- 5
- GitHub forks
- 0
Skills in this repository
Showing 14 of 14 collected skills.
Write a ticket — a Markdown plan with phases and a checkbox per piece of work, filed in a subject folder under ../docs/features/, ../docs/refactor/ or ../docs/fixes/. Reads ../docs/README.md first so it never re-plans what the tree already answered, writes…
Design a ticket before anyone builds it. Watches the fault happen in a running copy before it will name a cause — and where nothing can watch it, files the tooling that would as a ticket in front of this one rather than guessing. Then opens every line it…
Build a ticket from its path under ../docs/features/, ../docs/refactor/ or ../docs/fixes/. Designs it when needed, works its phases in order, drives what it can reach, runs the one complete check the ticket pays for after the last phase, and always stops at…
The one complete gate a ticket pays for, run once at the end of its build. Reads the change with /sync-tests so it has a test, then `just verify`; a failure is fixed and re-run, never explained past. Use when the user says "check it" or "verify", and when…
Retire a ticket on the owner's word, at any status. Moves it into ../docs/done/, updates the README and both plan files, syncs any page the change made false, reranks the live work and reads the running order back. Use when the owner says a ticket works, says…
Commit and push releases, the only skill allowed to write git. Ships built tickets for testing, sets their stage to Released, and tells the owner to run the done skill afterward. Use only when the user explicitly requests a release or git operation.
Update the docs under docs/ (and the site nav) so they match the current app — edit the right pages, take missing screenshots, lint the set for faults that live between pages, sweep every Markdown file in the repo and the plan tree next door off the disk,…
Make the tests match the code. Names the test that covers each change, writes the ones that are missing, and says what cannot be tested. With no argument it works the uncommitted diff; pass a path to audit a file or folder, or a git ref to work everything…
Teach the app to read another kind of file. One arm in src/format.rs, then fix every match the compiler then refuses — the file dialog, drag and drop, link following, the pager, the library pane and the render router all ask that one table, so there is never…
The comment bar for this repo, in one place. Why not what, match the density next door, one line if it fits, cut the drafting history, keep the version-numbered or measured history. A quality pass over comments only; it changes no logic. Use when the user…
Change how the app looks without writing a value by hand. A color goes in design/colors.md, any other value in design/tokens.md, an icon in design/icons.md, a component in design/components.md — then `just bundle-tokens`, `bundle-icons`, `bundle-gallery`.…
Add, split or reorder a file in src/assets/shell/ — the front-end, written as ordered fragments sharing one scope. Where it goes in the list is load-bearing, state.js holds only what more than one fragment touches, no fragment may carry a placeholder, and…
Weigh a new crate before it ships. Reports what it drags in transitively (`cargo tree`), what the platform already offers instead, whether default features can be off and whether one platform can be gated — then asks, because every crate reaches users and…