Loading...
Loading...
Found 3,718 Skills
Generates Tzatziki-based Cucumber BDD tests (.feature files) from a functional specification. Use this skill whenever a user wants to write Cucumber tests, add BDD scenarios, create feature files, generate tests, or test application behaviors with Gherkin — especially in Java/Spring projects using Tzatziki step definitions for HTTP, JPA, Kafka, MongoDB, OpenSearch, logging, or MCP. Also use when the user mentions writing integration tests, acceptance tests, or end-to-end tests in a project that already has Tzatziki/Cucumber dependencies, including TestNG-based setups.
프로젝트에 E2E 테스트 환경을 설정합니다. 글로벌 도구 설치 체크, Chrome Beta 확인, e2e/ 인프라 코드 배포. Use when: "e2e 세팅", "e2e setup", "E2E 환경 설정", "E2E 초기 설정" 키워드.
Verify that a change really works before you claim completion
TypeScript echo CLI
Find SSRF (Server-Side Request Forgery) vulnerabilities in captured traffic. Use when user asks about URL fetching, webhooks, integrations, or internal network access.
Faraday integration. Manage Organizations. Use when the user wants to interact with Faraday data.
Use when the user wants a quality review, interaction audit, or to test the workflow against realistic scenarios.
This skill should be used when the user asks to "set up an A/B test", "calculate sample size", "design an experiment", "analyze A/B test results", "check statistical significance", "determine test duration", or "evaluate conversion rate experiments".
Brain health checks: back-link enforcement, citation audit, filing validation, stale info detection, orphan pages, and benchmarks. Use when asked to check brain health, run maintenance, or audit quality.
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes
Generates structured Given/When/Then acceptance criteria for a user story or feature slice. Use when translating product requirements into testable scenarios that cover the happy path, edge cases, error states, and non-functional expectations for engineering handoff and QA.
Use when asked to identify and fix errors in an OpenAPI specification that are preventing it from running as mock or test