Ecosystem Patterns FAQs

Question 1

What does the Ecosystem Patterns skill do?

Accepted Answer

This skill enforces a standardized environment for Claude Code. It implements the iMi worktree system for branch management, establishes naming conventions for paths and aliases, and ensures all projects follow a specific tech stack (like UV for Python and Cargo for Rust) to maintain consistency across repositories.

Question 2

What tech stacks are prioritized by this skill?

Accepted Answer

The skill defaults to a high-performance stack: UV for Python, Cargo for Rust, Vite for React, ShadCN/UI for components, and FastMCP for server development. It also ensures that Mise is used for tool versioning and Mise Tasks are used for script orchestration.

Question 3

How does this skill prevent 'Script Disease'?

Accepted Answer

The skill enforces the 'No-Script-Disease' rule, which strictly prohibits Claude from creating versioned file variants like 'script-v2.sh' or 'build-old.sh'. Instead, it forces in-place updates and leverages Git history for rollbacks, preventing technical debt and directory clutter.

Question 4

When should I use the Ecosystem Patterns skill?

Accepted Answer

You should use this skill when initializing new projects, refactoring existing repositories, or when you need Claude to generate documentation that syncs with an Obsidian vault. It is essential whenever you want Claude to respect a deterministic project structure and specific tool versions managed by Mise.

Question 5

How does it improve my AI-assisted coding workflow?

Accepted Answer

It reduces complexity by trading agency for deterministic behavior. By providing Claude with a strict framework—such as universal paths ($CODE, $VAULT) and standardized project layouts—it minimizes the tokens spent on orientation and prevents common architecture mistakes.

Ecosystem Patterns

Ecosystem Patterns

Key Features

Use Cases

Key Features

Use Cases