Skill Creator
v4lheru
8 published skills · 0 GitHub stars across the catalog. View on GitHub ↗
pact-database-patterns
CODE PHASE (Database): Data layer implementation patterns and best practices.Provides schema design patterns, query optimization strategies, indexing guidelines,data integrity constraints, migration patterns, and database security practices.Use when: designing schemas, writing queries, optimizing performance, planningmigrations, implementing data validation, ensuring data integrity.
pact-testing-patterns
TEST PHASE: Testing strategies, patterns, and quality assurance workflows.Provides test strategy frameworks, coverage guidelines, unit/integration/e2e patterns,performance testing approaches, and security testing checklists.Use when: designing test strategies, writing tests, evaluating coverage,planning QA workflows, implementing test automation.
pact-api-design
CROSS-CUTTING: API contract design patterns for architects and implementers.Provides REST API design patterns, GraphQL schema design, API versioning strategies,error response formats, pagination patterns, and API documentation standards.Use when: designing API contracts, choosing between REST/GraphQL, planning versioning,defining error formats, implementing pagination, documenting APIs.
pact-prepare-research
PREPARE PHASE: Research methodologies and documentation gathering workflows.Provides systematic research approaches, source evaluation criteria, documentationtemplates, API exploration techniques, and technology comparison frameworks.Use when: conducting technology research, evaluating documentation sources,comparing framework options, analyzing API documentation, gathering requirements.
pact-security-patterns
CROSS-CUTTING: Security patterns and best practices for ALL PACT phases.Provides OWASP Top 10 guidance, authentication/authorization patterns, input validation,secure coding practices, secrets management, and security testing checklists.Use when: implementing authentication, handling user input, storing secrets,designing authorization, reviewing code for vulnerabilities, planning security tests.
pact-frontend-patterns
CODE PHASE (Frontend): Client-side implementation patterns and best practices.Provides component architecture patterns, state management strategies, accessibilityguidelines, performance optimization, and responsive design approaches.Use when: building UI components, managing state, implementing forms, optimizingperformance, ensuring accessibility, creating responsive layouts.
pact-architecture-patterns
ARCHITECT PHASE: Architectural design patterns, component templates, and system design guidance.Provides proven architectural patterns including microservices, layered architecture,event-driven systems, C4 diagram templates, API contract formats, and design anti-patterns.Use when: designing system architecture, creating component diagrams, defining interfaces,planning component boundaries, choosing architectural patterns, organizing system modules,or when user mentions: architecture, components, system design, diagrams, C4, microservices,API contracts, service boundaries, architectural patterns.Use for: component design, interface definition, system boundaries, dependency management,architecture documentation, design patterns, integration patterns.DO NOT use for: code implementation details, specific framework syntax, database schema design,frontend-specific patterns, testing strategies, or security implementation (use dedicated skills).
pact-backend-patterns
CODE PHASE (Backend): Server-side implementation patterns and best practices.Provides service layer patterns, API implementation guidance, error handling strategies,data validation approaches, middleware patterns, and backend security practices.Use when: implementing APIs, creating services, handling errors, validating data,building middleware, implementing authentication/authorization.