lld-reviewer
LLD review, Low-Level Design review, 详细设计评审。Use when: 审查正式 LLD，或评审已批准职责内的有限工程修复方案与整改 delta。Do not use for architecture ownership/trust changes, API contract approval, code review, or deployment approval.
lld-writer
Write LLD, Low-Level Design, 写详细设计。Use when: PRD/HLD/API Contract 完成后需要写模块设计、接口设计、实现级技术方案。 也用于既有相关文档的有限增量更新。
prd-reviewer
PRD review, 需求评审, 检查 PRD 质量。Use when: PRD 完成后需要评审、"审查 PRD"、"PRD 评审"、"需求评审"。
prd-writer
Write PRD, 写产品需求文档。Use when: 需要写新功能 PRD（有UI/无UI）、第三方集成、功能重构、性能/安全优化需求。
prototype-designer
Prototype, 交互原型, 原型设计, UI prototype, 原型视觉优化。Use when: PRD 和 User Journey 完成后，需要在前端仓库中生成或打磨视觉精美、可交互的隔离原型，在进入 HLD/API Contract 之前验证视觉方向、交互和页面状态。
prototype-reviewer
Prototype review, 原型评审, 交互原型审查。Use when: prototype-designer 完成后、进入 API Contract/HLD 之前需要审查原型的上游对齐、视觉品质、真实交互、工程隔离和下游可用性。
runbook-writer
Write Runbook, 撰写运维手册。Use when: LLD 完成后需要编写部署、回滚、监控、故障处理等运维文档。 也用于既有相关文档的有限增量更新。
test-reviewer
Review test design and readiness, 测试评审。Use when: Test Spec/Test Case Package 完成后，需要审查独立测试范围内的覆盖、追溯、执行证据与遗留风险，作为发布准备前的测试门禁。
test-spec-writer
Write test spec, 测试规格/测试用例包撰写。Use when: LLD 完成且测试策略已确认后，需要产出独立测试范围内完整的 test case package、追溯矩阵与执行说明。 也用于既有相关文档的有限增量更新。
test-strategy-reviewer
Review test strategy, 测试策略评审。Use when: 测试策略写完后，需要审查风险覆盖、独立测试分层、阶段化执行规则、环境策略与入口/出口标准是否成立。
test-strategy-writer
Write test strategy, 测试策略撰写。Use when: PRD、API Contract、HLD 基线明确后，需要定义独立测试范围、独立测试层次、阶段化执行规则、环境策略、入口/出口标准。 也用于既有相关文档的有限增量更新。
uc-interviewer
User journey interview, use case interview, 用户旅程访谈。Use when: 基于 BRD 访谈、整理或补全 User Journey，"对齐 use case"、"确认用户操作流程"。
prompt-optimizer
撰写提示词、优化提示词、改写 Prompt、Prompt 优化。Use when: 用户需要创建或修改可执行提示词；按任务、调用方输出契约与实际工具能力优化，不按模型品牌强制格式。
media-writer
Social media writing, content creation, 自媒体写作。Use when: 需要写微信公众号/知乎/小红书/LinkedIn/Medium/Reddit 文章、单阶段选题或稿件润色。
elysiajs
Create backend with ElysiaJS, a type-safe, high-performance framework.
ui-skills
Opinionated constraints for building better interfaces with agents.
agency-digest-setup
Get daily A/B test updates in Slack for multiple brands. Use when you want morning summaries of all your Intelligems tests, need to monitor tests across multiple stores or clients, or want automated Slack notifications with key metrics like revenue per visitor, profit per visitor, and conversion rates. Perfect for agencies managing multiple brands.
test-health-check-setup
Get alerts in Slack when your A/B tests need attention. Use when you want daily health checks for your Intelligems tests, need to know when conversion drops or traffic is low, or want to monitor statistical significance progress. Sends one message per test with clear status indicators. Great for single-brand monitoring.
intelligems-segment-analysis
Analyze which audience segments each active Intelligems experiment is winning in. Shows device type, visitor type, and traffic source breakdowns with confidence levels. Use when you want to see segment-level performance of A/B tests.
using-firebase
Comprehensive Firebase development guidance for GCP-hosted applications. Covers Firestore database operations (CRUD, queries, transactions, data modeling), Cloud Functions (1st and 2nd generation, TypeScript and Python, all trigger types), Firebase CLI operations, emulator setup and data persistence, security rules (Firestore and Storage), authentication integration, hosting configuration, and GCP service integration. Use when working with Firebase projects, deploying Cloud Functions, querying Firestore, setting up triggers (Firestore, Auth, Storage, HTTP, Callable, Scheduled, Pub/Sub), managing security rules, configuring hosting rewrites/headers, managing secrets, or integrating with GCP services like BigQuery and Cloud Tasks. Triggers include firebase, firestore, cloud functions, firebase functions, firebase hosting, firebase auth, firebase storage, firebase emulator, firebase deploy, firebase init, firebase rules, callable function, scheduled function, onDocumentCreated, onRequest, onCall, onSchedule.
swift-testing
Expert guidance on Swift Testing best practices, patterns, and implementation. Use when developers mention: (1) Swift Testing, @Test, #expect, #require, or @Suite, (2) "use Swift Testing" or "modern testing patterns", (3) test doubles, mocks, stubs, spies, or fixtures, (4) unit tests, integration tests, or snapshot tests, (5) migrating from XCTest to Swift Testing, (6) TDD, Arrange-Act-Assert, or F.I.R.S.T. principles, (7) parameterized tests or test organization.
flutter-bloc-development
Build Flutter features using BLoC state management, clean architecture layers, and the project's design system. Apply when creating screens, widgets, or data integrations.
dev:create-skill
Create New Skill - scaffolds a skill definition following Claude Code conventions and this repository's patterns. Use when adding a new skill.
git:amend
Amend Commit - modifies the last commit with staged changes or new message
git:changelog
Generate Changelog - analyzes git history and creates a human-readable changelog for non-technical teams
git:commit
Smart Commit - stages all changes and creates a conventional commit
project:init
Project Init - defines the overall system goals, stakeholders, constraints, and shared architectural decisions. Use when starting a new multi-spec project.
agent:audit
Agent Audit - audits an existing AI agent against the 22 patterns from "Patterns for Building AI Agents" and the 12 factors of production-reliable agents, emitting a scored maturity report with a security gate. Use when reviewing, scoring, or assessing the production-readiness of an AI agent or agent design.
agent:developer
Designs and builds AI agents. Use when working on agent architecture, prompts, model selection, tool design, MCP, memory, context engineering, RAG, graph workflows, multi-agent systems, evaluation, or production reliability.
dev:claude-audit
Claude Code Setup Audit - reviews CLAUDE.md hierarchy, .claude/settings.json deny-list, per-directory commands, and extension layer against best practices for large codebases. Use periodically (every 3-6 months or after a major model release) or when onboarding a new repo.
journal:capture
Journal Capture - captures a thought, problem, edge case, idea, or decision into ~/journal and updates README indexes. Use when the user wants to write down a development thought or observation.
journal:promote
Journal Promote - graduates a journal entry into a new spec by seeding .specs/<name>/ with the entry's content, then linking the journal entry back. Use when the user wants to turn a captured idea, problem, or decision into a full specification.
journal:search
Journal Search - searches entries in ~/journal by query, type, project, topic, tags, or date range. Use when the user wants to find past thoughts, decisions, problems, or ideas they captured.
project:plan
Project Plan - breaks the vision into individual specs with dependencies, execution order, and shared interfaces. Use when decomposing a project into features.
project:status
Project Status - dashboard showing progress across all specs with dependency tracking and next action suggestions.
review:diff
Diff Review - analyzes code changes and provides structured feedback before commit
review:investigate
Investigate Problem - analyzes a problem in the codebase and proposes actionable solutions
review:ux
UX Review - analyzes feature for efficiency-first UX patterns, keyboard navigation, and pro-tool experience
spec:design
Technical Design - picks one variant per problem area from the research catalogue, then produces architecture diagrams, interfaces, and data flow. Decisions live here, not in research.
spec:implement
Implement Tasks - executes tasks from the tasks document using subagents. Use when ready to start coding a feature.
spec:requirements
Requirements Analysis - gathers requirements through structured questions and produces a requirements document with testable acceptance criteria. Use when starting a new feature spec or documenting requirements.
spec:research
Technical Research - investigates the codebase and builds a catalogue of solution variants per problem area. Iterative — can be re-run to widen the catalogue. Does not make decisions; selection happens in spec:design.
spec:review
Review Specification - validates documents for completeness, quality, and consistency against the codebase. Use when checking spec quality at any pipeline stage.
spec:status
Spec Status - displays pipeline progress dashboard for a single specification showing document statuses, blockers, and next action.
spec:tasks
Task Breakdown - generates an implementation plan with tracked tasks based on requirements and design documents. Use when breaking down a design into actionable work items.
spec:test-plan
Test Plan - creates a manual test plan with traceable test cases from specification documents. Use when preparing to verify a feature implementation.
spec:test
Execute Tests - walks through test cases from the test plan, collects results, and updates the plan. Use when verifying a feature implementation.
commit
Commit workflow for agent-media - builds, typechecks, creates changeset, and pushes
agent-media
Agent-first media toolkit for image, video, and audio processing. Use when you need to resize, convert, generate, edit, upscale images, remove backgrounds, extend or crop canvases, extract audio, transcribe speech, or generate videos. All commands return deterministic JSON output.
audio-extract
Extracts audio track from a video file. Use when you need to get audio from video, prepare audio for transcription, or separate audio from video content. Runs locally with no API key required.
Page 583 of 1646 · 82256 results