Skip to main content
adam-s
GitHub creator profile

adam-s

Repository-level view of 74 collected skills across 13 GitHub repositories.

skills collected
74
repositories
13
updated
Aug 13, 2026
repository map

Where the skills live

Top repositories by collected skill count, with their share of this creator catalog and occupation spread.

Showing the top 8 repositories here; full repository list continues below.
repository explorer

Repositories and representative skills

market-data-integrity
software-developers

Market data integrity rules — gap filling, look-forward bias prevention, and stock split handling. Use when writing or reviewing code that loads prices, fills missing data, computes returns, backtests strategies, or makes trading decisions. Applies across…

Feb 12, 2026
debug-logs
software-developers

Analyze Volatio debug logs from /tmp/volatio-debug/. Use when the user asks to check debug logs, analyze problems, or diagnose simulation issues.

Feb 7, 2026
systematic-testing
software-quality-assurance-analysts-and-testers

Apply bottom-up systematic testing to a multi-layer system. Use when asked to test, debug, or verify a pipeline that spans multiple layers (e.g., Python worker → bridge → processor → API → UI).

Feb 7, 2026
drizzle-migrations
software-developers

Drizzle Kit workflow for Volatio using idempotent migrations (generate + edit + migrate), never use push. Idempotent patterns prevent partial failure issues, enable safe re-runs, and work cleanly in CI. Use when schema changes, migration errors, or database…

Jan 29, 2026
experiment-creation
data-scientists-152051

Template for creating Volatio research experiments with Optuna optimization and portfolio backtesting. Includes proper train/test splits, lookahead bias prevention, results saving, and validated patterns from Exp 051-053.

Jan 20, 2026
lookahead-bias-checklist
data-scientists-152051

Financial research look-ahead bias verification for Volatio ML pipelines, mandatory baseline comparisons, timezone handling, feature leakage detection. Use when model accuracy seems too good or validating prediction experiments.

Jan 14, 2026
research-progression-docs
software-developers

Creating PROGRESSION.md documents for research experiment series in Volatio. Captures the evolution of ideas, learnings, and breakthroughs across numbered experiments (001, 002, ...). Use when documenting experiment series or reviewing research evolution.

Jan 10, 2026
ci-local-parity
software-developers

Run Volatio CI locally before pushing (ci-local.sh), mirrors GitHub Actions exactly, catches failures fast. Use when preparing to push, debugging CI failures, or verifying changes will pass.

Jan 10, 2026
Showing 8 of 13 collected skills.
api-discovery
software-developers

Discover any website's API and create domain plugins with proxy routes. Use when the user wants to create an API for a website, discover a web service's data transport, add a new domain, capture browser traffic, build typed API clients, or integrate with a…

Mar 24, 2026
app
software-developers

Build a complete application from a short description. Asks the developer clarifying questions, generates data requirements, launches discovery agents, and builds a dashboard. Use when the developer describes what they want to build in plain language —…

Mar 24, 2026
ec2-deploy
network-and-computer-systems-administrators

Deploy to EC2 production server. Use when deploying new code, rebuilding Docker images, wiping and reseeding the database, checking container health, or managing the EC2 instance via AWS CLI.

Mar 24, 2026
ci-check
software-developers

Run local CI checks and verify GitHub Actions status. Use before committing, after pushing, or when asked to check/fix CI.

Mar 23, 2026
dashboard-builder
web-developers

Build Next.js dashboard pages that consume domain proxy APIs. Use when the user wants to create a dashboard, build a UI page, add a search interface, display data from captured APIs, create comparison views, or build any frontend that calls /api/<domain>/…

Mar 23, 2026
debug-logs
software-developers

Iterative debugging with targeted logs. Use when browser connections fail, traffic capture returns empty, proxy routes return errors, WebSocket issues, or any problem that can't be solved on the first attempt. Add logs, read output, narrow the search, repeat…

Mar 23, 2026
instruction-dashboard-tuning
software-developers

Use sub-agents to iteratively improve dashboard-building instructions. Three-phase pipeline — discover APIs, build dashboard matching a wireframe, review code + UI with a SOTA reviewer agent. The dashboards are throwaway; instruction improvements and…

Mar 23, 2026
instruction-tuning
computer-occupations-all-other

Use sub-agents as test subjects to iteratively improve .claude/ instruction files. Run agent → inspect → fix instructions → re-run until agents follow the protocol correctly without hints.

Mar 23, 2026
Showing 8 of 10 collected skills.
citation-audit
software-quality-assurance-analysts-and-testers

Audit every user-facing legal citation in apps/web against the canonical OBL register at docs/case-management-research/enforcement-map.md. Enforces the three-tier legal-leakage taxonomy from CLAUDE.md — verbatim regulation text lives only in…

Jun 21, 2026
design-consistency
web-and-digital-interface-designers

Adversarial review of design-system fidelity in the plugin/ subtree (plugins/*/src/pages, plugins/*/src/components, packages/ui). Hunts editorial drift (facts surfaced twice, sections that dump tables instead of answering questions, lists that should be…

Jun 21, 2026
harness-run
software-quality-assurance-analysts-and-testers

Drive one or more control-room workflows end-to-end and diff the capture against the prior run for the same workflow. Surfaces which (persona, step) cells changed and why, so a cascade regression caused by a recent change becomes a structured finding instead…

Jun 21, 2026
mutation-red-team
software-quality-assurance-analysts-and-testers

Inline mutation testing for the apps/ monorepo — inject targeted regressions into @iep/domain (machine guards, rights derivation), @iep/data (Drizzle queries, schema), @iep/services (mutation contracts, composition), or apps/web (server actions), then run…

Jun 21, 2026
red-team-plugin
software-developers

Adversarial bug-hunting code review of the plugin-first framework in plugin/ — @plugin/{core,runtime,ui}, the host app, and plugin packages. Hunts real bugs in manifest validation, merger floor enforcement, mutator atomicity, registry collision detection,…

Jun 21, 2026
red-team-review
software-developers

Adversarial bug-hunting code review of the apps/ monorepo — apps/web, @iep/domain, @iep/data, @iep/services, @iep/auth. Hunts real bugs in state-machine guards, rights derivation, Drizzle queries, server actions, persona/audit emission, and idempotent…

Jun 21, 2026
test-red-team
software-quality-assurance-analysts-and-testers

Adversarial review of the TEST AND VALIDATION SURFACE of the apps/ monorepo — vitest unit suites in @iep/domain + @iep/data + @iep/services + @iep/ui + apps/web, the Drizzle integration tests under @iep/data/queries, the boundary.test.ts pattern enforcers in…

Jun 21, 2026
contribute
software-developers

Find a real upstream PrairieLearn bug with no open PR, reproduce + fix it in the harness, and publish it as an issue + pull request ON THE USER'S OWN FORK (never upstream) — packaged as a human-readable proposal a maintainer could copy over. Wraps debug-issue…

Jun 8, 2026
debug-issue
software-quality-assurance-analysts-and-testers

Drive one PrairieLearn GitHub issue or PR end-to-end through the harness — PRE-FLIGHT → GATHER → SCAN → CLASSIFY → BUILD. Spawns an isolated worktree + Docker journey, reproduces the bug with Playwright, injects the trace spine closest to the suspect code,…

Jun 7, 2026
journey-run
software-quality-assurance-analysts-and-testers

Drive a PrairieLearn Playwright journey — persona switching (student/instructor/admin), render-gating (never screenshot a blank/500 and call it fine), numbered before/after screenshots, socket-safe waits, and cold-vs-warm diffing. Spins the journey's…

Jun 7, 2026
slice
software-developers

Isolate one file/function/module and exercise it in isolation with full observability — instrument its inputs, intermediate values, and return with timestamped trace logs (Python or TS/JS), drive it with crafted cases, and assert expected results. The fastest…

Jun 7, 2026
trace
software-developers

Add precise timestamped debug logging across PrairieLearn using the concentric/adaptive model — start at the code CLOSEST to the issue (ring 0), read the merged cross-process timeline, widen the field only if the narrow ring didn't reveal it. Covers the…

Jun 6, 2026
tune
software-developers

Run one eval-driven instruction-tuning iteration on the harness itself. A blind sub-agent solves a CLOSED PrairieLearn issue (no access to the merged fix or this conversation), a blind judge compares its answer to the accepted PR, and you diagnose where the…

Jun 3, 2026
red-team
software-quality-assurance-analysts-and-testers

Adversarial bug-hunting review of a PrairieLearn diff, PR, or worktree change — hunts REAL bugs (not style) in the seams where PL breaks: the TS⇄Python code-caller boundary, zygote serialization, SQL/Drizzle edge cases, assessment/grading state, socket event…

Jun 2, 2026
mutation-red-team
software-quality-assurance-analysts-and-testers

Launch an adversarial mutation-testing agent (Opus) that injects targeted regressions into production code, runs the test suite, and reports which mutations SURVIVED — surviving mutations are direct evidence of test-coverage gaps. Use when the user says…

Jul 2, 2026
audit
software-quality-assurance-analysts-and-testers

Run a bounded live audit of the extension against multiple HN handles in parallel — Playwright + real Chromium + real HN, time-series snapshots, deterministic divergence analysis. Use when the user asks to "audit", "sit and observe", "live test", or "check…

Jul 1, 2026
design-critique
web-and-digital-interface-designers

Launch a Jony Ive–style product design adversary (Opus) to critique UI/UX *within* the project's existing aesthetic constraints. Finds what is graceless, disproportionate, clumsy — in the designer's own voice. Use when the user wants a "design critique",…

Jul 1, 2026
red-team-review
software-quality-assurance-analysts-and-testers

Launch an adversarial bug-hunting code reviewer (Opus) to find real bugs, correctness issues, concurrency hazards, and server/resource abuse risks — not style nits. Use when the user asks for a "red team", "bug hunt", "adversarial review", or at checkpoints…

Jul 1, 2026
test-red-team
software-quality-assurance-analysts-and-testers

Launch an adversarial reviewer (Opus) to find bugs IN THE TEST SUITE — tautological assertions, weak oracles, shim/mock lies, stale fixtures, coverage gaps, clock-mock pitfalls. Use when the user says "red team the tests", "audit the tests", "are our tests…

Jul 1, 2026
cluster-loop
network-and-computer-systems-administrators

Operating manual for the local GitOps twin (kind + registry + Gitea + Flux) — how to drive it, how to read it, and the failure catalogue that cost real time to learn. Use when working on deploy/, clusters/, scripts/cluster.mjs, scripts/gitops.mjs,…

Aug 13, 2026
red-team-temporal
software-quality-assurance-analysts-and-testers

Adversarial review of TIME — instants, calendar dates, zones, DST, precision and ordering — across this repo's store, wire and run planes; hunts the defect that never throws (a plausible-looking wrong moment) and reports it only with the input that produces…

Aug 13, 2026
stress-test
software-quality-assurance-analysts-and-testers

Load-test the API with stress.mjs scenarios (read-heavy, cold-heavy, ingest-heavy, mixed, rate-limit-storm), snapshot /metrics before and after, and write a findings report naming any failing budget. Use for stress testing, load testing, soak checks, or…

Aug 13, 2026
obs-verify
network-and-computer-systems-administrators

Audit the observability system itself — every catalog metric present at /metrics with expected labels, bounded label cardinality, Prometheus targets all up, budgets board agreeing with direct PromQL. Use after adding or renaming a metric, when…

Aug 13, 2026
perf-verify
software-developers

Verify a performance change with before/after evidence — baseline runs, labeled diffs, then the asserting layer. Use when optimizing API or web performance, investigating a perf regression, comparing latency, DOM nodes, or script time across a change, or…

Aug 13, 2026
Showing 12 of 13 repositories