All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- React Native Architecture Integration Parity TraceUse when React Native application architecture exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for React Native application architecture 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 native-module boundaries, navigation state, offline behavior, ...Votes: 0GitHub stars: 2
- React Native Architecture Performance EnvelopeUse when React Native application architecture must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for React Native application architecture 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 native-module boundaries, navigatio...Votes: 0GitHub stars: 2
- React Native Architecture Permission Boundary ReviewUse when React Native application architecture may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for React Native application architecture 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 native-module boundaries...Votes: 0GitHub stars: 2
- React Native Architecture Release Handoff RecordUse when a React Native application architecture review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for React Native application architecture 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 native-module bou...Votes: 0GitHub stars: 2
- React Native Architecture Reproducibility Fixture PlanUse when a React Native application architecture result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for React Native application architecture 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 ...Votes: 0GitHub stars: 2
- React Native Architecture Version CompatibilityUse when a React Native application architecture integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for React Native application architecture 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 native-modul...Votes: 0GitHub stars: 2
- React State Management Capability Surface MapUse when the actual capability boundary of React state management needs to be distinguished from assumptions. Produce a capability map for React state management 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 server/client state ownership, cache invalidati...Votes: 0GitHub stars: 2
- React State Management Change Impact AssessmentUse when a proposed React state management version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for React state management 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 server/client state ownership, cache invalida...Votes: 0GitHub stars: 2
- React State Management Failure Triage RecordUse when a reproducible React state management symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for React state management 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 server/client state ownership, cache invalidation, update ordering, and observable ...Votes: 0GitHub stars: 2
- React State Management Input Output ContractUse when the accepted inputs or produced outputs for React state management need a checkable boundary. Produce an input/output contract for React state management 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 server/client state ownership, cache invalidation, update ordering, and obs...Votes: 0GitHub stars: 2
- React State Management Integration Parity TraceUse when React state management exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for React state management 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 server/client state ownership, cache invalidation, update ordering, and observable UI state....Votes: 0GitHub stars: 2
- React State Management Performance EnvelopeUse when React state management must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for React state management 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 server/client state ownership, cache invalidation, update orderin...Votes: 0GitHub stars: 2
- React State Management Permission Boundary ReviewUse when React state management may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for React state management 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 server/client state ownership, cache invalidation, upd...Votes: 0GitHub stars: 2
- React State Management Release Handoff RecordUse when a React state management review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for React state management 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 server/client state ownership, cache invalidati...Votes: 0GitHub stars: 2
- React State Management Reproducibility Fixture PlanUse when a React state management result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for React state management 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 server/client state...Votes: 0GitHub stars: 2
- React State Management Version CompatibilityUse when a React state management integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for React state management 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 server/client state ownership, cache inval...Votes: 0GitHub stars: 2
- React Ui Patterns Capability Surface MapUse when the actual capability boundary of React asynchronous UI patterns needs to be distinguished from assumptions. Produce a capability map for React asynchronous UI patterns 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 loading, empty, error, retry, a...Votes: 0GitHub stars: 2
- React Ui Patterns Change Impact AssessmentUse when a proposed React asynchronous UI patterns version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for React asynchronous UI patterns 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 loading, empty, error, retry,...Votes: 0GitHub stars: 2
- React Ui Patterns Failure Triage RecordUse when a reproducible React asynchronous UI patterns symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for React asynchronous UI patterns 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 loading, empty, error, retry, and success states around asynchronou...Votes: 0GitHub stars: 2
- React Ui Patterns Input Output ContractUse when the accepted inputs or produced outputs for React asynchronous UI patterns need a checkable boundary. Produce an input/output contract for React asynchronous UI patterns 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 loading, empty, error, retry, and success states around asy...Votes: 0GitHub stars: 2
- React Ui Patterns Integration Parity TraceUse when React asynchronous UI patterns exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for React asynchronous UI patterns 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 loading, empty, error, retry, and success states around asynchronous data. U...Votes: 0GitHub stars: 2
- React Ui Patterns Performance EnvelopeUse when React asynchronous UI patterns must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for React asynchronous UI patterns 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 loading, empty, error, retry, and success states ...Votes: 0GitHub stars: 2
- React Ui Patterns Permission Boundary ReviewUse when React asynchronous UI patterns may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for React asynchronous UI patterns 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 loading, empty, error, retry, and succ...Votes: 0GitHub stars: 2
- React Ui Patterns Release Handoff RecordUse when a React asynchronous UI patterns review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for React asynchronous UI patterns 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 loading, empty, error, retry, a...Votes: 0GitHub stars: 2
- React Ui Patterns Reproducibility Fixture PlanUse when a React asynchronous UI patterns result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for React asynchronous UI patterns 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 loa...Votes: 0GitHub stars: 2
- React Ui Patterns Version CompatibilityUse when a React asynchronous UI patterns integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for React asynchronous UI patterns 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 loading, empty, error, ret...Votes: 0GitHub stars: 2
- Responsive Overflow Breakpoint LocalizerUse when a responsive page clips content or introduces an unwanted horizontal scrollbar to create or update a viewport-to-overflow map with responsible component evidence. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the first failing width and the corrected layout are reproducible. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreve...Votes: 0GitHub stars: 2
- Skeleton To Content Layout Shift CaptureUse when a page uses skeletons, placeholders, or async data replacement to create or update a before/after layout trace for major content anchors. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: final content does not unexpectedly move controls or obscure the user’s current target. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversib...Votes: 0GitHub stars: 2
- Spline 3d Integration Capability Surface MapUse when the actual capability boundary of Spline 3D web integration needs to be distinguished from assumptions. Produce a capability map for Spline 3D web integration 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 embed boundary, external asset identity, ...Votes: 0GitHub stars: 2
- Spline 3d Integration Change Impact AssessmentUse when a proposed Spline 3D web integration version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Spline 3D web integration 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 embed boundary, external asset identity...Votes: 0GitHub stars: 2
- Spline 3d Integration Failure Triage RecordUse when a reproducible Spline 3D web integration symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Spline 3D web integration 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 embed boundary, external asset identity, interaction events, accessibility, a...Votes: 0GitHub stars: 2
- Spline 3d Integration Input Output ContractUse when the accepted inputs or produced outputs for Spline 3D web integration need a checkable boundary. Produce an input/output contract for Spline 3D web integration 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 embed boundary, external asset identity, interaction events, accessib...Votes: 0GitHub stars: 2
- Spline 3d Integration Integration Parity TraceUse when Spline 3D web integration exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Spline 3D web integration 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 embed boundary, external asset identity, interaction events, accessibility, and runtim...Votes: 0GitHub stars: 2
- Spline 3d Integration Performance EnvelopeUse when Spline 3D web integration must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Spline 3D web integration 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 embed boundary, external asset identity, interaction events...Votes: 0GitHub stars: 2
- Spline 3d Integration Permission Boundary ReviewUse when Spline 3D web integration may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Spline 3D web integration 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 embed boundary, external asset identity, interac...Votes: 0GitHub stars: 2
- Spline 3d Integration Release Handoff RecordUse when a Spline 3D web integration review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Spline 3D web integration 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 embed boundary, external asset identity, ...Votes: 0GitHub stars: 2
- Spline 3d Integration Reproducibility Fixture PlanUse when a Spline 3D web integration result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Spline 3D web integration 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 embed boundar...Votes: 0GitHub stars: 2
- Spline 3d Integration Version CompatibilityUse when a Spline 3D web integration integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Spline 3D web integration 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 embed boundary, external asset ident...Votes: 0GitHub stars: 2
- Sveltekit Capability Surface MapUse when the actual capability boundary of SvelteKit application workflows needs to be distinguished from assumptions. Produce a capability map for SvelteKit application workflows 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 server/client execution bound...Votes: 0GitHub stars: 2
- Sveltekit Change Impact AssessmentUse when a proposed SvelteKit application workflows version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for SvelteKit application workflows 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 server/client execution bou...Votes: 0GitHub stars: 2
- Sveltekit Failure Triage RecordUse when a reproducible SvelteKit application workflows symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for SvelteKit application workflows 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 server/client execution boundaries, route data, form handling, an...Votes: 0GitHub stars: 2
- Sveltekit Input Output ContractUse when the accepted inputs or produced outputs for SvelteKit application workflows need a checkable boundary. Produce an input/output contract for SvelteKit application workflows 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 server/client execution boundaries, route data, form hand...Votes: 0GitHub stars: 2
- Sveltekit Integration Parity TraceUse when SvelteKit application workflows exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for SvelteKit application workflows 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 server/client execution boundaries, route data, form handling, and secret ...Votes: 0GitHub stars: 2
- Sveltekit Performance EnvelopeUse when SvelteKit application workflows must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for SvelteKit application workflows 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 server/client execution boundaries, route data,...Votes: 0GitHub stars: 2
- Sveltekit Permission Boundary ReviewUse when SvelteKit application workflows may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for SvelteKit application workflows 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 server/client execution boundaries, ...Votes: 0GitHub stars: 2
- Sveltekit Release Handoff RecordUse when a SvelteKit application workflows review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for SvelteKit application workflows 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 server/client execution bound...Votes: 0GitHub stars: 2
- Sveltekit Reproducibility Fixture PlanUse when a SvelteKit application workflows result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for SvelteKit application workflows 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 s...Votes: 0GitHub stars: 2
- Sveltekit Version CompatibilityUse when a SvelteKit application workflows integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for SvelteKit application workflows 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 server/client execution ...Votes: 0GitHub stars: 2
- Swiftui Accessibility Focus Order TestUse when a task involves testing accessible focus, labels, and action order in a SwiftUI view 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
- Swiftui Animation Frame Budget AnalysisUse when a task involves investigating dropped frames during a SwiftUI animation or transition 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