All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Terraform Aws Integration Parity TraceUse when Terraform on AWS exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Terraform on AWS 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 provider pinning, state identity, planned resource changes, and AWS identity scope. Use only authorized ...Votes: 0GitHub stars: 2
- Terraform Aws Performance EnvelopeUse when Terraform on AWS must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Terraform on AWS 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 provider pinning, state identity, planned resource changes, and AWS identity ...Votes: 0GitHub stars: 2
- Terraform Aws Permission Boundary ReviewUse when Terraform on AWS may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Terraform on AWS 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 provider pinning, state identity, planned resource changes, and AW...Votes: 0GitHub stars: 2
- Terraform Aws Release Handoff RecordUse when a Terraform on AWS review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Terraform on AWS 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 provider pinning, state identity, planned resource changes,...Votes: 0GitHub stars: 2
- Terraform Aws Reproducibility Fixture PlanUse when a Terraform on AWS result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Terraform on AWS 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 provider pinning, state identit...Votes: 0GitHub stars: 2
- Terraform Aws Version CompatibilityUse when a Terraform on AWS integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Terraform on AWS 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 provider pinning, state identity, planned resource cha...Votes: 0GitHub stars: 2
- Terraform Module Library Capability Surface MapUse when the actual capability boundary of Terraform module libraries needs to be distinguished from assumptions. Produce a capability map for Terraform module libraries 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 input/output contracts, address stabili...Votes: 0GitHub stars: 2
- Terraform Module Library Change Impact AssessmentUse when a proposed Terraform module libraries version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Terraform module libraries 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 input/output contracts, address stabi...Votes: 0GitHub stars: 2
- Terraform Module Library Failure Triage RecordUse when a reproducible Terraform module libraries symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Terraform module libraries 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 input/output contracts, address stability, module versioning, and isolated ...Votes: 0GitHub stars: 2
- Terraform Module Library Input Output ContractUse when the accepted inputs or produced outputs for Terraform module libraries need a checkable boundary. Produce an input/output contract for Terraform module libraries 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 input/output contracts, address stability, module versioning, and i...Votes: 0GitHub stars: 2
- Terraform Module Library Integration Parity TraceUse when Terraform module libraries exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Terraform module libraries 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 input/output contracts, address stability, module versioning, and isolated validatio...Votes: 0GitHub stars: 2
- Terraform Module Library Performance EnvelopeUse when Terraform module libraries must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Terraform module libraries 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 input/output contracts, address stability, module version...Votes: 0GitHub stars: 2
- Terraform Module Library Permission Boundary ReviewUse when Terraform module libraries may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Terraform module libraries 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 input/output contracts, address stability, mod...Votes: 0GitHub stars: 2
- Terraform Module Library Release Handoff RecordUse when a Terraform module libraries review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Terraform module libraries 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 input/output contracts, address stabili...Votes: 0GitHub stars: 2
- Terraform Module Library Reproducibility Fixture PlanUse when a Terraform module libraries result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Terraform module libraries 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 input/outpu...Votes: 0GitHub stars: 2
- Terraform Module Library Version CompatibilityUse when a Terraform module libraries integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Terraform module libraries 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 input/output contracts, address st...Votes: 0GitHub stars: 2
- Vercel Deployment Capability Surface MapUse when the actual capability boundary of Vercel deployment readiness needs to be distinguished from assumptions. Produce a capability map for Vercel deployment readiness 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 build identity, preview versus produc...Votes: 0GitHub stars: 2
- Vercel Deployment Change Impact AssessmentUse when a proposed Vercel deployment readiness version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Vercel deployment readiness 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 build identity, preview versus prod...Votes: 0GitHub stars: 2
- Vercel Deployment Failure Triage RecordUse when a reproducible Vercel deployment readiness symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Vercel deployment readiness 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 build identity, preview versus production scope, environment variables, a...Votes: 0GitHub stars: 2
- Vercel Deployment Input Output ContractUse when the accepted inputs or produced outputs for Vercel deployment readiness need a checkable boundary. Produce an input/output contract for Vercel deployment readiness 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 build identity, preview versus production scope, environment vari...Votes: 0GitHub stars: 2
- Vercel Deployment Integration Parity TraceUse when Vercel deployment readiness exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Vercel deployment readiness 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 build identity, preview versus production scope, environment variables, and rollba...Votes: 0GitHub stars: 2
- Vercel Deployment Performance EnvelopeUse when Vercel deployment readiness must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Vercel deployment readiness 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 build identity, preview versus production scope, enviro...Votes: 0GitHub stars: 2
- Vercel Deployment Permission Boundary ReviewUse when Vercel deployment readiness may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Vercel deployment readiness 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 build identity, preview versus production sc...Votes: 0GitHub stars: 2
- Vercel Deployment Release Handoff RecordUse when a Vercel deployment readiness review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Vercel deployment readiness 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 build identity, preview versus produc...Votes: 0GitHub stars: 2
- Vercel Deployment Reproducibility Fixture PlanUse when a Vercel deployment readiness result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Vercel deployment readiness 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 build ide...Votes: 0GitHub stars: 2
- Vercel Deployment Version CompatibilityUse when a Vercel deployment readiness integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Vercel deployment readiness 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 build identity, preview versus p...Votes: 0GitHub stars: 2
- Vercel Optimize Capability Surface MapUse when the actual capability boundary of Vercel performance optimization needs to be distinguished from assumptions. Produce a capability map for Vercel performance optimization 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 measured baseline, build outp...Votes: 0GitHub stars: 2
- Vercel Optimize Change Impact AssessmentUse when a proposed Vercel performance optimization version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Vercel performance optimization 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 measured baseline, build ou...Votes: 0GitHub stars: 2
- Vercel Optimize Failure Triage RecordUse when a reproducible Vercel performance optimization symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Vercel performance optimization 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 measured baseline, build output, function limits, cache behavior,...Votes: 0GitHub stars: 2
- Vercel Optimize Input Output ContractUse when the accepted inputs or produced outputs for Vercel performance optimization need a checkable boundary. Produce an input/output contract for Vercel performance optimization 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 measured baseline, build output, function limits, cache b...Votes: 0GitHub stars: 2
- Vercel Optimize Integration Parity TraceUse when Vercel performance optimization exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Vercel performance optimization 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 measured baseline, build output, function limits, cache behavior, and cost...Votes: 0GitHub stars: 2
- Vercel Optimize Performance EnvelopeUse when Vercel performance optimization must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Vercel performance optimization 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 measured baseline, build output, function limit...Votes: 0GitHub stars: 2
- Vercel Optimize Permission Boundary ReviewUse when Vercel performance optimization may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Vercel performance optimization 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 measured baseline, build output, fun...Votes: 0GitHub stars: 2
- Vercel Optimize Release Handoff RecordUse when a Vercel performance optimization review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Vercel performance optimization 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 measured baseline, build outp...Votes: 0GitHub stars: 2
- Vercel Optimize Reproducibility Fixture PlanUse when a Vercel performance optimization result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Vercel performance optimization 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 m...Votes: 0GitHub stars: 2
- Vercel Optimize Version CompatibilityUse when a Vercel performance optimization integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Vercel performance optimization 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 measured baseline, build...Votes: 0GitHub stars: 2
- Azure Web Pubsub Ts Capability Surface MapUse when the actual capability boundary of Azure Web PubSub SDK for TypeScript needs to be distinguished from assumptions. Produce a capability map for Azure Web PubSub SDK for TypeScript 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 connection identity, ...Votes: 0GitHub stars: 2
- Azure Web Pubsub Ts Change Impact AssessmentUse when a proposed Azure Web PubSub SDK for TypeScript version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Azure Web PubSub SDK for TypeScript 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 connection identity...Votes: 0GitHub stars: 2
- Azure Web Pubsub Ts Failure Triage RecordUse when a reproducible Azure Web PubSub SDK for TypeScript symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Azure Web PubSub SDK for TypeScript 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 connection identity, event delivery, negotiated protocols...Votes: 0GitHub stars: 2
- Azure Web Pubsub Ts Input Output ContractUse when the accepted inputs or produced outputs for Azure Web PubSub SDK for TypeScript need a checkable boundary. Produce an input/output contract for Azure Web PubSub SDK for TypeScript 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 connection identity, event delivery, negotiated p...Votes: 0GitHub stars: 2
- Azure Web Pubsub Ts Integration Parity TraceUse when Azure Web PubSub SDK for TypeScript exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Azure Web PubSub SDK for TypeScript 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 connection identity, event delivery, negotiated protocols, group m...Votes: 0GitHub stars: 2
- Azure Web Pubsub Ts Performance EnvelopeUse when Azure Web PubSub SDK for TypeScript must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Azure Web PubSub SDK for TypeScript 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 connection identity, event delivery, ne...Votes: 0GitHub stars: 2
- Azure Web Pubsub Ts Permission Boundary ReviewUse when Azure Web PubSub SDK for TypeScript may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Azure Web PubSub SDK for TypeScript 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 connection identity, event d...Votes: 0GitHub stars: 2
- Azure Web Pubsub Ts Release Handoff RecordUse when a Azure Web PubSub SDK for TypeScript review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Azure Web PubSub SDK for TypeScript 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 connection identity, ...Votes: 0GitHub stars: 2
- Azure Web Pubsub Ts Reproducibility Fixture PlanUse when a Azure Web PubSub SDK for TypeScript result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Azure Web PubSub SDK for TypeScript 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 boun...Votes: 0GitHub stars: 2
- Azure Web Pubsub Ts Version CompatibilityUse when a Azure Web PubSub SDK for TypeScript integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Azure Web PubSub SDK for TypeScript 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 connection ident...Votes: 0GitHub stars: 2
- Cloudflare Pages Capability Surface MapUse when the actual capability boundary of Cloudflare Pages delivery needs to be distinguished from assumptions. Produce a capability map for Cloudflare Pages delivery 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 build adapter, route behavior, environmen...Votes: 0GitHub stars: 2
- Cloudflare Pages Change Impact AssessmentUse when a proposed Cloudflare Pages delivery version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Cloudflare Pages delivery 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 build adapter, route behavior, environm...Votes: 0GitHub stars: 2
- Cloudflare Pages Failure Triage RecordUse when a reproducible Cloudflare Pages delivery symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Cloudflare Pages delivery 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 build adapter, route behavior, environment bindings, preview identity, and de...Votes: 0GitHub stars: 2
- Cloudflare Pages Input Output ContractUse when the accepted inputs or produced outputs for Cloudflare Pages delivery need a checkable boundary. Produce an input/output contract for Cloudflare Pages delivery 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 build adapter, route behavior, environment bindings, preview identity...Votes: 0GitHub stars: 2