visionos-widgetkit-developer
Build and debug WidgetKit widgets for Apple Vision Pro (visionOS), including mounting styles (elevated/recessed), textures (glass/paper), proximity-aware layouts via LevelOfDetail, interactive widgets with AppIntents, widget rendering modes (accented/fullColor), and timeline update troubleshooting. (visionOS widgets are pinned spatial objects, not watch complications.)
bazi-mingli
八字命理 (Bazi / Four Pillars of Destiny) divination skill. Use when users request birth chart analysis, fortune telling based on birth date/time, or Chinese astrology. Triggers on: 八字, 四柱, 命盤, 排盤, 算命, 命理, 生辰八字, 天干地支, 五行, 流年, 大運, bazi, four pillars, Chinese astrology, birth chart.
tasuku
Agent-first task management. Use when tracking multi-session work, recording learnings/decisions, managing task dependencies, or persisting context across sessions. Provides tk_list, tk_add, tk_done, tk_start, tk_learn, tk_decide, tk_note, tk_show, tk_find, tk_ready, tk_context, tk_stats, tk_block, tk_task, tk_metadata, tk_manage, tk_health, tk_suggest, tk_deps, and tk_help tools.
ss-build
Spec-driven feature development workflow. Triggers on build/create/add/implement/develop intent.
ss-fix
Fix bugs with regression testing and auto-retry. Triggers on fix/debug/broken/error/not-working intent.
ss-init
Initialize SpecSwarm for a project with constitution and standards. Triggers on setup/initialize/configure intent.
ss-metrics
Show feature metrics and sprint analytics. Triggers on metrics/stats/analytics/how-did-we-do intent.
ss-modify
Modify features with impact analysis and compatibility checks. Triggers on modify/change/update/refactor intent.
ss-release
Prepare releases with changelog, version bump, and tagging. Confirms on release/tag/publish/version intent.
ss-rollback
Safely rollback failed features (DESTRUCTIVE). ALWAYS confirms on rollback/undo/revert/abort intent.
ss-ship
Quality-gated merge to parent branch (DESTRUCTIVE). ALWAYS confirms on ship/deploy/merge/release intent.
ss-status
Check build progress and session status. Triggers on progress/status/done/how's-the-build intent.
ss-upgrade
Upgrade deps/frameworks with breaking change analysis. Triggers on upgrade/update/migrate/modernize intent.
better-mousetraps
Evaluate build-vs-import decisions before writing new functionality. Use when (1) about to implement non-trivial functionality that likely exists as a library, (2) the user's request could be solved by an existing tool or package, (3) you catch yourself writing utility code (parsing, validation, HTTP, crypto, dates, etc.) that smells like a solved problem, or (4) planning a feature and need to weigh develop-in-house vs. adopt a dependency.
code-ratchets
Implement code quality ratchets to prevent proliferation of deprecated patterns. Use when (1) migrating away from legacy code patterns, (2) enforcing gradual codebase improvements, (3) preventing copy-paste proliferation of deprecated practices, or (4) setting up pre-commit hooks to count and limit specific code patterns. A ratchet fails if pattern count exceeds OR falls below expected—ensuring patterns never increase and prompting updates when they decrease.
keepachangelog
Maintain `docs/CHANGELOG.md` in the Keep a Changelog 1.1.0 format. Use when adding a CHANGELOG entry for a new feature, bug fix, deprecation, or removal; preparing a release (cutting an `[Unreleased]` section into a versioned section); reviewing a PR for missing or malformed CHANGELOG entries; or whenever the user mentions "changelog", "release notes", "what's new", or "Unreleased" section.
madsci-cli
Working with the MADSci CLI (the `madsci` command). Use when adding, modifying, or debugging CLI commands, or when using the CLI to operate a MADSci lab.
madsci-experiments
Working with MADSci experiment modalities and the experiment lifecycle. Use when creating, modifying, or debugging experiments using ExperimentScript, ExperimentNotebook, ExperimentTUI, or ExperimentNode.
madsci-managers
Working with MADSci manager services (Event, Experiment, Resource, Data, Workcell, Location, Lab). Use when creating, modifying, debugging, or configuring manager servers.
madsci-nodes
Working with MADSci node modules for laboratory instrument integration. Use when creating, modifying, debugging, or testing node modules that interface with scientific instruments.
madsci-release-audit
Audit MADSci release artifacts for completeness and correctness. Use when preparing a PR, finishing a plan, completing a feature branch, or before any merge to main/unstable. Checks CHANGELOG, docs, guides, example lab, notebooks, templates, and skills for staleness, broken imports, and deprecated patterns.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
quality-checks
Treat type errors, test failures, lint warnings, and coverage gaps as authoritative feedback rather than obstacles. Use when running tests, type checkers, linters, or coverage tools; when tempted to add `# type: ignore`, `# noqa`, `as any`, `@ts-ignore`, `# pragma: no cover`, or to skip/quarantine a test; when deciding how strict to be in an existing codebase; or when designing code that is hard to type or test.
plang
Expert guidance for Plang programming language (plang.is). Use when the user asks about Plang syntax, wants to generate Plang code, needs help debugging Plang goals, wants to understand Plang patterns, or is working on Plang projects. Plang is a natural language pseudo-code language with goal-based architecture using SQLite databases.
submit-forma-reimbursement
Use for submitting Forma reimbursement claims from receipt files.
animation-vocabulary
Name a motion effect from a visual or verbal description; use for terminology questions.
apple-design
Apply Apple-inspired interaction principles when designing web gestures, interruptible springs, or translucent surfaces.
branch
Create or name a Git branch using the user's conventional-commit naming rules.
codebase-design
Design or refactor module interfaces to hide complexity, reduce caller coupling, and clarify dependency ownership.
code-quality
Review maintainability or clean up comments in specified code without expanding the change's scope.
commit
Create a conventional commit from staged changes.
emil-design-eng
Refine web component feedback and motion when implementing or polishing a specific interaction.
english-mode
Toggle English-only mode. Forces English input and provides grammar feedback. Use when: '/english', 'english mode', 'toggle english'.
find-animation-opportunities
Identify and propose useful new animations in an existing interface when the user requests suggestions.
find-skills
Find and evaluate installable agent skills when the user asks to discover skills or extend agent capabilities.
grilling
Stress-test a plan, decision, or idea by questioning the user relentlessly when they ask to be grilled or challenged.
handoff
Compact the current conversation into a handoff document for another agent to pick up.
improve-animations
Produce a read-only animation audit and implementation roadmap when the user requests planning rather than fixes.
investigate
Diagnose reproducible or intermittent failures by tracing evidence to a root cause and verifying a targeted fix.
ios-app-design
Design or review iOS navigation, layout, accessibility, and system materials using the project's target OS and UI framework.
nix-darwin
Configure this macOS dotfiles repository's Nix modules, hosts, and packages, or diagnose darwin-rebuild failures.
no-useeffect
Apply the user's ban on direct React useEffect calls when implementing or refactoring component synchronization.
prototype
Build a throwaway prototype when the user wants to test whether a state model, logic, or UI direction works before committing to it.
react-best-practices
Diagnose React performance problems or review and improve state and effect design.
resolving-merge-conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.
review-animations
Audit animation and gesture changes for behavioral defects, accessibility, performance, and visual coherence.
rust-design-patterns
Resolve Rust ownership and lifetime problems or design Rust APIs, resource lifecycles, and FFI boundaries.
Page 679 of 1685 · 84231 results
