openspec-demo

GoFrame v2 development skill. TRIGGER when writing/modifying Go files, implementing services, creating APIs, or database operations. DO NOT TRIGGER for frontend/shell scripts.

Organize, fix, verify, and cover with tests any bugs, improvements, or gaps reported during verification of an OpenSpec change. Use this skill when the user reports bugs, issues, defects, problems, missing test cases, missing coverage, improvement points, or UX feedback — whether discovered during manual verification, testing, or daily use. Trigger phrases include (but are not limited to): "bug", "issue", "fix", "feedback", "问题反馈", "问题", "反馈", "缺陷", "修复", "改进", "优化", "改善", "功能改进", "改进点", or numbered/bulleted lists of problems or improvements (中文或英文编号列表均可触发). This skill ensures every reported issue is tracked as a task artifact before any fix begins, and that each fix is covered by E2E test cases following the openspec-e2e conventions. IMPORTANT: This skill MUST be activated whenever the user provides any form of bug report, issue list, improvement suggestion, or feedback — regardless of language. If the message contains multiple numbered items describing problems or desired changes, this skill takes priority

Playwright E2E test case management conventions for the OpenSpec workflow. Defines test file naming (TC{NNNN}), directory organization by module, TC ID allocation, file independence rules, and sub-assertion patterns. Use when creating, planning, or reviewing E2E test cases within an OpenSpec change.