common-non-native-mistakesRecurring error patterns from non-native English speakers in developer contexts: article misuse, preposition confusion, tense mismatch, 'I am agree'-style anti-patterns, and other frequent L2 slips. Use when scanning for patterns a reader can map back to…grammar-fundamentalsCore English grammar rules most likely to trip non-native developers: articles, subject-verb agreement, tense consistency, prepositions, countable vs mass nouns, comparatives. Use when reviewing grammar correctness of prose written for developer contexts…punctuation-rulesPunctuation conventions for developer prose: commas (serial, Oxford, clause-joining), semicolons, colons, hyphens vs en-dashes vs em-dashes, apostrophes, quotation marks. Use when reviewing punctuation of documentation, commit messages, or any prose where…technical-writingTechnical writing patterns for developer prose: API documentation structure, README shape, error-message wording, terminology consistency, and the active vs passive voice trade-off. Use when the text under review is documentation, a README, an API reference,…tone-calibrationPer-context tone rubrics for developer communication: commit messages, PR descriptions, code comments, API docs, emails, inline chat. Use when judging whether the register and formality of a piece of text fit its destination, not just whether it is…writing-guideMeta-skill that routes to the five focused writing skills in this plugin. Loads nothing substantive on its own — read this to decide which of grammar-fundamentals, punctuation-rules, tone-calibration, technical-writing, or common-non-native-mistakes to…
repository explorer
xiaolai · Repositories and representative skills - Page 2
Repository-level view of 208 collected skills across 22 GitHub repositories.
xros-compileCompile an XROS methodology spec through an oracle-first interview. Classifies the problem into verification tier A/B/C before anything else, then fills and validates a schema-valid JSON spec.xros-reasonThe Tier-C path — structured, adversarial reasoning for a claim that has NO mechanical check. Decomposes the claim into premises and verifies the checkable ones, runs a pre-mortem, and emits dated tripwires. Never runs the CDC engine, never claims a verified…xros-runExecute an XROS methodology spec — run a CDC-style search (diverse independent routes, blocked-route state, adversarial refutation, counterexample-fed loop-until-dry), then authoritatively verify the winning candidate by running its oracle command and gating…xros-sharpenOrient a newcomer in an unfamiliar field, sharpen a vague question into a falsifiable claim, then discover the currently best-available way to check it. First maps the field's minimal vocabulary (the nouns you can ask about, the verbs you can do), then…
experience-synthesisThis skill should be used when the user asks to "learn from past sessions", "extract lessons", "find what worked", "identify patterns in my workflow", "what mistakes did I make", "what decisions were made", or wants to synthesize wisdom and actionable…memory-managementUse when auditing, extracting, pruning, or writing Claude Code memory files. Covers memory file format, MEMORY.md index conventions, staleness scoring, claim extraction heuristics, destination routing, mutation rules, and archive conventions.git-miningThis skill should be used when the user asks to "check git history", "trace code changes", "find when something was added", "correlate commits with sessions", "find hotspot files", or needs to mine git repository history for insights. Only applicable when the…jsonl-coreThis skill should be used when the user asks to "analyze conversation history", "parse JSONL files", "read past sessions", "search conversation logs", "find what happened in a session", or needs to work with Claude Code's .jsonl conversation format. It…