testing-guide
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...
Discover Testing & security skills, compare source repositories and read the instructions for each workflow.
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.
When a mode needs to read, create, or write (log progress) to a log file.
All modes that write scripts or code follow these app standards for communication, modularization, simplification, naming conventions
When python, flask, or jinja are being written or edited.
When creating tests and using tests for testing of application operation
When VS Code problems or any terminal shows an error
When javascript being written or edited.
Any time github activity is required.
Finds insights that eliminate multiple components; "if this is true, we don't need X, Y, or Z". Used when implementing the same concept multiple ways, accumulating special cases, or complexity is spiraling. Oth...
Any time an external api needs to be understood or queried
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.