All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Mobile Deep Link Routing Source Provenance LedgerUse when a decision about mobile deep-link routing depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the deep-link route test matrix. Success means each material claim has a source, version/date, location, and confidence note; valid links reach the intended screen and malformed or unauthorized links fail closed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, ...Votes: 0GitHub stars: 2
- Aas Mobile Deep Link Routing Threshold Rule CheckUse when a mobile deep-link routing decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the deep-link route test matrix 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; valid links reach the intended screen and malformed or unauthorized links fail closed. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Aas Mobile Locale Layout Approval Evidence PacketUse when a mobile localization layout resilience result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the localized layout stress sheet 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; critical controls remain readable and operable across the tested locales. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Mobile Locale Layout Change Impact TraceUse when a version, rule, source, or stakeholder change may affect mobile localization layout resilience to produce a before/after change record and impact map for the localized layout stress sheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; critical controls remain readable and operable across the tested locales. Use configured search, fetch, read, browser, test, and write capabilities only when relevan...Votes: 0GitHub stars: 2
- Aas Mobile Locale Layout Closeout Handoff LedgerUse when a mobile localization layout resilience work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the localized layout stress sheet 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; critical controls remain readable and operable across the tested locales. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Aas Mobile Locale Layout Completeness ReconciliationUse when the mobile localization layout resilience workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the localized layout stress sheet 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; critical controls remain readable and operable across the tested locales. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Aas Mobile Locale Layout Exception Triage QueueUse when the mobile localization layout resilience workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the localized layout stress sheet 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; critical controls remain readable and operable across the tested locales. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Aas Mobile Locale Layout Recovery Readiness DrillUse when the mobile localization layout resilience workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the localized layout stress sheet 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; critical controls remain readable and operable across the tested locales. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Aas Mobile Locale Layout Scenario Sensitivity MatrixUse when the mobile localization layout resilience team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the localized layout stress sheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; critical controls remain readable and operable across the tested locales. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Aas Mobile Locale Layout Scope Intake GateUse when a new mobile localization layout resilience request needs a bounded work scope to produce a scoped intake card for the localized layout stress sheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; critical controls remain readable and operable across the tested locales. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three ...Votes: 0GitHub stars: 2
- Aas Mobile Locale Layout Source Provenance LedgerUse when a decision about mobile localization layout resilience depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the localized layout stress sheet. Success means each material claim has a source, version/date, location, and confidence note; critical controls remain readable and operable across the tested locales. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence...Votes: 0GitHub stars: 2
- Aas Mobile Locale Layout Threshold Rule CheckUse when a mobile localization layout resilience decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the localized layout stress sheet 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; critical controls remain readable and operable across the tested locales. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Aas Mobile Mobile Accessibility Approval Evidence PacketUse when a mobile interaction accessibility result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the accessible interaction test record 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; core interaction remains operable across declared assistive settings. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Aas Mobile Mobile Accessibility Change Impact TraceUse when a version, rule, source, or stakeholder change may affect mobile interaction accessibility to produce a before/after change record and impact map for the accessible interaction test record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; core interaction remains operable across declared assistive settings. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...Votes: 0GitHub stars: 2
- Aas Mobile Mobile Accessibility Closeout Handoff LedgerUse when a mobile interaction accessibility work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the accessible interaction test record 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; core interaction remains operable across declared assistive settings. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Aas Mobile Mobile Accessibility Completeness ReconciliationUse when the mobile interaction accessibility workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the accessible interaction test record 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; core interaction remains operable across declared assistive settings. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Aas Mobile Mobile Accessibility Exception Triage QueueUse when the mobile interaction accessibility workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the accessible interaction test record 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; core interaction remains operable across declared assistive settings. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Aas Mobile Mobile Accessibility Recovery Readiness DrillUse when the mobile interaction accessibility workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the accessible interaction test record 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; core interaction remains operable across declared assistive settings. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Aas Mobile Mobile Accessibility Scenario Sensitivity MatrixUse when the mobile interaction accessibility team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the accessible interaction test record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; core interaction remains operable across declared assistive settings. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Aas Mobile Mobile Accessibility Scope Intake GateUse when a new mobile interaction accessibility request needs a bounded work scope to produce a scoped intake card for the accessible interaction test record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; core interaction remains operable across declared assistive settings. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focu...Votes: 0GitHub stars: 2
- Aas Mobile Mobile Accessibility Source Provenance LedgerUse when a decision about mobile interaction accessibility depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the accessible interaction test record. Success means each material claim has a source, version/date, location, and confidence note; core interaction remains operable across declared assistive settings. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, li...Votes: 0GitHub stars: 2
- Aas Mobile Mobile Accessibility Threshold Rule CheckUse when a mobile interaction accessibility decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the accessible interaction test record 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; core interaction remains operable across declared assistive settings. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Accessibility Audit And RemediationUse when auditing or improving a web or application interface for accessibility, including keyboard access, focus behavior, semantics, text alternatives, forms, and assistive-technology compatibility to select the applicable standard and user flows, combine automated checks with manual testing, and report evidence and gaps. Trigger for accessibility reviews or inclusive UI changes.Votes: 0GitHub stars: 2
- Angular DeveloperUse when a task involves building or maintaining an Angular application with version-matched framework patterns and tests 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 r...Votes: 0GitHub stars: 2
- Augmented Reality DevelopmentUse when building or modifying an augmented-reality experience that aligns digital content with camera imagery, tracked devices, or physical surfaces to define coordinate spaces, tracking inputs, permission boundaries, and a safe test method before adding interaction. Trigger for AR scene placement, anchors, pose tracking, or camera-based overlays.Votes: 0GitHub stars: 2
- Avalonia Layout Zafiro Capability Surface MapUse when the actual capability boundary of Avalonia layout with Zafiro needs to be distinguished from assumptions. Produce a capability map for Avalonia layout with Zafiro covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to XAML and shared-style boundaries, reu...Votes: 0GitHub stars: 2
- Avalonia Layout Zafiro Change Impact AssessmentUse when a proposed Avalonia layout with Zafiro version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Avalonia layout with Zafiro with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to XAML and shared-style boundaries, r...Votes: 0GitHub stars: 2
- Avalonia Layout Zafiro Failure Triage RecordUse when a reproducible Avalonia layout with Zafiro symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Avalonia layout with Zafiro with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to XAML and shared-style boundaries, reusable controls, version identity, an...Votes: 0GitHub stars: 2
- Avalonia Layout Zafiro Input Output ContractUse when the accepted inputs or produced outputs for Avalonia layout with Zafiro need a checkable boundary. Produce an input/output contract for Avalonia layout with Zafiro with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to XAML and shared-style boundaries, reusable controls, version iden...Votes: 0GitHub stars: 2
- Avalonia Layout Zafiro Integration Parity TraceUse when Avalonia layout with Zafiro exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Avalonia layout with Zafiro showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to XAML and shared-style boundaries, reusable controls, version identity, and rendere...Votes: 0GitHub stars: 2
- Avalonia Layout Zafiro Performance EnvelopeUse when Avalonia layout with Zafiro must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Avalonia layout with Zafiro with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to XAML and shared-style boundaries, reusable controls, ve...Votes: 0GitHub stars: 2
- Avalonia Layout Zafiro Permission Boundary ReviewUse when Avalonia layout with Zafiro may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Avalonia layout with Zafiro showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to XAML and shared-style boundaries, reusable c...Votes: 0GitHub stars: 2
- Avalonia Layout Zafiro Release Handoff RecordUse when a Avalonia layout with Zafiro review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Avalonia layout with Zafiro with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to XAML and shared-style boundaries, reu...Votes: 0GitHub stars: 2
- Avalonia Layout Zafiro Reproducibility Fixture PlanUse when a Avalonia layout with Zafiro result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Avalonia layout with Zafiro defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to XAML and ...Votes: 0GitHub stars: 2
- Avalonia Layout Zafiro Version CompatibilityUse when a Avalonia layout with Zafiro integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Avalonia layout with Zafiro with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to XAML and shared-style boundaries...Votes: 0GitHub stars: 2
- Browser Accessibility Locator Fallback PolicyUse when a task involves choosing a safe fallback when an interactive element lacks a reliable accessible locator 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 p...Votes: 0GitHub stars: 2
- Browser Accessibility Snapshot Diff EvaluationUse when a task involves comparing browser accessibility-tree snapshots after a UI change 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 w...Votes: 0GitHub stars: 2
- Browser Account Settings Change PreviewUse when a task involves previewing a browser account setting change before saving it 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 witho...Votes: 0GitHub stars: 2
- Browser Ambiguous Identity Human HandoffUse when a task involves pausing browser automation when the active account, organization, or record identity is uncertain 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 st...Votes: 0GitHub stars: 2
- Browser Archive Extraction Path Traversal ReviewUse when a task involves checking archive paths before extracting a file downloaded through a browser 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 exter...Votes: 0GitHub stars: 2
- Browser Async Spinner And Network Idle PolicyUse when a task involves choosing when an asynchronous browser workflow is stable enough to verify 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...Votes: 0GitHub stars: 2
- Browser Auth Cookie Storage Boundary AuditUse when a task involves reviewing how browser automation handles session cookies without disclosing their contents 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 Auth State Transfer MinimizationUse when a task involves minimizing authenticated browser state transferred between local and remote automation 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 per...Votes: 0GitHub stars: 2
- Browser Authenticated Form Fill ApprovalUse when a task involves reviewing authorization and scope before entering data into an authenticated web form 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 perf...Votes: 0GitHub stars: 2
- Browser Automation Rate Limit And ThrottleUse when a task involves setting bounded request pacing and concurrency for authorized browser automation 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 e...Votes: 0GitHub stars: 2
- Browser Background Tab Visibility PolicyUse when a task involves deciding when browser automation may activate a tab in the user's visible browser 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
- Browser Beforeunload Unsaved Work SafeguardUse when a task involves preventing accidental loss when navigating away from a browser page with unsaved changes 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 p...Votes: 0GitHub stars: 2
- Browser Browser Profile DecommissioningUse when a task involves planning cleanup of a temporary browser profile after a task ends 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 ...Votes: 0GitHub stars: 2
- Browser Cache Service Worker State ResetUse when a task involves creating a known browser cache and service-worker state for a reproducible test 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 ex...Votes: 0GitHub stars: 2
- Browser Captcha And Bot Challenge EscalationUse when a task involves defining a compliant response when a browser encounters CAPTCHA or anti-bot challenges 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 per...Votes: 0GitHub stars: 2