Loading...
Loading...
Found 3,310 Skills
Primary Playwright governance skill for sandbox browser verification and deterministic end-to-end authoring or rewrite work.
Percy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Percy data.
Spec-driven E2E test creation: plan what to test through structured discovery phases, then scaffold a local Shiplight test project and write YAML tests by walking through the app in a browser.
E2E 시나리오 생성, 실행, 자동수정을 통합 처리하는 스킬. "시나리오 만들어줘", "시나리오 실행", "e2e 실행", "E2E 돌려", "시나리오 돌려", "시나리오 변환", "녹화 변환", "e2e 변환", "codegen 변환", "e2e 생성", "시나리오 생성", "시나리오 검증" 키워드로 트리거.
E2E 단위 시나리오를 조합한 통합 테스트 시나리오를 md로 생성·관리·실행하는 스킬. "통합 시나리오", "e2e suite", "통합 테스트", "시나리오 조합", "e2e 통합", "전체 흐름 테스트" 키워드로 트리거.
Integrate a raw customer agent repo with Veris end to end. Installs or verifies veris-cli, logs in, creates or reuses a Veris environment, analyzes the repo, generates or updates `.veris/veris.yaml`, `.veris/Dockerfile.sandbox`, `.veris/.dockerignore`, configures runtime env vars, and can finish with `veris env push`. Use when a repo has no Veris setup yet, or when an existing `.veris/` integration is stale and needs to be refreshed.
Faraday integration. Manage data, records, and automate workflows. Use when the user wants to interact with Faraday data.
Analyze repository and suggest improvements
Vertical-slice TDD for any production code. One test → one impl → repeat. Tests verify behavior through public interfaces, not internals. Use when implementing any feature, bugfix, or behavior change.
Discover PUDA machine capabilities at bears and choose the right machines for protocol generation. Use when you need to know more about a machine, how to use a machine, or how to generate commands and protocols for any PUDA-connected machine.
Defines a testable hypothesis with clear success metrics and validation approach. Use when forming assumptions to test, designing experiments, or aligning team on what success looks like.
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.