Render financial charts via the local chart web app (workspace at the repo root — Hono server + React front end, port 1792). Four chart types: intraday capital-flow line (flow) and cross-symbol signed-bar comparison (cohort) — both Recharts — plus SEPA strategy dashboard (sepa) and short-term multi-timeframe…
Short-term multi-timeframe (5m/15m/1h) technical read for a single symbol — pulls K-line across three timeframes, reads MACD + swing structure, writes a direction call (long/short/neutral) with an explicit anchor price, a 2–4 scenario forward read, a range-bound playbook (long tactic + short tactic; a neutral call…
A checklist for reviewing trading actions before buying, adding to a position, selling, or reducing one. It records whether the decision followed the checks, but does not technically block orders.
An investment-research workflow based on value-investing viewpoints associated with four well-known investors. It routes a question to the relevant research steps and produces a structured web report.
A workflow for writing a researched series of three to eight independent long-form articles that explain a company in depth. The series covers the business, important changes, evidence, risks, and decision points.
A financial-data checking guide for verifying figures such as revenue, profit, market value, and valuation ratios. It uses financial statements and market quotes, then checks calculations with a second source when available.
Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, or applications and the visual direction matters as much as the code quality.
Add or modify HTTP endpoints in a Darto (Dart) web app — verbs, path/query params, request-body reading, route groups, and Context response helpers. Use when building or changing API routes in a project that depends on the darto package (import 'package:darto/darto.dart'). Not for Express/Node — Darto handlers take a…
Validate the body, query, params, or headers of a Darto (Dart) request using the zValidator middleware and zard (Zod-style) schemas. Use when adding input validation to a Darto endpoint, defining a z.map/z.string/z.int schema, reading validated data with c.req.valid, or customizing the validation error response.…
Write and register middleware in a Darto (Dart) app — the Middleware factory pattern, global/path-scoped/route-level registration, short-circuiting, per-request state, and global error/404 handlers. Use when adding cross-cutting behavior (auth, logging, CORS, timing) or configuring app.onError / app.notFound in a…
How to instrument features on www.gamedev.pl so product health stays measurable — the telemetry architecture, its privacy invariants, the event vocabulary, and the questions the data must always be able to answer. Use whenever you add or change a user-facing flow (play, creation, sign-in, sharing, party mode), touch…
Safely verify code produced by any autonomous coding agent (Copilot, agy, Codex, a subagent, or a containerized CLI) before trusting or merging it. Use whenever you are about to accept, review, or merge work you did not write yourself, or when running agents in parallel against a shared repo.
A/B testing and feature optimization for AI agents. Pick the best option automatically using Multi-Armed Bandits and Contextual Bandits (LinUCB). No data warehouse needed — works from request.
Decision intelligence for AI agents. Analyze options, map decision dependencies with PageRank, detect when information sources conflict, and find the choices that matter most.
A pathfinding and task sequencing for AI agents. Find the optimal path through workflows, dependencies, and decision trees. K-shortest paths via Yen's algorithm. Cost/time/risk breakdown.
Use Kanera MCP tools to search product guidance and discover, inspect, summarize, triage, create, or update project work. Trigger for requests about Kanera behavior, workspaces, boards, cards, standups, notes, comments, checklists, labels, custom fields, due dates, or project status.
Use when a WISP run failed unexpectedly or is stuck — fetches the event timeline for a run, highlights failures, and prints the verify-failed payloads with full output so the user can see exactly why a task failed. Trigger on phrases like "why did the run fail", "diagnose the harness", "what went wrong with the run".
Use when the user wants to inspect the result branch of a completed WISP run — shows files in the result branch, the per-task git log graph, and a brief summary. Trigger on phrases like "what did harness produce", "show the run output", "inspect the result branch".
Use when the user wants to resume a previously paused WISP run (e.g. paused by rate-limit, by /pause, or by an earlier shutdown). Lists resumable runs and resumes a chosen one. Trigger on phrases like "resume my run", "continue the harness", "pick up where we left off".