aiskillstore/project-testing
skills/consiliency/stack-analyzer/templates/project-testing/SKILL.md
Custom test patterns and fixtures for {project}. Covers E2E, integration, and specialized testing requirements.
$ install --global
skillsauthnpx skillsauth add aiskillstore/marketplace project-testingInstall 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: Mar 31, 2026, 5:47 PM57.5s1 file scanned
SKILL.md
- name:
- project-testing
- description:
- Custom test patterns and fixtures for {project}. Covers E2E, integration, and specialized testing requirements.
- generated_by:
- ai-dev-kit:recommend-skills
<!-- Generated by ai-dev-kit:recommend-skills on {date} -->
<!-- This skill can be safely deleted if no longer needed -->
{project} Testing Patterns
Custom testing patterns, fixtures, and strategies for this project.
Variables
| 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 |
Instructions
- Identify test type needed (unit/integration/e2e)
- Use appropriate fixtures and patterns
- Follow project naming conventions
- Ensure proper cleanup
Red Flags - STOP and Reconsider
If you're about to:
- Write a test without proper isolation
- Skip cleanup in fixtures
- Hardcode test data instead of using fixtures
- Write flaky tests (timing-dependent, order-dependent)
STOP -> Use proper fixtures -> Ensure isolation -> Then write test
Test Categories
Unit Tests
Location: tests/unit/
Patterns:
- Test single functions/methods in isolation
- Mock external dependencies
- Fast execution (< 100ms each)
Integration Tests
Location: tests/integration/
Patterns:
- Test component interactions
- Use test database/fixtures
- May have external dependencies
E2E Tests
Location: tests/e2e/ or playwright/
Patterns:
- Test full user workflows
- Use browser automation
- Longer execution time acceptable
Fixtures
Database Fixtures
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
Mock Services
Location: tests/mocks/
Available mocks:
- [TODO: List project-specific mocks]
Naming Conventions
| 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>') |
Coverage Requirements
| Component | Minimum Coverage | |-----------|-----------------| | Core logic | 90% | | API routes | 80% | | Utilities | 70% |
CI Integration
Tests run in CI:
- On PR: unit + integration
- On merge: all including E2E
- Nightly: full regression suite
Customization
Edit this file to add:
- New fixture definitions
- Additional mock services
- Custom test patterns
- Coverage exceptions
Related Skills
aiskillstore/hig-components-content
development
VerifiedTrustedCommunity
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/helpdesk-automation
tools
VerifiedTrustedCommunity
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/haskell-pro
testing
VerifiedTrustedCommunity
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/graphql
tools
VerifiedTrustedCommunity
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
244SKILL.mdUpdated Apr 10, 2026