All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Codelab Typescript Services Module Boundaries Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Software implementation and code architecture: TypeScript services for module boundaries. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Record the pre-change behavior and baseline tests before modifying a legacy module; preserve uncovered behavior as an explicit risk. Success means requirements have priorities, evidence, own...Votes: 0GitHub stars: 2
- Codelab Typescript Services Module Boundaries Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Software implementation and code architecture: TypeScript services for module boundaries. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Record the pre-change behavior and baseline tests before modifying a legacy module; preserve uncovered behavior as an explicit risk. Success means the owner, constraints, baseline, and acceptance signal are expl...Votes: 0GitHub stars: 2
- Codelab Typescript Services Module Boundaries Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Software implementation and code architecture: TypeScript services for module boundaries. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Record the pre-change behavior and baseline tests before modifying a legacy module; preserve uncovered behavior as an explicit risk. Success means the review names relevant...Votes: 0GitHub stars: 2
- Codelab Typescript Services Module Boundaries Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Software implementation and code architecture: TypeScript services for module boundaries. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Record the pre-change behavior and baseline tests before modifying a legacy module; preserve uncovered behavior as an explicit risk. Success means material claims are linked to current primary sources with dates and limitation...Votes: 0GitHub stars: 2
- Codelab Typescript Services Module Boundaries Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Software implementation and code architecture: TypeScript services for module boundaries. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Record the pre-change behavior and baseline tests before modifying a legacy module; preserve uncovered behavior as an explicit risk. Success means each critical requirement ma...Votes: 0GitHub stars: 2
- Codelab Typescript Services Performance Budgets Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Software implementation and code architecture: TypeScript services for performance budgets. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Use boundary, malformed, empty, large, and privacy-sensitive fixtures without exposing real customer data. Success means the prepared result is reproducible, reviewable, and within the a...Votes: 0GitHub stars: 2
- Codelab Typescript Services Performance Budgets Design BlueprintUse when a solution needs a coherent structure before implementation or production for Software implementation and code architecture: TypeScript services for performance budgets. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Use boundary, malformed, empty, large, and privacy-sensitive fixtures without exposing real customer data. Success means interfaces, dependencies, constraints, and review points are testable before build. Use ...Votes: 0GitHub stars: 2
- Codelab Typescript Services Performance Budgets Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Software implementation and code architecture: TypeScript services for performance budgets. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Use boundary, malformed, empty, large, and privacy-sensitive fixtures without exposing real customer data. Success means the failure is bounded by observations, one testable hypo...Votes: 0GitHub stars: 2
- Codelab Typescript Services Performance Budgets Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Software implementation and code architecture: TypeScript services for performance budgets. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Use boundary, malformed, empty, large, and privacy-sensitive fixtures without exposing real customer data. Success means the proposed change is compared with a ba...Votes: 0GitHub stars: 2
- Codelab Typescript Services Performance Budgets Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Software implementation and code architecture: TypeScript services for performance budgets. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Use boundary, malformed, empty, large, and privacy-sensitive fixtures without exposing real customer data. Success means options are compared on user-approved criteria with uncertainty and tr...Votes: 0GitHub stars: 2
- Codelab Typescript Services Performance Budgets Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Software implementation and code architecture: TypeScript services for performance budgets. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Use boundary, malformed, empty, large, and privacy-sensitive fixtures without exposing real customer data. Success means requirements have priorities, evidence, owners, and measurable acce...Votes: 0GitHub stars: 2
- Codelab Typescript Services Performance Budgets Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Software implementation and code architecture: TypeScript services for performance budgets. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Use boundary, malformed, empty, large, and privacy-sensitive fixtures without exposing real customer data. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned i...Votes: 0GitHub stars: 2
- Codelab Typescript Services Performance Budgets Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Software implementation and code architecture: TypeScript services for performance budgets. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Use boundary, malformed, empty, large, and privacy-sensitive fixtures without exposing real customer data. Success means the review names relevant hazards, permissions, c...Votes: 0GitHub stars: 2
- Codelab Typescript Services Performance Budgets Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Software implementation and code architecture: TypeScript services for performance budgets. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Use boundary, malformed, empty, large, and privacy-sensitive fixtures without exposing real customer data. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inpu...Votes: 0GitHub stars: 2
- Codelab Typescript Services Performance Budgets Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Software implementation and code architecture: TypeScript services for performance budgets. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Use boundary, malformed, empty, large, and privacy-sensitive fixtures without exposing real customer data. Success means each critical requirement maps to a reproducible che...Votes: 0GitHub stars: 2
- Aas Mobile Offline Sync Approval Evidence PacketUse when a offline mobile synchronization result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the offline synchronization scenario 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; queued changes reconcile deterministically or remain visible for user resolution. Use configured search, fetch,...Votes: 0GitHub stars: 2
- Aas Mobile Offline Sync Change Impact TraceUse when a version, rule, source, or stakeholder change may affect offline mobile synchronization to produce a before/after change record and impact map for the offline synchronization scenario record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; queued changes reconcile deterministically or remain visible for user resolution. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Aas Mobile Offline Sync Closeout Handoff LedgerUse when a offline mobile synchronization work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the offline synchronization scenario 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; queued changes reconcile deterministically or remain visible for user resolution. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Mobile Offline Sync Completeness ReconciliationUse when the offline mobile synchronization workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the offline synchronization scenario 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; queued changes reconcile deterministically or remain visible for user resolution. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Aas Mobile Offline Sync Exception Triage QueueUse when the offline mobile synchronization workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the offline synchronization scenario 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; queued changes reconcile deterministically or remain visible for user resolution. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Aas Mobile Offline Sync Recovery Readiness DrillUse when the offline mobile synchronization workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the offline synchronization scenario 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; queued changes reconcile deterministically or remain visible for user resolution. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Mobile Offline Sync Scenario Sensitivity MatrixUse when the offline mobile synchronization team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the offline synchronization scenario record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; queued changes reconcile deterministically or remain visible for user resolution. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Aas Mobile Offline Sync Scope Intake GateUse when a new offline mobile synchronization request needs a bounded work scope to produce a scoped intake card for the offline synchronization scenario record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; queued changes reconcile deterministically or remain visible for user resolution. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinemen...Votes: 0GitHub stars: 2
- Aas Mobile Offline Sync Source Provenance LedgerUse when a decision about offline mobile synchronization depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the offline synchronization scenario record. Success means each material claim has a source, version/date, location, and confidence note; queued changes reconcile deterministically or remain visible for user resolution. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Reco...Votes: 0GitHub stars: 2
- Aas Mobile Offline Sync Threshold Rule CheckUse when a offline mobile synchronization decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the offline synchronization scenario 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; queued changes reconcile deterministically or remain visible for user resolution. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Aas Mobile Release Cohort Approval Evidence PacketUse when a mobile staged release cohort readiness result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the staged-release cohort plan containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; the plan has observable stop thresholds and does not publish or expand the cohort. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Aas Mobile Release Cohort Change Impact TraceUse when a version, rule, source, or stakeholder change may affect mobile staged release cohort readiness to produce a before/after change record and impact map for the staged-release cohort plan. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the plan has observable stop thresholds and does not publish or expand the cohort. Use configured search, fetch, read, browser, test, and write capabilities only when ...Votes: 0GitHub stars: 2
- Aas Mobile Release Cohort Closeout Handoff LedgerUse when a mobile staged release cohort readiness work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the staged-release cohort plan with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; the plan has observable stop thresholds and does not publish or expand the cohort. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Aas Mobile Release Cohort Completeness ReconciliationUse when the mobile staged release cohort readiness workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the staged-release cohort plan with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; the plan has observable stop thresholds and does not publish or expand the cohort. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Aas Mobile Release Cohort Exception Triage QueueUse when the mobile staged release cohort readiness workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the staged-release cohort plan with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; the plan has observable stop thresholds and does not publish or expand the cohort. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Aas Mobile Release Cohort Recovery Readiness DrillUse when the mobile staged release cohort readiness workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the staged-release cohort plan with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; the plan has observable stop thresholds and does not publish or expand the cohort. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Aas Mobile Release Cohort Scenario Sensitivity MatrixUse when the mobile staged release cohort readiness team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the staged-release cohort plan with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the plan has observable stop thresholds and does not publish or expand the cohort. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Aas Mobile Release Cohort Scope Intake GateUse when a new mobile staged release cohort readiness request needs a bounded work scope to produce a scoped intake card for the staged-release cohort plan. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the plan has observable stop thresholds and does not publish or expand the cohort. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to...Votes: 0GitHub stars: 2
- Aas Mobile Release Cohort Source Provenance LedgerUse when a decision about mobile staged release cohort readiness depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the staged-release cohort plan. Success means each material claim has a source, version/date, location, and confidence note; the plan has observable stop thresholds and does not publish or expand the cohort. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record e...Votes: 0GitHub stars: 2
- Aas Mobile Release Cohort Threshold Rule CheckUse when a mobile staged release cohort readiness decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the staged-release cohort plan showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; the plan has observable stop thresholds and does not publish or expand the cohort. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Batch FilesUse when a task involves writing or debugging Windows batch files that automate a bounded local workflow to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not install or run third-party co...Votes: 0GitHub stars: 2
- Bevy Ecs Expert Capability Surface MapUse when the actual capability boundary of Bevy ECS architecture needs to be distinguished from assumptions. Produce a capability map for Bevy ECS architecture 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 entity/component ownership, system scheduling, re...Votes: 0GitHub stars: 2
- Bevy Ecs Expert Change Impact AssessmentUse when a proposed Bevy ECS architecture version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Bevy ECS architecture 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 entity/component ownership, system scheduling, ...Votes: 0GitHub stars: 2
- Bevy Ecs Expert Failure Triage RecordUse when a reproducible Bevy ECS architecture symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Bevy ECS architecture 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 entity/component ownership, system scheduling, resource access, and deterministic beh...Votes: 0GitHub stars: 2
- Bevy Ecs Expert Input Output ContractUse when the accepted inputs or produced outputs for Bevy ECS architecture need a checkable boundary. Produce an input/output contract for Bevy ECS architecture 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 entity/component ownership, system scheduling, resource access, and determini...Votes: 0GitHub stars: 2
- Bevy Ecs Expert Integration Parity TraceUse when Bevy ECS architecture exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Bevy ECS 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 entity/component ownership, system scheduling, resource access, and deterministic behavior. Us...Votes: 0GitHub stars: 2
- Bevy Ecs Expert Performance EnvelopeUse when Bevy ECS architecture must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Bevy ECS 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 entity/component ownership, system scheduling, resource access, and...Votes: 0GitHub stars: 2
- Bevy Ecs Expert Permission Boundary ReviewUse when Bevy ECS architecture may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Bevy ECS 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 entity/component ownership, system scheduling, resource ...Votes: 0GitHub stars: 2
- Bevy Ecs Expert Release Handoff RecordUse when a Bevy ECS architecture review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Bevy ECS 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 entity/component ownership, system scheduling, re...Votes: 0GitHub stars: 2
- Bevy Ecs Expert Reproducibility Fixture PlanUse when a Bevy ECS architecture result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Bevy ECS 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 bounded to entity/component owne...Votes: 0GitHub stars: 2
- Bevy Ecs Expert Version CompatibilityUse when a Bevy ECS architecture integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Bevy ECS 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 entity/component ownership, system schedulin...Votes: 0GitHub stars: 2
- Cuda Kernel Correctness ReviewUse when a task involves reviewing a CUDA kernel change for indexing, synchronization, memory safety, numerical behavior, and device compatibility to identify the research or operational question, target population or system, relevant version, sensitive data, and approval boundary before acting. Use current primary sources, produce a traceable artifact, and verify it against explicit criteria. Trigger for planning, analysis, review, or troubleshooting in this focused domain; do not execute ex...Votes: 0GitHub stars: 2
- Cuda Memory Transfer ProfilingUse when a task involves profiling host-device data movement and synchronization in a CUDA workload to identify the research or operational question, target population or system, relevant version, sensitive data, and approval boundary before acting. Use current primary sources, produce a traceable artifact, and verify it against explicit criteria. Trigger for planning, analysis, review, or troubleshooting in this focused domain; do not execute external writes or clinical actions without autho...Votes: 0GitHub stars: 2
- Emulator And Virtual Machine DevelopmentUse when implementing an emulator, virtual machine, instruction interpreter, device model, or guest execution environment to choose a documented ISA and bounded machine model, then validate instruction semantics and isolation before running guest programs. Trigger for CPU emulation, bytecode execution, virtual devices, or VM snapshots.Votes: 0GitHub stars: 2
- Golang Code StyleUse when a task involves reviewing or writing Go code to match idiomatic project conventions and current Go tooling to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not install or run thi...Votes: 0GitHub stars: 2