Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

experiment-bootstrap

Étoiles1

Forks0

Mis à jour26 avril 2026 à 01:12

Bootstrap new repo experiments with the red conventions for folder layout, runtime config, testing, and compose-based e2e.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Bind

Bind/red

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

3 fichiers

SKILL.md

readonly

name	experiment-bootstrap
description	Bootstrap new repo experiments with the red conventions for folder layout, runtime config, testing, and compose-based e2e.

Experiment Bootstrap

Use this skill when starting a new experiment under experiments/, or when standardizing an existing one onto the repo's experiment conventions.

Workflow

Create the experiment under experiments/<name>/.
Use a thin root with src/, compose/, README.md, Dockerfile, docker-compose.yml, package.json, tsconfig.json, and a local bun.lock.
Keep source layout singular:
- src/service/ for runtime services and adapters
- src/store/ for persistence abstractions
- src/util/ for config, errors, and shared types
- src/test/ for tests and fixtures
Keep HTTP routes thin; push behavior into services.
Use Hono for web routes, Bun for runtime, Biome for lint/format, and just for commands.
Make Compose strict: explicit env vars, fail-fast startup, and health checks that wait for readiness.
Prefer test-only fixtures over test-only state mutation routes. Delivery sinks may be fake; lifecycle transitions should be service-driven.
Verify the experiment with typecheck, tests, and compose E2E before calling it ready.

Conventions

Read the experiment checklist before scaffolding or refactoring an experiment.

Plus depuis ce dépôt

même dépôt

craft-release

Bind/red

Cut a production release for red and verify it is healthy in production. Use when the user wants to tag and publish a release, monitor the GitHub Release workflow, confirm `red.computer` is healthy after deploy, or reason about rollback for a bad production release.

2026-05-091

create-repo-daemon

Bind/red

Full lifecycle for repo daemons — create, seed memory, run, and refine via interactive resume. Use when adding a new `*.daemon.md` audit agent, tightening an existing one, seeding a daemon's initial memory with tracked facts from authority files, or verifying a new daemon reasons correctly before CI rotation.

2026-05-051

debug-preview

Bind/red

Debug a red preview deployment on the shared Hetzner box. Use when a preview URL, deploy, remote service, or per-PR stack needs investigation over SSH, or when you need to find where preview services, logs, caddy routes, env files, and compose state live on the host.

2026-04-261

wide-events-observability

Bind/red

Use when debugging red request flow, verifying wide-events ingestion, inspecting MinIO raw or rollup data, checking request_id propagation, or quickly tracing why a request did or did not materialize into a canonical rollup.

2026-04-261

name	experiment-bootstrap
description	Bootstrap new repo experiments with the red conventions for folder layout, runtime config, testing, and compose-based e2e.

Experiment Bootstrap

Use this skill when starting a new experiment under experiments/, or when standardizing an existing one onto the repo's experiment conventions.

Workflow

Create the experiment under experiments/<name>/.
Use a thin root with src/, compose/, README.md, Dockerfile, docker-compose.yml, package.json, tsconfig.json, and a local bun.lock.
Keep source layout singular:
- src/service/ for runtime services and adapters
- src/store/ for persistence abstractions
- src/util/ for config, errors, and shared types
- src/test/ for tests and fixtures
Keep HTTP routes thin; push behavior into services.
Use Hono for web routes, Bun for runtime, Biome for lint/format, and just for commands.
Make Compose strict: explicit env vars, fail-fast startup, and health checks that wait for readiness.
Prefer test-only fixtures over test-only state mutation routes. Delivery sinks may be fake; lifecycle transitions should be service-driven.
Verify the experiment with typecheck, tests, and compose E2E before calling it ready.

Conventions

Read the experiment checklist before scaffolding or refactoring an experiment.