elecdot

Help the human owner run CompeteHub delivery planning, issue slicing, PR readiness review, merge-readiness analysis, and standup sync.

Help a CompeteHub member regain enough context to continue assigned work.

Route non-trivial CompeteHub work through the project delivery workflow. Use when a task touches product scope, architecture, implementation, testing, documentation, GitHub issues or PRs, course reports, or agent-assisted delivery decisions.

Use CompeteHub's TDD workflow for testable behavior changes, bug regressions, backend rules, API validation, auth/permission checks, state transitions, reminders, subscriptions, recommendations, and review/publication workflows.

Deliver one focused CompeteHub implementation, bug fix, test, documentation, or process slice from issue or objective through impact analysis, TDD decision, code/docs changes, validation, and PR-ready summary.

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Create and edit reusable Obsidian note templates using the Templater plugin syntax and Templater JavaScript. Use when building daily, meeting, project, resource, or other note templates, converting notes into reusable templates, adding dynamic frontmatter or prompts, or organizing a repository-level template library under templates/.

Create and edit reusable Obsidian note templates using the Templater plugin syntax and Templater JavaScript. Use when building daily, meeting, project, resource, or other note templates, converting notes into reusable templates, adding dynamic frontmatter or prompts, or organizing a repository-level template library under templates/.

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.

Use when working on synthesizable RTL, custom AXI-Lite IP, protocol cores, register maps, hardware-facing Verilog/SystemVerilog changes, or simulation testbenches in this PYNQ-Z1 hardware design repository.

Use when working on PYNQ Python overlays, MMIO drivers, board-side runtime clients, notebooks, TCP socket transmission, PC-side receive services, payload protocols, storage, or analysis handoff in this sleep monitoring repository.

Use when working on Vivado projects, custom IP packaging, IP repositories, Block Design integration, Zynq PS wiring, AXI interconnects, XDC constraints, bitstream generation, or PYNQ overlay export in this PYNQ-Z1 repository.

Build compliant, reproducible crawlers for Chinese public policy text collection in the SRDI/Little-Giant research project. Use when Codex needs to plan, prototype, validate, or implement policy text crawlers; inspect government policy websites; create source maps; design policy-text schemas; parse HTML/API/PDF/Word policy sources; or turn exploratory crawler notebooks into production code. Always use a Jupytext percent-format notebook during the preparation and judgment phase before writing formal crawler code.

Use when Codex is asked to edit, create, refactor, or review research notebooks paired with Jupytext percent-format Python files, especially .ipynb plus .py:percent workflows where notebook content should be edited through the paired Python file instead of raw notebook JSON.