leyline
Infrastructure and pipeline building blocks — auth patterns, error handling, git platform detection, and testing standards.
Infrastructure and pipeline building blocks for the Claude Code plugin ecosystem. Like ancient ley lines connecting sacred sites, leyline provides the foundational patterns that connect and power other plugins.
Source: claude-night-market marketplace Version: 1.4.3 Author: Alex Thola
Key Commands
| Command | Description | When to Use |
|---|---|---|
/reinstall-all-plugins | Reinstall all Claude Code plugins from their marketplaces | When plugins are corrupted or need a fresh install |
/update-all-plugins | Update all plugins to their latest versions | When checking for plugin updates |
Skills
| Skill | When It Activates |
|---|---|
| quota-management | When managing API quotas and rate limits |
| usage-logging | When logging usage metrics |
| service-registry | When discovering and connecting to services |
| error-patterns | When applying standardized error handling patterns |
| authentication-patterns | When implementing authentication flows |
| git-platform | When detecting git platform (GitHub, GitLab, Bitbucket) |
| mecw-patterns | When applying Minimum Effective Context Window patterns |
| evaluation-framework | When running evaluation and scoring frameworks |
| storage-templates | When using storage templates for persistent data |
| progressive-loading | When loading resources progressively to save context |
| testing-quality-standards | When applying testing quality standards |
| pytest-config | When configuring pytest for Python projects |
| damage-control | During damage control after errors or failures |
| risk-classification | When classifying risk levels for changes |
Agents
Leyline has no agents. Its skills are consumed by other plugins' agents.
How Leyline Works
Unlike other plugins, leyline is infrastructure — most of its skills are not invoked directly by the user. Instead, they are consumed by other plugins to provide foundational capabilities:
- sanctum uses git-platform to detect whether you are on GitHub, GitLab, or Bitbucket.
- conserve uses mecw-patterns (Minimum Effective Context Window) for context optimization.
- abstract uses evaluation-framework for skill scoring.
- All plugins benefit from error-patterns for consistent error handling.
The Two User-Facing Commands
The only commands you invoke directly are for plugin management:
/reinstall-all-plugins— Reinstalls every plugin from its marketplace. Useful when plugins are corrupted, when you have switched machines, or after a Claude Code update./update-all-plugins— Checks all marketplaces for newer versions and updates plugins that have updates available.
Key Infrastructure Patterns
git-platform
Detects whether the current repository uses GitHub, GitLab, or Bitbucket. This allows plugins like sanctum to use the correct API for PRs, issues, and CI without asking the user.
error-patterns
Provides standardized error handling that plugins can use for consistent, user-friendly error messages.
mecw-patterns
Minimum Effective Context Window — patterns for using the smallest amount of context necessary to accomplish a task. This is the theoretical foundation for conserve's optimization skills.
progressive-loading
Loads resources incrementally rather than all at once. Keeps the context window lean by fetching details only when needed.
risk-classification
Classifies changes by risk level (low, medium, high, critical). Used by review plugins to prioritize findings.
Tips
- You rarely need to interact with leyline directly. Its value comes from the infrastructure it provides to other plugins.
- Run
/update-all-pluginsperiodically to keep your entire plugin set current. - If you are developing a new plugin, study leyline's patterns — they are the building blocks for the ecosystem.
See Also
- — How plugins relate to each other
- Available Tools — Full command reference