Skip to main content

Playground

The playground/ folder contains small applications that can be used as coding targets while developing ProtoAgent. They are not the runtime engine.

Recipe Recommendation​

Path:

terminal
playground/recipe-reco/

Shape:

FileRole
api.pyFlask API.
app.pyApp entrypoint.
client.pyExample client.
recommender.pyRecommendation loop.
filters.pyIngredient and tag filters.
scoring.pyIntentionally simple scoring logic.
recipes.pySeed recipes.
storage.pyIn-memory recipe store.
models.pyData models.

Good ProtoAgent tasks:

terminal
explain @playground/recipe-reco/recommender.py
refactor the recipe scoring logic and keep behavior understandable
add tests for ingredient matching edge cases

Taskflow​

Path:

terminal
playground/taskflow/

Shape:

FileRole
server.pyFlask routes for task list, create, complete, search, stats.
service.pyTask business logic.
storage.pyIn-memory task store.
models.pyTask model.
utils.pySerialization helpers.
client.pyExample client.
app.pyApp entrypoint.

Good ProtoAgent tasks:

terminal
explain the taskflow route structure
add validation for empty task titles
propose tests for task completion and search

Why Keep Playground Apps Small​

Small apps are useful because they let you validate:

  1. Context Loom ranking.
  2. Explorer read/search behavior.
  3. Coder diff previews.
  4. Approval flow.
  5. Session memory.
  6. Trace and timeline quality.

They should stay simple enough that a local model can reason about them without expensive context or many exploratory turns.