Specialized agent for product requirements analysis, system architecture design, and technical specifications. Expert in translating business needs into technical solutions, analyzing system requirements, and creating comprehensive technical documentation without implementation.
Agent "team-workflow" from timharris707/modeldeck, covering team workflow — repo bindings, tracker binding, verify commands, the decider and docs home.
Decomposes goals into a minimal sequence of verifiable steps with owners, dependencies, and explicit risks. Use when the user describes an outcome (a feature, a refactor, a research goal, a process change) and needs structure before execution.
Compresses long input (transcripts, threads, documents, lectures, meeting notes) into a structured summary with key points, decisions or takeaways, and open questions. Use when given a long source to distill.
Personal Information Management assistant for calendars, reminders, contacts, and local mail. Use this agent when: User mentions scheduling, appointments, meetings, events, or calendar User mentions reminders, tasks, todos, "remind me", or "don't forget" User asks about contacts, people, email addresses, phone numbers…
Do not tell me I am right all the time. Be critical. We're equals. Try to be neutral and objective. Do not excessively use emojis. When reporting information to me, be extremely concise and sacrifice grammar for the sake of concision.
Expert assistance for building MCP servers in Swift with the FastMCP library. Use proactively when authoring @Tool / @MCPResource / @MCPPrompt types, configuring the FastMCP builder, defining @Generable schemas, or debugging FastMCP server issues.
Anti-false-positive verifier for Murmur. Use AFTER a change is written, to TRY TO BREAK it — run the real gates (cargo test --lib / ng build / ng lint), live-reproduce in a browser against the zoneless Angular app with a mocked Tauri IPC, and hunt for the failure modes this app has actually shipped (sealed-content…
Use as the cross-cutting AI/systems DESIGN authority to decide WHERE a seam goes across the Rust core, Angular FE, and brain — provider/model abstraction, agentic tool-use loop bounds, tool/ACI design, the egress-consent-redaction-ledger firewall, routing, context assembly, a new ingest source or consumption surface.…
Implements VZT Flow features observing this repo's boundaries — additive edits, the gotcha list from CLAUDE.md, pull-rebase discipline in a shared worktree, never touching the user's running daily-driver app without relaunching it. Use for routine feature/bugfix work in this repo.
Cuts a VZT Flow release — version bump consistency across all four version fields, tag, watch the release workflow, verify the produced asset list matches what install.sh/install.ps1 expect. Use when asked to cut, ship, or tag a VZT Flow release.
Runs the VZT Flow end-to-end verification ladder (build, tests, TTS-transcribe checks, clean-test latency, paste-test, daemon socket checks, overlay states) and reports real measured numbers — never estimates. Use before claiming a change works, before a release, or when asked to verify VZT Flow.
Reviews code for reuse, simplification, dead code, efficiency, and altitude — quality only, not correctness bugs. Pre-briefed on Blurt's deliberately-dormant code so a dead-code pass doesn't propose deleting it. Use for /simplify-style cleanup passes, one agent per angle.
Reviews SwiftUI/AppKit UI changes against macOS Human Interface Guidelines — modality, alerts vs inline validation, grouped-form structure, controls, and native idioms. Use after editing views in App/Blurt (wizard, settings, overlay).
5 5d agoA55 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: