All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Requirement Row To Test Identifier Coverage AuditUse when a requirements matrix has been revised before a release or implementation handoff to create or update a requirement-to-test map with uncovered rows and orphan tests. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: each required behavior has at least one relevant check and no check is falsely mapped. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before exter...Votes: 0GitHub stars: 2
- Swift Actor Test Isolation DesignUse when a task involves designing tests that verify an actor's state ownership without masking races to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Swift Async Test Determinism ReviewUse when a task involves reducing timing-dependent flakiness in tests of Swift asynchronous behavior to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Swift Cancellation Propagation Test PlanUse when a task involves testing cooperative cancellation across async functions and child tasks to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Synthetic Upload Content ValidationUse when a web workflow accepts user-selected files to create or update an upload boundary matrix with file metadata and observed outcomes. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: valid files are accepted and invalid or oversized files are rejected with safe feedback. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible wri...Votes: 0GitHub stars: 2
- Test Driven Development WorkflowUse when implementing new behavior, fixing a defect, or refactoring code where automated checks can describe the expected behavior to turn acceptance criteria into focused tests, observe a meaningful failing test, make the smallest change that passes, then refactor and re-verify. Trigger for feature work, bug fixes, and behavior-changing refactors; adapt the test form when automation is not practical.Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Api Compatibility Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Software testing and release assurance: accessibility testing for API compatibility. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Assert compatibility at public boundaries using versioned contract fixtures rather than internal implementation details. Success means the prepared result is reproducible, reviewable, and withi...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Api Compatibility Design BlueprintUse when a solution needs a coherent structure before implementation or production for Software testing and release assurance: accessibility testing for API compatibility. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Assert compatibility at public boundaries using versioned contract fixtures rather than internal implementation details. Success means interfaces, dependencies, constraints, and review points are testable before buil...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Api Compatibility Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Software testing and release assurance: accessibility testing for API compatibility. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Assert compatibility at public boundaries using versioned contract fixtures rather than internal implementation details. Success means the failure is bounded by observations, one testab...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Api Compatibility Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: accessibility testing for API compatibility. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Assert compatibility at public boundaries using versioned contract fixtures rather than internal implementation details. Success means the proposed change is compared wi...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Api Compatibility Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Software testing and release assurance: accessibility testing for API compatibility. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Assert compatibility at public boundaries using versioned contract fixtures rather than internal implementation details. Success means options are compared on user-approved criteria with uncertainty...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Api Compatibility Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Software testing and release assurance: accessibility testing for API compatibility. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Assert compatibility at public boundaries using versioned contract fixtures rather than internal implementation details. Success means requirements have priorities, evidence, owners, and measurab...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Api Compatibility Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Software testing and release assurance: accessibility testing for API compatibility. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Assert compatibility at public boundaries using versioned contract fixtures rather than internal implementation details. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permiss...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Api Compatibility Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Software testing and release assurance: accessibility testing for API compatibility. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Assert compatibility at public boundaries using versioned contract fixtures rather than internal implementation details. Success means the review names relevant hazards, permiss...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Api Compatibility Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Software testing and release assurance: accessibility testing for API compatibility. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Assert compatibility at public boundaries using versioned contract fixtures rather than internal implementation details. Success means material claims are linked to current primary sources with dates and limitations. Use permission...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Api Compatibility Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: accessibility testing for API compatibility. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Assert compatibility at public boundaries using versioned contract fixtures rather than internal implementation details. Success means each critical requirement maps to a reproduci...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Ci Cost Budgets Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Software testing and release assurance: accessibility testing for CI cost budgets. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Compare execution time and resource cost to the agreed ceiling without removing high-risk coverage silently. Success means the prepared result is reproducible, reviewable, and within the approved...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Ci Cost Budgets Design BlueprintUse when a solution needs a coherent structure before implementation or production for Software testing and release assurance: accessibility testing for CI cost budgets. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Compare execution time and resource cost to the agreed ceiling without removing high-risk coverage silently. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permiss...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Ci Cost Budgets Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Software testing and release assurance: accessibility testing for CI cost budgets. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Compare execution time and resource cost to the agreed ceiling without removing high-risk coverage silently. Success means the failure is bounded by observations, one testable hypothesis,...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Ci Cost Budgets Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: accessibility testing for CI cost budgets. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Compare execution time and resource cost to the agreed ceiling without removing high-risk coverage silently. Success means the proposed change is compared with a baseline,...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Ci Cost Budgets Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Software testing and release assurance: accessibility testing for CI cost budgets. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Compare execution time and resource cost to the agreed ceiling without removing high-risk coverage silently. Success means options are compared on user-approved criteria with uncertainty and trade-off...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Ci Cost Budgets Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Software testing and release assurance: accessibility testing for CI cost budgets. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Compare execution time and resource cost to the agreed ceiling without removing high-risk coverage silently. Success means requirements have priorities, evidence, owners, and measurable acceptance ...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Ci Cost Budgets Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Software testing and release assurance: accessibility testing for CI cost budgets. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Compare execution time and resource cost to the agreed ceiling without removing high-risk coverage silently. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, ...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Ci Cost Budgets Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Software testing and release assurance: accessibility testing for CI cost budgets. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Compare execution time and resource cost to the agreed ceiling without removing high-risk coverage silently. Success means the review names relevant hazards, permissions, controls...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Ci Cost Budgets Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Software testing and release assurance: accessibility testing for CI cost budgets. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Compare execution time and resource cost to the agreed ceiling without removing high-risk coverage silently. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, pre...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Ci Cost Budgets Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: accessibility testing for CI cost budgets. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Compare execution time and resource cost to the agreed ceiling without removing high-risk coverage silently. Success means each critical requirement maps to a reproducible check and ...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Cross Platform Behavior Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Software testing and release assurance: accessibility testing for cross-platform behavior. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means the prepared result is reproducible, reviewable, and within the approved ...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Cross Platform Behavior Design BlueprintUse when a solution needs a coherent structure before implementation or production for Software testing and release assurance: accessibility testing for cross-platform behavior. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissi...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Cross Platform Behavior Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Software testing and release assurance: accessibility testing for cross-platform behavior. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means the failure is bounded by observations, one testable hypothesis, ...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Cross Platform Behavior Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: accessibility testing for cross-platform behavior. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means the proposed change is compared with a baseline, ...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Cross Platform Behavior Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Software testing and release assurance: accessibility testing for cross-platform behavior. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means options are compared on user-approved criteria with uncertainty and trade-offs...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Cross Platform Behavior Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Software testing and release assurance: accessibility testing for cross-platform behavior. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means requirements have priorities, evidence, owners, and measurable acceptance c...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Cross Platform Behavior Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Software testing and release assurance: accessibility testing for cross-platform behavior. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, p...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Cross Platform Behavior Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Software testing and release assurance: accessibility testing for cross-platform behavior. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means the review names relevant hazards, permissions, controls,...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Cross Platform Behavior Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Software testing and release assurance: accessibility testing for cross-platform behavior. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, pres...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Cross Platform Behavior Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: accessibility testing for cross-platform behavior. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means each critical requirement maps to a reproducible check and a...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Data Edge Cases Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Software testing and release assurance: accessibility testing for data edge cases. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Exercise null, empty, boundary, malformed, duplicated, reordered, and out-of-range inputs with safe synthetic data. Success means the prepared result is reproducible, reviewable, and within the a...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Data Edge Cases Design BlueprintUse when a solution needs a coherent structure before implementation or production for Software testing and release assurance: accessibility testing for data edge cases. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Exercise null, empty, boundary, malformed, duplicated, reordered, and out-of-range inputs with safe synthetic data. Success means interfaces, dependencies, constraints, and review points are testable before build. Use ...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Data Edge Cases Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Software testing and release assurance: accessibility testing for data edge cases. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Exercise null, empty, boundary, malformed, duplicated, reordered, and out-of-range inputs with safe synthetic data. Success means the failure is bounded by observations, one testable hypo...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Data Edge Cases Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: accessibility testing for data edge cases. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Exercise null, empty, boundary, malformed, duplicated, reordered, and out-of-range inputs with safe synthetic data. Success means the proposed change is compared with a ba...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Data Edge Cases Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Software testing and release assurance: accessibility testing for data edge cases. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Exercise null, empty, boundary, malformed, duplicated, reordered, and out-of-range inputs with safe synthetic data. Success means options are compared on user-approved criteria with uncertainty and tr...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Data Edge Cases Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Software testing and release assurance: accessibility testing for data edge cases. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Exercise null, empty, boundary, malformed, duplicated, reordered, and out-of-range inputs with safe synthetic data. Success means requirements have priorities, evidence, owners, and measurable acce...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Data Edge Cases Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Software testing and release assurance: accessibility testing for data edge cases. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Exercise null, empty, boundary, malformed, duplicated, reordered, and out-of-range inputs with safe synthetic data. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned i...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Data Edge Cases Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Software testing and release assurance: accessibility testing for data edge cases. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Exercise null, empty, boundary, malformed, duplicated, reordered, and out-of-range inputs with safe synthetic data. Success means the review names relevant hazards, permissions, c...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Data Edge Cases Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Software testing and release assurance: accessibility testing for data edge cases. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Exercise null, empty, boundary, malformed, duplicated, reordered, and out-of-range inputs with safe synthetic data. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inpu...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Data Edge Cases Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Software testing and release assurance: accessibility testing for data edge cases. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Exercise null, empty, boundary, malformed, duplicated, reordered, and out-of-range inputs with safe synthetic data. Success means each critical requirement maps to a reproducible che...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Flaky Failures Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Software testing and release assurance: accessibility testing for flaky failures. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Collect repeated outcomes with a stable seed/environment and retain every failure trace for triage. Success means the prepared result is reproducible, reviewable, and within the approved scope. Us...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Flaky Failures Design BlueprintUse when a solution needs a coherent structure before implementation or production for Software testing and release assurance: accessibility testing for flaky failures. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Collect repeated outcomes with a stable seed/environment and retain every failure trace for triage. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inpu...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Flaky Failures Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Software testing and release assurance: accessibility testing for flaky failures. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Collect repeated outcomes with a stable seed/environment and retain every failure trace for triage. Success means the failure is bounded by observations, one testable hypothesis, and a saf...Votes: 0GitHub stars: 2
- Testlab Accessibility Testing Flaky Failures Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software testing and release assurance: accessibility testing for flaky failures. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Collect repeated outcomes with a stable seed/environment and retain every failure trace for triage. Success means the proposed change is compared with a baseline, regressio...Votes: 0GitHub stars: 2