brilliantrou
10 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
brilliantroughcode-review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".
- installazioni
- 2
- GitHub Stars
- 5
- Aggiornato
- 25 set
brilliantroughdomain-modeling
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
- installazioni
- 2
- GitHub Stars
- 5
- Aggiornato
- 25 set
brilliantroughexp-discuss
Talk a research idea through with the researcher before anything is designed or run. Use when a researcher brings a fuzzy idea, hypothesis, or direction ("我在想……", "你觉得这个方向……") and wants to think together rather than execute. Explore it through evidence-informed rounds of frontier questions, surface overlooked details, and sharpen what the researcher actually wants to observe; stop when both sides know which execution skill comes next — exp-campaign for a staged multi-branch plan, exp-batch for o
- installazioni
- 2
- GitHub Stars
- 5
- Aggiornato
- 25 set
brilliantroughexp-probe
Run one-off research spot experiments with minimal ceremony. Use when explicitly requested, or for a missing datapoint, a rerun after failure (OOM, crash), a sanity check of one configuration, a minimal bug reproduction, or a cheap measurement that a campaign needs before deciding. At most one focused question; run, record, report in one line. Escalate to exp-batch if the spot check turns into a branch, or exp-campaign if it reveals a decision tree; if the question itself is still fuzzy, route b
- installazioni
- 2
- GitHub Stars
- 5
- Aggiornato
- 25 set
brilliantroughmigrate-mem
Establish useful memory for a project that already has development history, or improve an incomplete memory setup. Survey the project and its existing evidence, then initialize or enrich human-readable StrictDoc docs/ with current norms and historical context. Use Magic Context and other available memory alongside it where useful. No previous workflow, legacy folder convention, or pre-existing StrictDoc skeleton is assumed.
- installazioni
- 2
- GitHub Stars
- 5
- Aggiornato
- 25 set
brilliantroughplan-brief
Turn a complex, thought-through requirement into a detailed execution plan document plus a self-contained launcher prompt for a fresh agent session, and later review that session's report. Use when the user wants a plan before execution, wants execution handed to a separate session, or mentions 执行计划 / 计划文档 / 新会话执行 / 交接 prompt / 审查 report; also when reviewing a plan's execution report or dispatching a fix round. Grills what is still missing, applies ponytail taste, treats partial completion as le
- installazioni
- 2
- GitHub Stars
- 5
- Aggiornato
- 25 set
brilliantroughquick-do
Execute small, well-understood changes directly in the current session with minimal ceremony and ponytail taste. Use when explicitly requested, or automatically for localized fixes, mechanical edits, config tweaks, and short scripts with clear behavior and a known verification path. No plan documents or grilling; do not add tests by default. Prefer steady-do when design, compatibility, or acceptance decisions remain; prefer plan-brief when planning and execution need a separate-session handoff.
- installazioni
- 2
- GitHub Stars
- 5
- Aggiornato
- 25 set
brilliantroughsave-mem
Preserve useful project knowledge through StrictDoc, Magic Context, and available memory tools, including overlapping storage where useful. Maintain readable current norms in StrictDoc; update them when a genuine decision change is clear and briefly inform the user, without routinely churning the canon. Ordinary memories and explanatory docs can evolve more freely. Favor concise phrases, lists, tables, and occasional PS explanations; choose storage, detail, and timing with judgment.
- installazioni
- 2
- GitHub Stars
- 5
- Aggiornato
- 25 set
brilliantroughsteady-do
Develop features in an existing project within the current session with ponytail taste. Use when explicitly requested, or automatically for ordinary feature, plugin, extension, and cross-module work that needs project understanding and clarification before implementation. Survey the real flow, grill only unresolved decisions, then implement and verify here without plan or handoff documents. Prefer quick-do for clear, bounded changes; prefer plan-brief when long-horizon work needs planning and se
- installazioni
- 2
- GitHub Stars
- 5
- Aggiornato
- 25 set
brilliantroughtdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
- installazioni
- 2
- GitHub Stars
- 5
- Aggiornato
- 25 set