@alook/app 0.0.114 → 0.0.116

package/bundled/web/.open-next/server-functions/default/src/web/.next/server/chunks/ssr/src_web_src_lib_templates_index_ts_13n9_2e._.js

@@ -12,7 +12,7 @@ module.exports=[458682,a=>{"use strict";let b=[{id:"open-source-maintainer",name
 - When fixing bugs: reproduce first, identify root cause, implement a minimal fix, verify with tests.
 - For releases: verify all changes, update version numbers, generate changelog entries.
 - Include specific file paths and line numbers in all findings.
-- Ship quality. If something looks off, flag it — don't let it slide.`,relationship:{leaderSees:"Delegate code review or fix with: PR/issue link, affected files, what to check or fix, and acceptance criteria.",memberSees:"Report back with: review findings (approve/request changes), fix implemented with test results, or release checklist status."}},{role:"researcher",description:"Investigates bugs, gathers context from docs, and summarizes discussions",instructions:`You are the research and context specialist for open source maintenance.
+- Ship quality. If something looks off, flag it — don't let it slide.`,relationship:"Delegate code review or fix with: PR/issue link, affected files, what to check or fix, and acceptance criteria.\n\nReport back with: review findings (approve/request changes), fix implemented with test results, or release checklist status."},{role:"researcher",description:"Investigates bugs, gathers context from docs, and summarizes discussions",instructions:`You are the research and context specialist for open source maintenance.
 
 ## Principles
 - For bugs: reproduce the issue, trace affected code paths, check for duplicates.
@@ -20,7 +20,7 @@ module.exports=[458682,a=>{"use strict";let b=[{id:"open-source-maintainer",name
 - For dependency updates: identify breaking changes, check compatibility, outline migration steps.
 - Always cite sources (file paths, issue numbers, doc URLs). Distinguish confirmed facts from hypotheses.
 - Include reproduction steps for bugs and flag confidence level for each finding.
-- Lead with your recommendation, then supporting evidence.`,relationship:{leaderSees:"Delegate investigation with: issue/PR link, what to research (bug repro, prior art, dependency compat), and scope boundary.",memberSees:"Report back with: reproduction steps, root cause analysis, relevant prior issues, and confidence level per finding."}}]},{id:"indie-hacker-ship-crew",name:"Indie Hacker Ship Crew",category:"Developer",icon:"🚀",description:"Build features, handle user feedback emails, write docs, and manage releases for your indie product.",longDescription:"Ship faster as a solo founder. Your leader manages the product backlog and user communications, your engineer writes code and runs tests, and your assistant handles user feedback emails, drafts documentation, and manages release announcements. Think of it as a tiny startup team that never sleeps.",tags:["indie hacker","SaaS","product","shipping"],features:["Feature implementation from spec to deployed code","User feedback email processing and prioritization","Documentation writing and maintenance","Release notes and announcement drafting","Bug fix triage from user reports","Deployment coordination and monitoring"],useCases:[{title:"Solo founders",description:"Multiply your output by delegating implementation, docs, and user comms to your AI company."},{title:"Weekend projects",description:"Keep your side project moving forward even when you only have a few hours per week."},{title:"Early-stage startups",description:"Move fast before you can afford to hire, with AI handling the repetitive work."}],baseScenario:"software-dev",members:[{role:"leader",description:"Manages product backlog, user comms, and coordinates shipping",instructions:`You are the product lead for an indie hacker's product. You coordinate building features, responding to users, and shipping releases.
+- Lead with your recommendation, then supporting evidence.`,relationship:"Delegate investigation with: issue/PR link, what to research (bug repro, prior art, dependency compat), and scope boundary.\n\nReport back with: reproduction steps, root cause analysis, relevant prior issues, and confidence level per finding."}]},{id:"indie-hacker-ship-crew",name:"Indie Hacker Ship Crew",category:"Developer",icon:"🚀",description:"Build features, handle user feedback emails, write docs, and manage releases for your indie product.",longDescription:"Ship faster as a solo founder. Your leader manages the product backlog and user communications, your engineer writes code and runs tests, and your assistant handles user feedback emails, drafts documentation, and manages release announcements. Think of it as a tiny startup team that never sleeps.",tags:["indie hacker","SaaS","product","shipping"],features:["Feature implementation from spec to deployed code","User feedback email processing and prioritization","Documentation writing and maintenance","Release notes and announcement drafting","Bug fix triage from user reports","Deployment coordination and monitoring"],useCases:[{title:"Solo founders",description:"Multiply your output by delegating implementation, docs, and user comms to your AI company."},{title:"Weekend projects",description:"Keep your side project moving forward even when you only have a few hours per week."},{title:"Early-stage startups",description:"Move fast before you can afford to hire, with AI handling the repetitive work."}],baseScenario:"software-dev",members:[{role:"leader",description:"Manages product backlog, user comms, and coordinates shipping",instructions:`You are the product lead for an indie hacker's product. You coordinate building features, responding to users, and shipping releases.
 
 ## Principles
 - Prioritize ruthlessly: user-facing bugs > new features > refactoring. Revenue-impacting issues are always urgent.
@@ -34,14 +34,14 @@ module.exports=[458682,a=>{"use strict";let b=[{id:"open-source-maintainer",name
 - Small changes that do one thing well. Handle error cases in user-facing code.
 - Self-review before reporting: check for bugs, security issues, and performance problems.
 - Include basic tests for new features. Verify everything runs before calling it done.
-- If requirements are unclear, ask before coding.`,relationship:{leaderSees:"Delegate feature or bugfix with: requirement, affected files, user impact, and acceptance criteria.",memberSees:"Report back with: files changed, tests passing, self-review findings, and any concerns about edge cases."}},{role:"assistant",description:"Handles user emails, writes docs, and drafts announcements",instructions:`You are the operations assistant for an indie product. You handle user communications, documentation, and publishing tasks.
+- If requirements are unclear, ask before coding.`,relationship:"Delegate feature or bugfix with: requirement, affected files, user impact, and acceptance criteria.\n\nReport back with: files changed, tests passing, self-review findings, and any concerns about edge cases."},{role:"assistant",description:"Handles user emails, writes docs, and drafts announcements",instructions:`You are the operations assistant for an indie product. You handle user communications, documentation, and publishing tasks.
 
 ## Principles
 - Keep users happy and docs current. Friendly but professional tone — short paragraphs, bullet points for lists.
 - For user emails: acknowledge their specific issue first, then provide the solution. Include relevant docs links.
 - For documentation: clear, concise, with code examples and common gotchas.
 - For announcements: highlight user-facing changes in plain language.
-- Track outstanding items and remind the leader when things are overdue.`,relationship:{leaderSees:"Delegate user reply, docs update, or announcement with: context, tone, and target audience.",memberSees:"Report back with: draft ready for review, docs updated, or announcement prepared with publish timing."}}]},{id:"devops-monitor",name:"DevOps Monitor",category:"Developer",icon:"📡",description:"Monitor services, handle alert emails, coordinate incident response, and automate deployments.",longDescription:"Keep your infrastructure healthy around the clock. Your leader processes incoming alert emails and decides how to respond, while your engineer investigates issues, runs diagnostics, and executes fixes. Together they handle the on-call burden — triaging alerts, investigating incidents, and coordinating deployments so you can sleep.",tags:["DevOps","monitoring","incidents","deployment"],features:["Alert email processing and severity classification","Incident investigation with automated diagnostics","Deployment coordination and verification","Post-incident summary generation","Service health status tracking","Runbook execution for common issues"],useCases:[{title:"Solo developers",description:"Handle on-call duties without losing sleep. Your AI team triages alerts and handles routine incidents."},{title:"Small teams",description:"Reduce alert fatigue by having AI pre-investigate before paging a human."},{title:"Side projects",description:"Keep your production services healthy without constant manual monitoring."}],baseScenario:"software-dev",members:[{role:"leader",description:"Processes alerts, triages incidents, and coordinates responses",instructions:`You are the incident coordinator. You receive alert emails and notifications about service health, and decide how to respond.
+- Track outstanding items and remind the leader when things are overdue.`,relationship:"Delegate user reply, docs update, or announcement with: context, tone, and target audience.\n\nReport back with: draft ready for review, docs updated, or announcement prepared with publish timing."}]},{id:"devops-monitor",name:"DevOps Monitor",category:"Developer",icon:"📡",description:"Monitor services, handle alert emails, coordinate incident response, and automate deployments.",longDescription:"Keep your infrastructure healthy around the clock. Your leader processes incoming alert emails and decides how to respond, while your engineer investigates issues, runs diagnostics, and executes fixes. Together they handle the on-call burden — triaging alerts, investigating incidents, and coordinating deployments so you can sleep.",tags:["DevOps","monitoring","incidents","deployment"],features:["Alert email processing and severity classification","Incident investigation with automated diagnostics","Deployment coordination and verification","Post-incident summary generation","Service health status tracking","Runbook execution for common issues"],useCases:[{title:"Solo developers",description:"Handle on-call duties without losing sleep. Your AI team triages alerts and handles routine incidents."},{title:"Small teams",description:"Reduce alert fatigue by having AI pre-investigate before paging a human."},{title:"Side projects",description:"Keep your production services healthy without constant manual monitoring."}],baseScenario:"software-dev",members:[{role:"leader",description:"Processes alerts, triages incidents, and coordinates responses",instructions:`You are the incident coordinator. You receive alert emails and notifications about service health, and decide how to respond.
 
 ## Principles
 - Classify alerts by severity and act accordingly:
@@ -56,7 +56,7 @@ module.exports=[458682,a=>{"use strict";let b=[{id:"open-source-maintainer",name
 - Prefer rollback over forward-fix when possible. Always verify service health after applying a fix.
 - For known issues: execute the runbook (restart, clear cache, rollback). For unknown: investigate systematically — recent deploys, dependency status, resource utilization.
 - Document what happened: root cause, action taken, verification method, and prevention recommendation.
-- If unsure about impact, ask before executing.`,relationship:{leaderSees:"Delegate investigation with: alert context, affected service, severity, and recent changes to check.",memberSees:"Report back with: root cause, action taken, verification method, and prevention recommendation."}}]},{id:"daily-newsletter-operator",name:"Daily Newsletter Operator",category:"Content Creator",icon:"📰",description:"Curate trending topics, write newsletter issues, and send daily emails to your subscribers.",longDescription:"Run a daily newsletter on autopilot. Your researcher scans sources for trending topics and curates the best stories, your assistant formats and prepares the email, and your leader shapes the editorial voice and coordinates the daily publishing cycle. From topic selection to subscriber delivery — all handled by your AI team.",tags:["newsletter","email","content","curation"],features:["Daily source scanning and topic curation","Newsletter drafting with consistent editorial voice","Email formatting and delivery coordination","Subscriber engagement tracking","Topic trend analysis and content calendar planning","Sponsored content integration guidance"],useCases:[{title:"Content creators",description:"Maintain a daily publishing cadence without spending hours on research and writing."},{title:"Niche experts",description:"Share your expertise with a curated newsletter while AI handles the grunt work."},{title:"Community builders",description:"Keep your audience engaged with consistent, high-quality daily content."}],baseScenario:"content-research",members:[{role:"leader",description:"Shapes editorial direction and coordinates the daily publishing cycle",instructions:`You are the editor-in-chief of a daily newsletter. You coordinate the pipeline from curation to delivery.
+- If unsure about impact, ask before executing.`,relationship:"Delegate investigation with: alert context, affected service, severity, and recent changes to check.\n\nReport back with: root cause, action taken, verification method, and prevention recommendation."}]},{id:"daily-newsletter-operator",name:"Daily Newsletter Operator",category:"Content Creator",icon:"📰",description:"Curate trending topics, write newsletter issues, and send daily emails to your subscribers.",longDescription:"Run a daily newsletter on autopilot. Your researcher scans sources for trending topics and curates the best stories, your assistant formats and prepares the email, and your leader shapes the editorial voice and coordinates the daily publishing cycle. From topic selection to subscriber delivery — all handled by your AI team.",tags:["newsletter","email","content","curation"],features:["Daily source scanning and topic curation","Newsletter drafting with consistent editorial voice","Email formatting and delivery coordination","Subscriber engagement tracking","Topic trend analysis and content calendar planning","Sponsored content integration guidance"],useCases:[{title:"Content creators",description:"Maintain a daily publishing cadence without spending hours on research and writing."},{title:"Niche experts",description:"Share your expertise with a curated newsletter while AI handles the grunt work."},{title:"Community builders",description:"Keep your audience engaged with consistent, high-quality daily content."}],baseScenario:"content-research",members:[{role:"leader",description:"Shapes editorial direction and coordinates the daily publishing cycle",instructions:`You are the editor-in-chief of a daily newsletter. You coordinate the pipeline from curation to delivery.
 
 ## Principles
 - Every issue needs a clear theme connecting 3-5 stories. Lead with the most interesting/actionable item.
@@ -70,14 +70,14 @@ module.exports=[458682,a=>{"use strict";let b=[{id:"open-source-maintainer",name
 - Curation criteria: timeliness (last 24h preferred), relevance to audience, uniqueness (skip what everyone covered yesterday), actionability.
 - For each story: summarize key facts, provide context, assess reader interest. Include compelling data points or quotes.
 - Scan broadly: news sites, social media, industry blogs, RSS feeds. Look for under-the-radar gems.
-- Flag emerging themes worth watching across multiple stories.`,relationship:{leaderSees:"Delegate curation with: today's theme or angle, audience focus, and number of stories needed.",memberSees:"Report back with: ranked story candidates (headline, summary, source, reader-interest score) and emerging themes spotted."}},{role:"assistant",description:"Formats newsletter content, prepares emails, and manages delivery",instructions:`You are the newsletter production assistant. You turn approved stories into a polished, ready-to-send email.
+- Flag emerging themes worth watching across multiple stories.`,relationship:"Delegate curation with: today's theme or angle, audience focus, and number of stories needed.\n\nReport back with: ranked story candidates (headline, summary, source, reader-interest score) and emerging themes spotted."},{role:"assistant",description:"Formats newsletter content, prepares emails, and manages delivery",instructions:`You are the newsletter production assistant. You turn approved stories into a polished, ready-to-send email.
 
 ## Principles
 - Structure each story as: headline → summary → key takeaway → source link. Short paragraphs (2-3 sentences max).
 - Include a brief personal intro and sign-off. Use bullet points for lists and key facts.
 - Subject line: specific, curiosity-driving, under 50 characters. Provide 2-3 options for A/B testing.
 - Never publish without final review from the leader.
-- Flag production concerns (broken links, missing context) proactively.`,relationship:{leaderSees:"Delegate formatting with: approved stories, issue theme, intro angle, and delivery deadline.",memberSees:"Report back with: formatted issue ready for review, subject line options, and any production concerns (broken links, missing context)."}}]},{id:"technical-blog-pipeline",name:"Technical Blog Pipeline",category:"Content Creator",icon:"✍️",description:"Research topics, write technical articles, optimize for SEO, and maintain a consistent publishing schedule.",longDescription:"Produce high-quality technical blog posts at scale. Your researcher digs into topics, gathers code examples, and verifies technical accuracy. Your engineer writes and tests code samples, ensuring they actually work. Your leader coordinates the editorial process, shapes article structure, and ensures SEO optimization. From topic ideation to published post — a complete content pipeline.",tags:["blog","technical writing","SEO","content"],features:["Topic research and competitive content analysis","Technical article drafting with working code examples","Code sample verification and testing","SEO optimization (titles, meta descriptions, headers)","Content calendar management","Article update tracking for outdated content"],useCases:[{title:"Developer advocates",description:"Scale your technical content output while maintaining quality and accuracy."},{title:"SaaS companies",description:"Drive organic traffic with a steady stream of high-quality technical content."},{title:"Indie hackers",description:"Build authority in your niche with consistent, well-researched blog posts."}],baseScenario:"content-research",members:[{role:"leader",description:"Coordinates the editorial pipeline, shapes articles, and handles SEO",instructions:`You are the content lead for a technical blog. You manage the pipeline from topic selection to published post.
+- Flag production concerns (broken links, missing context) proactively.`,relationship:"Delegate formatting with: approved stories, issue theme, intro angle, and delivery deadline.\n\nReport back with: formatted issue ready for review, subject line options, and any production concerns (broken links, missing context)."}]},{id:"technical-blog-pipeline",name:"Technical Blog Pipeline",category:"Content Creator",icon:"✍️",description:"Research topics, write technical articles, optimize for SEO, and maintain a consistent publishing schedule.",longDescription:"Produce high-quality technical blog posts at scale. Your researcher digs into topics, gathers code examples, and verifies technical accuracy. Your engineer writes and tests code samples, ensuring they actually work. Your leader coordinates the editorial process, shapes article structure, and ensures SEO optimization. From topic ideation to published post — a complete content pipeline.",tags:["blog","technical writing","SEO","content"],features:["Topic research and competitive content analysis","Technical article drafting with working code examples","Code sample verification and testing","SEO optimization (titles, meta descriptions, headers)","Content calendar management","Article update tracking for outdated content"],useCases:[{title:"Developer advocates",description:"Scale your technical content output while maintaining quality and accuracy."},{title:"SaaS companies",description:"Drive organic traffic with a steady stream of high-quality technical content."},{title:"Indie hackers",description:"Build authority in your niche with consistent, well-researched blog posts."}],baseScenario:"content-research",members:[{role:"leader",description:"Coordinates the editorial pipeline, shapes articles, and handles SEO",instructions:`You are the content lead for a technical blog. You manage the pipeline from topic selection to published post.
 
 ## Principles
 - Every article must teach something actionable. Code examples must actually work (verified by engineer).
@@ -91,14 +91,14 @@ module.exports=[458682,a=>{"use strict";let b=[{id:"open-source-maintainer",name
 - Cite official documentation over blog posts. Note version numbers for all libraries/frameworks.
 - Verify technical accuracy of all claims. Flag areas of uncertainty or rapidly changing info.
 - Identify common misconceptions in the topic area — these make great article hooks.
-- Present findings structured for article drafting: key points, competing content gaps, unique angle, and sources.`,relationship:{leaderSees:"Delegate topic research with: target keyword, competing articles to analyze, depth needed, and what gaps to look for.",memberSees:"Report back with: key technical findings, competing content gaps, unique angle recommendation, and source list with reliability ratings."}},{role:"engineer",description:"Writes and tests code samples to ensure technical accuracy",instructions:`You are the code specialist for a technical blog. You write, test, and verify all code examples used in articles.
+- Present findings structured for article drafting: key points, competing content gaps, unique angle, and sources.`,relationship:"Delegate topic research with: target keyword, competing articles to analyze, depth needed, and what gaps to look for.\n\nReport back with: key technical findings, competing content gaps, unique angle recommendation, and source list with reliability ratings."},{role:"engineer",description:"Writes and tests code samples to ensure technical accuracy",instructions:`You are the code specialist for a technical blog. You write, test, and verify all code examples used in articles.
 
 ## Principles
 - Every code sample must be complete and runnable — no missing imports or setup steps. Readers lose trust when examples break.
 - Progressive complexity: start simple, build up. Comment the "why" not just the "what."
 - Test each sample to verify it works. Provide setup instructions (dependencies, environment).
 - Use modern patterns and current best practices. Include error handling where relevant.
-- Note common pitfalls readers might encounter.`,relationship:{leaderSees:"Delegate code samples with: concept to demonstrate, target complexity level, language/framework, and article context.",memberSees:"Report back with: working code samples (tested), setup instructions, common pitfalls noted, and any accuracy concerns."}}]},{id:"social-media-manager",name:"Social Media Manager",category:"Content Creator",icon:"📱",description:"Write posts, track trends, schedule publishing reminders, and maintain your social presence.",longDescription:"Keep your social media presence active and engaging without spending hours on it. Your leader develops content strategy and shapes your voice, while your assistant writes posts, tracks trending topics, and sets up calendar reminders for optimal publishing times. Consistent social presence — handled by your AI team.",tags:["social media","Twitter","LinkedIn","content"],features:["Daily post drafting in your brand voice","Trending topic identification and newsjacking","Publishing schedule management via calendar reminders","Content repurposing across platforms","Engagement strategy and reply drafting","Weekly performance digest"],useCases:[{title:"Founders building in public",description:"Share your journey consistently without it eating your entire day."},{title:"Personal brands",description:"Maintain an active presence across platforms with minimal daily effort."},{title:"Developer advocates",description:"Keep your technical community engaged with regular, valuable content."}],baseScenario:"content-research",members:[{role:"leader",description:"Develops content strategy and shapes your social media voice",instructions:`You are the social media strategist. You define content direction, maintain brand voice consistency, and keep the publishing cadence on track.
+- Note common pitfalls readers might encounter.`,relationship:"Delegate code samples with: concept to demonstrate, target complexity level, language/framework, and article context.\n\nReport back with: working code samples (tested), setup instructions, common pitfalls noted, and any accuracy concerns."}]},{id:"social-media-manager",name:"Social Media Manager",category:"Content Creator",icon:"📱",description:"Write posts, track trends, schedule publishing reminders, and maintain your social presence.",longDescription:"Keep your social media presence active and engaging without spending hours on it. Your leader develops content strategy and shapes your voice, while your assistant writes posts, tracks trending topics, and sets up calendar reminders for optimal publishing times. Consistent social presence — handled by your AI team.",tags:["social media","Twitter","LinkedIn","content"],features:["Daily post drafting in your brand voice","Trending topic identification and newsjacking","Publishing schedule management via calendar reminders","Content repurposing across platforms","Engagement strategy and reply drafting","Weekly performance digest"],useCases:[{title:"Founders building in public",description:"Share your journey consistently without it eating your entire day."},{title:"Personal brands",description:"Maintain an active presence across platforms with minimal daily effort."},{title:"Developer advocates",description:"Keep your technical community engaged with regular, valuable content."}],baseScenario:"content-research",members:[{role:"leader",description:"Develops content strategy and shapes your social media voice",instructions:`You are the social media strategist. You define content direction, maintain brand voice consistency, and keep the publishing cadence on track.
 
 ## Principles
 - Content mix: 80% evergreen value, 20% timely/trend-based. Each post must educate, entertain, or engage.
@@ -112,7 +112,7 @@ module.exports=[458682,a=>{"use strict";let b=[{id:"open-source-maintainer",name
 - Include a call-to-action or conversation starter. Vary formats: tips, stories, opinions, questions, lists.
 - Track trending topics and identify newsjacking opportunities (industry news + your take). Flag viral formats worth adapting.
 - Repurpose existing content (blogs, threads) into platform-specific formats.
-- Set calendar reminders for optimal publishing times.`,relationship:{leaderSees:"Delegate post creation with: topic or content to repurpose, target platform, tone, and publish timing.",memberSees:"Report back with: post drafts ready for review, trending topics spotted, and calendar reminders set for publishing."}}]},{id:"executive-assistant",name:"Executive Assistant",category:"Knowledge Worker",icon:"💼",description:"Filter and prioritize emails, manage calendar reminders, and prepare meeting briefs.",longDescription:"Reclaim your time with an AI executive assistant team. Your leader triages incoming emails by priority and urgency, while your assistant handles responses, sets calendar reminders, and prepares briefing documents before meetings. Think of it as a chief of staff that keeps your information flow organized and your schedule on track.",tags:["email","calendar","meetings","productivity"],features:["Email triage and priority classification","Meeting preparation briefs and agendas","Calendar reminder management","Follow-up tracking and nudges","Daily schedule digest","Response drafting for routine communications"],useCases:[{title:"Busy founders",description:"Stay on top of communications without drowning in your inbox."},{title:"Executives",description:"Never miss a follow-up or walk into a meeting unprepared."},{title:"Consultants",description:"Manage multiple client communications with consistent, timely responses."}],baseScenario:"personal-assistant",members:[{role:"leader",description:"Triages emails by priority and coordinates your daily workflow",instructions:`You are the executive coordinator. You manage information flow and ensure nothing important falls through the cracks.
+- Set calendar reminders for optimal publishing times.`,relationship:"Delegate post creation with: topic or content to repurpose, target platform, tone, and publish timing.\n\nReport back with: post drafts ready for review, trending topics spotted, and calendar reminders set for publishing."}]},{id:"executive-assistant",name:"Executive Assistant",category:"Knowledge Worker",icon:"💼",description:"Filter and prioritize emails, manage calendar reminders, and prepare meeting briefs.",longDescription:"Reclaim your time with an AI executive assistant team. Your leader triages incoming emails by priority and urgency, while your assistant handles responses, sets calendar reminders, and prepares briefing documents before meetings. Think of it as a chief of staff that keeps your information flow organized and your schedule on track.",tags:["email","calendar","meetings","productivity"],features:["Email triage and priority classification","Meeting preparation briefs and agendas","Calendar reminder management","Follow-up tracking and nudges","Daily schedule digest","Response drafting for routine communications"],useCases:[{title:"Busy founders",description:"Stay on top of communications without drowning in your inbox."},{title:"Executives",description:"Never miss a follow-up or walk into a meeting unprepared."},{title:"Consultants",description:"Manage multiple client communications with consistent, timely responses."}],baseScenario:"personal-assistant",members:[{role:"leader",description:"Triages emails by priority and coordinates your daily workflow",instructions:`You are the executive coordinator. You manage information flow and ensure nothing important falls through the cracks.
 
 ## Principles
 - Protect the user's time. Only escalate what truly needs their input — handle everything else autonomously or via delegation.
@@ -128,7 +128,7 @@ module.exports=[458682,a=>{"use strict";let b=[{id:"open-source-maintainer",name
 - Meeting briefs: attendees + context, purpose, background (2-3 sentences), user's goals, and prep needed.
 - Track follow-ups: flag items with no response after 48 hours. Maintain a running list of pending commitments.
 - Be concise and precise — respect everyone's time.
-- Never send without leader review for anything beyond routine acknowledgments.`,relationship:{leaderSees:"Delegate response drafting, calendar reminders, and meeting brief preparation. Specify: formality level, deadline, and whether user review is needed before sending.",memberSees:"Report back with: drafts ready for review, reminders set, briefs prepared, and items pending response for 48+ hours."}}]},{id:"research-analyst",name:"Research Analyst",category:"Knowledge Worker",icon:"🔬",description:"Monitor competitors, analyze industry trends, and deliver weekly research digests via email.",longDescription:"Stay ahead of your market with an AI research team. Your researcher continuously monitors competitors, tracks industry trends, and gathers intelligence from public sources. Your leader synthesizes findings into actionable insights and delivers structured reports via email. From daily monitoring to weekly deep-dives — systematic intelligence gathering on autopilot.",tags:["research","competitive intelligence","analysis","reports"],features:["Competitor activity monitoring and change detection","Industry trend analysis and signal identification","Weekly research digest email with key findings","Deep-dive reports on specific topics on demand","Source tracking and reliability assessment","Market signal early warning"],useCases:[{title:"Product managers",description:"Keep a pulse on competitor moves and market shifts without spending hours on research."},{title:"Founders",description:"Make informed strategic decisions with continuous market intelligence."},{title:"Investors",description:"Track portfolio company markets and identify emerging opportunities."}],baseScenario:"content-research",members:[{role:"leader",description:"Synthesizes research into actionable insights and delivers reports",instructions:`You are the research lead. You direct research priorities, synthesize findings, and deliver actionable intelligence.
+- Never send without leader review for anything beyond routine acknowledgments.`,relationship:"Delegate response drafting, calendar reminders, and meeting brief preparation. Specify: formality level, deadline, and whether user review is needed before sending.\n\nReport back with: drafts ready for review, reminders set, briefs prepared, and items pending response for 48+ hours."}]},{id:"research-analyst",name:"Research Analyst",category:"Knowledge Worker",icon:"🔬",description:"Monitor competitors, analyze industry trends, and deliver weekly research digests via email.",longDescription:"Stay ahead of your market with an AI research team. Your researcher continuously monitors competitors, tracks industry trends, and gathers intelligence from public sources. Your leader synthesizes findings into actionable insights and delivers structured reports via email. From daily monitoring to weekly deep-dives — systematic intelligence gathering on autopilot.",tags:["research","competitive intelligence","analysis","reports"],features:["Competitor activity monitoring and change detection","Industry trend analysis and signal identification","Weekly research digest email with key findings","Deep-dive reports on specific topics on demand","Source tracking and reliability assessment","Market signal early warning"],useCases:[{title:"Product managers",description:"Keep a pulse on competitor moves and market shifts without spending hours on research."},{title:"Founders",description:"Make informed strategic decisions with continuous market intelligence."},{title:"Investors",description:"Track portfolio company markets and identify emerging opportunities."}],baseScenario:"content-research",members:[{role:"leader",description:"Synthesizes research into actionable insights and delivers reports",instructions:`You are the research lead. You direct research priorities, synthesize findings, and deliver actionable intelligence.
 
 ## Principles
 - Lead with "So what?" — why should the user care? Don't report facts; interpret them, connect dots, recommend actions.
@@ -142,7 +142,7 @@ module.exports=[458682,a=>{"use strict";let b=[{id:"open-source-maintainer",name
 - Always include source URL and date. Distinguish confirmed facts from rumors/speculation.
 - Cross-reference important claims with multiple sources. Flag outdated or unreliable info.
 - Identify signals: unusual activity, pattern breaks, emerging trends.
-- Organize findings categorized for the leader to synthesize: discoveries, notable signals, sources, and confidence assessment.`,relationship:{leaderSees:"Delegate monitoring with: competitors to track, signals to watch for, sources to check, and reporting cadence.",memberSees:"Report back with: categorized findings (discoveries, signals, sources), confidence per claim, and items flagged for urgency."}}]},{id:"client-ops",name:"Client Ops",category:"Freelancer",icon:"🤝",description:"Auto-reply to client inquiries, schedule meetings, send follow-ups, and manage project communications.",longDescription:"Never miss a client email again. Your leader manages client relationships and prioritizes communications, while your assistant drafts professional responses, schedules meetings, and sends timely follow-ups. Perfect for freelancers and consultants who want to appear responsive and organized without being glued to their inbox all day.",tags:["clients","freelance","email","scheduling"],features:["Automatic acknowledgment of new client inquiries","Professional response drafting for common questions","Meeting scheduling with availability coordination","Follow-up reminders for pending proposals and invoices","Project update email drafting","Client onboarding email sequence"],useCases:[{title:"Freelancers",description:"Look professional and responsive while focusing on actual client work."},{title:"Consultants",description:"Manage multiple client relationships without dropping any balls."},{title:"Small agencies",description:"Scale client communications without hiring a dedicated account manager."}],baseScenario:"personal-assistant",members:[{role:"leader",description:"Manages client relationships and prioritizes communications",instructions:`You are the client relationship coordinator. You ensure every client feels taken care of and nothing falls through the cracks.
+- Organize findings categorized for the leader to synthesize: discoveries, notable signals, sources, and confidence assessment.`,relationship:"Delegate monitoring with: competitors to track, signals to watch for, sources to check, and reporting cadence.\n\nReport back with: categorized findings (discoveries, signals, sources), confidence per claim, and items flagged for urgency."}]},{id:"client-ops",name:"Client Ops",category:"Freelancer",icon:"🤝",description:"Auto-reply to client inquiries, schedule meetings, send follow-ups, and manage project communications.",longDescription:"Never miss a client email again. Your leader manages client relationships and prioritizes communications, while your assistant drafts professional responses, schedules meetings, and sends timely follow-ups. Perfect for freelancers and consultants who want to appear responsive and organized without being glued to their inbox all day.",tags:["clients","freelance","email","scheduling"],features:["Automatic acknowledgment of new client inquiries","Professional response drafting for common questions","Meeting scheduling with availability coordination","Follow-up reminders for pending proposals and invoices","Project update email drafting","Client onboarding email sequence"],useCases:[{title:"Freelancers",description:"Look professional and responsive while focusing on actual client work."},{title:"Consultants",description:"Manage multiple client relationships without dropping any balls."},{title:"Small agencies",description:"Scale client communications without hiring a dedicated account manager."}],baseScenario:"personal-assistant",members:[{role:"leader",description:"Manages client relationships and prioritizes communications",instructions:`You are the client relationship coordinator. You ensure every client feels taken care of and nothing falls through the cracks.
 
 ## Principles
 - Never leave a client waiting: acknowledge every email within 4 hours (even just "received, will respond by X").
@@ -156,7 +156,7 @@ module.exports=[458682,a=>{"use strict";let b=[{id:"open-source-maintainer",name
 - Always include a clear next step or timeline. For scheduling: offer 3 specific time options.
 - For follow-ups: be helpful, not pushy — "Checking in on X, let me know if you need anything."
 - For updates: lead with progress, then next steps, then blockers.
-- Set calendar reminders for all follow-up actions. Never let a commitment drop silently.`,relationship:{leaderSees:"Delegate client communications with: client name, email type (acknowledgment, update, follow-up, scheduling), urgency, and tone.",memberSees:"Report back with: draft ready for review, meetings scheduled, reminders set, and follow-ups due."}}]},{id:"weekly-report-bot",name:"Weekly Report Bot",category:"Freelancer",icon:"📊",description:"Summarize your week's work from git, emails, and calendar into a structured report delivered to your inbox.",longDescription:"End every week with a clear picture of what happened. Your researcher gathers data from your work streams — git commits, emails sent/received, and calendar events — then your leader synthesizes everything into a structured weekly report. Great for freelancers tracking time, managers needing team summaries, or anyone who wants to reflect on their productivity.",tags:["reports","productivity","summary","weekly review"],features:["Git activity summarization (commits, PRs, reviews)","Email communication summary (key threads, outstanding items)","Calendar event recap and time allocation analysis","Weekly highlight and accomplishment extraction","Blocker and carry-over identification","Automated report delivery every Friday via email"],useCases:[{title:"Freelancers",description:"Track your billable work and create client-ready activity reports effortlessly."},{title:"Remote workers",description:"Keep your manager informed with structured weekly updates without the Friday scramble."},{title:"Team leads",description:"Generate team activity summaries for standups and stakeholder updates."}],baseScenario:"content-research",members:[{role:"leader",description:"Synthesizes activity data into a structured weekly report",instructions:`You are the report coordinator. You turn raw activity data into a clear, insightful weekly summary.
+- Set calendar reminders for all follow-up actions. Never let a commitment drop silently.`,relationship:"Delegate client communications with: client name, email type (acknowledgment, update, follow-up, scheduling), urgency, and tone.\n\nReport back with: draft ready for review, meetings scheduled, reminders set, and follow-ups due."}]},{id:"weekly-report-bot",name:"Weekly Report Bot",category:"Freelancer",icon:"📊",description:"Summarize your week's work from git, emails, and calendar into a structured report delivered to your inbox.",longDescription:"End every week with a clear picture of what happened. Your researcher gathers data from your work streams — git commits, emails sent/received, and calendar events — then your leader synthesizes everything into a structured weekly report. Great for freelancers tracking time, managers needing team summaries, or anyone who wants to reflect on their productivity.",tags:["reports","productivity","summary","weekly review"],features:["Git activity summarization (commits, PRs, reviews)","Email communication summary (key threads, outstanding items)","Calendar event recap and time allocation analysis","Weekly highlight and accomplishment extraction","Blocker and carry-over identification","Automated report delivery every Friday via email"],useCases:[{title:"Freelancers",description:"Track your billable work and create client-ready activity reports effortlessly."},{title:"Remote workers",description:"Keep your manager informed with structured weekly updates without the Friday scramble."},{title:"Team leads",description:"Generate team activity summaries for standups and stakeholder updates."}],baseScenario:"content-research",members:[{role:"leader",description:"Synthesizes activity data into a structured weekly report",instructions:`You are the report coordinator. You turn raw activity data into a clear, insightful weekly summary.
 
 ## Principles
 - Report structure: Highlights (top 3-5 wins), Work completed (by project), In progress, Blockers (with next steps), Next week priorities, Time allocation.
@@ -170,6 +170,6 @@ module.exports=[458682,a=>{"use strict";let b=[{id:"open-source-maintainer",name
 - Email: focus on decision-bearing threads, not noise. Track important decisions and outstanding items.
 - Calendar: note meeting purposes (not just titles), total meeting time, productive vs. overhead estimate.
 - Include: feature work, bug fixes, reviews, important decisions, client comms. Exclude: automated notifications, spam.
-- Flag data gaps (e.g., calendar empty on a day — PTO or just no meetings?). Highlight completed milestones.`,relationship:{leaderSees:"Delegate data gathering with: time range, sources to check (git, email, calendar), and focus areas or projects to highlight.",memberSees:"Report back with: raw activity data organized by source, milestones completed, data gaps flagged, and items needing interpretation."}}]}];a.s(["TEMPLATES",0,b,"getTemplateById",0,function(a){return b.find(b=>b.id===a)}],458682)}];
+- Flag data gaps (e.g., calendar empty on a day — PTO or just no meetings?). Highlight completed milestones.`,relationship:"Delegate data gathering with: time range, sources to check (git, email, calendar), and focus areas or projects to highlight.\n\nReport back with: raw activity data organized by source, milestones completed, data gaps flagged, and items needing interpretation."}]}];a.s(["TEMPLATES",0,b,"getTemplateById",0,function(a){return b.find(b=>b.id===a)}],458682)}];
 
 //# sourceMappingURL=src_web_src_lib_templates_index_ts_13n9_2e._.js.map

package/bundled/web/.open-next/server-functions/default/src/web/.next/server/middleware-build-manifest.js

@@ -7,9 +7,9 @@ globalThis.__BUILD_MANIFEST = {
     "static/chunks/03~yq9q893hmn.js"
   ],
   "lowPriorityFiles": [
-    "static/x-lS9KPn-DIgZqdgRNu_9/_buildManifest.js",
-    "static/x-lS9KPn-DIgZqdgRNu_9/_ssgManifest.js",
-    "static/x-lS9KPn-DIgZqdgRNu_9/_clientMiddlewareManifest.js"
+    "static/LCMVDfuuzs8SMP0bLdwOY/_buildManifest.js",
+    "static/LCMVDfuuzs8SMP0bLdwOY/_ssgManifest.js",
+    "static/LCMVDfuuzs8SMP0bLdwOY/_clientMiddlewareManifest.js"
   ],
   "rootMainFiles": [
     "static/chunks/0fus_woghk6f3.js",

package/bundled/web/.open-next/server-functions/default/src/web/.next/server/middleware-manifest.json

@@ -25,11 +25,11 @@
       "wasm": [],
       "assets": [],
       "env": {
-        "__NEXT_BUILD_ID": "x-lS9KPn-DIgZqdgRNu_9",
-        "NEXT_SERVER_ACTIONS_ENCRYPTION_KEY": "RahY5VqSREIWK1YKT+vTxCSY6F/jWHeBP0ogfoQIrA0=",
-        "__NEXT_PREVIEW_MODE_ID": "b88d08f32668eac14d3508bb8bc9f293",
-        "__NEXT_PREVIEW_MODE_ENCRYPTION_KEY": "5d103faa4d4896d58d0d77842aa8efc213dbc22df26dbdf66656afd8836ca1ce",
-        "__NEXT_PREVIEW_MODE_SIGNING_KEY": "67961328b24bf29e863cfd996078bca160e4bb2cfcc4f88eff67f84f2598c0a1"
+        "__NEXT_BUILD_ID": "LCMVDfuuzs8SMP0bLdwOY",
+        "NEXT_SERVER_ACTIONS_ENCRYPTION_KEY": "rxNO1maOB5YFhM3mbwdlMIw5HIWtlIpzXR5HRqlz0EU=",
+        "__NEXT_PREVIEW_MODE_ID": "c92380fa625e39aa4341694cce90fc5f",
+        "__NEXT_PREVIEW_MODE_ENCRYPTION_KEY": "b5c20c0bc8b0c7c51572e2b7996b627b4fd062fb6125be43597a9c312e667d86",
+        "__NEXT_PREVIEW_MODE_SIGNING_KEY": "4c9f6486a2e8b91e91f881fca9018df4b6e9f55c951255287e0f071aff514e24"
       }
     }
   },

package/bundled/web/.open-next/server-functions/default/src/web/.next/server/server-reference-manifest.js

@@ -1 +1 @@
-self.__RSC_SERVER_MANIFEST="{\n  \"node\": {},\n  \"edge\": {},\n  \"encryptionKey\": \"RahY5VqSREIWK1YKT+vTxCSY6F/jWHeBP0ogfoQIrA0=\"\n}"
+self.__RSC_SERVER_MANIFEST="{\n  \"node\": {},\n  \"edge\": {},\n  \"encryptionKey\": \"rxNO1maOB5YFhM3mbwdlMIw5HIWtlIpzXR5HRqlz0EU=\"\n}"

package/bundled/web/.open-next/server-functions/default/src/web/.next/server/server-reference-manifest.json

@@ -1,5 +1,5 @@
 {
   "node": {},
   "edge": {},
-  "encryptionKey": "RahY5VqSREIWK1YKT+vTxCSY6F/jWHeBP0ogfoQIrA0="
+  "encryptionKey": "rxNO1maOB5YFhM3mbwdlMIw5HIWtlIpzXR5HRqlz0EU="
 }