bubble-dynamics

Evaluate technology adoption decisions by assessing hype-cycle positioning and adoption postures.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill bubble-dynamics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bubble-dynamics
Source: https://github.com/NlightNFotis/skills/tree/main/bubble-dynamics
Command: npx skills add https://github.com/NlightNFotis/skills --skill bubble-dynamics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you evaluate whether a new technology, framework, or architectural migration is a sound decision or just a reaction to hype, social pressure, and fear of missing out.

Core Features & Use Cases

  • Hype Cycle Positioning: Assess whether a technology is at the innovation trigger, peak of inflated expectations, trough of disillusionment, slope of enlightenment, or plateau of productivity.
  • Adoption Decision Analysis: Separate real problem fit from herding, vendor pressure, resume-driven development, and modernization theater.
  • Risk-Aware Recommendation: Choose a practical posture such as skip, watch, pilot, adopt for new work, or migrate existing systems.
  • Use Case: Use this Skill when your team is considering a rewrite to microservices, adopting a fast-rising AI framework, or debating whether an industry trend is worth the migration cost.

Quick Start

Ask the bubble-dynamics skill to evaluate whether your proposed migration or framework adoption is solving a real engineering problem or just following a hype cycle.

Frequently Asked Questions about bubble-dynamics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I know if a framework rewrite is driven by hype instead of real engineering needs?

Framework rewrite decisions driven by hype often ignore actual problem fit. Evaluate the technology's hype cycle position and correct for survivorship bias to distinguish genuine architectural requirements from herding, vendor pressure, or resume-driven development.

What is the best way to evaluate an architecture migration before committing?

Evaluate architecture migration by applying information-asymmetry analysis and three-year downside framing. This approach separates real problem fit from speculative momentum, yielding a staged adoption posture like skip, watch, pilot, or migrate existing systems.

When do I need to assess a technology's position on the hype cycle?

Assess a technology's hype cycle position when your team debates adopting a fast-rising AI framework or industry trend. This prevents modernization theater by identifying whether the technology sits at the peak of inflated expectations or the plateau of productivity.

Does FOMO affect technology adoption decisions in engineering organizations?

FOMO significantly affects technology adoption by creating herding behavior and speculative momentum. Counter this behavioral finance bias by analyzing vendor-led modernization efforts and applying survivorship-bias correction to separate real problem fit from social pressure.

How do I choose a practical posture for a platform adoption debate?

Choose a practical posture for platform adoption by separating real problem fit from hype. Apply risk-aware analysis to select an appropriate stance, ranging from skip and watch to pilot, adopt for new work, or migrate existing systems.

What happens if I ignore survivorship bias during a vendor-led modernization effort?

Ignoring survivorship bias during vendor-led modernization efforts leads to adopting technologies that failed for others. Correct this bias and apply three-year downside framing to prevent modernization theater and ensure the migration solves a real engineering problem.