All authors
Claude Skills by JashIbra
github.com/JashIbra6 skills0 installs0 views
- Explain LineDrill-down explanation of one line of code, one question at a time — a one-sentence answer first, then only what the reader asks next, with real values from their project and, when asked, the equivalent in the language they write every day. Use when someone points at a specific line of code and asks what it does or checks, where a value in it comes from, or how it knows something; or invokes /explain-line with a line of code, a file:line, or a step number from a request trace (`N` or `N.M`). ...Votes: 0GitHub stars: 3
- Request Feature TraceFeature walkthrough — one user action followed through EVERY call in order, changed or not, with each function, variable and command explained the way a senior colleague explains it to a junior, and the work this feature added marked along the way. Use when the user types /request-feature-trace, or asks for the whole path of a feature "from the button press", "every function in order", "explain it like to a junior". For a review of a branch's changes only, use `request-trace`.Votes: 0GitHub stars: 3
- Request Trace ShortA short request trace — the same numbered walk of one user action through the code as `request-trace`, cut to about ten steps with one-sentence bullets, for a reader who wants the route at a glance rather than every mechanism. Use only when the user types /request-trace-short or asks for a "short", "brief" or "condensed" request trace. For the full trace use `request-trace`.Votes: 0GitHub stars: 3
- Request Trace Ste ShortA short request trace in ASD-STE100 wording — the condensed walk of `request-trace-short` (about ten steps, one-sentence bullets) written in the simple style of `request-trace-ste`. Use only when the user types /request-trace-ste-short or asks for a short request trace "in STE" or "in simple language". For the full STE trace use `request-trace-ste`.Votes: 0GitHub stars: 3
- Request Trace SteRequest trace written in the style of ASD-STE100 (Simplified Technical English), about 80% strict — the same numbered walk through the code as `request-trace`, with every sentence short, one idea each, active voice, present tense. Use only when the user types /request-trace-ste or asks for the request trace "in STE", "in simple language" or "by ASD-STE100". For the ordinary trace use `request-trace`.Votes: 0GitHub stars: 3
- Request TraceRequest trace — a numbered walk of one user action through the code, from the tap in the client to the response and what happens afterwards, with the mechanics of each call spelled out underneath. Use when someone asks for the path of a request, the call chain, "what calls what", "walk me through it", or is about to review an unfamiliar feature.Votes: 0GitHub stars: 3