New: canonical tasks, previews, docs, and skills

Build Better Tasks,
Preview Faster,
Share Clearer Workflows.

TaskBeacon brings together canonical tasks, the TAPS structure, PsyFlow authoring, psyflow-web previews, automation skills, and contribution guidance in one place.

Preview Tasks See Tasks

35+

Canonical tasks

2+

Web previews

3

Automation skills

T000002Smoke testedMar 09, 2026

Balloon Analogue Risk Task (BART)

A risk-taking task based on BART with color-specific burst profiles.

Overview

Explore The Main TaskBeacon Sections

Start here for the big picture, then jump into the section you need next.

Understand the Task Package Standard

See how TAPS keeps code, config, references, and docs in one auditable package.

FrameworkResource

Inspect PsyFlow and psyflow-web

Follow the local runtime and the browser preview layer as one connected stack.

Jump to framework

Use build, plot, and translation skills

Use automation skills for building, plotting, and local-to-web transfer.

TutorialResource

Learn localization, voice, and QA

Open practical guides for setup, localization, voice, and validation.

Jump to tutorials

ContributeResource

Contribute tasks and variants clearly

Start from the registry and keep variants explicit and reviewable.

Jump to contribute

TAPS

A structure standard for task packages, not just another gallery label.

TAPS organizes task logic, config, references, and documentation into a package that remains inspectable for labs, reviewers, and downstream tooling. It is the backbone that lets TaskBeacon pair canonical local tasks with aligned previews and reusable docs.

Entry Layer

README + taskbeacon.yaml

Start with one public description of the paradigm and one machine-readable metadata file.

Config

parameters, stimuli, subject info

Keep participant-facing text and tunable settings outside runtime code.

Runtime

main + run_trial + controller

Keep the task flow auditable and the state machine easy to review.

Evidence + Review

references + task flow artifacts

Map protocol evidence, plots, and README snapshots back to the implementation.

TAPS Outcome

One task package that stays readable across code, docs, and deployment.

Canonical local task for installation, editing, QA, and review

Optional aligned browser preview without breaking the local contract

Reusable documentation for localization, voice, publication, and contribution

Framework

PsyFlow authors the task. psyflow-web previews the same task in the browser.

Keep the local task canonical, then attach a browser-native companion only when it stays aligned.

Open Framework Page

PsyFlowResource

Local runtime and authoring workflow

Author canonical tasks, run QA and sim modes, and keep the local repo canonical.

psyflow-webResource

Shared browser preview runtime

Launch HTML companions from one shared runner and keep them aligned to local tasks.

Open psyflow-web

Skills

Automation skills for building, plotting, and translating tasks

These skills focus on concrete production work instead of generic prompts.

task-buildResource

Build literature-grounded PsyFlow tasks

Create or refactor cognitive tasks into validated PsyFlow/TAPS projects from literature evidence.

Open task-build

task-plotResource

Generate auditable task flow plots

Render condition-wise flow diagrams with audit artifacts for review.

task-py2jsResource

Port local tasks into aligned web previews

Convert a canonical PsyFlow task into an aligned psyflow-web companion.

Open task-py2js

Tutorial

Learn the practical workflows that matter first

Start with setup, then move into localization, voice instructions, and QA before release.

Getting StartedResource

Scaffold your first task

Start with project setup, task structure, and the first runnable experiment.

LocalizationResource

Translate task content without touching logic

Use config-driven localization instead of rewriting runtime code.

Open localization

Create instruction audio from config

See a concrete task example that keeps instruction audio inside task config.

Open voice example

CLI + QAResource

Validate tasks before release

Use the CLI and QA tutorials to inspect metadata and smoke-test tasks.

Contribute

Add new tasks and variants without making the catalog harder to read

Contribution should start with a clear registry path, explicit variant handling, and docs that stay usable before someone opens the source code.

Open Contribute Page

RegistryResource

Submit a new task

Start with task-registry issue templates and bring metadata with the task.

VariantsResource

Track meaningful branches

Keep major task variants explicit instead of hiding incompatible changes in place.

Read versioning