LanternCX

Use when changes may affect MailBot GitHub Actions, packaging, dependency setup, or release artifacts.

Use when implementing or reviewing MailBot Python changes that must follow project-specific architecture, callback, and logging conventions.

Use when MailBot behavior/config/UX changes and both English and Chinese documentation must remain synchronized.

Use when creating branches or commits in this repository and you must enforce MailBot git-flow, commit format, and agent co-author footer rules.

Use when major changes or blockers must be recorded and the .opencode progress index plus related governance docs need synchronization.

Use when non-instant work reaches a user-facing checkpoint and you need the user back for review, confirmation, reply, or completion.

Use this before creating or editing OpenCode skills, commands, agents, plugins, or config so you can confirm the official OpenCode docs and file locations first.

Use when a closed, reviewable change unit should be recorded in docs/superpowers/memory/

Use when design, planning, or implementation may depend on prior project decisions, existing boundaries, or earlier similar work

Use when performing any git branch, commit, merge, tag, or release action in this project.

Use when worktree setup is suggested in this repository, when a workflow references using-git-worktrees, or when Git actions must stay under the project-local git rules instead of the superpowers worktree flow.

Use when creating or modifying code, architecture, comments, logging, or persistent file behavior in this project.

Use when creating or updating README, user guides, developer guides, deployment docs, or documentation structure in this project.

Use when 需要创建模块、重构模块、补充代码注释、接入日志能力, 或确认本项目架构、注释、持久化与日志硬性规范时

Use when 需要新增、更新或整理项目文档, 并且必须判断用户文档与开发文档归属时

Use when 需要创建分支、准备提交、整理发布流程，或判断本项目 git flow、angular commit、提交确认与 co-author 约束时

Use when 提到 worktree、隔离工作区、并行工作区、避免污染当前工作区或不想影响当前未提交改动时

Use when performing branch, merge, and commit operations in this repository under Git Flow and Angular conventional commit constraints.

Use when adding or modifying Go source code in this repository and architecture boundaries, conventions, or test expectations need to be enforced.

Use when updating repository documentation so README, architecture notes, privacy boundary, OAuth setup, and git-flow guidance stay consistent.

Use when performing branch, merge, and commit operations in this repository under Git Flow and Angular commit constraints.

Use when adding or modifying Python source code in this repository and coding conventions or module boundaries need to be enforced.

Use when updating repository documentation so English and Chinese docs, architecture notes, and privacy boundaries remain consistent.

Locate project reference material. Use when a task depends on manuals, protocols, licenses, or other external reference documents.

Use when working in the HZCU Summer Semester project, preparing commits, writing commit messages, or deciding how project workflow rules should override generic process guidance.

Use when working in this course repository to turn a lab PDF into Markdown and produce a new 作业计划.md that matches an earlier lab's structure, answer style, and screenshot guidance.