GitHub
nosql
Nosql standards for nosql in Database environments. Covers best practices,
☆ 12Voir le skill
Skills IA testing security architecture patterns
Découvrez les skills testing security architecture patterns, comparez leurs dépôts et consultez leurs instructions.
Catégories: testing security architecture patterns
testing security architecture patterns Effacer les filtres
Explorer
GitHub
fintech-compliance
Payment card security, SOC2 compliance, and financial services regulatory requirements
☆ 12Voir le skill
GitHub
valid-skill
A valid skill for testing with proper structure and content
☆ 12Voir le skill
GitHub
aws-advanced-patterns
Orchestration & Events:
☆ 12Voir le skill
GitHub
data-quality
Core Principles:
☆ 12Voir le skill
GitHub
containers
Core Principles:
☆ 12Voir le skill
GitHub
security-practices
Modern security standards including Zero Trust Architecture, supply chain security, DevSecOps integration, and cloud-native protection
☆ 12Voir le skill
GitHub
coding-standards
Comprehensive coding standards and best practices for maintainable, consistent software development across multiple languages and paradigms
☆ 12Voir le skill
GitHub
infrastructure-as-code
Basic Resource:
☆ 12Voir le skill
GitHub
nist
Nist standards for nist in Compliance environments. Covers best practices,
☆ 12Voir le skill
GitHub
patterns
Patterns standards for patterns in Microservices environments. Covers
☆ 12Voir le skill
GitHub
integration-testing
Integration testing standards for API testing, database testing, and service-to-service communication. Covers test containers, Docker Compose, API mocking, and contract testing for reliable integration suites.
☆ 12Voir le skill
GitHub
ux
Ux standards for ux in Design environments. Covers best practices, implementation
☆ 12Voir le skill
GitHub
service-mesh
A service mesh is an infrastructure layer that provides transparent service-to-service communication with built-in observability, traffic management, and security features without requiring application code cha...
☆ 12Voir le skill
GitHub
dry-philosophy
Don't Repeat Yourself (DRY) and Never Reinvent the Wheel (NRtW) - core b00t principles. Use existing libraries, leverage Rust via PyO3 instead of duplicating logic in Python, and contribute to upstream projects...
☆ 12Voir le skill
GitHub
architecture-discipline
Use when designing/modifying system architecture or evaluating technology choices. Enforces 7-section TodoWrite with 22+ items. Triggers: "design architecture", "system design", "architectural decision", "shoul...
☆ 12Voir le skill
GitHub
threat-modeling
Use when implementing auth, file uploads, payments, or external APIs. Applies STRIDE framework systematically. Triggers: "authentication", "file upload", "payment", "multi-tenant", "external API". If thinking "...
☆ 12Voir le skill
GitHub
brainstorming
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validatio...
☆ 12Voir le skill
GitHub
tdd-enforcement-algorithm
Algorithmic decision tree enforcing test-first development via boolean conditions instead of imperatives
☆ 12Voir le skill
GitHub
following-plans
Algorithmic decision tree for when to follow plan exactly vs when to report BLOCKED - prevents scope creep and unauthorized deviations
☆ 12Voir le skill
GitHub
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures u...
☆ 12Voir le skill
GitHub
capturing-learning-from-completed-work
Systematic retrospective to capture decisions, lessons, and insights from completed work
☆ 12Voir le skill
GitHub
algorithmic-command-enforcement
Use boolean decision trees instead of imperatives for 100% compliance under pressure
☆ 12Voir le skill
GitHub
creating-research-packages
Document complex domain knowledge as self-contained packages with multiple reading paths
☆ 12Voir le skill
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é.