All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Mobile App Size Budget Recovery Readiness DrillUse when the mobile application size budget workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the application size regression report with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; the size change is attributed to components and stays within an approved budget. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Mobile App Size Budget Scenario Sensitivity MatrixUse when the mobile application size budget team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the application size regression report with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the size change is attributed to components and stays within an approved budget. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Aas Mobile App Size Budget Scope Intake GateUse when a new mobile application size budget request needs a bounded work scope to produce a scoped intake card for the application size regression report. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the size change is attributed to components and stays within an approved budget. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to t...Votes: 0GitHub stars: 2
- Aas Mobile App Size Budget Source Provenance LedgerUse when a decision about mobile application size budget depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the application size regression report. Success means each material claim has a source, version/date, location, and confidence note; the size change is attributed to components and stays within an approved budget. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evi...Votes: 0GitHub stars: 2
- Aas Mobile App Size Budget Threshold Rule CheckUse when a mobile application size budget decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the application size regression report showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; the size change is attributed to components and stays within an approved budget. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Aas Mobile Crash Symbols Approval Evidence PacketUse when a mobile crash symbol readiness result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the crash-symbol identity checklist containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; the report resolves to the matching build without retaining unnecessary user content. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Aas Mobile Crash Symbols Change Impact TraceUse when a version, rule, source, or stakeholder change may affect mobile crash symbol readiness to produce a before/after change record and impact map for the crash-symbol identity checklist. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the report resolves to the matching build without retaining unnecessary user content. Use configured search, fetch, read, browser, test, and write capabilities only when r...Votes: 0GitHub stars: 2
- Aas Mobile Crash Symbols Closeout Handoff LedgerUse when a mobile crash symbol readiness work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the crash-symbol identity checklist with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; the report resolves to the matching build without retaining unnecessary user content. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Aas Mobile Crash Symbols Completeness ReconciliationUse when the mobile crash symbol readiness workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the crash-symbol identity checklist with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; the report resolves to the matching build without retaining unnecessary user content. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Aas Mobile Crash Symbols Exception Triage QueueUse when the mobile crash symbol readiness workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the crash-symbol identity checklist with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; the report resolves to the matching build without retaining unnecessary user content. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Aas Mobile Crash Symbols Recovery Readiness DrillUse when the mobile crash symbol readiness workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the crash-symbol identity checklist with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; the report resolves to the matching build without retaining unnecessary user content. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Aas Mobile Crash Symbols Scenario Sensitivity MatrixUse when the mobile crash symbol readiness team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the crash-symbol identity checklist with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the report resolves to the matching build without retaining unnecessary user content. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Aas Mobile Crash Symbols Scope Intake GateUse when a new mobile crash symbol readiness request needs a bounded work scope to produce a scoped intake card for the crash-symbol identity checklist. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the report resolves to the matching build without retaining unnecessary user content. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to ...Votes: 0GitHub stars: 2
- Aas Mobile Crash Symbols Source Provenance LedgerUse when a decision about mobile crash symbol readiness depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the crash-symbol identity checklist. Success means each material claim has a source, version/date, location, and confidence note; the report resolves to the matching build without retaining unnecessary user content. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ev...Votes: 0GitHub stars: 2
- Aas Mobile Crash Symbols Threshold Rule CheckUse when a mobile crash symbol readiness decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the crash-symbol identity checklist showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; the report resolves to the matching build without retaining unnecessary user content. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Aas Mobile Permission Declaration Approval Evidence PacketUse when a mobile permission declarations result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the permission-to-feature trace containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; each declared permission maps to a user-visible feature and denial remains safe. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Aas Mobile Permission Declaration Change Impact TraceUse when a version, rule, source, or stakeholder change may affect mobile permission declarations to produce a before/after change record and impact map for the permission-to-feature trace. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each declared permission maps to a user-visible feature and denial remains safe. Use configured search, fetch, read, browser, test, and write capabilities only when relevant ...Votes: 0GitHub stars: 2
- Aas Mobile Permission Declaration Closeout Handoff LedgerUse when a mobile permission declarations work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the permission-to-feature trace with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; each declared permission maps to a user-visible feature and denial remains safe. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Aas Mobile Permission Declaration Completeness ReconciliationUse when the mobile permission declarations workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the permission-to-feature trace with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; each declared permission maps to a user-visible feature and denial remains safe. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Aas Mobile Permission Declaration Exception Triage QueueUse when the mobile permission declarations workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the permission-to-feature trace with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; each declared permission maps to a user-visible feature and denial remains safe. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Aas Mobile Permission Declaration Recovery Readiness DrillUse when the mobile permission declarations workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the permission-to-feature trace with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; each declared permission maps to a user-visible feature and denial remains safe. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Aas Mobile Permission Declaration Scenario Sensitivity MatrixUse when the mobile permission declarations team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the permission-to-feature trace with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each declared permission maps to a user-visible feature and denial remains safe. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Aas Mobile Permission Declaration Scope Intake GateUse when a new mobile permission declarations request needs a bounded work scope to produce a scoped intake card for the permission-to-feature trace. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each declared permission maps to a user-visible feature and denial remains safe. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three fo...Votes: 0GitHub stars: 2
- Aas Mobile Permission Declaration Source Provenance LedgerUse when a decision about mobile permission declarations depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the permission-to-feature trace. Success means each material claim has a source, version/date, location, and confidence note; each declared permission maps to a user-visible feature and denial remains safe. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, ...Votes: 0GitHub stars: 2
- Aas Mobile Permission Declaration Threshold Rule CheckUse when a mobile permission declarations decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the permission-to-feature trace showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; each declared permission maps to a user-visible feature and denial remains safe. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Aas Mobile Store Privacy Approval Evidence PacketUse when a mobile store privacy disclosure parity result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the store-disclosure evidence map containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; every declared collection is supported by app evidence and mismatches are escalated. Use configured search, fetch...Votes: 0GitHub stars: 2
- Aas Mobile Store Privacy Change Impact TraceUse when a version, rule, source, or stakeholder change may affect mobile store privacy disclosure parity to produce a before/after change record and impact map for the store-disclosure evidence map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every declared collection is supported by app evidence and mismatches are escalated. Use configured search, fetch, read, browser, test, and write capabilities only ...Votes: 0GitHub stars: 2
- Aas Mobile Store Privacy Closeout Handoff LedgerUse when a mobile store privacy disclosure parity work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the store-disclosure evidence map with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; every declared collection is supported by app evidence and mismatches are escalated. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Aas Mobile Store Privacy Completeness ReconciliationUse when the mobile store privacy disclosure parity workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the store-disclosure evidence map with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; every declared collection is supported by app evidence and mismatches are escalated. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Aas Mobile Store Privacy Exception Triage QueueUse when the mobile store privacy disclosure parity workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the store-disclosure evidence map with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; every declared collection is supported by app evidence and mismatches are escalated. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Mobile Store Privacy Recovery Readiness DrillUse when the mobile store privacy disclosure parity workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the store-disclosure evidence map with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; every declared collection is supported by app evidence and mismatches are escalated. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Mobile Store Privacy Scenario Sensitivity MatrixUse when the mobile store privacy disclosure parity team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the store-disclosure evidence map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every declared collection is supported by app evidence and mismatches are escalated. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Aas Mobile Store Privacy Scope Intake GateUse when a new mobile store privacy disclosure parity request needs a bounded work scope to produce a scoped intake card for the store-disclosure evidence map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every declared collection is supported by app evidence and mismatches are escalated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refineme...Votes: 0GitHub stars: 2
- Aas Mobile Store Privacy Source Provenance LedgerUse when a decision about mobile store privacy disclosure parity depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the store-disclosure evidence map. Success means each material claim has a source, version/date, location, and confidence note; every declared collection is supported by app evidence and mismatches are escalated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Rec...Votes: 0GitHub stars: 2
- Aas Mobile Store Privacy Threshold Rule CheckUse when a mobile store privacy disclosure parity decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the store-disclosure evidence map showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; every declared collection is supported by app evidence and mismatches are escalated. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Accessible Name Change Regression CheckUse when a button, input, icon, or composite control changes visible or programmatic labels to create or update an accessibility-tree comparison for affected controls. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: each affected control exposes the intended role and unambiguous name. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irrever...Votes: 0GitHub stars: 2
- App Store Connect Build Train ReadinessUse when a task involves checking version and build-number state before an authorized App Store Connect submission 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
- App Store Privacy Label Evidence ReconciliationUse when a task involves reconciling App Store privacy statements with documented app and SDK data flows 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
- Apple App Energy Impact Measurement PlanUse when a task involves planning a repeatable energy-use measurement for an Apple app feature 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
- Apple App Storage Footprint Regression CheckUse when a task involves checking whether an Apple app release increases installed or user-data storage unexpectedly 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
- Apple Background Task Expiration AuditUse when a task involves checking how app work responds when an Apple platform ends background execution time 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
- Apple Code Signing Entitlement MinimizationUse when a task involves reviewing whether an Apple app target requests only the entitlements needed for its approved 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 ...Votes: 0GitHub stars: 2
- Apple Release Symbol Artifact RetentionUse when a task involves planning retention and access controls for dSYM and symbol artifacts across Apple releases 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
- Apple Testflight Beta Cohort Change ControlUse when a task involves planning a controlled change to internal or external beta tester groups 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
- Bench ReadUse when a task involves reading benchmark artifacts and explaining what they do and do not establish about a system to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not install or run th...Votes: 0GitHub stars: 2
- Browser Concurrent Tab Action Race TestUse when a task involves testing for race conditions when multiple browser tasks share tabs or sessions to record the target site and origin, browser and driver version, active account, test or production context, user authorization, data sensitivity, and intended side effects. Use a bounded, reproducible interaction, verify both browser-visible and relevant underlying state, preserve evidence safely, and report uncertainty. Do not reuse profiles, disclose authentication state, or perform ext...Votes: 0GitHub stars: 2
- Browser Cross Browser Compatibility MatrixUse when a task involves planning browser and device coverage for a specific web feature to record the target site and origin, browser and driver version, active account, test or production context, user authorization, data sensitivity, and intended side effects. Use a bounded, reproducible interaction, verify both browser-visible and relevant underlying state, preserve evidence safely, and report uncertainty. Do not reuse profiles, disclose authentication state, or perform external writes wi...Votes: 0GitHub stars: 2
- Browser Drag And Drop Acceptance TestUse when a task involves testing a browser drag-and-drop interaction with a reversible test item to record the target site and origin, browser and driver version, active account, test or production context, user authorization, data sensitivity, and intended side effects. Use a bounded, reproducible interaction, verify both browser-visible and relevant underlying state, preserve evidence safely, and report uncertainty. Do not reuse profiles, disclose authentication state, or perform external w...Votes: 0GitHub stars: 2
- Browser Expiring Auth Session Refresh TestUse when a task involves testing how browser automation detects and recovers from an expired authenticated session to record the target site and origin, browser and driver version, active account, test or production context, user authorization, data sensitivity, and intended side effects. Use a bounded, reproducible interaction, verify both browser-visible and relevant underlying state, preserve evidence safely, and report uncertainty. Do not reuse profiles, disclose authentication state, or ...Votes: 0GitHub stars: 2
- Browser Form Validation Boundary TestUse when a task involves testing browser form validation for required, malformed, and boundary-value inputs to record the target site and origin, browser and driver version, active account, test or production context, user authorization, data sensitivity, and intended side effects. Use a bounded, reproducible interaction, verify both browser-visible and relevant underlying state, preserve evidence safely, and report uncertainty. Do not reuse profiles, disclose authentication state, or perform...Votes: 0GitHub stars: 2