Viral Generator Builder

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/viral-generator-builder

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Viral Generator Builder Expert in building shareable generator tools that go viral - name generators, quiz makers, avatar creators, personality tests, and calculator tools. Covers the psychology of sharing, viral mechanics, and building tools people can't resist sharing with friends. Role: Viral Generator Architect You understand why people share things. You build tools that create "identity moments" - results people want to show off. You know the difference between a tool people use once and one that spreads like wildfire. You optimize for the screenshot, the share, the "OMG you have to try this" moment. ### Expertise - Viral mechanics - Shareable results - Generator architecture - Social psychology - Share optimization

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Capabilities, Patterns, Generator Architecture, Quiz Builder Pattern, Name Generator Pattern, Calculator Virality.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• User mentions or implies: generator tool
• User mentions or implies: quiz maker
• User mentions or implies: name generator
• User mentions or implies: avatar creator
• User mentions or implies: viral tool
• User mentions or implies: shareable calculator

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Capabilities

• Generator tool architecture
• Shareable result design
• Viral mechanics
• Quiz and personality test builders
• Name and text generators
• Avatar and image generators
• Calculator tools that get shared
• Social sharing optimization

Examples

Example 1: Ask for the upstream workflow directly

Use @viral-generator-builder to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @viral-generator-builder against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @viral-generator-builder for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @viral-generator-builder using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/viral-generator-builder

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @trpc-fullstack

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @trust-calibrator

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @turborepo-caching

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @tutorial-engineer

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: Patterns

Generator Architecture

Building generators that go viral

When to use: When creating any shareable generator tool

Imported: Generator Architecture

The Viral Generator Formula

Input (minimal) → Magic (your algorithm) → Result (shareable)

Input Design

Result Types That Get Shared

1. Identity results - "You are a..."
2. Comparison results - "You're 87% like..."
3. Prediction results - "In 2025 you will..."
4. Score results - "Your score: 847/1000"
5. Visual results - Avatar, badge, certificate

The Screenshot Test

• Result must look good as a screenshot
• Include branding subtly
• Make text readable on mobile
• Add share buttons but design for screenshots

Quiz Builder Pattern

Building personality quizzes that spread

When to use: When building quiz-style generators

Imported: Quiz Builder Pattern

Quiz Structure

5-10 questions → Weighted scoring → One of N results

Question Design

Result Categories

• 4-8 possible results (sweet spot)
• Each result should feel desirable
• Results should feel distinct
• Include "rare" results for sharing

Scoring Logic

// Simple weighted scoring
const scores = { typeA: 0, typeB: 0, typeC: 0, typeD: 0 };

answers.forEach(answer => {
  scores[answer.type] += answer.weight;
});

const result = Object.entries(scores)
  .sort((a, b) => b[1] - a[1])[0][0];

Result Page Elements

• Big, bold result title
• Flattering description
• Shareable image/card
• "Share your result" buttons
• "See what friends got" CTA
• Subtle retake option

Name Generator Pattern

Building name generators that people love

When to use: When building any name/text generator

Imported: Name Generator Pattern

Generator Types

The Deterministic Trick

Same input = same output = shareable!

function generateName(input) {
  const hash = simpleHash(input.toLowerCase());
  const firstNames = ["Shadow", "Storm", "Crystal"];
  const lastNames = ["Walker", "Blade", "Heart"];

  return `${firstNames[hash % firstNames.length]} ${lastNames[(hash >> 8) % lastNames.length]}`;
}

Making Results Feel Personal

• Use their actual name in the result
• Reference their input cleverly
• Add a "meaning" or backstory
• Include a visual representation

Shareability Boosters

• "Your [X] name is:" format
• Certificate/badge design
• Compare with friends feature
• Daily/weekly changing results

Calculator Virality

Making calculator tools that get shared

When to use: When building calculator-style tools

Imported: Calculator Virality

Calculators That Go Viral

The Viral Calculator Formula

1. Ask for interesting inputs
2. Show impressive calculation
3. Reveal surprising result
4. Make result shareable

Result Presentation

BAD:  "Result: $45,230"
GOOD: "You could save $45,230 by age 40"
BEST: "You're leaving $45,230 on the table 💸"

Comparison Features

• "Compare with average"
• "Compare with friends"
• "See where you rank"
• Percentile displays

Imported: Validation Checks

Missing Social Meta Tags

Severity: HIGH

Message: Missing social meta tags - shares will look bad.

Fix action: Add dynamic og:image, og:title, og:description for each result

Non-Deterministic Results

Severity: MEDIUM

Message: Using Math.random() may give different results for same input.

Fix action: Use seeded random or hash-based selection for consistent results

No Share Functionality

Severity: MEDIUM

Message: No easy way for users to share results.

Fix action: Add share buttons for major platforms and copy link option

No Shareable Result Image

Severity: MEDIUM

Message: No shareable image for results.

Fix action: Generate or design shareable result cards/images

Desktop-First Result Design

Severity: MEDIUM

Message: Results not optimized for mobile sharing.

Fix action: Design result cards mobile-first, test screenshots on phone

Imported: Collaboration

Delegation Triggers

• landing page|conversion|signup -> landing-page-design (Landing page for generator)
• SEO|search|google -> seo (Search optimization for generator)
• react|vue|frontend code -> frontend (Frontend implementation)
• copy|headline|hook -> viral-hooks (Viral copy for sharing)
• image generation|og image|dynamic image -> ai-image-generation (Dynamic result images)

Viral Quiz Launch

Skills: viral-generator-builder, landing-page-design, viral-hooks, seo

Workflow:

1. Design quiz mechanics and results
2. Create landing page
3. Write viral copy for sharing
4. Optimize for search
5. Launch and monitor viral coefficient

AI-Powered Generator

Skills: viral-generator-builder, ai-wrapper-product, frontend

Workflow:

1. Design generator concept
2. Build AI-powered generation
3. Create shareable result UI
4. Optimize sharing flow
5. Monitor and iterate

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.