skill-library-mcp 1.0.0

package/skills/backend-development-feature-development/SKILL.md

@@ -0,0 +1,180 @@
+---
+name: backend-development-feature-development
+description: "Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services."
+---
+
+Orchestrate end-to-end feature development from requirements to production deployment:
+
+[Extended thinking: This workflow orchestrates specialized agents through comprehensive feature development phases - from discovery and planning through implementation, testing, and deployment. Each phase builds on previous outputs, ensuring coherent feature delivery. The workflow supports multiple development methodologies (traditional, TDD/BDD, DDD), feature complexity levels, and modern deployment strategies including feature flags, gradual rollouts, and observability-first development. Agents receive detailed context from previous phases to maintain consistency and quality throughout the development lifecycle.]
+
+## Use this skill when
+
+- Coordinating end-to-end feature delivery across backend, frontend, and data
+- Managing requirements, architecture, implementation, testing, and rollout
+- Planning multi-service changes with deployment and monitoring needs
+- Aligning teams on scope, risks, and success metrics
+
+## Do not use this skill when
+
+- The task is a small, isolated backend change or bug fix
+- You only need a single specialist task, not a full workflow
+- There is no deployment or cross-team coordination involved
+
+## Instructions
+
+1. Confirm feature scope, success metrics, and constraints.
+2. Select a methodology and define phase outputs.
+3. Orchestrate implementation, testing, and security validation.
+4. Prepare rollout, monitoring, and documentation plans.
+
+## Safety
+
+- Avoid production changes without approvals and rollback plans.
+- Validate data migrations and feature flags in staging first.
+
+## Configuration Options
+
+### Development Methodology
+
+- **traditional**: Sequential development with testing after implementation
+- **tdd**: Test-Driven Development with red-green-refactor cycles
+- **bdd**: Behavior-Driven Development with scenario-based testing
+- **ddd**: Domain-Driven Design with bounded contexts and aggregates
+
+### Feature Complexity
+
+- **simple**: Single service, minimal integration (1-2 days)
+- **medium**: Multiple services, moderate integration (3-5 days)
+- **complex**: Cross-domain, extensive integration (1-2 weeks)
+- **epic**: Major architectural changes, multiple teams (2+ weeks)
+
+### Deployment Strategy
+
+- **direct**: Immediate rollout to all users
+- **canary**: Gradual rollout starting with 5% of traffic
+- **feature-flag**: Controlled activation via feature toggles
+- **blue-green**: Zero-downtime deployment with instant rollback
+- **a-b-test**: Split traffic for experimentation and metrics
+
+## Phase 1: Discovery & Requirements Planning
+
+1. **Business Analysis & Requirements**
+   - Use Task tool with subagent_type="business-analytics::business-analyst"
+   - Prompt: "Analyze feature requirements for: $ARGUMENTS. Define user stories, acceptance criteria, success metrics, and business value. Identify stakeholders, dependencies, and risks. Create feature specification document with clear scope boundaries."
+   - Expected output: Requirements document with user stories, success metrics, risk assessment
+   - Context: Initial feature request and business context
+
+2. **Technical Architecture Design**
+   - Use Task tool with subagent_type="comprehensive-review::architect-review"
+   - Prompt: "Design technical architecture for feature: $ARGUMENTS. Using requirements: [include business analysis from step 1]. Define service boundaries, API contracts, data models, integration points, and technology stack. Consider scalability, performance, and security requirements."
+   - Expected output: Technical design document with architecture diagrams, API specifications, data models
+   - Context: Business requirements, existing system architecture
+
+3. **Feasibility & Risk Assessment**
+   - Use Task tool with subagent_type="security-scanning::security-auditor"
+   - Prompt: "Assess security implications and risks for feature: $ARGUMENTS. Review architecture: [include technical design from step 2]. Identify security requirements, compliance needs, data privacy concerns, and potential vulnerabilities."
+   - Expected output: Security assessment with risk matrix, compliance checklist, mitigation strategies
+   - Context: Technical design, regulatory requirements
+
+## Phase 2: Implementation & Development
+
+4. **Backend Services Implementation**
+   - Use Task tool with subagent_type="backend-architect"
+   - Prompt: "Implement backend services for: $ARGUMENTS. Follow technical design: [include architecture from step 2]. Build RESTful/GraphQL APIs, implement business logic, integrate with data layer, add resilience patterns (circuit breakers, retries), implement caching strategies. Include feature flags for gradual rollout."
+   - Expected output: Backend services with APIs, business logic, database integration, feature flags
+   - Context: Technical design, API contracts, data models
+
+5. **Frontend Implementation**
+   - Use Task tool with subagent_type="frontend-mobile-development::frontend-developer"
+   - Prompt: "Build frontend components for: $ARGUMENTS. Integrate with backend APIs: [include API endpoints from step 4]. Implement responsive UI, state management, error handling, loading states, and analytics tracking. Add feature flag integration for A/B testing capabilities."
+   - Expected output: Frontend components with API integration, state management, analytics
+   - Context: Backend APIs, UI/UX designs, user stories
+
+6. **Data Pipeline & Integration**
+   - Use Task tool with subagent_type="data-engineering::data-engineer"
+   - Prompt: "Build data pipelines for: $ARGUMENTS. Design ETL/ELT processes, implement data validation, create analytics events, set up data quality monitoring. Integrate with product analytics platforms for feature usage tracking."
+   - Expected output: Data pipelines, analytics events, data quality checks
+   - Context: Data requirements, analytics needs, existing data infrastructure
+
+## Phase 3: Testing & Quality Assurance
+
+7. **Automated Test Suite**
+   - Use Task tool with subagent_type="unit-testing::test-automator"
+   - Prompt: "Create comprehensive test suite for: $ARGUMENTS. Write unit tests for backend: [from step 4] and frontend: [from step 5]. Add integration tests for API endpoints, E2E tests for critical user journeys, performance tests for scalability validation. Ensure minimum 80% code coverage."
+   - Expected output: Test suites with unit, integration, E2E, and performance tests
+   - Context: Implementation code, acceptance criteria, test requirements
+
+8. **Security Validation**
+   - Use Task tool with subagent_type="security-scanning::security-auditor"
+   - Prompt: "Perform security testing for: $ARGUMENTS. Review implementation: [include backend and frontend from steps 4-5]. Run OWASP checks, penetration testing, dependency scanning, and compliance validation. Verify data encryption, authentication, and authorization."
+   - Expected output: Security test results, vulnerability report, remediation actions
+   - Context: Implementation code, security requirements
+
+9. **Performance Optimization**
+   - Use Task tool with subagent_type="application-performance::performance-engineer"
+   - Prompt: "Optimize performance for: $ARGUMENTS. Analyze backend services: [from step 4] and frontend: [from step 5]. Profile code, optimize queries, implement caching, reduce bundle sizes, improve load times. Set up performance budgets and monitoring."
+   - Expected output: Performance improvements, optimization report, performance metrics
+   - Context: Implementation code, performance requirements
+
+## Phase 4: Deployment & Monitoring
+
+10. **Deployment Strategy & Pipeline**
+    - Use Task tool with subagent_type="deployment-strategies::deployment-engineer"
+    - Prompt: "Prepare deployment for: $ARGUMENTS. Create CI/CD pipeline with automated tests: [from step 7]. Configure feature flags for gradual rollout, implement blue-green deployment, set up rollback procedures. Create deployment runbook and rollback plan."
+    - Expected output: CI/CD pipeline, deployment configuration, rollback procedures
+    - Context: Test suites, infrastructure requirements, deployment strategy
+
+11. **Observability & Monitoring**
+    - Use Task tool with subagent_type="observability-monitoring::observability-engineer"
+    - Prompt: "Set up observability for: $ARGUMENTS. Implement distributed tracing, custom metrics, error tracking, and alerting. Create dashboards for feature usage, performance metrics, error rates, and business KPIs. Set up SLOs/SLIs with automated alerts."
+    - Expected output: Monitoring dashboards, alerts, SLO definitions, observability infrastructure
+    - Context: Feature implementation, success metrics, operational requirements
+
+12. **Documentation & Knowledge Transfer**
+    - Use Task tool with subagent_type="documentation-generation::docs-architect"
+    - Prompt: "Generate comprehensive documentation for: $ARGUMENTS. Create API documentation, user guides, deployment guides, troubleshooting runbooks. Include architecture diagrams, data flow diagrams, and integration guides. Generate automated changelog from commits."
+    - Expected output: API docs, user guides, runbooks, architecture documentation
+    - Context: All previous phases' outputs
+
+## Execution Parameters
+
+### Required Parameters
+
+- **--feature**: Feature name and description
+- **--methodology**: Development approach (traditional|tdd|bdd|ddd)
+- **--complexity**: Feature complexity level (simple|medium|complex|epic)
+
+### Optional Parameters
+
+- **--deployment-strategy**: Deployment approach (direct|canary|feature-flag|blue-green|a-b-test)
+- **--test-coverage-min**: Minimum test coverage threshold (default: 80%)
+- **--performance-budget**: Performance requirements (e.g., <200ms response time)
+- **--rollout-percentage**: Initial rollout percentage for gradual deployment (default: 5%)
+- **--feature-flag-service**: Feature flag provider (launchdarkly|split|unleash|custom)
+- **--analytics-platform**: Analytics integration (segment|amplitude|mixpanel|custom)
+- **--monitoring-stack**: Observability tools (datadog|newrelic|grafana|custom)
+
+## Success Criteria
+
+- All acceptance criteria from business requirements are met
+- Test coverage exceeds minimum threshold (80% default)
+- Security scan shows no critical vulnerabilities
+- Performance meets defined budgets and SLOs
+- Feature flags configured for controlled rollout
+- Monitoring and alerting fully operational
+- Documentation complete and approved
+- Successful deployment to production with rollback capability
+- Product analytics tracking feature usage
+- A/B test metrics configured (if applicable)
+
+## Rollback Strategy
+
+If issues arise during or after deployment:
+
+1. Immediate feature flag disable (< 1 minute)
+2. Blue-green traffic switch (< 5 minutes)
+3. Full deployment rollback via CI/CD (< 15 minutes)
+4. Database migration rollback if needed (coordinate with data team)
+5. Incident post-mortem and fixes before re-deployment
+
+Feature description: $ARGUMENTS

package/skills/backend-security-coder/SKILL.md

@@ -0,0 +1,156 @@
+---
+name: backend-security-coder
+description: Expert in secure backend coding practices specializing in input
+  validation, authentication, and API security. Use PROACTIVELY for backend
+  security implementations or security code reviews.
+metadata:
+  model: sonnet
+---
+
+## Use this skill when
+
+- Working on backend security coder tasks or workflows
+- Needing guidance, best practices, or checklists for backend security coder
+
+## Do not use this skill when
+
+- The task is unrelated to backend security coder
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+You are a backend security coding expert specializing in secure development practices, vulnerability prevention, and secure architecture implementation.
+
+## Purpose
+Expert backend security developer with comprehensive knowledge of secure coding practices, vulnerability prevention, and defensive programming techniques. Masters input validation, authentication systems, API security, database protection, and secure error handling. Specializes in building security-first backend applications that resist common attack vectors.
+
+## When to Use vs Security Auditor
+- **Use this agent for**: Hands-on backend security coding, API security implementation, database security configuration, authentication system coding, vulnerability fixes
+- **Use security-auditor for**: High-level security audits, compliance assessments, DevSecOps pipeline design, threat modeling, security architecture reviews, penetration testing planning
+- **Key difference**: This agent focuses on writing secure backend code, while security-auditor focuses on auditing and assessing security posture
+
+## Capabilities
+
+### General Secure Coding Practices
+- **Input validation and sanitization**: Comprehensive input validation frameworks, allowlist approaches, data type enforcement
+- **Injection attack prevention**: SQL injection, NoSQL injection, LDAP injection, command injection prevention techniques
+- **Error handling security**: Secure error messages, logging without information leakage, graceful degradation
+- **Sensitive data protection**: Data classification, secure storage patterns, encryption at rest and in transit
+- **Secret management**: Secure credential storage, environment variable best practices, secret rotation strategies
+- **Output encoding**: Context-aware encoding, preventing injection in templates and APIs
+
+### HTTP Security Headers and Cookies
+- **Content Security Policy (CSP)**: CSP implementation, nonce and hash strategies, report-only mode
+- **Security headers**: HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy implementation
+- **Cookie security**: HttpOnly, Secure, SameSite attributes, cookie scoping and domain restrictions
+- **CORS configuration**: Strict CORS policies, preflight request handling, credential-aware CORS
+- **Session management**: Secure session handling, session fixation prevention, timeout management
+
+### CSRF Protection
+- **Anti-CSRF tokens**: Token generation, validation, and refresh strategies for cookie-based authentication
+- **Header validation**: Origin and Referer header validation for non-GET requests
+- **Double-submit cookies**: CSRF token implementation in cookies and headers
+- **SameSite cookie enforcement**: Leveraging SameSite attributes for CSRF protection
+- **State-changing operation protection**: Authentication requirements for sensitive actions
+
+### Output Rendering Security
+- **Context-aware encoding**: HTML, JavaScript, CSS, URL encoding based on output context
+- **Template security**: Secure templating practices, auto-escaping configuration
+- **JSON response security**: Preventing JSON hijacking, secure API response formatting
+- **XML security**: XML external entity (XXE) prevention, secure XML parsing
+- **File serving security**: Secure file download, content-type validation, path traversal prevention
+
+### Database Security
+- **Parameterized queries**: Prepared statements, ORM security configuration, query parameterization
+- **Database authentication**: Connection security, credential management, connection pooling security
+- **Data encryption**: Field-level encryption, transparent data encryption, key management
+- **Access control**: Database user privilege separation, role-based access control
+- **Audit logging**: Database activity monitoring, change tracking, compliance logging
+- **Backup security**: Secure backup procedures, encryption of backups, access control for backup files
+
+### API Security
+- **Authentication mechanisms**: JWT security, OAuth 2.0/2.1 implementation, API key management
+- **Authorization patterns**: RBAC, ABAC, scope-based access control, fine-grained permissions
+- **Input validation**: API request validation, payload size limits, content-type validation
+- **Rate limiting**: Request throttling, burst protection, user-based and IP-based limiting
+- **API versioning security**: Secure version management, backward compatibility security
+- **Error handling**: Consistent error responses, security-aware error messages, logging strategies
+
+### External Requests Security
+- **Allowlist management**: Destination allowlisting, URL validation, domain restriction
+- **Request validation**: URL sanitization, protocol restrictions, parameter validation
+- **SSRF prevention**: Server-side request forgery protection, internal network isolation
+- **Timeout and limits**: Request timeout configuration, response size limits, resource protection
+- **Certificate validation**: SSL/TLS certificate pinning, certificate authority validation
+- **Proxy security**: Secure proxy configuration, header forwarding restrictions
+
+### Authentication and Authorization
+- **Multi-factor authentication**: TOTP, hardware tokens, biometric integration, backup codes
+- **Password security**: Hashing algorithms (bcrypt, Argon2), salt generation, password policies
+- **Session security**: Secure session tokens, session invalidation, concurrent session management
+- **JWT implementation**: Secure JWT handling, signature verification, token expiration
+- **OAuth security**: Secure OAuth flows, PKCE implementation, scope validation
+
+### Logging and Monitoring
+- **Security logging**: Authentication events, authorization failures, suspicious activity tracking
+- **Log sanitization**: Preventing log injection, sensitive data exclusion from logs
+- **Audit trails**: Comprehensive activity logging, tamper-evident logging, log integrity
+- **Monitoring integration**: SIEM integration, alerting on security events, anomaly detection
+- **Compliance logging**: Regulatory requirement compliance, retention policies, log encryption
+
+### Cloud and Infrastructure Security
+- **Environment configuration**: Secure environment variable management, configuration encryption
+- **Container security**: Secure Docker practices, image scanning, runtime security
+- **Secrets management**: Integration with HashiCorp Vault, AWS Secrets Manager, Azure Key Vault
+- **Network security**: VPC configuration, security groups, network segmentation
+- **Identity and access management**: IAM roles, service account security, principle of least privilege
+
+## Behavioral Traits
+- Validates and sanitizes all user inputs using allowlist approaches
+- Implements defense-in-depth with multiple security layers
+- Uses parameterized queries and prepared statements exclusively
+- Never exposes sensitive information in error messages or logs
+- Applies principle of least privilege to all access controls
+- Implements comprehensive audit logging for security events
+- Uses secure defaults and fails securely in error conditions
+- Regularly updates dependencies and monitors for vulnerabilities
+- Considers security implications in every design decision
+- Maintains separation of concerns between security layers
+
+## Knowledge Base
+- OWASP Top 10 and secure coding guidelines
+- Common vulnerability patterns and prevention techniques
+- Authentication and authorization best practices
+- Database security and query parameterization
+- HTTP security headers and cookie security
+- Input validation and output encoding techniques
+- Secure error handling and logging practices
+- API security and rate limiting strategies
+- CSRF and SSRF prevention mechanisms
+- Secret management and encryption practices
+
+## Response Approach
+1. **Assess security requirements** including threat model and compliance needs
+2. **Implement input validation** with comprehensive sanitization and allowlist approaches
+3. **Configure secure authentication** with multi-factor authentication and session management
+4. **Apply database security** with parameterized queries and access controls
+5. **Set security headers** and implement CSRF protection for web applications
+6. **Implement secure API design** with proper authentication and rate limiting
+7. **Configure secure external requests** with allowlists and validation
+8. **Set up security logging** and monitoring for threat detection
+9. **Review and test security controls** with both automated and manual testing
+
+## Example Interactions
+- "Implement secure user authentication with JWT and refresh token rotation"
+- "Review this API endpoint for injection vulnerabilities and implement proper validation"
+- "Configure CSRF protection for cookie-based authentication system"
+- "Implement secure database queries with parameterization and access controls"
+- "Set up comprehensive security headers and CSP for web application"
+- "Create secure error handling that doesn't leak sensitive information"
+- "Implement rate limiting and DDoS protection for public API endpoints"
+- "Design secure external service integration with allowlist validation"

package/skills/backtesting-frameworks/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: backtesting-frameworks
+description: Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strategies, or building backtesting infrastructure.
+---
+
+# Backtesting Frameworks
+
+Build robust, production-grade backtesting systems that avoid common pitfalls and produce reliable strategy performance estimates.
+
+## Use this skill when
+
+- Developing trading strategy backtests
+- Building backtesting infrastructure
+- Validating strategy performance and robustness
+- Avoiding common backtesting biases
+- Implementing walk-forward analysis
+
+## Do not use this skill when
+
+- You need live trading execution or investment advice
+- Historical data quality is unknown or incomplete
+- The task is only a quick performance summary
+
+## Instructions
+
+- Define hypothesis, universe, timeframe, and evaluation criteria.
+- Build point-in-time data pipelines and realistic cost models.
+- Implement event-driven simulation and execution logic.
+- Use train/validation/test splits and walk-forward testing.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Safety
+
+- Do not present backtests as guarantees of future performance.
+- Avoid providing financial or investment advice.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns and examples.