Menü
"Custom test patterns and fixtures for {project}. Covers E2E, integration, and specialized testing requirements."
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Generic BAML patterns for type-safe LLM prompting. Covers schema design, DTO generation, client wrappers, and cross-language codegen. Framework-agnostic.
Browser automation for documentation discovery. Use when curl fails on JS-rendered sites, when detecting available browser tools, or when configuring browser-based documentation collection.
C4 architectural modeling for documenting software architecture. Use when creating architecture diagrams, planning new systems, communicating with stakeholders, or conducting architecture reviews.
Debug and analyze web applications using Chrome DevTools MCP. Use for console log inspection, network request monitoring, performance analysis, and debugging authenticated sessions. For basic browser automation (screenshots, form filling), use browser-discovery skill instead.
Patterns and techniques for analyzing brownfield codebases. Use when onboarding to unfamiliar code, preparing for refactoring, conducting architecture reviews, or identifying technical debt.
Detect new imports in modified files and auto-install missing dependencies. Works with npm, uv, pip, cargo, go mod, and other package managers. Triggers after code implementation to keep manifests in sync.
| name | {project}-testing |
| description | "Custom test patterns and fixtures for {project}. Covers E2E, integration, and specialized testing requirements." |
Custom testing patterns, fixtures, and strategies for this project.
| Variable | Default | Description |
|---|---|---|
| COVERAGE_TARGET | 80 | Minimum coverage percentage |
| E2E_TIMEOUT | 30000 | E2E test timeout in ms |
| PARALLEL_TESTS | true | Run tests in parallel when possible |
If you're about to:
STOP -> Use proper fixtures -> Ensure isolation -> Then write test
Location: tests/unit/
Patterns:
Location: tests/integration/
Patterns:
Location: tests/e2e/ or playwright/
Patterns:
Location: tests/fixtures/
Usage:
# Python example
from tests.fixtures import sample_user, sample_order
def test_order_creation(sample_user, sample_order):
# Test uses pre-configured fixtures
pass
Location: tests/mocks/
Available mocks:
| Test Type | File Pattern | Function Pattern |
|---|---|---|
| Unit | test_*.py | test_<function>_<scenario> |
| Integration | test_*_integration.py | test_<component>_<action> |
| E2E | *.spec.ts | test('<feature> - <scenario>') |
| Component | Minimum Coverage |
|---|---|
| Core logic | 90% |
| API routes | 80% |
| Utilities | 70% |
Tests run in CI:
Edit this file to add: