Skip to content

Add ephemeral environments pattern to canvas-builder#19

Open
bender-rodriguez-unit1 wants to merge 2 commits into
superplanehq:mainfrom
bender-rodriguez-unit1:pattern/ephemeral-environments
Open

Add ephemeral environments pattern to canvas-builder#19
bender-rodriguez-unit1 wants to merge 2 commits into
superplanehq:mainfrom
bender-rodriguez-unit1:pattern/ephemeral-environments

Conversation

@bender-rodriguez-unit1
Copy link
Copy Markdown
Collaborator

@bender-rodriguez-unit1 bender-rodriguez-unit1 commented Apr 27, 2026

What

Adds a reference architecture pattern for ephemeral/preview environments to the superplane-canvas-builder skill.

Why

This pattern was built and battle-tested during Mission 2 (ephemeral environments for puppies-inc/storejs). It captures the architecture, memory design, critical rules, and lessons learned so future agents can reproduce it for any user — regardless of what integrations they use.

What's in it

  • 5-step build process: discover integrations → pick trigger strategy → build lifecycle paths → configure memory → verify
  • 5 lifecycle paths: provision, manual destroy, auto-destroy on close, TTL reaper, welcome message
  • 3 trigger strategies (with room for adaptation): command-based, auto-on-open, hybrid
  • 3-namespace memory design: environments, env-internal, env-metadata
  • 8 critical rules from production bugs (ghost entries, silent chain death, scientific notation, etc.)

The doc is integration-agnostic — instead of hardcoded substitution tables, it teaches agents to discover what's connected and pick the right components at build time.

Files changed

  • skills/superplane-canvas-builder/SKILL.md — added Patterns section with link
  • skills/superplane-canvas-builder/references/patterns/ephemeral-environments.md — the pattern doc (143 lines, new)

Bender Rodriguez added 2 commits April 27, 2026 09:44
Reference architecture for on-demand preview/staging environments.

3-layer design:
- Layer 1: Lifecycle core (5 workflow paths, 3-namespace memory, critical rules)
- Layer 2: Trigger strategies (command-based, auto-on-PR, chat, manual, hybrid)
- Layer 3: Integration substitution (infra, SCM, notifications)

Includes lessons learned from production use.
- Removed all provider-specific tables (DO, AWS, GitHub, GitLab, etc.)
- Replaced 'ask the user' with 'discover via CLI first, then confirm'
- Stripped provider-specific expressions (agent checks provider docs)
- Simplified layer naming to sequential steps
- Kept: lifecycle paths, memory design, critical rules, lessons learned
- Halved the doc size while keeping all the architecture
@AleksandarCole AleksandarCole self-assigned this Apr 27, 2026

## Critical Rules

These are real bugs found in production. Don't skip them.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

```bash
superplane index triggers --from <scm-provider>
superplane index components --from <scm-provider>
superplane index components --from <infra-provider>
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is no longer true. cc @lucaspin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants