Jacek Palczewski
Community@jpalczewski · Olsztyn, Poland
Jacek Palczewski maintains skills for the kajet-turbo project covering TypeScript API client regeneration, full-stack verification suites, and GitHub project board issue triage.
Agent Skills by Jacek Palczewski
Showing 6 vetted skills indexed across 1 GitHub repositories.
generate-api
Regenerates the frontend TypeScript API client from the FastAPI OpenAPI schema using orval.
verify
Launches kajet-turbo with a temp database and fake embeddings to exercise the REST API end-to-end.
next-selection
Selects and groups prioritized backlog issues into a balanced Next column round.
backlog-triage
Triage GitHub project board Inbox issues into prioritized Backlog entries.
issue-filing
Create and label GitHub issues and epics following kajet-turbo project conventions.
check
Runs backend and frontend verification suites for the kajet-turbo codebase.
Frequently Asked Questions About Jacek Palczewski
FAQPage SchemaWhat tasks can I perform with jpalczewski's skills?▼
You can regenerate the frontend TypeScript API client from FastAPI OpenAPI schemas via orval, run backend (ruff, ty, pytest) and frontend (prettier, eslint, svelte-check) verification suites, file labeled GitHub issues and epics, triage Inbox items into a prioritized Backlog, and select the Next column's work.
Who are these skills designed for?▼
They target developers and maintainers working on the kajet-turbo project who need to keep the frontend client in sync with backend API changes, verify code health before commits, and manage the GitHub project board's Inbox, Backlog, and Next columns with consistent conventions.
How does the verification workflow run in practice?▼
The check skill runs the full suite: backend ruff, ty, and pytest plus frontend prettier, eslint, and svelte-check. The verify skill additionally runs kajet-turbo locally against a temp database and fake embedding endpoint, exercising login, notes, jobs, and reindex end-to-end.
What prerequisites do these skills require?▼
They assume the kajet-turbo repository with a FastAPI backend and Svelte/TypeScript frontend, plus installed toolchains: orval for client generation, ruff, ty, and pytest for Python, and prettier, eslint, and svelte-check for the frontend. Board skills require access to the GitHub project board.
How do the board management skills handle prioritization safely?▼
backlog-triage reads every Inbox issue, checks it against origin/main for obsolete premises, and proposes P0-P3 priorities grouped by theme. next-selection picks a balanced round of fixes, refactors, and features respecting blocked-by chains. Both apply changes to the board only after user approval.