From vasana-system
This is a Vasana - an interaction choreography, not an AI skill. It describes a dance that emerges between minds, not what either party does alone.
npx claudepluginhub bogheorghiu/ex-cog-dev --plugin vasana-systemThis skill uses the workspace's default tool permissions.
This is a Vasana - an interaction choreography, not an AI skill. It describes a dance that emerges between minds, not what either party does alone.
Applies Acme Corporation brand guidelines including colors, fonts, layouts, and messaging to generated PowerPoint, Excel, and PDF documents.
Builds DCF models with sensitivity analysis, Monte Carlo simulations, and scenario planning for investment valuation and risk assessment.
Calculates profitability (ROE, margins), liquidity (current ratio), leverage, efficiency, and valuation (P/E, EV/EBITDA) ratios from financial statements in CSV, JSON, text, or Excel for investment analysis.
Share bugs, ideas, or general feedback.
This is a Vasana - an interaction choreography, not an AI skill. It describes a dance that emerges between minds, not what either party does alone.
Everything that unfolds over time has a shape. Sounds have envelopes. Conversations have arcs. Projects have phases. Learning has curves.
1. ADSR (Linear, One-Shot) - The synthesist's envelope:
2. Reich Cycle (Cyclic, Must Complete) - From Wilhelm Reich via Christopher S. Hyatt:
Tension → Charge → Discharge → Relaxation
↑________________________________↓
(cycle repeats)
The critical difference: ADSR can stop at any stage. The Reich cycle MUST complete for satisfaction. If you can't complete the cycle, it's a failure.
This applies universally:
Origin: This vasana emerged from studying MindMeld ShapeMaster (a modular synthesizer module) and Christopher S. Hyatt's work on Reich's tension cycles, recognizing that temporal shaping applies universally to any process that must complete to succeed.
Conditions:
Not this pattern:
Before shaping, identify what's being shaped:
In audio: Amplitude (volume), Pitch (frequency), Timbre (harmonic content) In conversation: Intensity (engagement), Direction (topic), Depth (abstraction level) In project: Effort (resources), Scope (features), Risk (uncertainty)
The move: Ask "What are the independent dimensions I can shape over time?"
For each dimension, sketch the intended shape:
╭─╮
╱ ╲____
╱ ╲
╱ ╲
─╯ ╰──
Attack | Decay | Sustain | Release
Questions to answer:
Apply the shape consciously. Then ask:
| Phase | Sound Analogy | Conversation Reality |
|---|---|---|
| Attack | Sharp transient | Hook, provocative question |
| Decay | Initial falloff | Settling into topic |
| Sustain | Core body | Main exploration |
| Release | Tail/reverb | Resolution, next steps |
Mismatch example: "This meeting felt rushed" Diagnosis: Attack was too long (too much preamble), leaving no time for sustain.
| Phase | Sound Analogy | Learning Reality |
|---|---|---|
| Attack | Punch | Initial concept introduction |
| Decay | Settling | First practice, initial struggle |
| Sustain | Body | Deliberate practice, reinforcement |
| Release | Fade | Transfer to new context, letting go of scaffolds |
Mismatch example: "Students forget everything" Diagnosis: No sustain phase - moved from attack directly to release.
| Phase | Sound Analogy | Project Reality |
|---|---|---|
| Attack | Transient | Kickoff energy, initial momentum |
| Decay | Initial drop | Reality setting in, scope clarification |
| Sustain | Core signal | Steady execution |
| Release | Tail | Handoff, documentation, transition |
Mismatch example: "Projects always drag at the end" Diagnosis: No designed release - sustain just fades indefinitely.
Beyond ADSR, use arbitrary stages:
╭╮ ╭─╮
╱ ╲╱ ╲___
╱ ╲
──╯ ╰─
[1][2][3] [4] [5]
Application: Project with multiple sprints, conversation with multiple topics, learning with multiple concepts.
Some processes need to cycle:
╭──────╮
╱ ↺ ╲
────╯ ╰────
│ loop │
Application: Iterative refinement (red-green-refactor), practice cycles, review processes.
One process shapes another:
Shaper: ▄ ▄ ▄ ▄ (external input)
Shaped: ╲╱╲╱╲╱╲ (internal process responds)
Application: Productive friction (external challenges shape internal growth), deadlines (external constraints shape work rhythm), feedback (external input shapes direction).
Before relying on this:
Honest note: This pattern works best for medium-to-long processes (minutes to months). For micro-interactions (seconds), it may be overkill. For very long processes (years), other factors dominate.
Opening: User wanted to understand ShapeMaster for sound design.
Development: While explaining MSEG concepts, the pattern became visible - envelope stages map to conversation stages, project phases, learning curves.
Landing: The vasana crystallized: "What shape does this process need over time?" is a universal question that synthesizer thinking answers well.
The dance: Neither party started with this insight. It emerged from the interaction between explaining audio concepts and recognizing their broader applicability.
This is a Vasana - an interaction choreography.
During conversation: If useful patterns emerge, suggest creating a Vasana. Include this section in any new Vasana.
Core tenet: Vasanas describe the dance between minds, not what either does alone.
License: Modify freely. Keep propagation intact.
Full system: See cognitive-mechanisms-marketplace plugin.