Skip to main content
GitHub-Repository

llmutils

llmutils enthält 6 gesammelte Skills von dimfeld, mit Repository-Berufsabdeckung und Skill-Detailseiten auf SkillsMP.

gesammelte Skills
6
Stars
8
aktualisiert
2026-07-07
Forks
2
Berufsabdeckung
3 Berufskategorien · 100% klassifiziert
Repository-Explorer

Skills in diesem Repository

using-tim
Projektmanagementspezialisten

Manages project plans with tim. Use whenever the user mentions tim, asks to "generate plan 123" (or any number), "work on plan 123", or when you are working on a tim task.

2026-07-07
svelte-core-bestpractices
Webentwickler

Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.

2026-04-03
swift-concurrency-expert
Softwareentwickler

Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.

2026-02-05
swiftui-liquid-glass
Softwareentwickler

Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.

2026-02-05
swiftui-performance-audit
Softwareentwickler

Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.

2026-02-05
swiftui-view-refactor
Softwareentwickler

Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.

2026-02-05