mac-widget-design
Use when creating, updating, or verifying a local macOS WidgetKit widget, especially desktop widgets with a native black dashboard visual system, reliable local install/run workflow, app-group snapshot/cache internals, timeline reloads, and real desktop screenshot proof.
What this skill does
# Mac Widget Design Build or retrofit macOS WidgetKit widgets that run locally, look native on the desktop, and have reliable data internals. Prefer updating an existing widget when the repo already has a carrier app, Widget extension, shared Swift package, or installer; create a new local widget only when no suitable surface exists or the user asks for a fresh widget. ## Decision Tree 1. **Existing widget present**: inspect `Package.swift`, `.xcodeproj`, `WidgetBundle`, `WidgetConfiguration`, `*Widget*.swift`, app-group IDs, cache writers, and install scripts. Update the current surface. 2. **No widget present**: create a native macOS carrier app plus WidgetKit extension. Use SwiftPM for shared core code and preview/test utilities, but do not assume SwiftPM alone can install a WidgetKit extension. 3. **Design-only request**: still check WidgetKit background behavior and desktop proof; widget design cannot be trusted from static preview alone. 4. **Internals-only request**: still verify the visible failure states; stale data, dead ring/battery, missing sensor timestamps, and unavailable metrics must be visible. ## Load References - For visual layout and colors, read `references/design-system.md`. - For WidgetKit architecture, local running, cache, and data safety, read `references/internals.md`. - Before final verification, read `references/local-proof.md`. ## Required Workflow 1. Retrieve current repo context before editing: - `rg --files -g 'Package.swift' -g '*.xcodeproj' -g '*.swift' -g '*install*' -g '*Widget*'` - `rg 'WidgetBundle|WidgetConfiguration|containerBackground|AppGroup|WidgetCenter|TimelineProvider|AppIntentTimelineProvider'` 2. Choose **update** or **create** explicitly. For an existing widget, keep existing bundle IDs, app-group IDs, signing setup, installer style, and cache locations unless they are broken. 3. Apply the black dashboard design system: - Use a black or near-black widget surface for the authored background. - Do not hardcode beige, cyan, blue glass, decorative gradients, or wallpaper-colored washes. - Use color only as semantic signal accents: red/orange/green/neutral. - Keep the layout data-first: priority summary, compact aligned rows, direct labels, small progress meters, minimal separators. 4. Implement or preserve reliable internals: - Widget reads cached snapshots; the app/sync command owns network calls. - Cache to app-group storage and at least one local fallback that the widget can read in local/dev installs. - Show stale/missing/unreliable data as a visible state, not as a healthy state. - Surface low/dead battery, missing sensor timestamp, stale sync, and failed refresh. - Trigger WidgetKit timeline reloads after cache writes or local install. 5. Run deterministic checks: - Use repo tests/builds first. - Run `python3 ~/.codex/skills/mac-widget-design/scripts/check_widget_design.py <repo-root>` after the widget files exist. 6. Prove the real widget: - Render a preview if the repo supports one. - Install the local carrier app/extension. - Capture the actual desktop widget with Finder active and app windows hidden. - Treat the desktop capture as authoritative for background, selected/inactive states, clipping, and legibility. ## Completion Standard Do not call the widget done from a SwiftUI preview alone. A valid finish needs current code inspection, tests/builds, local install evidence, and a real desktop screenshot showing the widget running with live or representative cached data.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.