All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Pcb Design Footprint Geometry Scope Intake GateUse when a new PCB footprint geometry review request needs a bounded work scope to produce a scoped intake card for the footprint geometry check sheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; footprint identity and geometry are traceable to the chosen component package. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three fo...Votes: 0GitHub stars: 2
- Pcb Design Footprint Geometry Source Provenance LedgerUse when a decision about PCB footprint geometry review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the footprint geometry check sheet. Success means each material claim has a source, version/date, location, and confidence note; footprint identity and geometry are traceable to the chosen component package. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, ...Votes: 0GitHub stars: 2
- Pcb Design Footprint Geometry Threshold Rule CheckUse when a PCB footprint geometry review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the footprint geometry check 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; footprint identity and geometry are traceable to the chosen component package. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Pcb Design Library Symbol Map Approval Evidence PacketUse when a component symbol and footprint mapping result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the library mapping 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; the mapping is consistent across symbol, package, and schematic netlist. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Pcb Design Library Symbol Map Change Impact TraceUse when a version, rule, source, or stakeholder change may affect component symbol and footprint mapping to produce a before/after change record and impact map for the library mapping manifest. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the mapping is consistent across symbol, package, and schematic netlist. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and...Votes: 0GitHub stars: 2
- Pcb Design Library Symbol Map Closeout Handoff LedgerUse when a component symbol and footprint mapping work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the library mapping 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; the mapping is consistent across symbol, package, and schematic netlist. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Pcb Design Library Symbol Map Completeness ReconciliationUse when the component symbol and footprint mapping workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the library mapping 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; the mapping is consistent across symbol, package, and schematic netlist. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Pcb Design Library Symbol Map Exception Triage QueueUse when the component symbol and footprint mapping workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the library mapping 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; the mapping is consistent across symbol, package, and schematic netlist. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Pcb Design Library Symbol Map Recovery Readiness DrillUse when the component symbol and footprint mapping workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the library mapping 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; the mapping is consistent across symbol, package, and schematic netlist. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Pcb Design Library Symbol Map Scenario Sensitivity MatrixUse when the component symbol and footprint mapping team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the library mapping manifest with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the mapping is consistent across symbol, package, and schematic netlist. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Pcb Design Library Symbol Map Scope Intake GateUse when a new component symbol and footprint mapping request needs a bounded work scope to produce a scoped intake card for the library mapping manifest. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the mapping is consistent across symbol, package, and schematic netlist. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focus...Votes: 0GitHub stars: 2
- Pcb Design Library Symbol Map Source Provenance LedgerUse when a decision about component symbol and footprint mapping depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the library mapping manifest. Success means each material claim has a source, version/date, location, and confidence note; the mapping is consistent across symbol, package, and schematic netlist. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, lim...Votes: 0GitHub stars: 2
- Pcb Design Library Symbol Map Threshold Rule CheckUse when a component symbol and footprint mapping decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the library mapping 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; the mapping is consistent across symbol, package, and schematic netlist. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Pcb Design Netlist Intent Approval Evidence PacketUse when a schematic and netlist intent result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the netlist-to-intent comparison 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; critical nets and pins match the approved design intent or remain flagged. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Pcb Design Netlist Intent Change Impact TraceUse when a version, rule, source, or stakeholder change may affect schematic and netlist intent to produce a before/after change record and impact map for the netlist-to-intent comparison. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; critical nets and pins match the approved design intent or remain flagged. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and aut...Votes: 0GitHub stars: 2
- Pcb Design Netlist Intent Closeout Handoff LedgerUse when a schematic and netlist intent work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the netlist-to-intent comparison 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; critical nets and pins match the approved design intent or remain flagged. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Pcb Design Netlist Intent Completeness ReconciliationUse when the schematic and netlist intent workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the netlist-to-intent comparison 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; critical nets and pins match the approved design intent or remain flagged. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Pcb Design Netlist Intent Exception Triage QueueUse when the schematic and netlist intent workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the netlist-to-intent comparison 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; critical nets and pins match the approved design intent or remain flagged. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Pcb Design Netlist Intent Recovery Readiness DrillUse when the schematic and netlist intent workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the netlist-to-intent comparison 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; critical nets and pins match the approved design intent or remain flagged. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Pcb Design Netlist Intent Scenario Sensitivity MatrixUse when the schematic and netlist intent team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the netlist-to-intent comparison with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; critical nets and pins match the approved design intent or remain flagged. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Pcb Design Netlist Intent Scope Intake GateUse when a new schematic and netlist intent request needs a bounded work scope to produce a scoped intake card for the netlist-to-intent comparison. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; critical nets and pins match the approved design intent or remain flagged. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused p...Votes: 0GitHub stars: 2
- Pcb Design Netlist Intent Source Provenance LedgerUse when a decision about schematic and netlist intent depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the netlist-to-intent comparison. Success means each material claim has a source, version/date, location, and confidence note; critical nets and pins match the approved design intent or remain flagged. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit r...Votes: 0GitHub stars: 2
- Pcb Design Netlist Intent Threshold Rule CheckUse when a schematic and netlist intent decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the netlist-to-intent comparison 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; critical nets and pins match the approved design intent or remain flagged. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Pcb Design Placement Keepout Approval Evidence PacketUse when a PCB placement and keepout review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the placement constraint map 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; each exception is measured against the controlling drawing and left for engineer disposition. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Pcb Design Placement Keepout Change Impact TraceUse when a version, rule, source, or stakeholder change may affect PCB placement and keepout review to produce a before/after change record and impact map for the placement constraint map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each exception is measured against the controlling drawing and left for engineer disposition. Use configured search, fetch, read, browser, test, and write capabilities only wh...Votes: 0GitHub stars: 2
- Pcb Design Placement Keepout Closeout Handoff LedgerUse when a PCB placement and keepout review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the placement constraint map 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; each exception is measured against the controlling drawing and left for engineer disposition. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Pcb Design Placement Keepout Completeness ReconciliationUse when the PCB placement and keepout review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the placement constraint map 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; each exception is measured against the controlling drawing and left for engineer disposition. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Pcb Design Placement Keepout Exception Triage QueueUse when the PCB placement and keepout review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the placement constraint map 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; each exception is measured against the controlling drawing and left for engineer disposition. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Pcb Design Placement Keepout Recovery Readiness DrillUse when the PCB placement and keepout review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the placement constraint map 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; each exception is measured against the controlling drawing and left for engineer disposition. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Pcb Design Placement Keepout Scenario Sensitivity MatrixUse when the PCB placement and keepout review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the placement constraint map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each exception is measured against the controlling drawing and left for engineer disposition. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Pcb Design Placement Keepout Scope Intake GateUse when a new PCB placement and keepout review request needs a bounded work scope to produce a scoped intake card for the placement constraint map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each exception is measured against the controlling drawing and left for engineer disposition. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement...Votes: 0GitHub stars: 2
- Pcb Design Placement Keepout Source Provenance LedgerUse when a decision about PCB placement and keepout review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the placement constraint map. Success means each material claim has a source, version/date, location, and confidence note; each exception is measured against the controlling drawing and left for engineer disposition. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Recor...Votes: 0GitHub stars: 2
- Pcb Design Placement Keepout Threshold Rule CheckUse when a PCB placement and keepout review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the placement constraint map 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; each exception is measured against the controlling drawing and left for engineer disposition. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Pcb Design Return Path Approval Evidence PacketUse when a PCB return-path continuity review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the return-path review ledger 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; review notes identify evidence-backed discontinuities without asserting unmeasured signal integrity. Use configured search...Votes: 0GitHub stars: 2
- Pcb Design Return Path Change Impact TraceUse when a version, rule, source, or stakeholder change may affect PCB return-path continuity review to produce a before/after change record and impact map for the return-path review ledger. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; review notes identify evidence-backed discontinuities without asserting unmeasured signal integrity. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Pcb Design Return Path Closeout Handoff LedgerUse when a PCB return-path continuity review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the return-path review ledger 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; review notes identify evidence-backed discontinuities without asserting unmeasured signal integrity. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Pcb Design Return Path Completeness ReconciliationUse when the PCB return-path continuity review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the return-path review ledger 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; review notes identify evidence-backed discontinuities without asserting unmeasured signal integrity. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Pcb Design Return Path Exception Triage QueueUse when the PCB return-path continuity review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the return-path review ledger 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; review notes identify evidence-backed discontinuities without asserting unmeasured signal integrity. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Pcb Design Return Path Recovery Readiness DrillUse when the PCB return-path continuity review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the return-path review ledger 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; review notes identify evidence-backed discontinuities without asserting unmeasured signal integrity. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Pcb Design Return Path Scenario Sensitivity MatrixUse when the PCB return-path continuity review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the return-path review ledger with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; review notes identify evidence-backed discontinuities without asserting unmeasured signal integrity. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Pcb Design Return Path Scope Intake GateUse when a new PCB return-path continuity review request needs a bounded work scope to produce a scoped intake card for the return-path review ledger. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; review notes identify evidence-backed discontinuities without asserting unmeasured signal integrity. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit r...Votes: 0GitHub stars: 2
- Pcb Design Return Path Source Provenance LedgerUse when a decision about PCB return-path continuity review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the return-path review ledger. Success means each material claim has a source, version/date, location, and confidence note; review notes identify evidence-backed discontinuities without asserting unmeasured signal integrity. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authoriz...Votes: 0GitHub stars: 2
- Pcb Design Return Path Threshold Rule CheckUse when a PCB return-path continuity review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the return-path review ledger 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; review notes identify evidence-backed discontinuities without asserting unmeasured signal integrity. Use configured search, f...Votes: 0GitHub stars: 2
- Pcb Design Rule Exception Approval Evidence PacketUse when a PCB design-rule exception governance result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the rule-exception disposition list 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; each exception is tied to the current revision and no warning is suppressed without approval. Use configured sear...Votes: 0GitHub stars: 2
- Pcb Design Rule Exception Change Impact TraceUse when a version, rule, source, or stakeholder change may affect PCB design-rule exception governance to produce a before/after change record and impact map for the rule-exception disposition list. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each exception is tied to the current revision and no warning is suppressed without approval. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Pcb Design Rule Exception Closeout Handoff LedgerUse when a PCB design-rule exception governance work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the rule-exception disposition list 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; each exception is tied to the current revision and no warning is suppressed without approval. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Pcb Design Rule Exception Completeness ReconciliationUse when the PCB design-rule exception governance workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the rule-exception disposition list 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; each exception is tied to the current revision and no warning is suppressed without approval. Use configured search, fetch...Votes: 0GitHub stars: 2
- Pcb Design Rule Exception Exception Triage QueueUse when the PCB design-rule exception governance workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the rule-exception disposition list 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; each exception is tied to the current revision and no warning is suppressed without approval. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Pcb Design Rule Exception Recovery Readiness DrillUse when the PCB design-rule exception governance workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the rule-exception disposition list 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; each exception is tied to the current revision and no warning is suppressed without approval. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Pcb Design Rule Exception Scenario Sensitivity MatrixUse when the PCB design-rule exception governance team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the rule-exception disposition list with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each exception is tied to the current revision and no warning is suppressed without approval. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2