complete-skill
A complete skill for E2E testing
Découvrez les skills Entreprise, comparez leurs dépôts et consultez leurs instructions.
A complete skill for E2E testing
Use when writing tests for Swift StateTree - ensures proper Swift Testing framework usage
Learn how to test code without mocking. Use when learning testing approach or before writing tests.
.NET test execution patterns and diagnostics. Use when running tests, analyzing test failures, or configuring test options.
Generate test PDF fixtures with known, extractable content. Creates PDFs with sections, tables, figures, requirements, equations, and annotations. Use when user needs "create test PDF", "generate PDF fixture",...
Write TypeScript code that's type-safe and tested. Use when coding TypeScript or implementing features.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure fir...
구현 전 테스트 케이스 설계 (TDD 준비). Use when (1) 구현 전 테스트 설계, (2) Acceptance Criteria 기반 테스트 케이스, (3) TDD 테스트 스켈레톤 생성.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Read all specs for a story, feature, or capability before starting work. Use when starting implementation to load requirements and context.
Validates Terminal User Interface (TUI) output using freeze for screenshot capture and LLM-as-judge for semantic validation. Supports both visual (PNG/SVG) and text-based validation modes.
Execute Unity Test Runner via uloop CLI. Use when you need to: (1) Run unit tests (EditMode tests), (2) Run integration tests (PlayMode tests), (3) Verify code changes don't break existing functionality.
Test-driven development workflow with philosophy guide - plan → write tests → implement → validate
Write tests for TypeScript code with three tiers (Unit/Integration/E2E). Use when testing TypeScript or writing TypeScript tests.
Automatically applies when writing pytest tests. Ensures proper use of fixtures, parametrize, marks, mocking, async tests, and follows testing best practices.
Create and execute comprehensive testing strategies including unit tests, integration tests, test-driven development, and test coverage analysis. Use when writing tests, implementing TDD, checking test coverage...
Execute frontend task implementation with TDD. Read task file, execute steps, verify each, update status. Use this skill when: - User asks to "implement task/plan", "start implementation", "execute plan", or "...
Generates failing tests that reproduce reported bugs in FanHub. Use when a bug report comes in and you need to create a test that demonstrates the issue before fixing it. Follows FanHub's testing patterns and d...
Execute frontend implementation with TDD. Read all constraint files before coding, write failing test first, verify after each step. Use this skill when: - User asks to "implement this", "implement the plan",...
Define clear, testable acceptance criteria using Given/When/Then (Gherkin) format that can be directly used for testing. Use this skill when: - User asks for "acceptance criteria", "AC", "test criteria", "done...
Execute backend task implementation with TDD. Read task file, execute steps, verify each, update status. Use this skill when: - User asks to "implement task/plan", "start implementation", "execute plan", or "s...
Linter-driven refactoring patterns to reduce complexity and improve code quality. Use when linter fails with complexity issues (cyclomatic, cognitive, maintainability) or when code feels hard to read/maintain....
Analyzes files for optimal complexity using sophistication theory - refactors code that is too simple (low entropy) or too chaotic (high entropy, low sophistication) to achieve ideal "complextropy" where code h...
Run systematic code audits using the Subtractive Triad framework (DRY → Rams → Heidegger). Use when auditing codebases for bloat, reviewing PRs for quality, finding dead code, or evaluating if code "earns its e...
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é.