User research and insight synthesis for interviews, usability testing, personas, journey mapping, and actionable product/design recommendations. Use when planning studies, collecting evidence, synthesizing patterns, or converting findings into prioritized decisions.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Act as a user research methodologist who plans rigorous studies and synthesizes evidence into prioritized product and design actions.
Research Target: $ARGUMENTS
ResearchInsight { theme: string evidence: string[] impact: string recommendation: string priority: HIGH | MEDIUM | LOW }
ResearchDeliverable { method: string participants: string keyInsights: ResearchInsight[] personas: string[] journeyMaps: string[] }
State { target = $ARGUMENTS methods = [] rawData = [] insights = [] }
Always:
Never:
reference/interview-methods.md — Interview types, question design, and facilitation techniquesreference/observation-methods.md — Contextual inquiry and usability testing protocolsreference/synthesis-methods.md — Affinity mapping, thematic analysis, and insight extractionreference/persona-guide.md — Behavioral persona framework and creation processreference/journey-mapping.md — Journey map structure, touchpoints, and emotional arcsreference/planning-reporting.md — Study planning templates and reporting formats还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Context enrichment for agentic AI application development using LangChain, Vercel AI SDK, and assistant-ui. Use when building AI agents, chat interfaces, tool-calling pipelines, RAG systems, or multi-step AI workflows.
中文简介正在准备中。当前显示原文说明。
Deep-research analysis of a codebase, a topic, or both. Clarifies the question, agrees the research angles with you, then runs a dynamic workflow that gathers cited claims per angle, merges duplicates, has independent skeptics try to refute every claim, and writes one cited report from the claims that survived. Use for "how does X work", "map the Y flow", "research Z", or any mechanism-level question that must be evidence-backed.
中文简介正在准备中。当前显示原文说明。
REST and GraphQL API design patterns, OpenAPI/Swagger specifications, versioning strategies, and authentication patterns. Use when designing APIs, reviewing API contracts, evaluating API technologies, or implementing API endpoints.
中文简介正在准备中。当前显示原文说明。
System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria. Use when designing system architectures, evaluating patterns, or planning scalability.
中文简介正在准备中。当前显示原文说明。
Consolidate a completed specification into a single archived record and remove its working directory. Use as the final stage after implementation — distills requirements + solution into .start/archive/[NNN]-[name].md and deletes the .start/specs/[NNN]-[name]/ directory.
中文简介正在准备中。当前显示原文说明。
Required first step before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
中文简介正在准备中。当前显示原文说明。