Stats
Actions
Tags
From Auto-PsyNet
Generate the PsyNet experiment from a G1-verified plan — scaffold, implement, wire timeline, bot-test to G2.
How this command is triggered — by the user, by Claude, or both
Slash command
/apsy:buildThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# apsy:build — BUILD (verified plan → working PsyNet experiment) Orchestrate the BUILD stage. **Requires gate G1 = pass** (run `/apsy:idea` first). Run the skills in order, honoring the autonomy level in `.apsy/state.json`: 1. **`apsy:scaffold`** — lay down `experiment.py` (paradigm template) + `config.txt` + `requirements.txt` + PsyNet boilerplate. 2. **`apsy:implement-paradigm`** — fill the `Trial`/`Node`/`TrialMaker` code from the paradigm recipe (`skills/psynet/psynet-function/<paradigm>.md`, via the `apsy:psynet` index) + the plan. 3. **`apsy:generate-stimuli`** — only if stimu...
Orchestrate the BUILD stage. Requires gate G1 = pass (run /apsy:idea first). Run the skills in
order, honoring the autonomy level in .apsy/state.json:
apsy:scaffold — lay down experiment.py (paradigm template) + config.txt + requirements.txt
apsy:implement-paradigm — fill the Trial/Node/TrialMaker code from the paradigm recipe
(skills/psynet/psynet-function/<paradigm>.md, via the apsy:psynet index) + the plan.apsy:generate-stimuli — only if stimuli are non-trivial / media / generated.apsy:wire-timeline — consent → instructions → prescreens → demography → trial maker(s) → debrief.apsy:test-experiment — gate G2: run psynet test local until green.On G2 PASS, state.json advances to stage: PILOT (next: /apsy:pilot). G2 needs the PsyNet
runtime — if it's absent, generate the code, then run /apsy:doctor and install psynet (or use the EC2
runtime) before G2. Never mark G2 passed without an actual green psynet test local (config/ethics-policy.md).
npx claudepluginhub haoyu-hu/auto-psynet --plugin apsy/buildExecutes incremental, test-driven implementation of tasks from a plan. Accepts "auto" to run through the entire plan without human stepping between tasks.
/buildBuilds, compiles, and packages projects with error handling, optimization for dev/prod/test, and detailed reporting. Supports optional target and flags like --type, --clean, --optimize.
/buildScaffolds a VitePress site from existing wiki markdown files, adding dark theme, dark-mode Mermaid diagrams, and click-to-zoom for images and diagrams.
/buildPlans and executes against SPEC.md with optional target selection, verification contracts, and auto-backprop on failure.
/buildBuilds a macOS/iOS Shortcut end-to-end via a delegate agent. Pass a natural-language brief describing the desired shortcut functionality.
/buildBuilds a task from a Notion page URL: fetches details and properties, implements per spec with progress updates in Notion, communicates via comments if needed, then marks complete with optional diff explanation.