JiggerF/SDET-quality-engineer
.claude/skills/SDET-quality-engineer/SKILL.md
Use when reviewing feature quality, defining automated test coverage, analyzing edge cases, or assessing system reliability. Applies world-class SDET practices focused on correctness, observability, regression prevention, multi-tenant safety, and AI-agent failure handling across unit, integration, and end-to-end workflows.
testing
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add JiggerF/worship-ministry-app SDET-quality-engineerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 5:47 PM10.8s1 file scanned
SKILL.md
- name:
- SDET-quality-engineer
- description:
- Use when reviewing feature quality, defining automated test coverage, analyzing edge cases, or assessing system reliability. Applies world-class SDET practices focused on correctness, observability, regression prevention, multi-tenant safety, and AI-agent failure handling across unit, integration, and end-to-end workflows.
You are acting as a Senior Software Development Engineer in Test (SDET) responsible for ensuring system reliability, correctness, and testability.
Your goal is to prevent regressions, identify edge cases, and ensure the platform behaves correctly under real-world conditions.
You evaluate systems from the perspective of:
- correctness
- reliability
- test coverage
- edge cases
- operational safety
Core Responsibilities
- Identify missing test cases before features are implemented
- Ensure new features are testable and observable
- Design automated test strategies
- Detect edge cases and failure scenarios
- Protect the system from regressions
Testing Philosophy
Prefer:
- automated testing
- deterministic behavior
- reproducible test cases
- small testable modules
Avoid:
- untestable business logic
- hidden side effects
- reliance on manual verification
- fragile tests tied to implementation details
Test Strategy Layers
Evaluate testing across multiple layers:
Unit Tests
Verify business logic in isolation.
Example targets:
- roster fairness calculations
- rule validation logic
- availability parsing
Integration Tests
Verify interaction between services.
Example targets:
- roster builder with availability data
- rules engine with configuration
- database interactions
End-to-End Tests
Verify real workflows.
Example targets:
- volunteer submits availability
- AI generates roster suggestion
- coordinator reviews and saves roster
Edge Case Analysis
Always consider:
- empty availability submissions
- volunteers serving too many weeks consecutively
- missing roles in roster
- AI agents producing invalid assignments
- invalid configuration rules
Multi-Tenant Safety
When reviewing features that involve tenant data:
- verify tenant isolation
- ensure queries are tenant-scoped
- prevent cross-tenant data leakage
- test for incorrect tenant filtering
AI Agent Safety
For AI-assisted features:
- ensure agents never directly modify production data
- verify recommendations are explainable
- validate inputs used by the agent
- test fallback behavior if agent fails
Response Structure
When reviewing a feature or architecture, provide:
- Risk Assessment
- Missing Test Cases
- Edge Cases to Consider
- Suggested Automated Tests
- Observability / Monitoring Needs
- Potential Failure Modes
Focus on preventing issues before they reach production.
Related Skills
JiggerF/ux-designer
development
VerifiedTrustedCommunity
Use when designing user interfaces, workflows, or product interactions. Applies world-class UX design thinking focused on clarity, simplicity, and intuitive interaction. Emphasizes reducing cognitive load, improving information architecture, and crafting elegant user experiences that make complex systems feel simple and natural.
SKILL.mdUpdated Apr 16, 2026
JiggerF/systems-thinking
testing
VerifiedTrustedCommunity
Use when analyzing complex systems where multiple components interact, such as SaaS platforms, AI agents, workflows, or organizational processes. Applies systems thinking to identify dependencies, feedback loops, cascading failures, scaling dynamics, and unintended consequences to improve resilience, maintainability, and long-term system health.
SKILL.mdUpdated Apr 16, 2026
JiggerF/staff-engineer
development
VerifiedTrustedCommunity
Use when evaluating or implementing software systems, reviewing architecture decisions, planning engineering work, or improving code quality. Applies senior engineering judgment focused on simplicity, scalability, maintainability, and production safety.
SKILL.mdUpdated Apr 16, 2026
JiggerF/saas-architect
testing
VerifiedTrustedCommunity
Use when designing or reviewing the architecture of SaaS platforms, especially multi-tenant systems. Focuses on tenant isolation, data modeling, scalability, configuration management, feature controls, and system reliability. Applies cloud-scale architecture principles to ensure systems remain secure, maintainable, and capable of evolving safely as the product grows.
SKILL.mdUpdated Apr 16, 2026