All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Blenderlab Uv And Texture Workflows Render Budgets Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Blender and 3D production: UV and texture workflows for render budgets. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Record Blender/file version and make a checkpoint before migration; verify the reopened file and key outputs after change. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned input...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Render Budgets Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Blender and 3D production: UV and texture workflows for render budgets. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Record Blender/file version and make a checkpoint before migration; verify the reopened file and key outputs after change. Success means the review names relevant hazards, permissions, contr...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Render Budgets Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Blender and 3D production: UV and texture workflows for render budgets. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Record Blender/file version and make a checkpoint before migration; verify the reopened file and key outputs after change. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, ...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Render Budgets Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Blender and 3D production: UV and texture workflows for render budgets. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Record Blender/file version and make a checkpoint before migration; verify the reopened file and key outputs after change. Success means each critical requirement maps to a reproducible check a...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Scene Versioning Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Blender and 3D production: UV and texture workflows for scene versioning. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Validate import units, transforms, normals, material assignments, and asset rights before merging CAD geometry. Success means the prepared result is reproducible, reviewable, and within the approved scope...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Scene Versioning Design BlueprintUse when a solution needs a coherent structure before implementation or production for Blender and 3D production: UV and texture workflows for scene versioning. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Validate import units, transforms, normals, material assignments, and asset rights before merging CAD geometry. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned ...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Scene Versioning Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Blender and 3D production: UV and texture workflows for scene versioning. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Validate import units, transforms, normals, material assignments, and asset rights before merging CAD geometry. Success means the failure is bounded by observations, one testable hypothesis, and a...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Scene Versioning Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Blender and 3D production: UV and texture workflows for scene versioning. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Validate import units, transforms, normals, material assignments, and asset rights before merging CAD geometry. Success means the proposed change is compared with a baseline, regre...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Scene Versioning Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Blender and 3D production: UV and texture workflows for scene versioning. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Validate import units, transforms, normals, material assignments, and asset rights before merging CAD geometry. Success means options are compared on user-approved criteria with uncertainty and trade-offs show...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Scene Versioning Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Blender and 3D production: UV and texture workflows for scene versioning. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Validate import units, transforms, normals, material assignments, and asset rights before merging CAD geometry. Success means requirements have priorities, evidence, owners, and measurable acceptance condit...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Scene Versioning Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Blender and 3D production: UV and texture workflows for scene versioning. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Validate import units, transforms, normals, material assignments, and asset rights before merging CAD geometry. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, preser...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Scene Versioning Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Blender and 3D production: UV and texture workflows for scene versioning. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Validate import units, transforms, normals, material assignments, and asset rights before merging CAD geometry. Success means the review names relevant hazards, permissions, controls, evid...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Scene Versioning Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Blender and 3D production: UV and texture workflows for scene versioning. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Validate import units, transforms, normals, material assignments, and asset rights before merging CAD geometry. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, preserve ...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Scene Versioning Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Blender and 3D production: UV and texture workflows for scene versioning. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Validate import units, transforms, normals, material assignments, and asset rights before merging CAD geometry. Success means each critical requirement maps to a reproducible check and a trut...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Stylized Characters Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Blender and 3D production: UV and texture workflows for stylized characters. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Verify UV islands, texel coverage, texture dimensions, and seam placement against the target asset constraints. Success means the prepared result is reproducible, reviewable, and within the approved sc...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Stylized Characters Design BlueprintUse when a solution needs a coherent structure before implementation or production for Blender and 3D production: UV and texture workflows for stylized characters. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Verify UV islands, texel coverage, texture dimensions, and seam placement against the target asset constraints. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permission...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Stylized Characters Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Blender and 3D production: UV and texture workflows for stylized characters. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Verify UV islands, texel coverage, texture dimensions, and seam placement against the target asset constraints. Success means the failure is bounded by observations, one testable hypothesis, an...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Stylized Characters Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Blender and 3D production: UV and texture workflows for stylized characters. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Verify UV islands, texel coverage, texture dimensions, and seam placement against the target asset constraints. Success means the proposed change is compared with a baseline, re...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Stylized Characters Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Blender and 3D production: UV and texture workflows for stylized characters. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Verify UV islands, texel coverage, texture dimensions, and seam placement against the target asset constraints. Success means options are compared on user-approved criteria with uncertainty and trade-offs s...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Stylized Characters Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Blender and 3D production: UV and texture workflows for stylized characters. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Verify UV islands, texel coverage, texture dimensions, and seam placement against the target asset constraints. Success means requirements have priorities, evidence, owners, and measurable acceptance con...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Stylized Characters Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Blender and 3D production: UV and texture workflows for stylized characters. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Verify UV islands, texel coverage, texture dimensions, and seam placement against the target asset constraints. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, pre...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Stylized Characters Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Blender and 3D production: UV and texture workflows for stylized characters. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Verify UV islands, texel coverage, texture dimensions, and seam placement against the target asset constraints. Success means the review names relevant hazards, permissions, controls, e...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Stylized Characters Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Blender and 3D production: UV and texture workflows for stylized characters. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Verify UV islands, texel coverage, texture dimensions, and seam placement against the target asset constraints. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, preser...Votes: 0GitHub stars: 2
- Blenderlab Uv And Texture Workflows Stylized Characters Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Blender and 3D production: UV and texture workflows for stylized characters. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Verify UV islands, texel coverage, texture dimensions, and seam placement against the target asset constraints. Success means each critical requirement maps to a reproducible check and a t...Votes: 0GitHub stars: 2
- Aas Game Asset Bundle Approval Evidence PacketUse when a game asset bundle dependency mapping result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the asset-bundle dependency manifest 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; every required runtime asset resolves and unused or duplicate bundle weight is attributable. Use configured sear...Votes: 0GitHub stars: 2
- Aas Game Asset Bundle Change Impact TraceUse when a version, rule, source, or stakeholder change may affect game asset bundle dependency mapping to produce a before/after change record and impact map for the asset-bundle dependency manifest. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every required runtime asset resolves and unused or duplicate bundle weight is attributable. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Aas Game Asset Bundle Closeout Handoff LedgerUse when a game asset bundle dependency mapping work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the asset-bundle dependency manifest 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; every required runtime asset resolves and unused or duplicate bundle weight is attributable. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Aas Game Asset Bundle Completeness ReconciliationUse when the game asset bundle dependency mapping workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the asset-bundle dependency manifest 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; every required runtime asset resolves and unused or duplicate bundle weight is attributable. Use configured search, fetch...Votes: 0GitHub stars: 2
- Aas Game Asset Bundle Exception Triage QueueUse when the game asset bundle dependency mapping workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the asset-bundle dependency manifest 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; every required runtime asset resolves and unused or duplicate bundle weight is attributable. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Game Asset Bundle Recovery Readiness DrillUse when the game asset bundle dependency mapping workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the asset-bundle dependency manifest 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; every required runtime asset resolves and unused or duplicate bundle weight is attributable. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Aas Game Asset Bundle Scenario Sensitivity MatrixUse when the game asset bundle dependency mapping team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the asset-bundle dependency manifest with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every required runtime asset resolves and unused or duplicate bundle weight is attributable. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Aas Game Asset Bundle Scope Intake GateUse when a new game asset bundle dependency mapping request needs a bounded work scope to produce a scoped intake card for the asset-bundle dependency manifest. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every required runtime asset resolves and unused or duplicate bundle weight is attributable. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit...Votes: 0GitHub stars: 2
- Aas Game Asset Bundle Source Provenance LedgerUse when a decision about game asset bundle dependency mapping depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the asset-bundle dependency manifest. Success means each material claim has a source, version/date, location, and confidence note; every required runtime asset resolves and unused or duplicate bundle weight is attributable. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and author...Votes: 0GitHub stars: 2
- Aas Game Asset Bundle Threshold Rule CheckUse when a game asset bundle dependency mapping decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the asset-bundle dependency manifest 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; every required runtime asset resolves and unused or duplicate bundle weight is attributable. Use configured search,...Votes: 0GitHub stars: 2
- Aas Game Input Remapping Approval Evidence PacketUse when a game input remapping accessibility result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the input-remapping acceptance sheet containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; required actions remain reachable after remapping and conflicts are surfaced. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Aas Game Input Remapping Change Impact TraceUse when a version, rule, source, or stakeholder change may affect game input remapping accessibility to produce a before/after change record and impact map for the input-remapping acceptance sheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; required actions remain reachable after remapping and conflicts are surfaced. Use configured search, fetch, read, browser, test, and write capabilities only when rel...Votes: 0GitHub stars: 2
- Aas Game Input Remapping Closeout Handoff LedgerUse when a game input remapping accessibility work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the input-remapping acceptance sheet with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; required actions remain reachable after remapping and conflicts are surfaced. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Aas Game Input Remapping Completeness ReconciliationUse when the game input remapping accessibility workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the input-remapping acceptance sheet with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; required actions remain reachable after remapping and conflicts are surfaced. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Aas Game Input Remapping Exception Triage QueueUse when the game input remapping accessibility workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the input-remapping acceptance sheet with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; required actions remain reachable after remapping and conflicts are surfaced. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Aas Game Input Remapping Recovery Readiness DrillUse when the game input remapping accessibility workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the input-remapping acceptance sheet with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; required actions remain reachable after remapping and conflicts are surfaced. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Aas Game Input Remapping Scenario Sensitivity MatrixUse when the game input remapping accessibility team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the input-remapping acceptance sheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; required actions remain reachable after remapping and conflicts are surfaced. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Aas Game Input Remapping Scope Intake GateUse when a new game input remapping accessibility request needs a bounded work scope to produce a scoped intake card for the input-remapping acceptance sheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; required actions remain reachable after remapping and conflicts are surfaced. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to th...Votes: 0GitHub stars: 2
- Aas Game Input Remapping Source Provenance LedgerUse when a decision about game input remapping accessibility depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the input-remapping acceptance sheet. Success means each material claim has a source, version/date, location, and confidence note; required actions remain reachable after remapping and conflicts are surfaced. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evid...Votes: 0GitHub stars: 2
- Aas Game Input Remapping Threshold Rule CheckUse when a game input remapping accessibility decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the input-remapping acceptance sheet showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; required actions remain reachable after remapping and conflicts are surfaced. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Game Multiplayer Desync Approval Evidence PacketUse when a multiplayer desynchronization reproduction result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the desync reproduction packet 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 divergence is bounded to a reproducible interval without exposing live player data. Use configured search, f...Votes: 0GitHub stars: 2
- Aas Game Multiplayer Desync Change Impact TraceUse when a version, rule, source, or stakeholder change may affect multiplayer desynchronization reproduction to produce a before/after change record and impact map for the desync reproduction packet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the divergence is bounded to a reproducible interval without exposing live player data. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Aas Game Multiplayer Desync Closeout Handoff LedgerUse when a multiplayer desynchronization reproduction work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the desync reproduction packet 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 divergence is bounded to a reproducible interval without exposing live player data. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Aas Game Multiplayer Desync Completeness ReconciliationUse when the multiplayer desynchronization reproduction workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the desync reproduction packet 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 divergence is bounded to a reproducible interval without exposing live player data. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Aas Game Multiplayer Desync Exception Triage QueueUse when the multiplayer desynchronization reproduction workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the desync reproduction packet 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 divergence is bounded to a reproducible interval without exposing live player data. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Game Multiplayer Desync Recovery Readiness DrillUse when the multiplayer desynchronization reproduction workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the desync reproduction packet 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 divergence is bounded to a reproducible interval without exposing live player data. Use configured search, fetch, read,...Votes: 0GitHub stars: 2