All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Swiftui Body Computation Cost AuditUse when a task involves finding expensive synchronous work performed while SwiftUI computes view bodies 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
- Swiftui Dynamic Type Text Truncation AuditUse when a task involves checking text readability and truncation at supported accessibility text sizes 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
- Swiftui Expensive Formatting Cache ReviewUse when a task involves reviewing repeated formatter or derived-value work during SwiftUI rendering 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
- Swiftui Geometry Proxy Dependency MinimizationUse when a task involves reviewing broad geometry dependencies that cause avoidable SwiftUI recalculation 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
- Swiftui Hitch Vs App Hang ClassificationUse when a task involves distinguishing dropped frames from a blocked main thread in a SwiftUI report 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
- Swiftui Image Decode Memory BudgetUse when a task involves controlling image decode size and peak memory on a SwiftUI screen 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
- Swiftui Large Collection Stack Profile PlanUse when a task involves profiling a SwiftUI screen that renders a large number of repeated views 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
- Swiftui Layout Feedback Loop DiagnosisUse when a task involves investigating repeated layout passes or unstable geometry in a SwiftUI view tree 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
- Swiftui Lazy Stack Benefit GateUse when a task involves deciding whether a SwiftUI lazy stack improves a measured workload 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
- Swiftui List Identity Stability CheckUse when a task involves checking stable identity for repeated SwiftUI rows and collection updates 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
- Swiftui Main Thread Hang Trace ReviewUse when a task involves triaging a frozen or unresponsive SwiftUI interaction using a 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
- Swiftui Multiplatform Layout Adaptation ReviewUse when a task involves reviewing a SwiftUI layout across iPhone, iPad, and macOS window conditions 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
- Swiftui Multiwindow Scene State Isolation TestUse when a task involves testing whether independent SwiftUI windows retain or share state according to the product design 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 appr...Votes: 0GitHub stars: 2
- Swiftui Navigation State Restoration TestUse when a task involves testing navigation path and restoration behavior across view and scene lifecycle changes 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
- Swiftui Observable Dependency Fanout ReviewUse when a task involves reducing unnecessary view updates caused by broad observable-model dependencies 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
- Swiftui Preference Key Update PropagationUse when a task involves checking preference-key flows that cause repeated layout or state updates 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
- Swiftui Preview Fixture Determinism ReviewUse when a task involves making SwiftUI previews reproducible without live services or user data 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
- Swiftui Scroll Hitch Reproduction PlanUse when a task involves creating a repeatable reproduction for a scroll hitch in a SwiftUI interface 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
- Swiftui State Owner And Lifetime ReviewUse when a task involves checking that SwiftUI state is owned by a view or model with the correct lifetime 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
- Swiftui Ui Test Flakiness AnalysisUse when a task involves diagnosing a UI test that intermittently fails in a SwiftUI navigation or rendering flow 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
- Swiftui View Extraction Regression CheckUse when a task involves verifying behavior after extracting or splitting a large SwiftUI view 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
- Swiftui View Model Introduction DecisionUse when a task involves deciding whether a complex SwiftUI view needs a separate model or can remain view-driven 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
- Swiftui View Task Cancellation Reload ReviewUse when a task involves reviewing asynchronous work started by SwiftUI view lifecycle modifiers 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
- Swiftui View Update Cause Trace AnalysisUse when a task involves finding which state or environment change triggers an unexpected SwiftUI update 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
- Tailwind Patterns Capability Surface MapUse when the actual capability boundary of Tailwind CSS patterns needs to be distinguished from assumptions. Produce a capability map for Tailwind CSS patterns 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 token ownership, class composition, responsive ru...Votes: 0GitHub stars: 2
- Tailwind Patterns Change Impact AssessmentUse when a proposed Tailwind CSS patterns version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Tailwind CSS patterns 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 token ownership, class composition, responsive ...Votes: 0GitHub stars: 2
- Tailwind Patterns Failure Triage RecordUse when a reproducible Tailwind CSS patterns symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Tailwind CSS patterns 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 token ownership, class composition, responsive rules, and generated-style drift. Use ...Votes: 0GitHub stars: 2
- Tailwind Patterns Input Output ContractUse when the accepted inputs or produced outputs for Tailwind CSS patterns need a checkable boundary. Produce an input/output contract for Tailwind CSS patterns 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 token ownership, class composition, responsive rules, and generated-style dri...Votes: 0GitHub stars: 2
- Tailwind Patterns Integration Parity TraceUse when Tailwind CSS patterns exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Tailwind CSS patterns 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 token ownership, class composition, responsive rules, and generated-style drift. Use only auth...Votes: 0GitHub stars: 2
- Tailwind Patterns Performance EnvelopeUse when Tailwind CSS patterns must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Tailwind CSS patterns 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 token ownership, class composition, responsive rules, and generated...Votes: 0GitHub stars: 2
- Tailwind Patterns Permission Boundary ReviewUse when Tailwind CSS patterns may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Tailwind CSS patterns 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 token ownership, class composition, responsive rules, an...Votes: 0GitHub stars: 2
- Tailwind Patterns Release Handoff RecordUse when a Tailwind CSS patterns review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Tailwind CSS patterns 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 token ownership, class composition, responsive ru...Votes: 0GitHub stars: 2
- Tailwind Patterns Reproducibility Fixture PlanUse when a Tailwind CSS patterns result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Tailwind CSS patterns 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 token ownership, clas...Votes: 0GitHub stars: 2
- Tailwind Patterns Version CompatibilityUse when a Tailwind CSS patterns integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Tailwind CSS patterns 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 token ownership, class composition, responsi...Votes: 0GitHub stars: 2
- Threejs Animation Capability Surface MapUse when the actual capability boundary of Three.js animation workflows needs to be distinguished from assumptions. Produce a capability map for Three.js animation workflows covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to clip identity, time-step behavior, ...Votes: 0GitHub stars: 2
- Threejs Animation Change Impact AssessmentUse when a proposed Three.js animation workflows version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Three.js animation workflows with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to clip identity, time-step behavior...Votes: 0GitHub stars: 2
- Threejs Animation Failure Triage RecordUse when a reproducible Three.js animation workflows symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Three.js animation workflows with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to clip identity, time-step behavior, mixer lifecycle, state transitions, ...Votes: 0GitHub stars: 2
- Threejs Animation Input Output ContractUse when the accepted inputs or produced outputs for Three.js animation workflows need a checkable boundary. Produce an input/output contract for Three.js animation workflows with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to clip identity, time-step behavior, mixer lifecycle, state trans...Votes: 0GitHub stars: 2
- Threejs Animation Integration Parity TraceUse when Three.js animation workflows exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Three.js animation workflows showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to clip identity, time-step behavior, mixer lifecycle, state transitions, and clean...Votes: 0GitHub stars: 2
- Threejs Animation Performance EnvelopeUse when Three.js animation workflows must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Three.js animation workflows with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to clip identity, time-step behavior, mixer lifecycle, s...Votes: 0GitHub stars: 2
- Threejs Animation Permission Boundary ReviewUse when Three.js animation workflows may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Three.js animation workflows showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to clip identity, time-step behavior, mixer l...Votes: 0GitHub stars: 2
- Threejs Animation Release Handoff RecordUse when a Three.js animation workflows review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Three.js animation workflows with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to clip identity, time-step behavior, ...Votes: 0GitHub stars: 2
- Threejs Animation Reproducibility Fixture PlanUse when a Three.js animation workflows result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Three.js animation workflows defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to clip id...Votes: 0GitHub stars: 2
- Threejs Animation Version CompatibilityUse when a Three.js animation workflows integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Three.js animation workflows with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to clip identity, time-step behav...Votes: 0GitHub stars: 2
- Threejs Fundamentals Capability Surface MapUse when the actual capability boundary of Three.js scene fundamentals needs to be distinguished from assumptions. Produce a capability map for Three.js scene fundamentals 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 scene graph identity, camera and rend...Votes: 0GitHub stars: 2
- Threejs Fundamentals Change Impact AssessmentUse when a proposed Three.js scene fundamentals version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Three.js scene fundamentals 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 scene graph identity, camera and re...Votes: 0GitHub stars: 2
- Threejs Fundamentals Failure Triage RecordUse when a reproducible Three.js scene fundamentals symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Three.js scene fundamentals 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 scene graph identity, camera and renderer lifecycle, coordinate assumptio...Votes: 0GitHub stars: 2
- Threejs Fundamentals Input Output ContractUse when the accepted inputs or produced outputs for Three.js scene fundamentals need a checkable boundary. Produce an input/output contract for Three.js scene fundamentals 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 scene graph identity, camera and renderer lifecycle, coordinate a...Votes: 0GitHub stars: 2
- Threejs Fundamentals Integration Parity TraceUse when Three.js scene fundamentals exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Three.js scene fundamentals 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 scene graph identity, camera and renderer lifecycle, coordinate assumptions, and d...Votes: 0GitHub stars: 2
- Threejs Fundamentals Performance EnvelopeUse when Three.js scene fundamentals must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Three.js scene fundamentals 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 scene graph identity, camera and renderer lifecycle, co...Votes: 0GitHub stars: 2