exception-coder
@exception-coder
Public Skills
comment-cleanup
by exception-coder
"当用户明确要求批量清理存量代码中的版本标记、历史叙事、废话、死代码或其他违规注释时使用；不用于普通改码时的顺手清理。"
git-commit-standards
by exception-coder
Use when a task has completed changes ready for automatic local commit, or before any git commit or commit-message generation. Requires synchronized documentation, current validation, scoped staging, a three-part Chinese body, and a real Author; push authorization is separate.
delivery-verification
by exception-coder
"Use after executable project changes and before declaring completion. Prefer forge_verify when available, require current PASS evidence, and drive a bounded repair-and-reverify loop."
change-readiness
by exception-coder
"Use before implementing a requirement, feature, refactor, concrete solution, architecture change, or source-code modification. Automatically routes OpenSpec-enabled projects through a matching or newly created change, keeps its artifacts current, reviews risk, and resolves precise implementation coordinates."
markdown-writing-standards
by exception-coder
"Use when delivering suite or project updates to synchronize affected documentation, and when creating or structurally editing Markdown. Covers documentation impact, deduplication, Markdown/Mermaid validation, and index registration."
backend-evidence
by exception-coder
"Use for backend changes or analysis involving DDL, SQL, data relations, states, fields, events, APIs, domain invariants, reverse impact, runtime evidence, or query performance. Keeps Graphify implementation facts, OpenSpec behavior, and database/runtime truth distinct."
business-logic-orientation
by exception-coder
"Use to understand existing business logic before refactoring, rewriting, migration, or regression review, or when the user explicitly requests a logic-orientation document. Prefers Graphify and accepted OpenSpec specs over rebuilding parallel code indexes."
init-project-docs
by exception-coder
"用于接入新代码项目或系统，以及初始化、刷新或检查项目上下文；安全幂等地建立 Agent、文档索引、OpenSpec、Graphify 输入与 Git 共享边界，并编排领域知识和新鲜度状态。"
daily-work-log
by exception-coder
"业务项目源码发生修改，或用户要求记录、更新工作日志时使用；将同一 Bug 或功能的多轮改动合并到当天个人工作日志。"
dart-coding-standards
by exception-coder
Use when writing, reviewing, or modifying Dart or Flutter code. Covers Dart-specific naming, dartdoc, formatting, null safety, and language conventions.
glossary-required
by exception-coder
"Use when business-domain terms are missing, ambiguous, inconsistent with code names, or explicitly need glossary maintenance; routes terminology through domain knowledge and verifies code mappings with Graphify."
design-system-bootstrap
by exception-coder
"Initialize or extend an evidence-driven design registry, create or bind a Design Profile, capture explicit user visual preferences, and mine repeated evidence into candidate patterns. Use for design bootstrap, profile binding, preference recording, or pattern learning."
planning-evidence-discovery
by exception-coder
"Use when exploring an initial PRD idea, generating an initialization specification, performing value analysis, or estimating effort where evidence may span a primary project and related refactor, migration, dependency, or integration projects. Requires deterministic project-scope resolution, relationship-driven evidence queries, a persisted planning-evidence-trace-v2 ledger, and a server-side completion gate."
design-system-guardian
by exception-coder
"Govern and review meaningful UI implementation by resolving the design registry, project binding, profile, references, and existing implementation before conservative reuse or controlled exploration. Use for UI work, visual drift checks, representative renders, responsive review, or release visual acceptance."
bug-doc-required
by exception-coder
"Use when a user reports a bug, error, exception, timeout, or broken behavior; asks for investigation or root-cause analysis; requests a bug-analysis document; or asks to implement a bug fix, align authoritative behavior, or remove redundant repair code."
coding-violation-log
by exception-coder
"当用户纠正 AI 的编码规范、分层、命名或依赖方向错误时使用；项目存在 coding-violations.md 时，也用于编码前回顾既有违规记录。"
java-coding-standards
by exception-coder
Use when writing, reviewing, or modifying Java code. Covers Java-specific rules derived from the Alibaba Huangshan guidelines and complements the common coding standards.
dev-log
by exception-coder
"Use for decision-level team-standards changes such as adding or removing Skills, changing triggers or core behavior, reversing rules, or changing cross-Skill workflows; not for routine wording or version updates."
frontend-excellence
by exception-coder
"Use when creating, redesigning, or substantially improving production Web frontends, including React, Vue, Next.js, dashboards, portals, landing pages, component libraries, or screenshot/Figma-to-code work. Enforces product-level visual direction, deliberate anti-generic composition, design systems, responsive behavior, accessibility, complete recoverable UI states, maintainable component architecture, and real-browser visual verification. Do not use for pure backend work, native mobile UI, or copy-only changes with no layout or interaction impact."
coding-standards-common
by exception-coder
Use when writing, reviewing, or modifying source code in any language. Provides cross-language rules for structure, naming, scope, errors, duplication, testing, and comments.
architecture-ddd-lite-fullstack
by exception-coder
"Use before writing or reviewing business code in Java, Python, Dart, React, or Vue to choose layers, feature boundaries, reusable capabilities, and one-way dependencies."
llm-agent-coding-standards
by exception-coder
Use when code integrates LLM SDKs, agents, prompts, tools or function calling, structured model output, or agent loops. Covers trust boundaries, deterministic contracts, and loop safeguards.