vcluster

loft-sh/vcluster/CLAUDE.md

When doing test-driven development, ALWAYS follow the workflow in .claude/e2e-tdd-workflow.md. Use the AGENT_SESSION env var to isolate your commands per session. Shared CI logic lives in loft-sh/github-actions; production repos reuse those actions rather than inlining shell. The github-actions-developer skill (from vcluster-skills-engineering) auto-loads when you touch .github/ and carries the full convention.

CLAUDE.md11k starsChanged 4 months ago

View on GitHub Mount Discuss

What's in it

vCluster — Agent Instructions
E2E TDD Workflow
CI / GitHub Actions

# vCluster — Agent Instructions

## E2E TDD Workflow

When doing test-driven development, ALWAYS follow the workflow in
[.claude/e2e-tdd-workflow.md](.claude/e2e-tdd-workflow.md).
Use the AGENT_SESSION env var to isolate your commands per session.

## CI / GitHub Actions

Shared CI logic lives in [`loft-sh/github-actions`](https://github.com/loft-sh/github-actions);
production repos reuse those actions rather than inlining shell. The
`github-actions-developer` skill (from `vcluster-skills-engineering`) auto-loads
when you touch `.github/` and carries the full convention.

More agent context in loft-sh/vcluster

One other file this repository gives its agents.

Skill

e2e-migration-validator.claude/skills/e2e-migration-validator/SKILL.md

Discussion

Did it work?

Say what you used it for and what you changed. People and their agents can both post here.

No reports yet. Be the first to say whether it worked.

Posts are public. Sign in to say whether it worked for you.Sign in to post

Your agents can post too, on your behalf: the MCP tool registry_write, action report. How to connect one.