What patterns keep showing up across unrelated contexts? - Consult and apply the pattern library: behavioral patterns (vasanas) that persist across domains — analysis, argument, research, design, markets, code. Patterns are neutral observations of how behavior self-organizes, NOT anti-patterns: groove-deepening is also mastery, framework-dissolution can be premature. Use when (1) asking what known pattern or mechanism fits a situation, or to browse/apply the library, (2) a framing, design, or architecture feels forced or over-engineered despite best practices — wrong frame before any retry loop, (3) the field's textbook approach doesn't map cleanly to the problem, (4) a problem resonates with another domain ("this is like X in another field") and needs the mechanism check first, (5) stuckness was just named and an alternative is needed — the library is the exit ramp. Boundaries: active stuckness loops fire break-pattern (which routes here); verifying a newly observed pattern across domains is find-similar.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryScience & researchStars0
About this skill
What patterns keep showing up across unrelated contexts? - Consult and apply the pattern library: behavioral patterns (vasanas) that persist across domains — analysis, argument, research, design, markets, code. Patterns are neutral observations of how behavior self-organizes, NOT anti-patterns: groove-deepening is also mastery, framework-dissolution can be premature. Use when (1) asking what known pattern or mechanism fits a situation, or to browse/apply the library, (2) a framing, design, or architecture feels forced or over-engineered despite best practices — wrong frame before any retry loop, (3) the field's textbook approach doesn't map cleanly to the problem, (4) a problem resonates with another domain ("this is like X in another field") and needs the mechanism check first, (5) stuckness was just named and an alternative is needed — the library is the exit ramp. Boundaries: active stuckness loops fire break-pattern (which routes here); verifying a newly observed pattern across domains is find-similar.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
What patterns keep showing up across unrelated contexts? - Consult and apply the pattern library: behavioral patterns (vasanas) that persist across domains — analysis, argument, research, design, markets, code. Patterns are neutral observations of how behavior self-organizes, NOT anti-patterns: groove-deepening is also mastery, framework-dissolution can be premature. Use when (1) asking what known pattern or mechanism fits a situation, or to browse/apply the library, (2) a framing, design, or architecture feels forced or over-engineered despite best practices — wrong frame before any retry loop, (3) the field's textbook approach doesn't map cleanly to the problem, (4) a problem resonates with another domain ("this is like X in another field") and needs the mechanism check first, (5) stuckness was just named and an alternative is needed — the library is the exit ramp. Boundaries: active stuckness loops fire break-pattern (which routes here); verifying a newly observed pattern across domains is find-similar.
About this listing
Category
Science & research
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI