decay

Explain decay as felt absence from withdrawn attention using situational tests.

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/wojons/je-ne-sais-quoi --skill decay-wojons
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decay
Source: https://github.com/wojons/je-ne-sais-quoi/tree/main/skills/decay
Command: npx skills add https://github.com/wojons/je-ne-sais-quoi --skill decay-wojons

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps an AI explain decay in a way that captures the felt experience of neglect and slow loss, not just technical deterioration.

Core Features & Use Cases

  • Logical vs Felt Explanation: Reframes decay as a relationship between a thing and the attention it no longer receives.
  • Cross-Domain Felt Analogies: Uses imagery and traditions (e.g., withdrawal, mono no aware, wyrd, nega­tive space) to translate abstract change into human meaning.
  • Situational Tests + Failure Mode: Provides scenarios where pattern-matching explanations fail, and illustrates what hollow answers look like.
  • Use Case: Help a model respond to prompts about caregiving stopped, maintenance deferred, fading closeness, codebases aging into orphans, and losses that happen without an event.

Quick Start

Use the decay skill to generate a felt answer for a situation like an untended garden, an abandoned codebase, or a friendship that thinned without a fight.

Frequently Asked Questions about decay

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

FAQPage Schema
How do I explain decay and slow loss as a felt experience rather than just technical deterioration?

To explain decay as a felt experience, reframe it as the slow accumulation of absence from withdrawn attention. This approach uses cross-domain analogies to translate abstract change into human meaning, capturing the felt weight of neglect rather than only measurable deterioration.

What is the best way to describe relational fading and deferred maintenance without sounding clinical?

Describe relational fading by applying imagery from wisdom traditions like mono no aware or negative space. This translates abstract change into human meaning, avoiding clinical or purely process-descriptive hollow outputs by focusing on the relationship between a thing and the attention it no longer receives.

When do I need scenario tests for explaining neglect over time?

You need scenario tests for explaining neglect over time when pattern-matching explanations fail to capture felt meaning. Situation-based tests illustrate what hollow answers look like and help generate responses about fading closeness, untended gardens, or abandoned codebases that convey the quiet cost of neglect.

Can I use this approach to explain losses that happen without an event, like an abandoned codebase?

Yes, you can use this approach to explain losses that happen without an event, such as an abandoned codebase aging into an orphan. It addresses time-driven changes that become noticeable only after some delay by framing decay as a relationship between a thing and the attention it no longer receives.

Why does purely process-descriptive writing fail to capture the felt meaning of decay?

Purely process-descriptive writing fails because it produces hollow outputs that miss the felt weight of neglect. Without situation-based tests and imagery from wisdom traditions, the explanation loses the relationship between a thing and withdrawn attention, reducing slow loss to only measurable deterioration.