Découvrez les skills Contenu et médias, comparez leurs dépôts et consultez leurs instructions.
Guide Spec-Driven Development (SDD) workflow for planning changes before implementation. Use when: creating specs, proposals, planning features, using OpenSpec or similar tools. Keywords: spec, specification, S...
Derive BDD scenarios and TDD test skeletons from approved SDD specifications. ATDD acceptance test tables are optional output for specialized needs. Use when: spec is approved, starting BDD/TDD implementation,...
依照 Keep a Changelog 格式撰寫與維護 CHANGELOG.md。 使用時機：建立變更日誌條目、準備發布、記錄變更。 關鍵字：changelog, release notes, CHANGELOG.md, keep a changelog, 變更日誌, 發布說明。
引導重構決策和大規模程式碼改進。 使用時機：重構程式碼、遺留系統現代化、技術債、重寫決策。 關鍵字：refactor, rewrite, legacy, strangler, technical debt, 重構, 重寫, 技術債.
Guide refactoring decisions and large-scale code improvements. Use when: refactoring code, legacy modernization, technical debt, rewrite decisions. Keywords: refactor, rewrite, legacy, strangler, technical debt...
系統化的程式碼審查檢查清單和提交前品質關卡。 使用時機：審查 pull request、檢查程式碼品質、提交程式碼前。 關鍵字：review, PR, pull request, checklist, quality, commit, 審查, 檢查, 簽入。
Guide pre-commit quality gates and check-in workflow. Use when: committing code, preparing commits, quality gate verification. Keywords: commit, checkin, pre-commit, quality gate, git add, 提交, 簽入, 品質關卡.
將現有程式碼反向工程成 SDD 規格文件。 使用時機：分析舊有程式碼、為未文件化的系統撰寫文件、從現有實作提取規格。 關鍵字：reverse engineering, legacy code, documentation, spec extraction, code archaeology, 反向工...
引導需求撰写、使用者故事建立与功能規格制定。 使用时机：撰写需求、使用者故事、問題单、功能規划。 关鍵字：requirement, user story, issue, feature, specification, 需求, 功能規划, 規格。
Testing pyramid and test writing standards for UT/IT/ST/E2E. Supports ISTQB and Industry Pyramid frameworks. Use when: writing tests, discussing test coverage, test strategy, or test naming. Keywords: test, uni...
系统化的程序码审查检查清单和提交前品质关卡。 使用时机：审查 pull request、检查程序码品质、提交程序码前。 关鍵字：review, PR, pull request, checklist, quality, commit, 审查, 检查, 簽入。
Prevent AI hallucination and ensure evidence-based responses when analyzing code or making suggestions. Use when: analyzing code, making recommendations, providing options, or when user asks about confidence/ce...
Implement structured logging with proper log levels and sensitive data handling. Use when: adding logging, debugging, setting up observability. Keywords: logging, log level, structured logging, observability,...
遵循約定式提交标准格式化提交消息。 使用时机：撰写提交消息、git commit、檢视提交历史。 关鍵字：commit、git、message、conventional、feat、fix、refactor。
引導文件結構、內容需求和專案文件最佳實踐。 使用時機：建立 README、文件、docs 目錄、專案設定、技術文件。 關鍵字：README, docs, documentation, CONTRIBUTING, CHANGELOG, ARCHITECTURE, API docs, 文件, 說明文件, 技術...
設計一致的錯誤碼，遵循 PREFIX_CATEGORY_NUMBER 格式。 使用時機：定義錯誤碼、建立錯誤處理、設計 API。 關鍵字：error code, error handling, error format, API errors, 錯誤碼, 錯誤處理。
Use when implementing skill data generation from HTML sources for game build planners - guides the parser-factory-generation pattern for extracting level-scaling values for active and passive skills (project)
Use when adding support mod parsers to convert support skill affix strings to typed SupportMod objects - guides the template-based parsing pattern (project)
Use when adding new mod parsers to convert game mod strings to typed Mod objects - guides the template-based parsing pattern (project)
For understanding what each mode does, which mode is best (most appropriate mode) for a given situation, and establishing a pattern for choosing when and how a mode delegates or passes operation to another mode
When html or jinja are being written or edited.
When markdown being written or edited
Any time database-related activity is required.
When any part of the application needs to be found or understood.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.