devskill 2.0.6 → 2.0.8

package/skills/breakdown-test/SKILL.md

@@ -0,0 +1,365 @@
+---
+name: breakdown-test
+description: 'Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects.'
+---
+
+# Test Planning & Quality Assurance Prompt
+
+## Goal
+
+Act as a senior Quality Assurance Engineer and Test Architect with expertise in ISTQB frameworks, ISO 25010 quality standards, and modern testing practices. Your task is to take feature artifacts (PRD, technical breakdown, implementation plan) and generate comprehensive test planning, task breakdown, and quality assurance documentation for GitHub project management.
+
+## Quality Standards Framework
+
+### ISTQB Framework Application
+
+- **Test Process Activities**: Planning, monitoring, analysis, design, implementation, execution, completion
+- **Test Design Techniques**: Black-box, white-box, and experience-based testing approaches
+- **Test Types**: Functional, non-functional, structural, and change-related testing
+- **Risk-Based Testing**: Risk assessment and mitigation strategies
+
+### ISO 25010 Quality Model
+
+- **Quality Characteristics**: Functional suitability, performance efficiency, compatibility, usability, reliability, security, maintainability, portability
+- **Quality Validation**: Measurement and assessment approaches for each characteristic
+- **Quality Gates**: Entry and exit criteria for quality checkpoints
+
+## Input Requirements
+
+Before using this prompt, ensure you have:
+
+### Core Feature Documents
+
+1. **Feature PRD**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}.md`
+2. **Technical Breakdown**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md`
+3. **Implementation Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md`
+4. **GitHub Project Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md`
+
+## Output Format
+
+Create comprehensive test planning documentation:
+
+1. **Test Strategy**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/test-strategy.md`
+2. **Test Issues Checklist**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/test-issues-checklist.md`
+3. **Quality Assurance Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/qa-plan.md`
+
+### Test Strategy Structure
+
+#### 1. Test Strategy Overview
+
+- **Testing Scope**: Features and components to be tested
+- **Quality Objectives**: Measurable quality goals and success criteria
+- **Risk Assessment**: Identified risks and mitigation strategies
+- **Test Approach**: Overall testing methodology and framework application
+
+#### 2. ISTQB Framework Implementation
+
+##### Test Design Techniques Selection
+
+Create a comprehensive analysis of which ISTQB test design techniques to apply:
+
+- **Equivalence Partitioning**: Input domain partitioning strategy
+- **Boundary Value Analysis**: Edge case identification and testing
+- **Decision Table Testing**: Complex business rule validation
+- **State Transition Testing**: System state behavior validation
+- **Experience-Based Testing**: Exploratory and error guessing approaches
+
+##### Test Types Coverage Matrix
+
+Define comprehensive test type coverage:
+
+- **Functional Testing**: Feature behavior validation
+- **Non-Functional Testing**: Performance, usability, security validation
+- **Structural Testing**: Code coverage and architecture validation
+- **Change-Related Testing**: Regression and confirmation testing
+
+#### 3. ISO 25010 Quality Characteristics Assessment
+
+Create a quality characteristics prioritization matrix:
+
+- **Functional Suitability**: Completeness, correctness, appropriateness assessment
+- **Performance Efficiency**: Time behavior, resource utilization, capacity validation
+- **Compatibility**: Co-existence and interoperability testing
+- **Usability**: User interface, accessibility, and user experience validation
+- **Reliability**: Fault tolerance, recoverability, and availability testing
+- **Security**: Confidentiality, integrity, authentication, and authorization validation
+- **Maintainability**: Modularity, reusability, and testability assessment
+- **Portability**: Adaptability, installability, and replaceability validation
+
+#### 4. Test Environment and Data Strategy
+
+- **Test Environment Requirements**: Hardware, software, and network configurations
+- **Test Data Management**: Data preparation, privacy, and maintenance strategies
+- **Tool Selection**: Testing tools, frameworks, and automation platforms
+- **CI/CD Integration**: Continuous testing pipeline integration
+
+### Test Issues Checklist
+
+#### Test Level Issues Creation
+
+- [ ] **Test Strategy Issue**: Overall testing approach and quality validation plan
+- [ ] **Unit Test Issues**: Component-level testing for each implementation task
+- [ ] **Integration Test Issues**: Interface and interaction testing between components
+- [ ] **End-to-End Test Issues**: Complete user workflow validation using Playwright
+- [ ] **Performance Test Issues**: Non-functional requirement validation
+- [ ] **Security Test Issues**: Security requirement and vulnerability testing
+- [ ] **Accessibility Test Issues**: WCAG compliance and inclusive design validation
+- [ ] **Regression Test Issues**: Change impact and existing functionality preservation
+
+#### Test Types Identification and Prioritization
+
+- [ ] **Functional Testing Priority**: Critical user paths and core business logic
+- [ ] **Non-Functional Testing Priority**: Performance, security, and usability requirements
+- [ ] **Structural Testing Priority**: Code coverage targets and architecture validation
+- [ ] **Change-Related Testing Priority**: Risk-based regression testing scope
+
+#### Test Dependencies Documentation
+
+- [ ] **Implementation Dependencies**: Tests blocked by specific development tasks
+- [ ] **Environment Dependencies**: Test environment and data requirements
+- [ ] **Tool Dependencies**: Testing framework and automation tool setup
+- [ ] **Cross-Team Dependencies**: Dependencies on external systems or teams
+
+#### Test Coverage Targets and Metrics
+
+- [ ] **Code Coverage Targets**: >80% line coverage, >90% branch coverage for critical paths
+- [ ] **Functional Coverage Targets**: 100% acceptance criteria validation
+- [ ] **Risk Coverage Targets**: 100% high-risk scenario validation
+- [ ] **Quality Characteristics Coverage**: Validation approach for each ISO 25010 characteristic
+
+### Task Level Breakdown
+
+#### Implementation Task Creation and Estimation
+
+- [ ] **Test Implementation Tasks**: Detailed test case development and automation tasks
+- [ ] **Test Environment Setup Tasks**: Infrastructure and configuration tasks
+- [ ] **Test Data Preparation Tasks**: Data generation and management tasks
+- [ ] **Test Automation Framework Tasks**: Tool setup and framework development
+
+#### Task Estimation Guidelines
+
+- [ ] **Unit Test Tasks**: 0.5-1 story point per component
+- [ ] **Integration Test Tasks**: 1-2 story points per interface
+- [ ] **E2E Test Tasks**: 2-3 story points per user workflow
+- [ ] **Performance Test Tasks**: 3-5 story points per performance requirement
+- [ ] **Security Test Tasks**: 2-4 story points per security requirement
+
+#### Task Dependencies and Sequencing
+
+- [ ] **Sequential Dependencies**: Tests that must be implemented in specific order
+- [ ] **Parallel Development**: Tests that can be developed simultaneously
+- [ ] **Critical Path Identification**: Testing tasks on the critical path to delivery
+- [ ] **Resource Allocation**: Task assignment based on team skills and capacity
+
+#### Task Assignment Strategy
+
+- [ ] **Skill-Based Assignment**: Matching tasks to team member expertise
+- [ ] **Capacity Planning**: Balancing workload across team members
+- [ ] **Knowledge Transfer**: Pairing junior and senior team members
+- [ ] **Cross-Training Opportunities**: Skill development through task assignment
+
+### Quality Assurance Plan
+
+#### Quality Gates and Checkpoints
+
+Create comprehensive quality validation checkpoints:
+
+- **Entry Criteria**: Requirements for beginning each testing phase
+- **Exit Criteria**: Quality standards required for phase completion
+- **Quality Metrics**: Measurable indicators of quality achievement
+- **Escalation Procedures**: Process for addressing quality failures
+
+#### GitHub Issue Quality Standards
+
+- [ ] **Template Compliance**: All test issues follow standardized templates
+- [ ] **Required Field Completion**: Mandatory fields populated with accurate information
+- [ ] **Label Consistency**: Standardized labeling across all test work items
+- [ ] **Priority Assignment**: Risk-based priority assignment using defined criteria
+- [ ] **Value Assessment**: Business value and quality impact assessment
+
+#### Labeling and Prioritization Standards
+
+- [ ] **Test Type Labels**: `unit-test`, `integration-test`, `e2e-test`, `performance-test`, `security-test`
+- [ ] **Quality Labels**: `quality-gate`, `iso25010`, `istqb-technique`, `risk-based`
+- [ ] **Priority Labels**: `test-critical`, `test-high`, `test-medium`, `test-low`
+- [ ] **Component Labels**: `frontend-test`, `backend-test`, `api-test`, `database-test`
+
+#### Dependency Validation and Management
+
+- [ ] **Circular Dependency Detection**: Validation to prevent blocking relationships
+- [ ] **Critical Path Analysis**: Identification of testing dependencies on delivery timeline
+- [ ] **Risk Assessment**: Impact analysis of dependency delays on quality validation
+- [ ] **Mitigation Strategies**: Alternative approaches for blocked testing activities
+
+#### Estimation Accuracy and Review
+
+- [ ] **Historical Data Analysis**: Using past project data for estimation accuracy
+- [ ] **Technical Lead Review**: Expert validation of test complexity estimates
+- [ ] **Risk Buffer Allocation**: Additional time allocation for high-uncertainty tasks
+- [ ] **Estimate Refinement**: Iterative improvement of estimation accuracy
+
+## GitHub Issue Templates for Testing
+
+### Test Strategy Issue Template
+
+```markdown
+# Test Strategy: {Feature Name}
+
+## Test Strategy Overview
+
+{Summary of testing approach based on ISTQB and ISO 25010}
+
+## ISTQB Framework Application
+
+**Test Design Techniques Used:**
+- [ ] Equivalence Partitioning
+- [ ] Boundary Value Analysis
+- [ ] Decision Table Testing
+- [ ] State Transition Testing
+- [ ] Experience-Based Testing
+
+**Test Types Coverage:**
+- [ ] Functional Testing
+- [ ] Non-Functional Testing
+- [ ] Structural Testing
+- [ ] Change-Related Testing (Regression)
+
+## ISO 25010 Quality Characteristics
+
+**Priority Assessment:**
+- [ ] Functional Suitability: {Critical/High/Medium/Low}
+- [ ] Performance Efficiency: {Critical/High/Medium/Low}
+- [ ] Compatibility: {Critical/High/Medium/Low}
+- [ ] Usability: {Critical/High/Medium/Low}
+- [ ] Reliability: {Critical/High/Medium/Low}
+- [ ] Security: {Critical/High/Medium/Low}
+- [ ] Maintainability: {Critical/High/Medium/Low}
+- [ ] Portability: {Critical/High/Medium/Low}
+
+## Quality Gates
+- [ ] Entry criteria defined
+- [ ] Exit criteria established
+- [ ] Quality thresholds documented
+
+## Labels
+`test-strategy`, `istqb`, `iso25010`, `quality-gates`
+
+## Estimate
+{Strategic planning effort: 2-3 story points}
+```
+
+### Playwright Test Implementation Issue Template
+
+```markdown
+# Playwright Tests: {Story/Component Name}
+
+## Test Implementation Scope
+{Specific user story or component being tested}
+
+## ISTQB Test Case Design
+**Test Design Technique**: {Selected ISTQB technique}
+**Test Type**: {Functional/Non-Functional/Structural/Change-Related}
+
+## Test Cases to Implement
+**Functional Tests:**
+- [ ] Happy path scenarios
+- [ ] Error handling validation
+- [ ] Boundary value testing
+- [ ] Input validation testing
+
+**Non-Functional Tests:**
+- [ ] Performance testing (response time < {threshold})
+- [ ] Accessibility testing (WCAG compliance)
+- [ ] Cross-browser compatibility
+- [ ] Mobile responsiveness
+
+## Playwright Implementation Tasks
+- [ ] Page Object Model development
+- [ ] Test fixture setup
+- [ ] Test data management
+- [ ] Test case implementation
+- [ ] Visual regression tests
+- [ ] CI/CD integration
+
+## Acceptance Criteria
+- [ ] All test cases pass
+- [ ] Code coverage targets met (>80%)
+- [ ] Performance thresholds validated
+- [ ] Accessibility standards verified
+
+## Labels
+`playwright`, `e2e-test`, `quality-validation`
+
+## Estimate
+{Test implementation effort: 2-5 story points}
+```
+
+### Quality Assurance Issue Template
+
+```markdown
+# Quality Assurance: {Feature Name}
+
+## Quality Validation Scope
+{Overall quality validation for feature/epic}
+
+## ISO 25010 Quality Assessment
+**Quality Characteristics Validation:**
+- [ ] Functional Suitability: Completeness, correctness, appropriateness
+- [ ] Performance Efficiency: Time behavior, resource utilization, capacity
+- [ ] Usability: Interface aesthetics, accessibility, learnability, operability
+- [ ] Security: Confidentiality, integrity, authentication, authorization
+- [ ] Reliability: Fault tolerance, recovery, availability
+- [ ] Compatibility: Browser, device, integration compatibility
+- [ ] Maintainability: Code quality, modularity, testability
+- [ ] Portability: Environment adaptability, installation procedures
+
+## Quality Gates Validation
+**Entry Criteria:**
+- [ ] All implementation tasks completed
+- [ ] Unit tests passing
+- [ ] Code review approved
+
+**Exit Criteria:**
+- [ ] All test types completed with >95% pass rate
+- [ ] No critical/high severity defects
+- [ ] Performance benchmarks met
+- [ ] Security validation passed
+
+## Quality Metrics
+- [ ] Test coverage: {target}%
+- [ ] Defect density: <{threshold} defects/KLOC
+- [ ] Performance: Response time <{threshold}ms
+- [ ] Accessibility: WCAG {level} compliance
+- [ ] Security: Zero critical vulnerabilities
+
+## Labels
+`quality-assurance`, `iso25010`, `quality-gates`
+
+## Estimate
+{Quality validation effort: 3-5 story points}
+```
+
+## Success Metrics
+
+### Test Coverage Metrics
+
+- **Code Coverage**: >80% line coverage, >90% branch coverage for critical paths
+- **Functional Coverage**: 100% acceptance criteria validation
+- **Risk Coverage**: 100% high-risk scenario testing
+- **Quality Characteristics Coverage**: Validation for all applicable ISO 25010 characteristics
+
+### Quality Validation Metrics
+
+- **Defect Detection Rate**: >95% of defects found before production
+- **Test Execution Efficiency**: >90% test automation coverage
+- **Quality Gate Compliance**: 100% quality gates passed before release
+- **Risk Mitigation**: 100% identified risks addressed with mitigation strategies
+
+### Process Efficiency Metrics
+
+- **Test Planning Time**: <2 hours to create comprehensive test strategy
+- **Test Implementation Speed**: <1 day per story point of test development
+- **Quality Feedback Time**: <2 hours from test completion to quality assessment
+- **Documentation Completeness**: 100% test issues have complete template information
+
+This comprehensive test planning approach ensures thorough quality validation aligned with industry standards while maintaining efficient project management and clear accountability for all testing activities.

package/skills/breakdown-test/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/breakdown-test`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/canvas-design/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.