All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Golang Design PatternsUse when a task involves choosing or implementing Go design patterns only where they simplify a concrete package or concurrency problem 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 no...Votes: 0GitHub stars: 2
- Kotlin Coroutines Expert Capability Surface MapUse when the actual capability boundary of Kotlin coroutines and Flow needs to be distinguished from assumptions. Produce a capability map for Kotlin coroutines and Flow 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 structured task lifetime, cancellation ...Votes: 0GitHub stars: 2
- Kotlin Coroutines Expert Change Impact AssessmentUse when a proposed Kotlin coroutines and Flow version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Kotlin coroutines and Flow 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 structured task lifetime, cancellatio...Votes: 0GitHub stars: 2
- Kotlin Coroutines Expert Failure Triage RecordUse when a reproducible Kotlin coroutines and Flow symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Kotlin coroutines and Flow 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 structured task lifetime, cancellation propagation, error handling, and det...Votes: 0GitHub stars: 2
- Kotlin Coroutines Expert Input Output ContractUse when the accepted inputs or produced outputs for Kotlin coroutines and Flow need a checkable boundary. Produce an input/output contract for Kotlin coroutines and Flow 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 structured task lifetime, cancellation propagation, error handling,...Votes: 0GitHub stars: 2
- Kotlin Coroutines Expert Integration Parity TraceUse when Kotlin coroutines and Flow exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Kotlin coroutines and Flow 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 structured task lifetime, cancellation propagation, error handling, and deterministi...Votes: 0GitHub stars: 2
- Kotlin Coroutines Expert Performance EnvelopeUse when Kotlin coroutines and Flow must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Kotlin coroutines and Flow 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 structured task lifetime, cancellation propagation, error...Votes: 0GitHub stars: 2
- Kotlin Coroutines Expert Permission Boundary ReviewUse when Kotlin coroutines and Flow may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Kotlin coroutines and Flow 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 structured task lifetime, cancellation propaga...Votes: 0GitHub stars: 2
- Kotlin Coroutines Expert Release Handoff RecordUse when a Kotlin coroutines and Flow review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Kotlin coroutines and Flow 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 structured task lifetime, cancellation ...Votes: 0GitHub stars: 2
- Kotlin Coroutines Expert Reproducibility Fixture PlanUse when a Kotlin coroutines and Flow result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Kotlin coroutines and Flow 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 structured ...Votes: 0GitHub stars: 2
- Kotlin Coroutines Expert Version CompatibilityUse when a Kotlin coroutines and Flow integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Kotlin coroutines and Flow 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 structured task lifetime, cancella...Votes: 0GitHub stars: 2
- Laravel Development Workflow Capability Surface MapUse when the actual capability boundary of Laravel application workflow needs to be distinguished from assumptions. Produce a capability map for Laravel application workflow 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 framework and package versions, rou...Votes: 0GitHub stars: 2
- Laravel Development Workflow Change Impact AssessmentUse when a proposed Laravel application workflow version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Laravel application workflow 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 framework and package versions, r...Votes: 0GitHub stars: 2
- Laravel Development Workflow Failure Triage RecordUse when a reproducible Laravel application workflow symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Laravel application workflow 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 framework and package versions, route behavior, data boundaries, and re...Votes: 0GitHub stars: 2
- Laravel Development Workflow Input Output ContractUse when the accepted inputs or produced outputs for Laravel application workflow need a checkable boundary. Produce an input/output contract for Laravel application workflow 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 framework and package versions, route behavior, data boundaries...Votes: 0GitHub stars: 2
- Laravel Development Workflow Integration Parity TraceUse when Laravel application workflow exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Laravel application workflow 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 framework and package versions, route behavior, data boundaries, and repository-...Votes: 0GitHub stars: 2
- Laravel Development Workflow Performance EnvelopeUse when Laravel application workflow must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Laravel application workflow 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 framework and package versions, route behavior, data ...Votes: 0GitHub stars: 2
- Laravel Development Workflow Permission Boundary ReviewUse when Laravel application workflow may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Laravel application workflow 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 framework and package versions, route beha...Votes: 0GitHub stars: 2
- Laravel Development Workflow Release Handoff RecordUse when a Laravel application workflow review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Laravel application workflow 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 framework and package versions, rou...Votes: 0GitHub stars: 2
- Laravel Development Workflow Reproducibility Fixture PlanUse when a Laravel application workflow result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Laravel application workflow 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 framewo...Votes: 0GitHub stars: 2
- Laravel Development Workflow Version CompatibilityUse when a Laravel application workflow integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Laravel application workflow 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 framework and package versions...Votes: 0GitHub stars: 2
- Macos Dsym Build Identity MatchUse when a task involves checking that debug symbols correspond to the exact macOS binary being analyzed 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
- Macos Gatekeeper First Launch CheckUse when a task involves testing the first-launch experience of an authorized macOS distribution artifact 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
- Macos Keychain Access Group ReviewUse when a task involves reviewing which signed Apple targets can read or write a keychain access group 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
- Macos Login Item Launch Agent Lifecycle AuditUse when a task involves reviewing a macOS app's background start, update, and uninstall behavior to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Macos Screen Capture Consent And Attribution CheckUse when a task involves checking screen-recording permission and responsible-process attribution for a macOS automation test 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 a...Votes: 0GitHub stars: 2
- Macos Universal Binary Slice ValidationUse when a task involves checking architecture slices and minimum OS metadata in a macOS release binary 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
- Macos Virtual Machine Guest Host Evidence CheckUse when a task involves cross-checking a GUI test result inside a macOS VM with independent host-side evidence 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
- Macos Virtual Machine Snapshot GovernanceUse when a task involves governing snapshot creation and rollback for a task-owned macOS test virtual machine 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
- Makepad 2 0 Dsl Capability Surface MapUse when the actual capability boundary of Makepad 2.0 DSL workflows needs to be distinguished from assumptions. Produce a capability map for Makepad 2.0 DSL 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 DSL version, component ownership, layout ...Votes: 0GitHub stars: 2
- Makepad 2 0 Dsl Change Impact AssessmentUse when a proposed Makepad 2.0 DSL workflows version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Makepad 2.0 DSL 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 DSL version, component ownership, layou...Votes: 0GitHub stars: 2
- Makepad 2 0 Dsl Failure Triage RecordUse when a reproducible Makepad 2.0 DSL workflows symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Makepad 2.0 DSL 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 DSL version, component ownership, layout behavior, build output, and local re...Votes: 0GitHub stars: 2
- Makepad 2 0 Dsl Input Output ContractUse when the accepted inputs or produced outputs for Makepad 2.0 DSL workflows need a checkable boundary. Produce an input/output contract for Makepad 2.0 DSL 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 DSL version, component ownership, layout behavior, build output, and ...Votes: 0GitHub stars: 2
- Makepad 2 0 Dsl Integration Parity TraceUse when Makepad 2.0 DSL workflows exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Makepad 2.0 DSL 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 DSL version, component ownership, layout behavior, build output, and local reproductio...Votes: 0GitHub stars: 2
- Makepad 2 0 Dsl Performance EnvelopeUse when Makepad 2.0 DSL workflows must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Makepad 2.0 DSL 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 DSL version, component ownership, layout behavior, build ou...Votes: 0GitHub stars: 2
- Makepad 2 0 Dsl Permission Boundary ReviewUse when Makepad 2.0 DSL workflows may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Makepad 2.0 DSL 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 DSL version, component ownership, layout behavio...Votes: 0GitHub stars: 2
- Makepad 2 0 Dsl Release Handoff RecordUse when a Makepad 2.0 DSL workflows review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Makepad 2.0 DSL 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 DSL version, component ownership, layout ...Votes: 0GitHub stars: 2
- Makepad 2 0 Dsl Reproducibility Fixture PlanUse when a Makepad 2.0 DSL workflows result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Makepad 2.0 DSL 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 DSL version, ...Votes: 0GitHub stars: 2
- Makepad 2 0 Dsl Version CompatibilityUse when a Makepad 2.0 DSL workflows integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Makepad 2.0 DSL 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 DSL version, component ownership, la...Votes: 0GitHub stars: 2
- Memory Safety PatternsUse when a task involves reviewing systems code for memory-safety risks across allocation, ownership, bounds, lifetimes, and foreign-function interfaces 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 focu...Votes: 0GitHub stars: 2
- Nvidia Cuda Performance WorkflowUse when a task involves profiling and improving a CUDA workload with reproducible baselines and GPU-specific correctness checks 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 insta...Votes: 0GitHub stars: 2
- Programming Language DevelopmentUse when designing or implementing a programming language, interpreter, compiler, bytecode format, or language tooling to define a small grammar and observable semantics first, then validate parsing, evaluation, diagnostics, and resource limits with a conformance suite. Trigger for language syntax, type rules, compiler passes, or runtime behavior.Votes: 0GitHub stars: 2
- Pydantic Model ValidationUse when a task involves designing Pydantic models that validate external data while preserving clear serialization contracts 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 ...Votes: 0GitHub stars: 2
- Qemu Kernel Lab Experiment DesignUse when a task involves designing a reproducible kernel experiment in an isolated QEMU environment to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, dev...Votes: 0GitHub stars: 2
- Regex Engine DevelopmentUse when implementing a regular-expression parser, matcher, or regex feature set to define syntax and matching semantics explicitly, choose an execution strategy with bounded worst-case behavior, and test edge cases before accepting untrusted patterns or text. Trigger for regex engine internals, compatibility, or ReDoS-sensitive matching.Votes: 0GitHub stars: 2
- Rust Agentic Development WorkflowUse when a task involves implementing a Rust change with a research-plan-implement sequence and project-specific validation to identify the intended outcome, affected account or artifact, exact product version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive details, produce a reviewable result, and verify it against explicit criteria. Trigger for planning, configuration, implementation, or troubleshooting in this focused area; do...Votes: 0GitHub stars: 2
- Rust Performance ProfilingUse when a task involves profiling a Rust workload and testing a performance hypothesis without sacrificing correctness to identify the intended outcome, affected account or artifact, exact product version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive details, produce a reviewable result, and verify it against explicit criteria. Trigger for planning, configuration, implementation, or troubleshooting in this focused area; do not...Votes: 0GitHub stars: 2
- Rust Unsafe Ffi Safety ReviewUse when a task involves reviewing Rust unsafe blocks and foreign-function interfaces for pointer validity, ownership, layout, aliasing, and panic safety to identify the intended outcome, affected account or artifact, exact product version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive details, produce a reviewable result, and verify it against explicit criteria. Trigger for planning, configuration, implementation, or troublesho...Votes: 0GitHub stars: 2
- Shell DevelopmentUse when implementing a shell, command interpreter, or scripting runtime that parses and executes user commands to define the grammar and authority model before execution, keep parsing separate from effects, and test in a disposable environment with a minimal command set. Trigger for pipelines, redirection, expansion, job control, or shell compatibility work.Votes: 0GitHub stars: 2
- Soc Memory Map Contract ReviewUse when a task involves reviewing a memory-mapped register specification for software and RTL agreement to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial...Votes: 0GitHub stars: 2