Stack-neutral scalability rules for HTTP APIs and services.
Retrieve active cyber-threat intelligence — malware IOCs, C2 infrastructure, and CISA known-exploited vulnerabilities — filterable by…
Use when context is about to be lost — approaching auto-compaction, ending a long session, wrapping a multi-agent coordination cycle…
Use when the user asks to initialize or bootstrap the complete project documentation/conventions set, set up project conventions…
Transcribe a web article from a URL into a local markdown file with YAML frontmatter (title, author, date, source URL, word count).
Code review an Azure DevOps pull request
Set up or repair Cisco SCC Firewall Manager with either a complete pipx runtime or a managed Ansible companion for an existing Homebrew…
Conventions for adding or editing the SceneMenuBar above a scene's <SceneTitleSection>.
Create a scheduled task that can be run on demand or automatically on an interval.
Schedule meetings, calls, or events on the calendar.
Schedule on-device reminders and local actions only.
Produces correct JSON-LD for a page: maps page type to schema type, states required versus recommended properties, generates the block…
Build data-entry forms with Zod → JSON Schema → JSON Forms (jsonforms.io), custom Tailwind/token renderers, and typed submit wiring.
Builds, validates, and injects Schema.org JSON-LD multi-entity graphs (Person, VideoObject, AggregateRating, OfferCatalog, LocalBusiness…
Use when deciding which sci-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal…
Orchestrates the end-to-end academic publishing lifecycle for submissions to Scientia Sinica Informationis from topic selection to…
Evaluate whether a specific scientific claim or scientific-validity objection is supported by controlling derivation, data, code, figure…
Use only when the current deliverable is holistic, prioritized, multi-lens critique of audience-facing scientific communication or…
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix…
Load at the start of any build, fix, refactor, or "make it better" request, and again before every follow-up iteration on work already…
Use ONLY when delegated by pr-review to review PR-caused cohesion, coupling, and module-boundary problems.