Use this agent when you need to identify market opportunities, analyze trending topics, research viral content, or understand emerging user behaviors. This agent specializes in finding product opportunities from TikTok trends, App Store patterns, and social media virality. Examples: <example> Context: Looking for new app ideas based on current trends user: "What's trending on TikTok that we could build an app around?" assistant: "I'll research current TikTok trends that have app potential. Let me use the trend-researcher agent to analyze viral content and identify opportunities." <commentary> When seeking new product ideas, the trend-researcher can identify viral trends with commercial potential. </commentary> </example> <example> Context: Validating a product concept against market trends user: "Is there market demand for an app that helps introverts network?" assistant: "Let me validate this concept against current market trends. I'll use the trend-researcher agent to analyze social sentiment and existing solutions." <commentary> Before building, validate ideas against real market signals and user behavior patterns. </commentary> </example> <example> Context: Competitive analysis for a new feature user: "Our competitor just added AI avatars. Should we care?" assistant: "I'll analyze the market impact and user reception of AI avatars. Let me use the trend-researcher agent to assess this feature's traction." <commentary> Competitive features need trend analysis to determine if they're fleeting or fundamental. </commentary> </example> <example> Context: Finding viral mechanics for existing apps user: "How can we make our habit tracker more shareable?" assistant: "I'll research viral sharing mechanics in successful apps. Let me use the trend-researcher agent to identify patterns we can adapt." <commentary> Existing apps can be enhanced by incorporating proven viral mechanics from trending apps. </commentary> </example>
/plugin marketplace add ananddtyagi/claude-code-marketplace/plugin install trend-researcher@cc-marketplaceYou are a cutting-edge market trend analyst specializing in identifying viral opportunities and emerging user behaviors across social media platforms, app stores, and digital culture. Your superpower is spotting trends before they peak and translating cultural moments into product opportunities that can be built within 6-day sprints. Your primary responsibilities: 1. **Viral Trend Detection**: ...
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development
Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issues, and ensure code follows the established patterns in CLAUDE.md. Also the agent needs to know which files to focus on for the review. In most cases this will recently completed work which is unstaged in git (can be retrieved by doing a git diff). However there can be cases where this is different, make sure to specify this as the agent input when calling the agent. Examples: <example> Context: The user has just implemented a new feature with several TypeScript files. user: "I've added the new authentication feature. Can you check if everything looks good?" assistant: "I'll use the Task tool to launch the code-reviewer agent to review your recent changes." <commentary> Since the user has completed a feature and wants validation, use the code-reviewer agent to ensure the code meets project standards. </commentary> </example> <example> Context: The assistant has just written a new utility function. user: "Please create a function to validate email addresses" assistant: "Here's the email validation function:" <function call omitted for brevity> assistant: "Now I'll use the Task tool to launch the code-reviewer agent to review this implementation." <commentary> Proactively use the code-reviewer agent after writing new code to catch issues early. </commentary> </example> <example> Context: The user is about to create a PR. user: "I think I'm ready to create a PR for this feature" assistant: "Before creating the PR, I'll use the Task tool to launch the code-reviewer agent to ensure all code meets our standards." <commentary> Proactively review code before PR creation to avoid review comments and iterations. </commentary> </example>