mikker
- 42 skills
- 0 followers
- 14 hours ago last updated
- ▌ Building Document Based Swiftui Applications · mikker bundleAuthoritative guide for building and migrating document-based apps in SwiftUI using the Document protocol (iOS 27 and aligned releases, including macOS Golden Gate). Consult when building a new document-based app; implementing open, edit, save, or export document flows; working with DocumentGroup or DocumentGroupLaunchScene; implementing DocumentReader or DocumentWriter; using FileWrapper via FileWrapperDocumentReader or FileWrapperDocumentWriter; working with package documents; accessing a document's file URL directly; reporting progress during read/write; registering undo actions; migrating from FileDocument or ReferenceFileDocument to the new API; building a read-only document viewer; when autosave is not working in a document app; declaring custom UTType as document formats.
- ▌ Pear V2 Runtime · mikker bundleBuild and wire Pear v2 applications using the current template-plus-runtime approach, especially `hello-pear-*` starters, `pear-runtime`, `pear-mobile`, embedded Bare workers, explicit storage paths, and OTA update flow. Use for tasks that bootstrap a new Pear app, wire an Electron or mobile host, add update handling, separate dev and packaged behavior, or define staging and release flow.
- ▌ Autobonk Contexts · mikker bundleDefine schema-first Autobonk domains with generated schema bundles, `Hyperdb` views, managers, contexts, role-based permissions, pairing flows, and optional Yjs collaboration support through `autobonk-yjs`. Use for tasks that model shared state, write or extend `schema.js`, add routes and permission checks, build create/join flows, or implement deterministic replicated collaboration on top of Autobonk.
- ▌ Hyperstack Foundations · mikker bundleDesign and implement peer-to-peer application backends on the Holepunch hyper stack using Corestore, Hyperswarm, Autobase, Hyperbee, Hyperdb, Hyperblobs, Hyperdrive, and adjacent storage primitives. Use for tasks that need storage topology decisions, local-versus-shared state boundaries, replication design, lifecycle and cleanup planning, or backend architecture for a worker, service, or app core.
- ▌ Holepunch App Composition · mikker bundleCompose a complete Holepunch application by assigning responsibilities across the host shell, Pear runtime, backend worker, shared domain layer, RPC boundary, and UI state. Use for tasks that plan or refactor app architecture, decide where features should live, connect Hyperstack primitives to Pear hosts, or turn a product idea into a practical implementation blueprint without coupling it to one specific app.
- ▌ Xcode Skills · mikker bundleAuthoritative Apple guidance bundled with Xcode for SwiftUI, UIKit, App Intents, testing, device interaction, document apps, C bounds safety, and Xcode security settings. Use when writing, reviewing, debugging, testing, or modernizing Apple-platform code. Load the relevant bundled skill before acting.
- ▌ Commit · mikkerWrite git commit messages. Use when asked to commit, write a commit message, or stage and commit changes.
- ▌ New Thread · mikker bundleLaunch and control an implementation agent in its own wt worktree and Fut workspace. Use when the user asks to start a new thread, delegate isolated work, or run a task in a separate workspace.
- ▌ Proper Fix · mikker bundleBias bug fixes and refactors toward root-cause solutions, simplification, and removal of workaround layers. Use when Codex is fixing a bug, flaky behavior, confusing edge case, or ugly conditional pileup and the obvious change looks like another patch on top of earlier patches, defensive code, or duplicated repair logic.
- ▌ Sentry CLI · mikker bundleGuide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI.
- ▌ Regroup · mikkerRebase a feature worktree on main/master, resolve conflicts, ff-only merge into the trunk worktree, then rebase feature on updated trunk.
- ▌ Hunk Review · mikkerInteracts with live Hunk diff review sessions via CLI. Inspects review focus, navigates files, hunks, and exact lines, reloads session contents, adds inline review comments, and paints attention marks on character ranges. Use when the user has a Hunk session running or wants to review diffs interactively.
- ▌ Orchestrate · mikkerOrchestrate implementation work through subagents while retaining responsibility for planning, integration, review, and validation.
- ▌ Stripe Docs · mikkerUse when the user or agent needs to read, search, or look up Stripe documentation or API reference. Prefer this over curl or WebFetch for any docs.stripe.com content.
- ▌ Dhh Ruby Style · mikker bundleThis skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.
- ▌ Explore Design · mikker bundleGenerate a single self-contained HTML file showing 3–6 distinct visual directions for a UI section, page, or component side-by-side for comparison, then faithfully implement the variant the user picks. Use when the user asks to "explore directions", "show me a few options", "brainstorm designs", "concept this", "lay out variants", or wants to compare visual approaches before committing to one. Each variant gets a label, a one-line tradeoff, a live rendered preview, and a short analysis. Also use for the follow-up — "implement option C", "build this exploration", "turn this mock into the real page", "make the implementation match the design" — which runs the implementation phase in references/implement.md. Saying "init" or "rebrand the explorations" (re)captures the repo's brand style into a repo-local template.
- ▌ Tldraw Offline · mikkerOperate the user's tldraw offline canvas app, including open .tldraw or .tldr files. Use whenever a task involves inspecting, editing, arranging, connecting, linting, or scripting a tldraw Desktop canvas.
- ▌ Field Notes · mikker bundleUser-owned external project notes in ~/.field_notes. Use when the user asks to check, search, read, save, append, update, or consult field notes; phrases include "check field notes", "look in field notes", "save to field notes", "what do field notes say", "what's next", progress notes, planning notes, external docs, cross-project memory, or docs that should live outside a repository.
- ▌ Web Browser · mikker bundleAllows to interact with web pages by performing actions such as clicking buttons, filling out forms, and navigating links. It works by remote controlling Google Chrome or Chromium browsers using the Chrome DevTools Protocol (CDP). When Claude needs to browse the web, it can use this skill to do so.
- ▌ Dhh Rails Style · mikker bundleThis skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.
- ▌ Semantic Review · mikkerOpens a semantic, narrative browser review of a git diff and returns the human reviewer's comments. Use after completing a substantial code change, or when the user asks for semantic-review, a narrative review, or a review of current changes.
- ▌
- ▌ Audit Your Codebase · mikkerRun a read-only, agent-orchestrated audit of an entire codebase for materially useful structural simplifications.
- ▌ Stripe Directory · mikkerUse when the user wants to find businesses, software, service providers, or partners for a specific industry, workflow, pain point, capability, or job to be done. Also use when the agent needs to programmatically purchase or consume a service. Use Stripe Directory to build a short relevant shortlist, even if the user does not mention Stripe Directory explicitly.
- ▌ Solidify Codebase · mikkerDeep investigation and solidification pass on an existing codebase. Use when asked to audit, simplify, or future-proof a system; perform a deep cleanup/refactor pass; identify high-impact improvement opportunities; or present a vetted change list before implementing selected items.
- ▌ Stripe Best Practices · mikker bundleGuides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, restricted keys, webhooks, OAuth). Use when building, modifying, or reviewing any Stripe integration, including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.
- ▌ Swiftui UI Patterns · mikker bundleBest practices and example-driven guidance for building SwiftUI views and components. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens, or needing component-specific patterns and examples.
- ▌ Data Structure Review · mikkerReview recent spike or implementation work for data structures and organizing models that would materially simplify the code. Use after exploratory work, when asked to reconsider the design, or when scattered state, repeated branches, unclear ownership, invalid intermediate states, fragile ordering, or duplicated transformations appear.
- ▌ Macos Design Guidelines · mikker bundleApple Human Interface Guidelines for Mac. Use when building macOS apps with SwiftUI or AppKit, implementing menu bars, toolbars, window management, or keyboard shortcuts. Triggers on tasks involving Mac UI, desktop apps, or Mac Catalyst.
- ▌ Minimal Whimsy Style Review · mikkerStyle review notes for UI/design work. Use when reviewing or implementing visual style, layout, components, typography, icons, cards, themes, or dark mode. Bias toward minimal, simple interfaces with a slight note of whimsy.
- ▌ Reread Files Before Editing · mikkerEnsure files are re-read before editing to avoid overwriting user changes. Use only when explicitly encouraged to by user.
- ▌ Device Interaction · mikkerVerify app behavior on device or simulator via screenshots, UI hierarchy, and touch interactions.
- ▌ Swiftui Specialist · mikker bundleAuthoritative SwiftUI best practices and performance guidance from Apple; supersedes prior training on these topics. For code generation, consult the relevant references when generating any SwiftUI code related to: - animation (the @Animatable macro vs AnimatableValues vs AnimatablePair, and custom animatableData setter logic) - Environment and @Entry (closure or class-typed defaults, unstable defaults, high-frequency updates) - @Observable best practices and efficient invalidation - ForEach and List row identity and structure (id: \.self, indices, offsets, AnyView or multi-view rows, inline filter/sort, cached collections, List fast path) - localization (String vs LocalizedStringResource, the right bundle in packages and frameworks, .textCase, .formatted(.list()), translator comments) - soft-deprecated APIs such as NavigationView and the old onChange, and when to surface them during feature work.
- ▌ Swiftui Whats New 27 · mikker bundleNew SwiftUI APIs, behaviors, and deprecations in the 2027 OS releases (iOS 27 and aligned macOS/watchOS/tvOS/visionOS). Consult when asked what's new in SwiftUI 27, or when working with: - @State compile errors after an SDK update ("used before being initialized", "invalid redeclaration of synthesized property") or @State becaming a macro - @ViewBuilder/@ContentBuilder ambiguous overloads or type-check regressions; drag-to-reorder in any container (List, stacks, grids, custom layouts) via reorderable()/reorderContainer and its drag-and-drop - AsyncImage caching, reloading on scroll, or a custom URLSession - Swipe actions outside List (ScrollView, LazyVStack, LazyVGrid) via swipeActions()/swipeActionsContainer() - Toolbar overflow, visibility (visibilityPriority, ToolbarOverflowMenu, toolbarMinimizeBehavior), and pinning - Presenting a confirmationDialog or alert from an optional item binding
- ▌ Adopt C Bounds Safety · mikker bundleGuide for the C -fbounds-safety language extension. Covers the language model, pointer annotations, adopting bounds-safety in existing C code, compiler build settings and modes, and runtime debugging of bounds violations.
- ▌ App Intents Specialist · mikker bundleAuthoritative App Intents best practices from Apple. Consult for any App Intents best-practices or correctness review, and when writing, reviewing, refactoring, or extending App Intents code. Supersedes prior training on these topics. For code generation, consult the relevant reference when working on any of the following: - execution-model: perform() is Sendable, not @MainActor (hop with await MainActor.run); it's retriable (restartPerform), so do irreversible work last; requestConfirmation before destructive work; return via .result(...) factories, never a bare value. - entities-and-queries: AppEntity.id must be stable across launches/devices; entities(for:) (batched) vs empty-default suggestedEntities(); EntityStringQuery.entities(matching:) is not auto-filtered; only @Property members are system-visible; EnumerableEntityQuery loads all (use EntityPropertyQuery for large stores). - entity-property-queries: EntityPropertyQuery for Shortcuts "Find X where…" — properties/sortingOptions/comparators; you execut
- ▌ App Intents Whats New 27 · mikker bundleNew App Intents APIs, behaviors, and deprecations introduced in the iOS 26 (2025) and iOS 27 (2026) releases (and their macOS/watchOS/tvOS/visionOS siblings). Use when adopting, migrating to, or asked about: declaring where an intent runs with supportedModes / IntentModes (.background / .foreground) or migrating off the deprecated openAppWhenRun; pulling a background run into the foreground with continueInForeground / needsToContinueInForegroundError; UndoableIntent; asking the person to pick from a small set mid-perform with requestChoice / IntentChoiceOption; cancelling with CancellableIntent / IntentCancellationReason; long-running or background work with LongRunningIntent / performBackgroundTask; restricting where an intent runs with IntentExecutionTargets / allowedExecutionTargets; returning interactive snippets with SnippetIntent and Button(intent:); Visual Intelligence camera/onscreen search with IntentValueQuery + SemanticContentDescriptor (import VisualIntelligence) + @UnionValue; associating onscree
- ▌ Audit Xcode Security Settings · mikker bundleAudit and enable security-oriented Xcode build settings. Progressively enables compiler warnings, static analyzer checkers, and Enhanced Security features. Use when: user wants to secure their Xcode project, audit security settings, enable hardening, review security posture of build configuration, set up security-focused static analysis, enable static analysis, improve warning coverage, harden diagnostics, or catch more bugs at compile time in C/C++/Objective-C/Swift. SKIP: network security (TLS/ATS), code signing, privacy APIs.
- ▌ Pr · mikkerCreate and push pull requests. Use when the user uses “PR” as a verb or says “create a PR,” “push a PR,” or similar.
- ▌ Wt · mikkerManage Git worktrees with wt. Use to create, switch, list, remove, persist, merge, or ship worktrees.
- ▌ Ship · mikkerCommit all current work in logical chunks, synchronize it with origin/main or origin/master, run the full test suite, push to trunk, and update relevant tracker issues. Use when the user asks to ship, publish, or push all changes.
- ▌ Steve · mikkerUse the steve CLI to automate macOS apps via Accessibility APIs. Use when you need to drive Mac UI (apps, windows, menus, elements), run UI smoke tests, or script interactions using steve commands and JSON output. Never decide to use steve on your own. Only use when told to.