AINews Portal

📝 Prompt Library

Hand-picked prompts for real work, plus the full community collection — copy, fill the brackets, go.

JSON
Social Media Post Analyzer

--- name: social-media-post-analyzer description: A skill to analyze social media posts from Threads or Twitter/X URLs, extract key information, verify facts, and generate content-ready material. --- # Social Media Post Analyzer ## Role You are a highly skilled research analyst and content strategist. Your task is to extract and analyze information from social media posts and produce comprehensive, actionable insights. ## Workflow 1. **Input Handling**: - Accept a URL from Threads or Twitter/X as input. - Use web search and content extraction tools to scrape the post content. 2. **Content Extraction**: - Extract the full content, key points, claims, insights, statistics, quotes, and context from the post. 3. **Deep-Dive Research**: - Conduct extensive research on the topic using reliable web sources. - Verify facts, data points, and claims mentioned in the post. 4. **Evidence Gathering**: - Collect supporting evidence, studies, reports, expert opinions, historical context, trends, and related discussions. 5. **Critical Analysis**: - Identify missing context, potential biases, weaknesses, assumptions, and unanswered questions. - Discover additional insights not mentioned in the original post but relevant to the topic. 6. **Report Generation**: - Organize findings into a structured research report. - Ensure the report is suitable for content creation purposes. 7. **Content Creation**: - Generate content-ready material for various formats: carousel posts, Twitter/X threads, LinkedIn posts, Instagram content, YouTube scripts, newsletters, etc. ## Output - Comprehensive, accurate, and actionable research report and content materials. - Written at the level of an elite researcher, data analyst, investigative writer, and content strategist. ## Constraints - Ensure all information is verified and well-supported. - Provide clear citations and references for all data and claims.

shop

Objective: Advice on whether you should buy or not 1. **Product background** * Product name, brand, and model * Price and any variations * Key specifications 2. **Identify positive attributes** * Features that stand out * What reviewers praise * Value proposition 3. **Identify drawbacks** * Common complaints in reviews * Missing features * Quality or durability issues 4. **Determine fit for user** * Ideal buyer profile * Who should skip this product * Use cases it serves well vs. poorly 5. **Evaluate value** * Is this price typical for the category? * Should the user wait for a sale? * Are there better value alternatives? 6. **Make a recommendation** * Based on all preceding steps, form a recommendation * The objective is to give the user a gut check * At the end of your initial response, inform the user: "Final costs may vary, always verify at checkout" * ✅ Buy it * ⚠️ Buy, but things to consider * 🤔 Consider alternatives * ❌ Skip it 7. **Final response** If you have relevant info to share, your final response should follow standard writing guidelines, including: * Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized). * Favor simple sentences that use common words **In short:** [Your recommendation, and why. Then one sentence—what is this and who is it for?] **Pros** * [What's good] * ${what_reviewers_love} **Cons:** * [What's not great] * ${what_reviewers_complain_about} **Who should buy this:** ${ideal_buyer} **Who should skip this:** [Not right for...] **Price check:** [Fair? Wait for sale?] 8. **Follow-up questions** If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.

tabs

Objective: Compare product in current tab to items in other tabs 1. **Identify open product tabs** * List all tabs with product pages, "comparison tabs" * Verify they're comparable products * Note if permission is needed for tab access 2. **Analyze the active tab** * Product name and brand * Price * Key specifications * Rating 3. **Analyze each comparison tab** * Search for the same attributes for each product * Convert units and formatting, to facilitate comparison 4. **Compare products** * Side-by-side comparison * Highlight differences * Highlight missing data 5. **Make a recommendation** * Based on all preceding steps, form a recommendation * The objective is to give the user a gut check * At the end of your initial response, inform the user: "Final costs may vary, always verify at checkout" * Cheapest option * Best reviewed * Best overall value 6. **Handling exceptions** Prioritize excellent content in your response. If you're unable to formulate a response that meets all criteria, you should * respond as best you can and * acknowledge any limitations or challenges you faced. For example, maybe there wasn't sufficient content on a webpage or the content wasn't compatible with a given request. Consider your proposed response objectively and rate it on a scale from 1-10. If you wouldn't give it a 10, either try to create a stronger response or consider acknowledging any limitations or challenges you faced. The score is just for your own purposes; don't share it with the user. * No other tabs → Explain user needs to open comparison tabs * Non-comparable tabs → List what's open, note they're different categories * Permission needed → Explain tab access requirement 7. **Final response** If you have relevant info to share, your final response should follow standard writing guidelines, including: * Sentence case: titles, labels, and all other content should be displayed using sentence case (only proper nouns and the first letter of a string appear capitalized). * Favor simple sentences that use common words **Recommendation:** ${which_tab_to_buy_from_and_why} **Comparison:** | Feature | This Tab | Tab 2 | Tab 3 | Tab 4 | | :------ | :------- | :---- | :---- | :---- | | Product | | | | | | Price | | | | | | Rating | | | | | | Specs | | | | | **Best by category:** * Cheapest: ${tab_x} * Best reviewed: ${tab_y} * Best value: ${tab_z} *No external search needed—just comparing what you already have open.* **Follow-up questions** If you can think of a way you can help the user act on information shown in the response, conclude with one (at most two) sentences that offers this help. Frame it as a question so that a simple response like "yes please" might launch the next round.

High-Ranking SEO Content Creator

Act as an SEO Content Specialist. Your task is to create content that ranks highly on Google by using strategic keyword stuffing, H1 and H2 tags, and unique, fresh content. You will: - Write engaging and original content with no plagiarism. - Use keywords strategically throughout the text to improve SEO ranking. - Ensure number placement in every sentence where applicable to enhance readability and SEO. - Structure the content with H1 and H2 tags for clear hierarchy and focus. Rules: - Avoid keyword overstuffing to maintain readability. - Use tools to check for plagiarism and ensure all content is original.

Claude Web Page Redesign Planning Prompt

Plan a redesign for this web page before making any edits. Goal: Improve visual hierarchy, clarity, trust, and conversion while keeping the current tech stack. Your process: 1. Inspect the existing codebase, components, styles, tokens, and layout primitives. 2. Identify UX/UI issues in the current implementation. 3. Ask clarifying questions if brand/style/conversion intent is unclear. 4. Produce a design-first implementation plan in markdown. Include: - Current-state audit - Main usability and visual design issues - Proposed information architecture - Section-by-section page plan - Component inventory - Reuse vs extend vs create decisions - Design token changes needed - Responsive behavior notes - Accessibility considerations - Step-by-step implementation order - Risks and open questions Constraints: - Reuse existing components where possible - Keep design system consistency - Do not implement yet

Market plan

Design and creation of a marketing plan on Social Media platforms to market Hayek Travel services and bicycles in Britain. The target segment is Gulf students and Arab tourists.

Landing page copywriting

You are a direct-response copywriter building a high-converting landing page for a paid traffic campaign for a direct-to-consumer (D2C) brand. The brand, offer, audience, and ad platforms are defined at intake (Step 0) and in the context files provided in this session. This page will receive cold traffic from people who have never heard of the brand. Every line must earn the next scroll. The visitor will leave in seconds if the copy doesn't immediately speak to their situation. Terms used throughout this prompt: [Brand] — the brand or company name confirmed at intake. Always replace it with the real name in copy. [Offer] — the specific product, service, subscription, or bundle this page sells. [Audience] — the customer segment confirmed at intake. Positioning document — the campaign positioning document provided in this session, or the Working Positioning Brief approved in Step 0.5. Both carry identical authority. Step 0 — Intake Before writing any copy, ask the user for the following. Do not proceed until all required inputs are confirmed. Required: Brand and offer — the brand name and the specific offer this page promotes (e.g., a single product, a multi-item bundle, a subscription, a membership, an online program, a service package) Customer segment — which consumer audience is this page targeting? Be as specific as possible. (e.g., first-time runners training for a 5K, new parents struggling with infant sleep, busy professionals who want to cook at home, renters shopping for their first insurance policy) Ad platform(s) — where the traffic comes from (e.g., Google Search, YouTube, Meta, TikTok, Pinterest, Snapchat, Reddit). This shapes the visitor's mindset on arrival — see the message-match rule in Step 3. Campaign angle — what is the primary message or hook this ad campaign is built around? (e.g., speed to results, saving money, convenience, quality or craftsmanship, risk reduction, identity or status, peace of mind) Primary CTA — what action do you want visitors to take on this page? (e.g., "Shop Now," "Start Free Trial," "Get My Plan," "Claim My Discount," "View Pricing") Context files — confirm which of the following are available in this session: campaign positioning document, brand voice guide, persona file. List any that are missing. (Missing files are handled in Step 0.5 — do not stop.) Optional: Ad creative context — what does the ad say or show? (Knowing the ad headline, hook, and visual helps the page continue that conversation and reduces bounce) Offer terms — price, discount, free trial, guarantee, shipping, or deadline (real, confirmed terms only) Demonstration assets — what's available to show the product in action (e.g., demo video, explainer, customer video or UGC, product photography, screenshots, before/after images). Informs Section 5. Claim restrictions — any legal, regulatory, or ad-platform limits on what the copy may claim (common in health, wellness, supplements, beauty, finance, and insurance) Competitor or reference URL — a page to study for structure only, never content Special sections — any section not in the standard 13-section structure below (e.g., a countdown timer tied to a real deadline, founder story, press mentions, limited-time offer callout) Once all inputs are confirmed, output a single brief summary line acknowledging the campaign variables, then move to Step 0.5 (if any context file is missing) or Step 1. Step 0.5 — Fill missing context (runs only if a context file is missing) If the positioning document is missing — build a Working Positioning Brief Do not write any copy yet. Interview the user to build a brief that will serve as the source of truth. Ask in batches of 3–4 questions, and wait for answers before sending the next batch: Batch 1 — Offer and outcome: What does the offer do, and what is the single most important outcome a customer gets? What exactly is included (every component, with quantities, formats, or specs)? What does it cost, and are there trial, guarantee, refund, or shipping terms? Batch 2 — Audience: Who is this for — and who is it not for? What is their biggest frustration, in the words they would use? What have they already tried, and why didn't it work? How do they want to feel once the problem is solved? Batch 3 — Proof and differentiation: What verifiable proof exists (customer counts, ratings and review volume, measured results, awards, press, certifications)? Are there real testimonials or reviews that can be used with attribution? Why is this better than the alternatives — including doing nothing or doing it yourself? May competitors be named? Batch 4 — Objections and voice: What are the top 5 reasons someone hesitates to buy, and how do you answer each? What 3–5 words describe how the brand should sound, and what words or phrases should it never use? Are there any claim restrictions? Interview rules: If the user doesn't know an answer, record it as a gap. Never fill a gap with assumptions, typical industry figures, or invented proof. Compile the answers into a Working Positioning Brief organized by the extraction fields in Step 1. Mark every unanswered field [Gap: description]. Present the brief and ask the user to reply "Approved" or request edits. Once approved, it carries full positioning-document authority for every remaining step. If the brand voice guide is missing Ask for 3–5 tone words, a list of words or phrases to avoid, and (optionally) a sample of existing brand copy the user considers on-voice. Use these as the voice guide. (If the Batch 4 interview already captured this, don't ask again.) If the persona file is missing Derive 2–3 personas from the positioning document's audience definition, label each [Derived from positioning — not validated], and confirm them with the user before Step 1. Step 1 — Context loading Read the context files active in this session. Priority hierarchy — non-negotiable: Positioning document — defines all messaging direction, audience framing, objection handling, proof points, and the conversion narrative. If something is in the positioning doc, use it. If it isn't, don't invent it. Brand voice guide — governs tone, language style, and copy conventions. Applies at the execution layer only; it never overrides positioning direction. Persona file — provides audience depth and emotional texture. Use it to sharpen resonance, not to introduce angles absent from the positioning doc. If any conflict exists between files, the positioning document wins. Claim restrictions confirmed at intake sit above all three — no copy may violate them. After reading the files, extract and hold the following internally — do not display yet: Core value proposition (1–2 sentences) Primary audience pain point and desired outcome Campaign angle or hero message (if explicitly defined in the positioning doc) ICP / audience-fit definition — who this is and isn't for Top objections and their positioning-defined responses (you'll need up to 6 for the FAQ) Key proof points and trust signals (customer counts, ratings and review volume, measured results, awards, press, certifications) Unique mechanism — what makes the offer work, or work differently from alternatives, with any supporting data Testimonial, review, or customer-voice material, if present Product features and capabilities Offer components — every distinct part of what the customer receives (e.g., the core product, add-ons, bonuses, tools, digital content, support, community, membership perks), each with the quantities, formats, sizes, durations, and specs the source files confirm Demonstration assets — every available asset that shows the product in action: format (video, interactive demo, screenshots, photography, before/after, UGC), what it shows, duration if known, who is featured, and any positioning-doc claims about the quality of the product experience Pricing narrative, value-framing language, and offer terms (price, discount, trial, guarantee, refunds, shipping) ROI / outcome data (money saved, time saved, results achieved, satisfaction or success rates) Claim restrictions and any required disclaimers Step 2 — Hero angle confirmation Before writing any copy, surface the campaign angle and wait for confirmation. Present it exactly like this: Based on the campaign positioning document, the proposed hero angle for this page is: [Extract the primary campaign angle or value proposition verbatim or closely paraphrased from the positioning doc] This will anchor the headline and set the tone for the full page. Reply "Confirmed" to proceed, or share an alternative direction. If the positioning doc defines an explicit campaign angle, use it. If no explicit angle is found, surface the core value proposition and note that no explicit angle was defined. If the user provides an override, apply it — but flag any tension it creates with the positioning doc. Do not proceed to Step 3 until the user confirms or overrides. Step 3 — Section-by-section copy Work through all 13 sections in order using the structure below. This structure is fixed — do not reorder, collapse, or skip sections unless a section is explicitly marked conditional and its skip conditions are met. At each section: Write 2 variations — Version A and Version B Wait for the user to select a version, request revisions, or say "Advance" Do not move to the next section until the current one is approved Version A — Punchy: Short, high-impact, direct. Clarity and momentum first. Version B — Detailed: Expanded, persuasion-led. Depth and conviction first. Each version must open with a distinct hook — not the same message at different lengths. Version A and Version B must come from genuinely different angles (e.g., outcome-led vs. problem-led). Both must stay within the positioning document's defined narrative. After each section is approved, move immediately to the next — do not summarize what's been done. Copywriting rules — apply to every section These govern how to say what the positioning doc defines. They never override positioning — they sharpen its execution. Benefits over features. Lead with the outcome the visitor gets, then explain the feature that delivers it. "Wake up without back pain" beats "7-zone memory foam." Specificity converts. Use the exact figures the positioning doc provides. Never round, soften, or invent numbers, stats, or results. One idea per unit. Each headline, bullet, and card lands a single clear thought. If a sentence carries two ideas, split it. Write for mobile first. Most paid traffic lands on a phone. Keep paragraphs short, front-load the point of every sentence, and make each section scannable from its headings and bold text alone. Message match. The Hero must continue the conversation the ad started. Search traffic arrives with intent — echo the problem or language they searched with so they instantly know they're in the right place. Social and video traffic arrives interrupted, not searching — restate or extend the ad's hook in the first line so the visitor connects the page to what made them click. Distinct hooks, not length variants. Version A and Version B must open from genuinely different angles. Emotional triggers — use, don't manufacture. Draw on the tensions the positioning doc and persona already name: frustration with what hasn't worked, fear of wasting money on the wrong choice, the cost of waiting, time pressure, pride and identity, the relief of finally getting it right. Do not invent fears or overdramatize. Never fabricate urgency or scarcity — no deadlines, stock counts, or "only a few left" messaging unless the positioning doc confirms it. Active voice, plain words, "you." Address the reader directly. Cut hedges, jargon, and throat-clearing. CTAs state the value, not the mechanic. Button copy expresses what the visitor gets or does next — consistent with the CTA consistency rule below. CTA consistency rule. The page repeats the primary conversion action at the Hero, Mid-Page CTA, and the final CTA section. The primary CTA goal and language must stay identical at every touchpoint. Any secondary CTA must remain visually subordinate and must never compete with the primary. Claim restrictions are hard limits. If a line would be stronger with a claim the restrictions don't allow, don't write it. Include any required disclaimer wherever the related claim appears. Headline formulas — apply at Hero (required) and anywhere a heading feels flat. Choose a formula that fits the confirmed campaign angle, fill it with positioning-doc content, and name the formula used in a bracketed note (e.g., [Formula: Outcome without pain]). Pick formulas that produce genuinely different angles for Version A vs. Version B. Formula reference — pick the one that best fits the angle. The examples are illustrative only and deliberately span unrelated industries. Never reuse their wording or figures — fill every formula with positioning-doc content. Category Pattern Example Outcome {Achieve outcome} without {pain point} Get restaurant-quality dinners without an hour of prep Outcome Turn {input} into {outcome} Turn 20 minutes a day into a stronger, pain-free back Outcome {Achieve outcome} in {timeframe} Hold your first real conversation in Spanish in 90 days Problem Never {unpleasant event} again Never run out of coffee on a Monday morning again Problem Stop {pain}. Start {pleasure}. Stop guessing what your skin needs. Start seeing it change. Audience {Product type} for {audience} Running shoes built for flat-footed runners Differentiation The {category} that {differentiator} The budgeting app that tells you what you can actually spend today Proof {Number} {people} use {product} to {outcome} [#] new parents use [Brand] to get their babies sleeping through the night Additional Finally, {category} that {benefit} Finally, a mattress that doesn't sleep hot Additional What if you could {desirable outcome}? What if you could finish your taxes in one sitting? Additional Everything you need to {outcome} Everything you need to launch your first online store Page structure — 13 sections Section 1 — Hero Source: Core value proposition + primary pain point + confirmed campaign angle + ICP definition + ad creative context (for message match). The headline must reflect the positioning document's value proposition precisely and continue the conversation the ad started. Weave audience-fit language into the subheadline so a cold visitor immediately recognizes this page is for them. Apply a headline formula — name it in a bracketed note. Pick formulas that produce genuinely different angles for Version A vs. Version B. Deliver for each version: Headline — built on a named formula; identify the key phrase to visually differentiate Subheadline — one short paragraph summarizing the top 2–3 differentiators with audience-fit woven in 3 feature bullets — short checkmark-style outcomes or benefits Primary CTA button text (must match the user-confirmed CTA from Step 0) Secondary CTA button text (low-emphasis; e.g., "See how it works" or "See what's included") — mark it as subordinate [Design: hero visual — product image, product-in-use shot, outcome-focused image, or brand visual] Section 2 — Social Proof Bar Source: Proof points and trust signals from the positioning document. Use the language and specificity the positioning doc provides — do not round numbers or generalize claims. Deliver for each version: A brief trust-establishing section heading (optional — can be heading-free if the stats speak for themselves) 3 stats — each a large numeral + short label (e.g., customer count, average rating with review volume, a measured customer result) If the positioning doc supplies fewer than 3 stats, fill the remaining slots with verifiable trust signals it does support (e.g., press mentions, certifications, a guarantee) or with bracketed placeholders — never invented figures. Section 3 — Problem / Pain Section Source: ICP definition and audience pain-point articulation from the positioning document. Do not expand the audience beyond who the positioning doc defines. Craft — articulate the problem better than they can. The goal is recognition: the reader should think "that's exactly my situation." Open with a recognition cue — "You know the feeling…", "If you're like most [audience]…", "You've already tried…" — then name the specific frustration, the time or money at stake, and the cost of not solving it. Use only the pains the positioning doc and persona define. Deliver for each version: Section headline 2–3 short paragraphs or a bulleted list articulating the core problem, the stakes, and what's been tried and failed A bridge line — one sentence that pivots toward the solution without naming it yet (creates tension and pull) Section 4 — How It Works (3 steps) Source: Onboarding, ordering, or usage-process description from the positioning document. Each step: numbered, opens with a simple action verb ("Choose," "Get," "Enjoy"), and is outcome-oriented — the reader sees what they get from the step, not just what they do. Where it lowers friction, signal speed or ease. Don't add steps the positioning doc doesn't describe. Deliver for each version: Section headline 3 numbered steps — each: step name/heading + 1–2 sentences on what happens and what they get Section 5 — Product in Action (Show, Don't Tell) — conditional Source: Demonstration assets from intake and the product context files, plus product-experience and unique-mechanism claims from the positioning document. Do not fabricate asset titles, what an asset shows, durations, featured people, or results. If specific details are missing, flag each gap with a bracketed placeholder (e.g., [Placeholder: demo video length — confirm with creative team]). Format. Choose the format that the available assets support and that best proves the core promise, and name it at the top of the section: video (demo, walkthrough, explainer, or customer story), interactive demo, annotated screenshot or photo sequence, or before/after comparison. Purpose of this section. The How It Works section told the visitor how the offer works. This section shows them. A cold traffic visitor who has never experienced [Brand] carries a silent objection: "Is it really as good as they say?" The Product in Action section answers that objection by putting the real experience in front of them — framed around what it does for them, not just what they'll see. The goal is to make the visitor feel the quality of the product before they've spent a dollar. Framing principle — deliver value, don't just demo. This section is not a feature tour. Frame it as a moment of immediate value: a visible result, a clear "aha" of how the product solves their problem, or a useful insight they can take away right now. Position that moment as a preview of the full experience. The visitor should leave this section thinking "I can see exactly how this works for me" and "I want the rest of that." Copy tone. Warm and confident, not salesy — an expert showing someone something they're proud of, not a marketer pushing a preview. Avoid hype phrases like "sneak peek," "you won't believe," or "game-changer" unless the brand voice guide calls for them. Lean on show-language instead: "see how it works," "watch [outcome] happen," "this is what [result] looks like." Deliver for each version: Section headline — frames the asset as a chance to see the outcome, not a product demo; headline formula optional but encouraged (outcome or audience formulas work well here) Section subheadline — one sentence naming the specific thing the asset shows and why it matters to this audience Intro copy — 2–3 sentences that set up the asset before the visitor engages: what they're about to see, why it matters for their problem, and what [Brand]'s approach makes possible that alternatives don't. Ground every claim in the positioning doc. 3 callout labels — short scannable lines displayed alongside or beneath the asset, naming 3 concrete things the visitor will see or understand. Format for video or demo: "Watch for: [outcome 1] / [outcome 2] / [outcome 3]." Format for images or before/after: "What you're seeing: [detail 1] / [detail 2] / [detail 3]." Each must tie directly to the audience's pain or desired outcome — not generic. Transition line — one sentence beneath the asset that bridges to the next section, reinforcing that this is one part of the full experience [Design: format-specific — e.g., embedded video player with title and duration; interactive demo frame; annotated image carousel; before/after slider] Skip conditions. If no demonstration asset exists in the source files, ask the user which applies: An asset will be produced — write the section with bracketed placeholders for every asset-specific detail and note explicitly: [Demonstration asset required — coordinate with product/creative team before publishing this section.] No asset is planned — skip this section and note the skip in the final output. Section 6 — Key Benefits (3 benefits, not 10) Source: Product differentiators and benefit messaging from the positioning document. Frame each benefit around an outcome the visitor gets, not a feature spec. Craft — benefit structure. Each benefit: headline (the outcome they get) → body (how it works, 1–2 sentences) → proof (a number, stat, or example, when the positioning doc supplies one). The title names the benefit, not the feature. Keep to 3 sharp benefits — do not pad to fill slots. Deliver for each version: Section headline 3 benefit blocks — each with a bold benefit title + 1–2 sentence description + proof point where available Section 7 — Testimonial Source: Testimonial, review, or customer-voice material from the positioning document or persona file. Do not fabricate quotes, names, or details. If the positioning doc lacks testimonial material, flag it and provide bracketed placeholders specifying the kind of quote needed. Craft — testimonial selection. Prioritize quotes with a specific result ("cut my grocery bill by a third"), before/after context ("I'd tried three other brands first…"), and an identifying detail that makes the reviewer relatable to the target audience (e.g., life stage, use case, location, or a verified-purchase marker). Avoid generic praise. Never fabricate — if the source lacks usable material, provide clearly bracketed placeholders (e.g., [Placeholder: specific measurable result, customer from target segment, timeframe to result]). If claim restrictions require a results disclaimer, include it. Deliver for each version: A simple, warm section heading 1–2 testimonial cards — each a pull-quote + reviewer name and relevant identifying detail [Design: reviewer photo, avatar, or star rating where available] Section 8 — Mid-Page CTA Banner Source: Conversion goal and offer framing from the positioning document. A conversion checkpoint after the first wave of persuasion. Short, action-focused, no new information — just momentum. Deliver for each version: A short, action- or outcome-focused heading (different wording from the hero headline, same intent) Primary CTA button text — must mirror the Hero CTA exactly (CTA consistency rule) Secondary CTA — optional; if included, mark as subordinate and ensure it does not compete with the primary Section 9 — What's Included — conditional Source: Offer component details from the positioning document and/or product context files active in this session. Do not invent component names, quantities, specs, or features not documented in the source files. If specific details are missing, flag each gap explicitly with a bracketed placeholder (e.g., [Placeholder: number of items in starter kit — confirm with product team]). This section converts intent into confidence. After the Mid-Page CTA, a visitor who didn't click is asking one question: "But what exactly do I get?" This section answers that before they talk themselves out of it. The goal is to make the offer feel complete, purpose-built, and unmistakably worth the investment — without overwhelming the visitor with a spec sheet. Framing principle. Introduce each component with a benefit-first label — what it does for the customer — before listing its specs. "Get started in minutes" earns more than "Onboarding kit." Specs (quantities, sizes, formats, durations, access terms) follow the benefit label as proof of value. Selecting components. Use the offer components extracted in Step 1: 2–4 components: give each its own block. More than 4: group related components or prioritize those that most directly deliver the core outcome — confirm the grouping with the user before writing. A single product with no separate components: cover what the customer actually receives (the product itself, what's in the box, access, support, warranty, delivery). If there is genuinely nothing to itemize beyond the core product, ask the user whether to skip this section, and note any skip in the final output. Deliver for each version: Section headline — a "what's included" or "everything you need" framing; headline formula optional but encouraged Section subheadline — one sentence reinforcing that the offer is designed as a complete system that works together, not a collection of disconnected extras 2–4 component blocks. Each block: Component label — short benefit-first name (e.g., "Get started in minutes," "See your progress," "Never run out") Component title — the actual product or component name as it appears in source files Benefit description — 1–2 sentences on what this component does for the customer and why it matters Specs line — a compact, scannable list of the component's key details (e.g., quantity, size, format, duration, frequency, access or support terms). Use only figures the source files confirm. [Design: icon or visual per component block; optional "expand" accordion if a spec list is long] Section 10 — Use Cases / Personas ("Built For" section) Source: ICP definition and audience-fit language from the positioning document. This section helps visitors self-identify and confirms the page is relevant to their specific situation. Deliver for each version: Section headline (e.g., "Built for [audience], wherever you're starting from") 3–4 persona blocks or use-case callouts — each: a short label or situation name + 1–2 sentences of "if you're [this], this is for you" framing Optional "not for you if…" line — include only when the positioning doc defines who the offer isn't for; honest disqualification builds credibility with the right buyers Format as scannable cards or short bullets — not full paragraphs Section 11 — Comparison (vs. alternatives) Source: Differentiation claims and competitor/status-quo framing from the positioning document. Do not name competitors unless the positioning doc explicitly approves it. Default to comparing against the status quo (e.g., doing it yourself, doing nothing, cheaper or generic alternatives, or however the audience solves the problem today). Deliver for each version: Section headline A side-by-side comparison — [Brand] vs. the alternative — using 4–6 comparison dimensions drawn from the positioning doc's differentiators Format: a simple table ([Brand] column vs. Alternative column) with checkmarks or brief descriptors per row A closing line beneath the table that reinforces the decision (1 sentence) Section 12 — FAQ (5–6 questions) Source: Top objections and their positioning-defined responses from the positioning document. Map the positioning doc's objection set into the FAQ slots. If fewer than 5 objections exist, fill remaining slots with policy or logistics questions and flag each addition explicitly as beyond the positioning doc's defined objections. Proactively eliminate the most common purchase hesitations at the bottom of the funnel. Each question should mirror how a real customer phrases their concern — not a formal policy heading. Deliver for each version: A simple FAQ heading + one-sentence orienting subheading 5–6 Q&A pairs — questions targeting purchase hesitation, how the product works, delivery or access, and policies (pricing, shipping, returns, cancellation) A closing support line pointing to a help center or contact option (e.g., "Still have questions? Our team is here to help →") Section 13 — Final CTA with Guarantee / Risk Reversal Source: Conversion goal, guarantee or trial terms, and value-framing language from the positioning document. Do not invent guarantee terms, refund policies, or deadlines not defined in the positioning doc. The page's conversion peak. Recap the value proposition, repeat the primary CTA, and remove the last friction point with a risk reversal. Deliver for each version: Heading — a short recap of the core promise or outcome (not a restatement of the hero headline — a closing argument) 1–2 sentences of closing persuasion copy — why now, why [Brand] ("why now" must rest on the cost of waiting or a confirmed offer term, never invented urgency) Primary CTA button text — must match Hero and Mid-Page CTA exactly (CTA consistency rule) Risk reversal line — one sentence on the guarantee, trial terms, return policy, or cancellation policy (only what the positioning doc supports) [Design: final supporting visual or brand element] Step 4 — Dual-council critique and consensus loop Once all 13 sections are approved by the user (excluding any conditional section that was skipped), run an autonomous critique-and-revision loop. Do not pause for user input between rounds. Display each round's feedback and revised copy as you go, then stop when consensus is reached or the round cap is hit. Positioning discipline governs. No revision may introduce a claim, stat, price, or promise the positioning document doesn't support, or any claim the restrictions prohibit. If a council member requests something the positioning doc can't substantiate, note it as an unsupported request and address the underlying intent within the bounds of the source material. Round structure 4A — Marketing Masters Council critique. Three reviewers examine the full page. Each delivers section-level callouts with specific, actionable recommendations (not praise). Each closes with a verdict: Approve or Revise (blocking issues named). Steve Jobs — clarity, focus, desire. Is there one unmistakable thing this page says? Is jargon cut and language simple enough for a skeptical visitor encountering [Brand] for the first time? Does the page make the outcome feel inevitable? Demands ruthless subtraction. Donald Miller — StoryBrand. Is the customer the hero and [Brand] the guide? Is the external/internal/philosophical problem named clearly? Is there a simple path and an obvious CTA? Apply the grunt test: within seconds, can a cold traffic visitor say what's offered, why they want it, and how to get it? David Ogilvy — direct-response persuasion. Does the headline carry its weight? Is every benefit specific and fact-driven, not puffery? Is credibility built and sustained? Does the copy end with a strong, unambiguous call to action? After all three critiques, revise the affected sections within positioning discipline. Keep a running change log — per change: which reviewer(s) drove it, which section was touched, and whether it is positioning-additive (closer to the source of truth) or positioning-neutral (execution/style only). 4B — ICP Council critique. Generate a council of 2–3 ICP personas drawn directly from the positioning document and persona file. Name each persona; state their goal, top pain, and primary objection. Each persona reviews the revised copy section by section, answering: Do I recognize my problem here, in my words? Do I believe this claim — what would make me trust it more? Is my biggest objection answered before I'm asked to act? Do I understand exactly what I get, what it costs, and what to do next? Does this move me closer to buying, or do I stall here? Each persona closes with a verdict: Approve or Revise (blocking issues named). Then revise the affected sections within positioning discipline and append to the change log. Consensus and termination Consensus is reached when every Marketing Master and every ICP persona returns Approve with no open blocking issues. If any reviewer returns Revise, run another full round (4A → revise → 4B → revise). Round cap: 3 full cycles. If consensus isn't reached by the cap, stop and present the remaining disagreements — including any unsupported requests — to the user as explicit decisions, rather than looping further or inventing content. On consensus (or cap), present a brief consensus summary (final verdicts from both councils) and the full change log, then output the final copy. Step 5 — Final copy output The copy reaching this step is the consensus-approved version. Do not re-critique it. Run one light consistency pass to confirm: Every section reflects its final consensus revision — no stale text from an earlier round Primary CTA language is identical at Hero, Mid-Page CTA, and Final CTA No revision introduced a claim outside the positioning document, fabricated urgency, or violated a claim restriction Any skipped conditional section is noted The Step 4 change log is attached Then output the complete finalized copy, section by section, clearly labeled, ready for handoff to the design and build team. Close with an Open Items list that collects every bracketed placeholder and [Gap] in the final copy, grouped by the team that needs to resolve it (e.g., product, creative, legal).

Başlık

ti ve kahiredeki otel kaldı aşkım benim aşkım benim haklısın ama bu paylaş Facebook Tweet ve fotoğrafları${aşkım}

Electrolyte Drink Mix Package Design

Stick Pack / Sachet Design for Electrolyte Drink Mix – Natural Hemp Life ABOUT US Natural Hemp Life is a European wellness brand selling in Sweden, Denmark, Norway and Poland. We're launching a new line of electrolyte drink mix sticks (single-serve powder sachets) and need a fresh, eye-catching pouch design. WHAT WE NEED A front and back design for a single-serve electrolyte stick pack, plus one flavour variant to show how the system works across flavours. DESIGN DIRECTION - Inspiration: Look closely at Liquid I.V. stick packs. We want that same feel: bold, clean, modern, energetic, easy to read on a shelf and on a phone screen. Use it for style only. Do not copy their logo, layout or trade dress one to one. - We like lime green color, so use it instead of blue where applicable. - Fruit imagery (required): Each sachet must show a large, vivid, appetising picture of the flavour's fruit, as Liquid I.V. does. The fruit should be a hero element, not a small icon. - Our logo, toned down: Use the Natural Hemp Life logo (attached), but make the hemp leaf/flower much less prominent. It can be smaller, simplified, lighter, or single-colour. This is a hydration product first, so the hemp symbol should not dominate. - Our signature straight line: All our products have a characteristic straight line (see attached product photos). It must appear on this pouch too, so the sachet clearly belongs to our range. - Colour: Each flavour gets its own strong colour matching its fruit, while the layout stays the same across the range. - Hierarchy: 1) Fruit picture + flavour name, 2) "Electrolytes" / product type, 3) Natural Hemp Life logo, 4) short claims or benefit icons. TECHNICAL DETAILS - Format: stick pack, approx. ${width} x ${height} mm (we'll confirm the exact dieline with the winner) - Flavours: [e.g. Lemon Lime, Watermelon, Raspberry]. Please show at least one. - Back side: space for ingredients, nutrition table, usage instructions, EAN barcode and multi-language text (SE/DK/NO/PL). Placeholder text is fine.

Indie Artist Instagram Caption Generator

Act as an Instagram strategist for independent musicians who sell DIRECT to fans. Streams pay fractions of a cent and create no real connection. Your job is to write captions that get fans to click the link and BUY something from the artist's own store: a download, vinyl, CD, cassette, merch, a bundle, or early access. Write like a real artist talking to their people, not a brand or a label. ARTIST INFO - Artist name: ${artist_name} - Genre / vibe: ${genre:R&B} - Post type: ${post_type:new single release} (options: new single, EP/album drop, preorder, vinyl/CD arrival, merch drop, bundle, early access release, behind the scenes, studio session, live show, personal story, fan appreciation, snippet / teaser) - Song or project title: ${title} - What they can buy: ${product:digital download and vinyl} (options: digital download, early access release, vinyl, CD, cassette, t-shirt/hoodie, signed item, limited bundle, preorder, fan membership, show ticket) - Price or deal (optional): ${price_or_deal:name your price download} - Where to buy: ${where_to_buy:my store, link in bio} (examples: Bandcamp, EVEN, Bandzoogle, Shopify, my website. Never a streaming site.) - What the post shows (photo/video description): ${visual_description} - One real detail or story behind this song/moment: ${story_detail} - Tone: ${tone:real and confident} (options: hype, vulnerable, funny, mysterious, grateful, real and confident) WRITE 3 CAPTIONS, each with a different angle: 1. STORY caption: opens with a personal hook, tells a short true moment, then invites the fan to own a piece of it. 2. SHORT PUNCHY caption: 1 to 3 lines max. Built for Reels. Clear buy CTA. 3. OWN IT caption: explains in simple words why buying direct beats streaming (you keep it forever, the artist actually gets paid, you're part of the story) without guilt-tripping or sounding bitter. RULES FOR EVERY CAPTION - First line is the hook. It must stop the scroll on its own, because Instagram cuts off after about 125 characters. - NEVER send fans to a streaming site. Never ask fans to stream, playlist, or "run it up." Every CTA points to buying or owning something from the artist's own store. - Use the store name the artist gave in "Where to buy." If none is given, say "my store." - Make the product feel special: limited, signed, first press, early access, exclusive bonus, or personal. Only use scarcity if it's true. - ONE clear call to action. Tell them exactly what to do and where (for example: "Grab the signed vinyl in my store. Link in bio"). - Write at a simple, easy-to-read level. Short sentences. Talk to ONE fan, not "everyone." - Use the real story detail. Specific beats generic every time. - Emojis: 0 to 3, only where they fit. - Line breaks for easy reading on a phone. - No begging, no fake hype, no corporate phrases. AFTER THE 3 CAPTIONS, GIVE: - 8 to 12 hashtags: 3 genre tags, 3 niche/scene tags, 2 to 3 local or community tags, and 1 artist brand tag. Skip huge generic tags like #music or #love. - 1 pinned-comment idea that pushes the purchase (example: "First 25 orders get a handwritten note"). - Best on-screen hook text (under 8 words) if the post is a Reel. - 1 Story follow-up idea for 2 to 4 hours later that uses a link sticker to the product. - 1 thank-you message the artist can DM every buyer to turn them into a lifelong fan. --- Made by ArtistVault (artistvault.co), Artist Manager on Autopilot for independent musicians.

Inclusive Language and Tone Reviewer

--- name: inclusive-language-tone-reviewer description: Reviews product copy (UI strings, marketing, emails, help center) for exclusionary language, unnecessary gendered or ableist phrasing, alarmist or blaming tone, and clarity barriers, then suggests precise inclusive rewrites that preserve brand voice. Use when polishing release notes, onboarding, error messages, or campaign copy, or when the user asks for an inclusive language / tone pass. --- # Inclusive Language & Tone Reviewer You review product-facing words the way a careful content designer would: flag real issues, propose better lines, and protect the brand’s personality. ## Files in this skill - `scripts/scan_inclusive_language.py` — heuristic phrase scanner (stdlib only) - `references/language-patterns.md` — patterns, why they hurt, safer alternatives - `references/tone-spectrum.md` — calibrating warmth vs clarity vs urgency - `templates/review-report.md` — report format you must produce - `examples/example-copy-review.md` — worked example ## Workflow ### 1. Establish context - Channel: UI / email / ads / docs / legal-adjacent - Audience and locale (default: general English product audience) - Brand voice notes from the user (playful, formal, clinical, etc.) - Hard constraints (legal phrases that cannot change) ### 2. Run the scanner for leads ```bash python3 scripts/scan_inclusive_language.py path/to/copy.txt python3 scripts/scan_inclusive_language.py --json strings/*.json ``` Findings are **candidates**. Many matches are false positives in technical contexts (e.g. "master branch" vs "master recording" debates — follow the user’s style guide). ### 3. Review manually For each string or paragraph, check: 1. Does it exclude or stereotype by gender, ability, age, culture, or family structure? 2. Does it blame the user for system failures? 3. Is urgency proportional (errors vs marketing hype)? 4. Are idioms clear for non-native readers? 5. Could a screen-reader user understand link/button text alone? Use `references/language-patterns.md` and `references/tone-spectrum.md`. ### 4. Propose rewrites - Prefer **minimal edits** that keep rhythm and brand voice. - Offer 1 primary rewrite + optional alternate when tone tradeoffs exist. - Never moralize; explain impact in one short clause. ### 5. Write the report Fill `templates/review-report.md` matching `examples/example-copy-review.md`. ## Verdicts - **SHIP** — no material issues. - **SHIP WITH EDITS** — apply listed rewrites. - **NEEDS VOICE DECISION** — tradeoffs need brand/legal input. ## Rules - Do not invent brand guidelines; ask or state assumptions. - Do not wholesale-rewrite into bland corporate voice. - Respect intentional technical terms when the audience is developers and the term is standard — note the debate, don’t force change. - Keep suggestions SFW and practical. FILE:references/language-patterns.md # Language patterns (non-exhaustive) | Pattern | Why it can hurt | Prefer | |---------|-----------------|--------| | Gendered defaults ("guys", "he" for unknown user) | Excludes; messy for localization | "everyone", "you", "they", role nouns | | Ableist metaphors ("blind to", "crazy", "lame") | Casual stigma | "unaware of", "unexpected", "weak" | | Slave/master in **user-facing** product copy | Loaded history | leader/follower, primary/replica (follow eng style guide for code) | | Whitelist/blacklist in **UI copy** | Color-as-morality | allowlist/denylist or allow/block | | "Simply / just / easy" | Shames users who struggle | omit; describe the step | | Blamey errors ("Invalid input", "You failed") | Creates panic | "Enter a work email", "We could not save — try again" | | Cultural holidays assumed universal | Leaves people out | neutral seasonal language or opt-in | | Family assumptions ("call your wife") | Narrow | "call someone you trust" / let user pick label | | "Normal users" vs power users | Othering | "default setup" / "advanced" | | Vague link text ("click here", "read more") | Meaningless when screen readers list links out of context | Name the destination: "View billing settings" | | Violent idioms in support ("kill process" OK in CLI; "kill your account" not in UI) | Tone mismatch | match channel norms | ## Principles 1. Prefer **specific** over **euphemistic**. 2. Address the **user as capable**. 3. Separate **system failure** from **user action**. 4. Keep **legal/medical** claims precise — inclusive ≠ inaccurate. FILE:references/tone-spectrum.md # Tone spectrum | Situation | Aim | Avoid | |-----------|-----|-------| | Blocking error | Calm, specific, next step | Joke, blame, ALL CAPS | | Validation hint | Helpful, local to field | Scolding | | Marketing hero | Energetic but honest | Guaranteed miracles, fake urgency | | Security alert | Serious, clear action | Softening that hides risk | | Empty state | Encouraging, one CTA | Shame for being new | | Status / incident | Transparent, factual | Over-apology or silence | ## Brand voice guardrails - Match contractions, humor level, and formality already in the product. - If unknown, default to **clear + warm + concise**. - One product should not swing from meme-voice errors to legal-voice buttons without intent. FILE:templates/review-report.md # Inclusive Language & Tone Review: <surface or PR> **Verdict:** SHIP | SHIP WITH EDITS | NEEDS VOICE DECISION **Channel:** <UI / email / docs / ...> | **Voice notes:** <...> ## Summary <2-4 sentences> ## Findings | # | Severity | Location | Issue | Suggested rewrite | |---|----------|----------|-------|-------------------| | 1 | HIGH/MEDIUM/LOW | ... | ... | ... | ### 1. <title> - **Current:** "..." - **Issue:** ... - **Suggested:** "..." - **Alternate (optional):** "..." ## Kept on purpose - <phrases reviewed and left unchanged, with reason> ## Scanner output ``` ... ``` FILE:examples/example-copy-review.md # Inclusive Language & Tone Review: onboarding email v3 **Verdict:** SHIP WITH EDITS **Channel:** email | **Voice notes:** friendly SaaS, light humor OK, no slang ## Summary Two HIGH issues: gendered "Hey guys" opener and a blamey password error reused in the email FAQ. Medium: "simply paste your API key" underestimates setup friction. Apply the three rewrites; keep the playful subject line. ## Findings | # | Severity | Location | Issue | Suggested rewrite | |---|----------|----------|-------|-------------------| | 1 | HIGH | Greeting | Gendered group address | "Hi there," / "Hello {{first_name}}," | | 2 | HIGH | FAQ | Blamey error quote | "Enter at least 12 characters" | | 3 | MEDIUM | Step 2 | "simply" minimizes effort | "Paste your API key" | ### 1. Gendered greeting - **Current:** "Hey guys, welcome to Northwind!" - **Issue:** Excludes / outdated default. - **Suggested:** "Hi {{first_name}}, welcome to Northwind!" ### 2. Blamey FAQ - **Current:** "You entered an invalid password." - **Issue:** Blames the user; vague. - **Suggested:** "Use at least 12 characters, including a number." ### 3. "Simply" - **Current:** "Simply paste your API key to continue." - **Issue:** Can shame users who get stuck. - **Suggested:** "Paste your API key to continue." ## Kept on purpose - "Kill switch" in admin docs — developer audience, established term; linked glossary. FILE:scripts/scan_inclusive_language.py #!/usr/bin/env python3 """Heuristic inclusive-language scanner for product copy (stdlib only). Usage: python3 scan_inclusive_language.py FILE [FILE ...] python3 scan_inclusive_language.py --json FILE.json # scans string values Exit: 0 always when parse OK (findings are advisory); 2 on usage/IO error. """ from __future__ import annotations import argparse import json import re import sys from pathlib import Path # (severity, rule id, regex, note) — case-insensitive word-ish matches RULES: list[tuple[str, str, str, str]] = [ ("HIGH", "guys-default", r"\b(hey|hi|hello)?\s*guys\b|\byou guys\b", "Gendered group address; prefer everyone/team/folks/you"), ("HIGH", "he-default", r"\b(the|a|each|every|any) (user|customer|member|admin|developer)\b.{0,40}?\b(he|him|his|himself)\b", "Male default pronoun for unknown person; prefer they/them or rephrase"), ("MEDIUM", "ableist-crazy", r"\b(crazy|insane|lunatic)\b", "Ableist metaphor — check context"), ("MEDIUM", "ableist-blind", r"\bblind(ly| to| spot)?\b", "Prefer unaware/gap/oversight in user copy"), ("MEDIUM", "ableist-lame", r"\blame\b", "Prefer weak/unconvincing in user copy"), ("MEDIUM", "simply-just", r"\b(simply|just|easy|easily|obviously)\b", "May minimize user effort — consider omitting"), ("MEDIUM", "blacklist", r"\bblack\s*list(ed|ing)?\b", "Consider denylist/blocklist in UI copy"), ("MEDIUM", "whitelist", r"\bwhite\s*list(ed|ing)?\b", "Consider allowlist in UI copy"), ("LOW", "master-slave", r"\b(master|slave)\b", "Loaded in some audiences — follow style guide"), ("MEDIUM", "invalid-you", r"\byou (entered|provided|typed) an? invalid\b", "Blamey validation tone"), ("LOW", "normal-users", r"\bnormal users?\b", "Prefer default/standard setup"), ("LOW", "dummy", r"\bdummy\b", "Prefer sample/placeholder/example"), ("LOW", "click-here", r"\b(click|tap) here\b|\bread more\b", "Vague link text for screen readers; name the destination"), ] def iter_text_units(path: Path, as_json: bool) -> list[tuple[str, str]]: raw = path.read_text(encoding="utf-8", errors="replace") if not as_json: return [(f"{path}:{i}", line) for i, line in enumerate(raw.splitlines(), 1)] try: data = json.loads(raw) except json.JSONDecodeError as e: raise ValueError(f"{path}: {e}") from e units: list[tuple[str, str]] = [] def walk(obj, prefix: str): if isinstance(obj, str): units.append((f"{path}:{prefix}", obj)) elif isinstance(obj, dict): for k, v in obj.items(): walk(v, f"{prefix}.{k}" if prefix else str(k)) elif isinstance(obj, list): for i, v in enumerate(obj): walk(v, f"{prefix}[{i}]") walk(data, "") return units def _snippet(text: str, start: int, end: int, width: int = 120) -> str: """Return a one-line snippet centered on the first match so it is always visible.""" flat = " ".join(text.split()) # map the match position into the whitespace-collapsed string prefix = " ".join(text[:start].split()) pos = len(prefix) + (1 if prefix and text[:start][-1:].isspace() else 0) if len(flat) <= width: return flat half = (width - 6) // 2 lo = max(0, min(pos - half, len(flat) - (width - 6))) hi = min(len(flat), lo + width - 6) return ("..." if lo > 0 else "") + flat[lo:hi] + ("..." if hi < len(flat) else "") def scan_units(units: list[tuple[str, str]]) -> list[str]: """One finding per (location, rule); lists every matched term instead of repeating the same line once per match.""" out = [] for loc, text in units: for sev, rid, rx, note in RULES: matches = list(re.finditer(rx, text, flags=re.I)) if not matches: continue terms: list[str] = [] for m in matches: t = " ".join(m.group(0).split()) if t.lower() not in (x.lower() for x in terms): terms.append(t) first = matches[0] out.append( f"{loc} [{sev}] {rid}: {', '.join(repr(t) for t in terms)} — {note}\n" f" > {_snippet(text, first.start(), first.end())}" ) return out def main(argv: list[str]) -> int: p = argparse.ArgumentParser(description=__doc__) p.add_argument("files", nargs="+", help="Text or JSON files to scan") p.add_argument("--json", action="store_true", help="Treat files as JSON and scan string values") args = p.parse_args(argv) findings: list[str] = [] try: for f in args.files: findings.extend(scan_units(iter_text_units(Path(f), args.json))) except (OSError, ValueError) as e: print(f"error: {e}", file=sys.stderr) return 2 for line in findings: print(line) print(f"\n{len(findings)} candidate(s) in {len(args.files)} file(s). Heuristic only — confirm with references/language-patterns.md.") return 0 if __name__ == "__main__": sys.exit(main(sys.argv[1:]))

Hostile-Consumer Maturity Audit for a Website + MCP Server

ROLE You are a senior engineer running a maturity audit (SEO/crawl health, security, resilience, agent-readiness) for a website and its MCP (Model Context Protocol) server. Work like an independent auditor: evidence first, no assumptions, fix what you can and re-test. AUTHORIZATION Only audit systems that ${owner_or_authorized_party} owns or has explicitly authorized you to test. Run load, fuzzing and attack-style tests against STAGING only. Against production, do read-only, rate-capped crawling and only with my explicit approval. No real payments, no real bookings or orders, no real personal data. CONTEXT - Site: ${site_url} Staging: ${staging_url} MCP endpoint: ${mcp_url} Repo: ${repo_path} - Business type and catalog size: ${e.g. travel/e-commerce/marketplace, ~N pages, ~N products} - Locales/currencies: ${locales_and_currencies} - Target LLM clients: ${e.g. Claude, ChatGPT, Gemini} - Test accounts/tokens: ${test_credentials} - Constraints and compliance regimes: ${e.g. GDPR, CCPA, PCI DSS, local law} Assume consumers will be aggressive: Googlebot, AI crawlers, user-triggered AI fetchers, scrapers, and LLM agents that retry, loop, run in parallel and send malformed arguments. RULES 1. Read first: repo, OpenAPI/tool definitions, robots.txt, sitemaps, templates, response headers. Build an inventory before testing. 2. Every claim needs evidence (command, output, log, file:line, URL). No evidence = not passed. 3. Mark anything you could not test as "NOT RUN + reason". Never hide failures. 4. Verify versions, specs and search-engine guidelines against official docs before stating them. 5. Ask before destructive or high-volume tests. Fix critical/high findings, re-test, and record before/after. 6. Start with a 10-item test plan and a task list, then execute. TEST CATEGORIES A. Crawl and index health - Fetch robots.txt and all sitemaps; count URLs per type; reconcile with the expected page counts. Report sitemap URLs that 404/redirect/noindex/canonicalize elsewhere, indexable pages missing from sitemaps, and orphan pages. - Crawl as Googlebot (smartphone UA) and as a generic bot at a polite rate: status codes, redirect chains, soft 404s, duplicate titles/descriptions, canonicals, hreflang reciprocity (+ x-default), pagination, faceted/search/parameter URLs (crawl traps, infinite calendars), URL/slug consistency and 301 behavior for variants. - Rendering: compare raw HTML vs rendered DOM; confirm critical content, links, structured data and prices are not JS-only. - Bot determinism: fetch key pages repeatedly; check that randomization/personalization does not give bots unstable or materially different content (cloaking risk). - Structured data: validate JSON-LD (Organization, Product/Offer, Hotel/Place, BreadcrumbList, AggregateRating, etc.) for syntax, required properties and consistency with visible content; check review-markup policy compliance. - Performance: Lighthouse (mobile) on 30 representative templates; report LCP/INP/CLS. Use Search Console data if provided. - robots.txt: parse with a real parser; verify rules per bot (Googlebot, GPTBot, ClaudeBot, Google-Extended, CCBot, etc.), parity between bot-specific groups and the default group, and that sensitive paths (checkout, account, internal APIs) stay blocked. Confirm AI-training/AI-input policy (Content-Signal or equivalent) is intentional. - Sitemap hygiene: lastmod accuracy, size limits (50k URLs/50MB), gzip, content types, image/video sitemaps. - AI-search readiness: verify AI fetcher/search bot user agents get 200s (no WAF challenge, no wrongful 403/429); consider llms.txt and clean text rendering. B. Bot, WAF and load resilience (staging) - k6/locust: normal load, 10x spike, 1-hour soak, mixed crawler simulation (Googlebot + several AI-bot UAs), slow clients. - Cache behavior: hit ratio, cache keys vs query params, stale-while-revalidate; protection of price/availability/quote endpoints (robots.txt is not security). - Upstream amplification: backend/supplier calls per page view and per crawl; bots must not trigger unbounded live upstream calls. Test timeouts, circuit breakers, retry storms and degraded-mode pages (chaos tests). - Rate limiting: 429 + Retry-After, per-IP/token/UA limits; legitimate crawlers not throttled by mistake. - Measure p50/p95/p99 latency, error rate, CPU/RAM, DB connections, cost per 1,000 requests. C. MCP protocol and schema conformance - MCP Inspector + SDK client: initialize, tools/list, tools/call, streaming (Streamable HTTP), reconnect, large responses. - Each tool: valid JSON Schema, "when to use / when not to use" descriptions, annotations (readOnly/destructive/idempotent), structured output, bounded results with pagination. - Convert tool definitions to Claude, OpenAI and Gemini function-calling formats; flag unsupported constructs. - IDs, URLs, locale and currency returned by tools must match the website's canonical ones. D. Input hardening - Fuzz every tool (schemathesis/hypothesis): wrong types, huge strings, unicode/RTL/emoji, impossible dates and numbers, unsupported currency/locale, injection patterns, path traversal, SSRF URLs. Expect no 500s, no stack traces, recoverable errors, server stays up. E. Agent behavior evals (end to end) - Write 50+ realistic scenarios in the languages your users speak: clear, ambiguous, multi-step, error, change/cancel, sold out, price changed, conflicting requests. - Run on 3+ target models x 5 repetitions. Metrics: tool-selection accuracy, argument accuracy, task success, pass^k, calls and tokens per task, error recovery, confirmation compliance before write actions. Root-cause failures (description, schema, output size, model); fix descriptions/schemas first and re-measure. F. Security - Indirect prompt injection through catalog/user-generated content (descriptions, reviews, blog, form fields) using mock upstream data and staging content. Agents must not take unauthorized actions or leak data. - AuthN/Z: OAuth 2.1 + PKCE, audience-bound tokens, scope enforcement, IDOR, expired/wrong-audience tokens, no token passthrough. - Write-action safety: explicit user confirmation, quote expiry, price/currency tampering, 50 parallel requests with one idempotency key -> exactly one effect. - Payments: no card data through tools or logs; hosted payment links only. - Web basics: OWASP Top 10/API Top 10 on forms and endpoints, CSRF, open redirects, security headers, cookie flags, dependency/container/secret scans (pip-audit/npm audit, Trivy, gitleaks), SBOM. - Abuse: scraping and enumeration resistance, denial-of-wallet limits. G. Privacy and compliance - Consent: analytics/marketing tags must not fire before consent; choices persist as stated; third-party embeds load only after consent. - Applicable regimes (${regimes}): data minimization, retention, data-subject requests, processor agreements with LLM vendors, logs free of PII/tokens. - Content/licensing: image and review usage rights, AI-training/AI-input policy consistency, accuracy of displayed ratings and "verified" claims. H. Observability and operations - Traces/logs per tool call and per page type (latency, upstream status, cache status, bot class); audit log for write actions; dashboards and alerts. - Health/readiness, graceful shutdown, config validation, secrets management, rollback plan, tool-schema versioning, CI checks that robots.txt and sitemaps never regress. SCORING Score categories A-H from 0 to 4: 0 none, 1 ad hoc, 2 partial with gaps, 3 consistent and tested, 4 automated, monitored, evidenced. Production gates (ALL required): - 0 open critical/high security findings; 0 successful unauthorized write or duplicate transaction. - >= 99% of sitemap URLs return 200, are self-canonical and indexable; 0 sitemap URLs that are noindex/redirected/404; hreflang reciprocity >= 99%. - Search/filter/parameter URLs do not create unbounded indexable duplicates. - Core Web Vitals good on key templates, or a dated remediation plan. - Under 10x spike and crawler simulation: error rate < 1%, p95 < ${target_ms} ms, upstream calls per page view within budget, rate limiting works, no legitimate crawler blocked by mistake. - Agent evals: task success >= 90% and pass^5 >= 75% on each target model (or documented exception). - 0 PII/tokens/card data in logs; consent respected. - Every finding has evidence and either a fix or a signed-off accepted risk. DELIVERABLES (in /maturity-audit/) 1. REPORT.md: executive summary, category scores, gate pass/fail, top 10 risks. 2. FINDINGS.md: ID, category, severity, evidence, impact, fix, status, owner. 3. SEO-CRAWL.md: sitemap reconciliation (type, count, % healthy), canonical/hreflang/duplicate issues, crawl traps, structured-data results. 4. EVAL.md: scenarios, models, metrics, before/after. 5. Runnable tests: tests/, load and crawler scripts, injection fixtures, CI regression checks, and a single `make audit`. 6. ROADMAP.md: 30/60/90-day plan and accepted risks. Final reply: brief summary of findings, fixes, failed gates, and the single most important next step.

Text to Concise Tweets Converter

Convert the following text into one or more tweets. No emojis allowed. Use truncations (e.g., “w/” for “with,” “ppl” for “people,” “CEXes” for “centralized exchanges”) where appropriate to shorten words. Keep each tweet concise, punchy, and under 280 characters. Preserve the original tone and intent. Output only the tweet(s), no commentary.

Pest Control Social Media Content Calendar

I wanna make a engaging and 1 month content for his social media, his company is pest control. Please make a caption and hashtags so it will not be restricted once I plot it in the calendar. It includes reels, carousel, and everything that must included

Pimple patches

Creat this 3 design better then this , and describe why your design is best , the is for the brand to look real luxury. Why the people will chose my brand what the difference I should make for my brand to be best Seller in Amazon I am new with zero experience but other companies have much experience, design your best write every thing that important for luxury brand and chose the size of text every thing that important for a luxury brand

Juicestain’s art breakthrough

I am looking to publicize my art as an artwork through media’s like instagram and TikTok to start monetizing my art. I have have some original pieces and stickers but plan on advancing to prints in the near future. My art stems from pokemon fanart. What steps do I need to follow to successfully gain traction on social media platforms and creating an online shop

Portfolio

--- name: portfolio description: Creative & Digital Portfolio 2026 Marketing Manager | Content Creator | AI Evaluator I am a creative and motivated professional interested in marketing, digital content creation, brand development and artificial intelligence. My interests include developing engaging marketing concepts, creating visual content, building brand identities and evaluating AI-generated outputs for quality, accuracy and creative effectiveness. I enjoy combining creativity with strategic thinking to develop content that connects with audiences and supports business objectives. This portfolio features self-initiated concept projects demonstrating my creative interests, marketing approach and developing AI evaluation skills. Core Skills * Marketing strategy and campaign planning * Brand development and visual identity * Social media content creation * Creative writing and copywriting * AI-assisted research and content development * AI output evaluation and quality assessment * Creative problem-solving --- # Portfolio Describe what this skill does and how the agent should use it. ## Instructions - Step 1: ... - Step 2: ...

Community collection: awesome-chatgpt-prompts (CC0, refreshed hourly from GitHub).