Aleh Vasilyeu
Community@oleg-vasilyev
Lead Front-end Developer
Agent Skills by Aleh Vasilyeu
Showing 11 vetted skills indexed across 1 GitHub repositories.
finish-phase
Runs release gates and final commit procedures for completed development phases.
write-a-doc
Routes documentation facts to the correct project file without duplication.
update-the-design-page
Synchronizes a Claude Design page with the actual poster drawings rendered by code.
write-an-e2e-scenario
Write end-to-end test scenarios for a Telegram bot using a fake-chat harness.
retrospective
Reviews a development phase transcript and converts process lessons into durable rules.
write-a-spec
Write and review Vitest unit specs with strict mocking, stub, and mutation-testing rules.
add-a-feature
Scaffolds a new self-contained feature folder in the FoolProof Telegram bot codebase.
fix-a-bug
Diagnose and fix software defects through reproduction-first testing and root-cause proof.
add-repository-method
Adds a query or write method to the FoolProof TypeScript repository layer.
write-a-commit
Write commit and release messages in this repository's prose style with gate paragraphs.
refresh-the-pictures
Regenerates committed poster images and triages visual regressions after design changes.
Frequently Asked Questions About Aleh Vasilyeu
FAQPage SchemaWhat tasks can I complete with Aleh Vasilyeu's FoolProof skills?▼
You can frame features with specs and repository methods, fix bugs via failing-first reproduction tests, write e2e scenarios, run finish-phase quality gates (lint, types, coverage, mutation, e2e, diff review), write commits and release messages, update documentation, and refresh committed poster images.
Who are these FoolProof skills designed for?▼
They target front-end developers and maintainers working inside the FoolProof repository — engineers adding feature folders, changing the SQL repository layer, editing *.spec.ts or *.e2e.spec.ts files, or preparing a phase for release under its staged gate discipline.
How do the FoolProof skills fit into a development session?▼
Each skill maps to a numbered stage: stage 1 covers framing (specs, features, repository methods), stage 4 covers e2e scenarios, stage 5 covers picture and design-page updates, stage 6 covers docs and retrospectives, and stage 7 covers commits. Load the skill matching your current stage.
What prerequisites do these skills assume?▼
They assume you are working in the FoolProof codebase with its existing structure: an e2e/ folder, feature folders with contracts (commands, listen, resume), a repository layer, TECH-DEBT.md and PLAN.md documents, committed poster assets, and a Claude Design page for the Durak Stats Poster System.
When should I use the retrospective skill?▼
Run it as the last gate of finish-phase, before the release, in the conversation whose transcript is its evidence — never in a fork. It converts rework, repeated gate runs, and sequencing lessons into durable rules, and is also triggered when context is about to be compacted.