gnurio

Engineer ideas to spread successfully using Heylighen's 4-stage memetic replication model (Assimilation → Retention → Expression → Transmission). Use this skill whenever someone wants to make an idea stick, spread, or survive in an organization or audience — e.g., "my idea isn't landing", "people keep forgetting this", "nobody is sharing it", "how do I get buy-in", "help me pitch this", "why isn't this spreading", "how do I make this go viral internally", "I need this to survive a meeting". Also use for diagnosing why a specific idea is dying (which of the 4 stages is failing) and prescribing targeted fixes. Grounded in Finkelstein's Memetics Compendium (2009).

Intelligent router for the memetics skill network. Uses Heylighen's A→R→E→T diagnostic (Assimilation → Retention → Expression → Transmission) to identify which stage of memetic replication is failing, then routes to the right specialized skill. Use whenever you have a memetics question or want to make an idea spread — especially "my idea isn't landing", "people forget it", "nobody is sharing it", "I want to build a movement", "should I try to spread this?", or any memetics question where you're not sure which skill to start with.

Map the ecosystem of reinforcing ideas around a concept. Identifies which memeplex an idea belongs to, what ideas support or compete with it, and what mimetic desire dynamics drive its carriers. Use when you need to understand the ideological landscape before spreading an idea, or when you want to understand why an idea is thriving or dying. Trigger on: "What's the memeplex around this?", "What ideas compete with mine?", "Why does this idea keep coming back?", "Map the idea ecosystem", "What's reinforcing this narrative?"

Adapt memetics playbooks to specific application domains (personal branding, product launches, social movements, etc.). Takes general memetics strategy and tailors it to domain-specific contexts, metrics, and tactics. [NEEDS SOURCE MATERIAL] Source provides brief examples of three domains but doesn't fully detail the domain-specific playbooks. Each domain needs detailed expansion.

Design and implement tactics to strengthen a network's resistance to unwanted memes and supermeme traps. Standalone defensive skill for teams, organizations, or networks wanting to build critical thinking and memetic resilience. [NEEDS SOURCE MATERIAL] Source describes immunity-building goal but doesn't detail the full implementation methodology, frequency, or specific frameworks to teach.

Classify a raw idea or concept into its memetic type (meme, antimeme, supermeme, or cliche). Use this skill when you have an idea and need to understand its spreading properties, or when you're evaluating whether an idea will naturally transmit or face resistance. Trigger on: "What type of meme is this?", "Will this spread?", "Is this a good idea to promote?", "Classify this idea", "What kind of meme is X?"

Create optimized viral content variants from a core idea. Takes a message and produces 2-5 shareable content pieces using proven memetic tactics: villain narratives, emotional activation, lightweight format, niche targeting. Output is ready-to-post content with transmissibility assessment.

Create a phased strategy for spreading your idea. For antimemes: dark forest → coordinated emergence → tipping point. For memes: viral content tactics. Takes all prior analysis (classification, fitness, network, champions) and produces a concrete action plan with phases, milestones, and tactical steps.

Review existing requirements or convert raw context into requirements that meet 18 quality characteristics (unambiguous, clear, cohesive, consistent, conformant, current, modifiable, traceable, relevant, unique, categorised, complete, correct, concise, testable, implementation-independent, owned, feasible). Use whenever the user mentions requirements, PRDs, specs, user stories, acceptance criteria, requirements review, requirements audit, BRD, FRD, requirements quality, requirements catalogue, requirements traceability, "are my requirements any good", "turn this into requirements", "make these requirements better", or shares meeting notes, interview transcripts, stakeholder input, or feature ideas that need to be formalised. Trigger even when the user does not use the word "requirement" if the artifact they share is functionally a requirement (e.g., "the system should let users export to PDF", "we need a way for admins to revoke access").

Find, diagnose, and fix misalignment in corporate settings. Use this skill when teams are stuck, decisions aren't being made, meetings are dysfunctional, or there's confusion about who has authority. Trigger on: "we're misaligned", "can't get everyone on the same page", "meetings are a waste of time", "who's supposed to decide this?", "too many cooks", "analysis paralysis", "nothing gets decided", "people aren't following the process", or any time group dynamics are blocking progress.

Represent messy work as durable obligations, workflow building blocks, fragments, AI/automation insertion points, and exception queues. Use this whenever the user wants to analyze interviews, messy notes, customer research, operational workflows, PM workflows, vertical SaaS opportunities, AI insertion points, automation opportunities, "durable obligations", fragmented work, hated execution burden, or where AI should fit into an existing workflow. This skill is primarily a thinking and workflow-mapping tool, not a startup idea generator.

PM stress-test roleplay. Use this skill whenever a PM wants to practice handling a difficult situation with a designer or engineer, stress-test their instincts in a realistic scenario, or understand what it feels like to be on their team when things go wrong. You play a frustrated, skeptical, or overloaded team member and respond as they would. Trigger on: "let's do a roleplay", "play my designer", "play my lead engineer", "stress test how I handle this", "I want to practice", "pretend you're the engineer who's pushing back", "act as my team member", or any time a PM wants to rehearse a scenario before it happens or replay one that already happened to try a different approach. Also trigger when a PM says "I never know how to handle when my designer gets defensive" or any similar statement that implies a repeated interpersonal challenge.

PM blind spot identifier. Use this skill whenever a PM wants a comprehensive read on which behavioral gaps they have that they can't see themselves. This is the deepest and most comprehensive mode — a full interview that surfaces systematic patterns across all 7 behavioral clusters. Trigger on: "what are my blind spots?", "what am I missing as a PM?", "give me an honest full assessment", "I want a comprehensive read on where I fall short", "test me across everything", "what do I consistently get wrong?", "I want to know what I'm not seeing about myself", or any time a PM wants a thorough behavioral audit that goes beyond a single situation or decision. Also trigger at the end of another mode when a pattern has emerged across multiple interactions and the PM wants to go deeper.

PM decision quality auditor. Use this skill whenever a PM wants to audit a specific decision they made — not just whether it worked out, but whether it was a *good decision* by the criteria that define PM excellence. Trigger on: "was this the right call?", "I want to audit this decision", "I'm not sure I made this well", "help me think through whether this was a good PM decision", "I made a call about X and I want to pressure-test it", "I cut this feature / changed this priority / chose this direction — was that right?", or any time a PM wants structured feedback on the quality of a specific decision they made, regardless of whether it turned out well. Important: good outcomes don't make good decisions; bad outcomes don't make bad decisions. This skill audits the *process*, not the result.

PM alignment coach and router. Use this skill whenever a product manager (or someone managing products) wants to reflect on their own performance, check their behaviors against a standard of excellence, get coaching, practice a difficult scenario, audit a decision, or understand their blind spots. Trigger on phrases like: "am I being a good PM?", "check how I'm doing", "coach me", "how would my team see me?", "let's roleplay a scenario", "audit my decision", "what am I missing as a PM", "what are my blind spots", "test me as a PM", "I want to improve as a PM", or any time a PM is reflecting on their own practice. Also trigger when someone mentions PM self-improvement, PM development, or wanting to think through how they handled a team situation.

PM behavioral retrospective. Use this skill whenever a PM wants to debrief a specific situation they recently handled — a meeting, a conflict, a decision, a conversation with an engineer or designer, a feature that shipped badly, a standup that went sideways. The PM describes what happened and you map their actual behavior against the PM excellence framework to surface what they did well and where they fell short. Trigger on: "I just had a situation where...", "I want to think through how I handled...", "something happened this week that I want to debrief", "was this the right call?", "I'm not sure I handled this well", or any time a PM describes a specific recent event and wants feedback on their behavior.

Analyze industry structure using Porter's Five Forces. Use when asked to assess industry attractiveness, competitive dynamics, profit potential, or structural threats.

Evaluate market entry opportunities using Porter's entry analysis framework. Use when asked to assess whether to enter a new market, how to enter, or what entry barriers exist.

Audit a competitive strategy for internal consistency using Porter's tests. Use when evaluating whether a strategy hangs together, after formulating strategy, or when diagnosing strategic drift.

Design offensive or defensive competitive moves using Porter's framework. Use when planning competitive actions, responding to competitor moves, or managing industry discipline.

Classify an industry's evolutionary stage and structural type using Porter's criteria. Use when asked to diagnose industry maturity, identify if an industry is emerging/fragmented/declining, or understand industry evolution.

Map strategic groups within an industry using Porter's framework. Use when asked to segment competitors, identify positioning opportunities, or analyze mobility barriers.

Route competitive strategy analysis to the right Porter skill. Use when asked for broad competitive analysis, industry assessment, strategy formulation, or any Porter-related question.

Build a comprehensive competitor profile using Porter's four-component framework. Use when asked to analyze a competitor, predict competitor moves, or assess competitive threats.

Determine what UI element draws attention first, second, third using size, weight, color, and de-emphasis strategies

Create clear typographic hierarchy using hand-crafted font sizes, weights, and colors

Create comprehensive palette with 8-10 greys, 5-10 primary, 5-10 accent shades

Use systematic spacing with 25% minimum jumps, start with excess whitespace

Create clear primary/secondary/tertiary action distinctions

Remove unnecessary borders, backgrounds, shadows, decorations

Create helpful, actionable zero-content states

Add depth only when functionally necessary (elevation, not decoration)

Use this skill after /pmf-research-synthesis has identified the riskiest PMF dimension. Takes that dimension (or any business idea/strategy) and runs a structured assumption extraction, mapping, and experiment design sequence. Triggers include: 'validate my riskiest dimension', 'extract assumptions', 'what are the riskiest assumptions', 'run assumption mapping', 'design an experiment', 'pressure test this', 'what could go wrong with this', or any request to surface and test specific assumptions before committing resources. Runs a guided Extract → Map → Test workflow.

Guide user through defining initial PMF narrative with 6 dimensions, confidence scores, and validation priorities. This skill should be used when starting a new product-market fit discovery process or formalizing an initial product insight into a structured hypothesis.

Conduct comprehensive market research across 6 PMF dimensions by identifying analogs (successes) and antilogs (failures) in parallel. This skill should be used after creating an initial PMF narrative (V1) to validate hypotheses with external market evidence before investing in customer interviews.

Synthesize market research and expert advice to identify the riskiest PMF dimension and update the narrative. This skill should be used after completing market research and optional expert calls to determine what to validate next.

Show current PMF project status and recommend next action. This skill should be used when checking where you are in the PMF workflow or deciding what to do next.

Produce a real, publication-ready data graphic (SVG or HTML) that obeys Tufte's principles — minimal ink, range-frame axes, direct labels, honest proportions. Use whenever someone wants to design, build, create, draw, or actually produce a chart the Tufte way, or to rebuild a chart after assessment found problems. This is the only skill in the toolkit that outputs an actual chart file.

Evaluate a data graphic against Edward Tufte's nine criteria, name the chartjunk species present, compute lie factor, compare against VDQI's named-failure catalogue, and return prioritised fixes tagged with the specific Tufte remedy (B1–B7), genre to switch to (C1–C10), and exemplar to emulate. Use whenever someone asks whether a chart is good, what is wrong with a chart, how to clean up or declutter a chart, whether a graphic is misleading, or for any Tufte-style critique of an existing visualization.

Router for the Tufte data-visualization toolkit. Use whenever someone has a chart or data-visualization request and you are not sure which Tufte skill to use — it decides between assessing an existing graphic, producing a new one, or fixing a cluttered/misleading one, and chains them when needed.