vasana-system

Browse, add, or update patterns in the library

Periodically reviews memories, builds insight graph, suggests improvement plans. Use when (1) starting new session and want growth review, (2) after completing significant work, (3) weekly self-audit, (4) user asks "what have you learned" or "how can we improve".

Am I trying harder at the wrong thing? - Detects stuckness loops and breaks them. Triggers on (1) explicit stuckness - "going in circles", "keep trying the same thing", "need fresh perspective", (2) implicit stuckness - blame-shifting ("the framework is broken"), false certainty ("I've tried everything"), escalation ("let me just try one more..."), (3) Claude self-observation - noticing own repeated similar attempts or escalating complexity. Does NOT trigger for first attempts, normal exploration, or standard debugging with clear errors. Core action: STOP the current approach, name the pattern, offer exit ramps to completely different approaches. References pattern-library for specific behavioral patterns.

Did I actually verify this, or am I assuming? - Challenges technical decisions against behavioral patterns before proceeding. Be direct. Be challenging. Point out BS. Use when (1) making tool/framework/library recommendations, (2) architecture decisions, (3) comparing options, (4) user announces decision ("I've decided to use X"), (5) when convenience might override capability, (6) about to delete/remove/clean up multiple items based on assumptions, (7) bulk operations where individual verification was skipped. Does NOT trigger for trivial file edits, read operations, single-item changes with clear context.

A vasana is a pattern that persists across unrelated contexts. If during

Use when a casual question leads to deeper exploration and the conversation seems to be building toward something larger - the pattern of curiosity → productive friction → iterative deepening → emergent system design. An interaction choreography for turning genuine inquiry into structured output.

**Seed question:** *Am I ACTUALLY done, or did I just stop?*

What patterns keep showing up across unrelated contexts? - Browse and apply universal behavioral patterns (vasanas) that persist across domains. Patterns are neutral observations about how behavior self-organizes - groove-deepening is also mastery, framework-dissolution can be premature. Use when (1) architecture feels forced or over-engineered despite following best practices, (2) debugging repeatedly reveals you're looking at the wrong layer or making incorrect assumptions, (3) standard patterns (MVC, CRUD, REST) don't map cleanly to the problem domain, (4) user explicitly requests "fresh perspective", "creative approach", or "think differently about this", (5) you notice habitual design choices constraining possibilities, (6) you observe yourself making repeated similar failed attempts (self-observation), (7) problem spans multiple domains or standard approaches repeatedly fail. Provides frameworks for concrete-to-abstract iteration, interface design as reality-creation, cross-domain analogies, and meta-debugging. Each pattern includes code examples, recognition signals, and integration with other patterns.

Records observed patterns with proper structure from current or described interactions. Use when (1) user explicitly asks to record a pattern, (2) user approved creating a pattern after vasana skill suggestion, or (3) user runs /pattern-library add command.

Am I investigating, or just confirming what I already believe? Self-correcting research methodology combining blind worker agents, nested iteration loops, and dialectic synthesis. Use when (1) research requires factual certainty not just plausibility, (2) topic has high bias risk, (3) multiple perspectives must be systematically tested, (4) user explicitly requests deep/thorough investigation, (5) previous single-pass research proved insufficient. Integrates with iterative-loop-engine and deep-investigation-protocol.

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.

Tests whether patterns actually work — trigger, emerge, and produce value. Use when (1) user wants to verify a pattern before relying on it, (2) user runs /test-pattern command, (3) a pattern was just recorded and needs verification, or (4) user suspects a pattern isn't working as expected.

Notices when patterns persist across unrelated contexts and suggests capturing them. Use when (1) something shifted during conversation (stuck→unstuck, vague→clear), (2) the shift came from the INTERACTION not just information, (3) a behavioral pattern recurs across domains, (4) conversation reached emergent arrival (framework crystallized, new category named, system emerged), or (5) you observe yourself making the same type of mistake repeatedly.

1 hook across 1 event