janjaszczak
28 verified skills
data-import-parsers
Implement or refactor data import/parsing so it streams files sequentially (memory-safe), validates/coerces types explicitly, skips irreparable records while logging them to an error CSV (full original columns + timestamp/file/line/error), emits rows_ok/rows_skipped/parse_errors metrics, and guarantees idempotent DB writes.
development
migration-and-doc-consolidation
Execute end-to-end migrations and consolidate docs/scripts (remove dead files, keep canonical runbooks). Use when changing runtime model, reorganizing repo, or doing “repo cleanup”.
documentation
task-planning-shrimp
Plan, split, and track multi-step work using Shrimp Task Manager MCP (or equivalent). Use for multi-file refactors, migrations, or any work that benefits from task tracking.
tools
cursor-deeplinks
Generate Cursor deeplinks (prompt/command/rule and MCP install links) using the repo generator and the project output contract. Use when the user asks for a Cursor deeplink, cursor:// links, cursor.com/link links, or wants to create prompts/commands/rules via deeplinks.
tools
deep-research
Conduct deep, source-grounded research with freshness checks and citations, then synthesize an actionable answer. Use for time-sensitive, niche, or high-stakes topics; when the user asks to “zweryfikuj”, “zrób research”, or when uncertainty is high.
testing
cross-platform-safety
Ensure commands and paths are safe across Windows + WSL + Docker (PowerShell vs bash, path translation, permissions). Use when instructions touch shell, filesystem, Docker, or OS-specific behavior.
testing
high-risk-review
Apply enhanced verification (CoVe-like review, security/arch/perf checks, targeted web research) for high-risk tasks or uncertainty. Use for security, infra, data loss risk, major refactors, or when facts may be outdated.
development
KeePassXC Integration
Integracja KeePassXC z Cursorem do bezpiecznego zarządzania sekretami (hasła, tokeny API, klucze SSH)
development
mcp-github-ops
Use GitHub MCP for issue/PR context, diffs, reviews, and automations. Use when the task references PR/issue numbers, review requests, or requires repo metadata beyond local git.
tools
mcp-apify
Use Apify Actors for scraping/data acquisition pipelines. Use when data collection from websites is required and needs repeatable runs.
tools
mcp-browser-verify
Use browser automation MCP (Playwright/Browser/Browser-Use) to validate UI flows, capture screenshots, and reproduce issues. Use when visual verification or web flow testing is needed.
tools
mcp-memory-recall
Recall and reuse prior decisions, constraints, and artifacts using MCP memory (e.g., Neo4j). Use when the user references past work (“jak ostatnio”, “kontynuuj”), when resuming a project thread, or when a repeated topic suggests existing decisions.
tools
mcp-neo4j-memory-ops
Use Neo4j memory MCP for creating/updating linked memories (entities, relations), de-duplication (DRY), and retrieval queries for project continuity. Use when saving global learnings or querying graph relationships.
tools
mcp-playwright
Automate browser flows and capture evidence (screenshots, console/network errors). Use for UI verification, repro steps, and end-to-end smoke tests.
tools
mcp-postman
Use Postman MCP to inspect/maintain collections, environments, and API workflows; generate or validate requests and tests. Use when API verification or collections are the source of truth.
tools
mcp-shrimp-execution-loop
Combine Shrimp task tracking with execution loops (plan → execute → verify → update status). Use for multi-step deliveries where progress tracking matters.
tools
next-stack
Next.js App Router frontend stack workflow: Server Components-first, Prisma server-only (Node runtime), Tailwind + shadcn/ui, TanStack Query, React Hook Form + Zod, and conventions for work under frontend/. Use when implementing or refactoring UI, routes, data fetching, mutations, or forms in this stack.
development
python-backend-fastapi
FastAPI + Pydantic v2 backend workflow: implement/modify API endpoints with thin handlers + service layer, add pytest tests, manage idempotent Alembic migrations, and implement streaming ETL/parsers with invalid-row CSV logging. Use this skill when working on Python backend APIs, schema changes, or ingestion/parsing pipelines.
development
structured-delivery
Provide structured outputs (plan/report/checklist/table) optimized for readability and reuse. Use when user requests a plan, report, checklist, template, or when high-risk requires explicit verification steps.
testing
solid-enforcer
Enforce SOLID design principles during code generation, refactors, and code review (SRP/OCP/LSP/ISP/DIP). Use when changing architecture, introducing new abstractions, reducing coupling, eliminating type-switches, or reviewing PRs for maintainability.
development
repo-grounding
Ground answers in the repository by reading relevant files, configs, and code paths. Use when the user asks to modify/debug code, configuration, CI/CD, or wants repo-specific reasoning.
development
vanilla-web
Build or modify plain HTML/CSS/JavaScript (no framework) using modular ES modules (ESM), SRP, minimal global state, and shippable runnable files with lightweight verification. Use for static pages, small UI widgets, vanilla JS refactors, and quick prototypes without React/Vue/Angular.
development
troubleshooting-rca
Perform root-cause analysis for bugs/errors/regressions using logs, repro steps, and hypothesis testing. Use when the user reports “nie działa”, stack traces, failing tests, or regressions.
testing
mcp-grafana
Query dashboards/logs/alerts to support incident analysis and regressions. Use when troubleshooting involves observability, incidents, latency, error rates.
tools
maintain-project-rules
Audit and maintain project rules in .cursor/rules/. Use when auditing project rules, checking prefix convention, syncing doc/rules.md, or when the user asks about .cursor/rules or prefix convention.
testing
python-style
Enforce consistent Python typing (type hints + return types), concise Google-style docstrings, PEP 8/Black formatting, and unit tests when creating or editing Python code. Use when working on .py files, Python APIs, refactors, or bug fixes where maintainability and correctness matter.
development
plan-as-contract
Produce a reviewable, file-referenced implementation plan that acts as a contract before execution. Use for risky ops, architecture changes, migrations, multi-file edits.
databases
keepass
KeePassXC cursor.kdbx — natywny keyring per OS, keepass-db.path bez fallbacków, agent instaluje brakujące narzędzia.
data-ai