All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Swift Actor Isolation Boundary AuditUse when a task involves mapping actor-isolated mutable state and its callers in a Swift codebase 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
- Swift Actor Reentrancy Invariant AnalysisUse when a task involves checking state invariants when an actor method suspends and later resumes 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
- Swift Async Sequence Buffer Backpressure PlanUse when a task involves choosing buffering and producer behavior for a high-volume asynchronous sequence 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
- Swift Async Stream Termination ReviewUse when a task involves reviewing producer ownership, finish behavior, and cleanup for an AsyncStream 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
- Swift Async Timeout Cancellation DesignUse when a task involves designing timeout behavior that cancels and joins asynchronous work safely 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
- Swift Await Suspension Point State AuditUse when a task involves checking whether local state remains valid across Swift await suspension points 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
- Swift Callback To Async Interop Migration ReviewUse when a task involves reviewing an incremental migration from completion handlers to async APIs 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
- Swift Concurrency Diagnostics TriageUse when a task involves classifying compiler diagnostics related to isolation, Sendable, and concurrency mode 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
- Swift Concurrency Runtime Compatibility MatrixUse when a task involves checking concurrency language and runtime assumptions across supported build targets 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
- Swift Concurrency Sanitizer Evidence ReviewUse when a task involves interpreting race-detector and concurrency-checking evidence for a Swift target 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
- Swift Continuation Single Resume AuditUse when a task involves checking exactly-once completion when bridging callback APIs with continuations 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
- Swift Detached Task Justification ReviewUse when a task involves reviewing whether Task.detached is necessary for a specific Swift operation 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
- Swift Main Actor Hop Responsiveness ReviewUse when a task involves reviewing main-actor work and hops that may delay UI responsiveness 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
- Swift Sendable Conformance Safety ReviewUse when a task involves reviewing whether Swift values can safely cross concurrency domains 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
- Swift Signpost Hitch CorrelationUse when a task involves correlating app-defined signposts with UI hitches and user actions in an Instruments trace 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
- Swift Strict Concurrency Migration Cohort PlanUse when a task involves planning a staged move toward stricter Swift concurrency checking 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
- Swift Task Group Fanout Budget ReviewUse when a task involves setting a bounded concurrency policy for dynamically sized Swift task groups 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
- Swift Task Group Partial Failure PolicyUse when a task involves defining results and cancellation semantics when one child in a Swift task group fails 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
- Swift Task Lifecycle Ownership AuditUse when a task involves finding Swift tasks whose lifetime is not owned by a view, service, or operation 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
- Swift Task Local Context Sensitivity AuditUse when a task involves reviewing what task-local metadata propagates into asynchronous child work 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
- Swift Task Priority Inversion InvestigationUse when a task involves investigating latency caused by task priorities, actor queues, or synchronous waits 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
- Swift Unsafe Sendable Exception RecordUse when a task involves documenting a narrowly justified unchecked Sendable conformance 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
- Template Engine DevelopmentUse when creating or modifying a template parser, renderer, layout system, or embedded expression language to define syntax and output context, escape untrusted values by default, and avoid executing template content as host code. Trigger for interpolation, includes, inheritance, filters, or compiled templates.Votes: 0GitHub stars: 2
- Typescript Advanced PatternsUse when a task involves using advanced TypeScript types or language features when they improve a concrete API or correctness boundary 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...Votes: 0GitHub stars: 2
- Versioned Library Documentation ResearchUse when an answer or implementation depends on current behavior of a named library, framework, SDK, or API to resolve the exact project and version, consult primary documentation, verify examples against the installed dependency where possible, and cite the relevant source. Trigger for setup, configuration, API usage, migrations, or version-sensitive code.Votes: 0GitHub stars: 2
- Voxel Engine DevelopmentUse when building a voxel renderer, terrain system, chunk store, or voxel-world interaction to define world coordinates, chunk dimensions, block representation, generation rules, and resource budgets before optimizing mesh or streaming behavior. Trigger for block-based worlds, voxel meshing, terrain, or chunk persistence.Votes: 0GitHub stars: 2
- Xcode App Launch Phase BudgetUse when a task involves breaking app launch time into attributable stages for an Apple application 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
- Xcode Archive Reproducibility CheckUse when a task involves checking whether repeated Xcode archives differ for a controlled source revision 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
- Xcode Build Configuration Parity ReviewUse when a task involves checking differences between Debug, Release, and CI build settings for an Apple target 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
- Xcode Build Log Failure Phase IsolationUse when a task involves finding the first causal failure in a long Xcode build or archive log 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
- Xcode Derived Data Cache IsolationUse when a task involves diagnosing stale or cross-target build artifacts in DerivedData 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
- Xcode Export Options Profile ValidationUse when a task involves checking export settings and provisioning profile compatibility for an Apple archive 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
- Xcode Result Bundle Diagnostic TriageUse when a task involves extracting actionable evidence from an Xcode xcresult bundle 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
- Xcode Simulator Runtime Compatibility CheckUse when a task involves checking that a required simulator runtime is installed and compatible with a test target 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
- Xcodebuild Destination Pinning ReviewUse when a task involves making an Xcode test or build select the intended destination reproducibly 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
- Aas Devtools Quickstart Parity Approval Evidence PacketUse when a developer quickstart executable parity result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the quickstart-to-release parity check 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 listed sequence works in a clean sandbox or every blocker is attributed. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Aas Devtools Quickstart Parity Change Impact TraceUse when a version, rule, source, or stakeholder change may affect developer quickstart executable parity to produce a before/after change record and impact map for the quickstart-to-release parity check. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the listed sequence works in a clean sandbox or every blocker is attributed. Use configured search, fetch, read, browser, test, and write capabilities only whe...Votes: 0GitHub stars: 2
- Aas Devtools Quickstart Parity Closeout Handoff LedgerUse when a developer quickstart executable parity work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the quickstart-to-release parity check 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 listed sequence works in a clean sandbox or every blocker is attributed. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Aas Devtools Quickstart Parity Completeness ReconciliationUse when the developer quickstart executable parity workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the quickstart-to-release parity check 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 listed sequence works in a clean sandbox or every blocker is attributed. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Devtools Quickstart Parity Exception Triage QueueUse when the developer quickstart executable parity workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the quickstart-to-release parity check 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 listed sequence works in a clean sandbox or every blocker is attributed. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Aas Devtools Quickstart Parity Recovery Readiness DrillUse when the developer quickstart executable parity workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the quickstart-to-release parity check 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 listed sequence works in a clean sandbox or every blocker is attributed. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Aas Devtools Quickstart Parity Scenario Sensitivity MatrixUse when the developer quickstart executable parity team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the quickstart-to-release parity check with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the listed sequence works in a clean sandbox or every blocker is attributed. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Aas Devtools Quickstart Parity Scope Intake GateUse when a new developer quickstart executable parity request needs a bounded work scope to produce a scoped intake card for the quickstart-to-release parity check. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the listed sequence works in a clean sandbox or every blocker is attributed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement ...Votes: 0GitHub stars: 2
- Aas Devtools Quickstart Parity Source Provenance LedgerUse when a decision about developer quickstart executable parity depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the quickstart-to-release parity check. Success means each material claim has a source, version/date, location, and confidence note; the listed sequence works in a clean sandbox or every blocker is attributed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record...Votes: 0GitHub stars: 2
- Aas Devtools Quickstart Parity Threshold Rule CheckUse when a developer quickstart executable parity decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the quickstart-to-release parity check 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 listed sequence works in a clean sandbox or every blocker is attributed. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Aas Mobile App Size Budget Approval Evidence PacketUse when a mobile application size budget result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the application size regression report 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 size change is attributed to components and stays within an approved budget. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Aas Mobile App Size Budget Change Impact TraceUse when a version, rule, source, or stakeholder change may affect mobile application size budget to produce a before/after change record and impact map for the application size regression report. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the size change is attributed to components and stays within an approved budget. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Aas Mobile App Size Budget Closeout Handoff LedgerUse when a mobile application size budget work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the application size regression report 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 size change is attributed to components and stays within an approved budget. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Aas Mobile App Size Budget Completeness ReconciliationUse when the mobile application size budget workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the application size regression report 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 size change is attributed to components and stays within an approved budget. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Aas Mobile App Size Budget Exception Triage QueueUse when the mobile application size budget workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the application size regression report 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 size change is attributed to components and stays within an approved budget. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2