Use when a Spark change needs its authoritative owner, affected boundaries, risks, acceptance criteria, and smallest verifiable slice established before implementation or review.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Establish the change boundary from live repository evidence before recommending edits.
AGENTS.md, architecture/packages.json, the owning specification, package README, and nearby tests.Do not choose an owner from directory names or prompt prose when an enforced inventory or runtime path contradicts it. Resolve ambiguity from those sources first. If a new state owner or unresolved product choice requires an architecture decision, report the specific decision and continue independent scoped work.
Return owner, surfaces, invariants, risks, acceptanceCriteria, outOfScope, and blockers, citing paths and symbols.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when Spark engineering knowledge must be placed, deduplicated, migrated, or validated across AGENTS, Notes, Roles, Skills, and Workflows.
The English summary is being prepared. Showing the original description.
Use when adding or updating Spark AI provider models or their compact and preflight metrics, especially baidu-oneapi, Grok, Claude, GPT, DeepSeek, OneAPI, context windows, output budgets, prices, thinking maps, or transports.
The English summary is being prepared. Showing the original description.
Use when a Spark implementation needs an evidence-based review for correctness, ownership, compatibility, failure handling, maintainability, and unnecessary complexity.
The English summary is being prepared. Showing the original description.
Use when designing a Spark feature or writing or materially revising a design proposal that needs repository-first research, user input on unresolved key choices, and an owner-aligned implementation plan before code changes.
The English summary is being prepared. Showing the original description.
Use when a working Spark implementation should be simplified without changing its observed behavior, ownership, compatibility, or public contract.
The English summary is being prepared. Showing the original description.
Use when a running Spark or DSH web service needs real-browser verification — page load, client-plugin boot errors, console errors, failed requests, or onboarding/dialog rendering — with the repository's own Playwright chromium.
The English summary is being prepared. Showing the original description.