Trending Skills
The hottest skills gaining momentum in the community right now.
mcp-playwright
by janjaszczak
Automate browser flows and capture evidence (screenshots, console/network errors). Use for UI verification, repro steps, and end-to-end smoke tests.
tailwind
by iulspop
Tailwind CSS patterns for layouts, color schemes, responsive design, and className handling. Use when writing or reviewing component styles.
mcp-neo4j-memory-ops
by janjaszczak
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.
continuous-mode
by iulspop
Continuously steers the codebase toward the VISION.md. Reads the vision, assesses current state, picks the highest-impact next action, builds with TDD, commits, and repeats. Never stops. Use when you want autonomous, vision-driven development.
mcp-grafana
by janjaszczak
Query dashboards/logs/alerts to support incident analysis and regressions. Use when troubleshooting involves observability, incidents, latency, error rates.
plan
by iulspop
Breaks down feature requests into sequential, implementable tasks with code changes under 50 lines each. Use when planning new features, refactors, or multi-step changes to ensure logical ordering and no broken intermediate states.
design-taste
by vijaykpatel
Apply principles of good design taste when creating, reviewing, or critiquing any creative or technical work. Use this skill whenever the user asks you to design something, review a design, create UI/UX, architect a system, write something with aesthetic intent, evaluate the quality of code or creative work, or asks for feedback on whether something is "good." Also trigger when users mention taste, aesthetics, beauty in design, elegance, simplicity, or when they want help making something not just functional but genuinely well-crafted. This skill applies across domains: software, writing, visual design, architecture, presentations, APIs, data models, and more. Even if the user doesn't explicitly mention "design," use this skill when the underlying task is about making something better, more elegant, or more refined.
python-style
by janjaszczak
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.
write
by iulspop
Improves text for clarity, directness, and engagement following professional writing best practices. Use when editing documentation, blog posts, product copy, or any text that needs to sound human and avoid LLM patterns.
continuous-claudemd-updates
by vijaykpatel
Maintains CLAUDE.md in sync with codebase changes after commits. Use when (1) A commit has been made and CLAUDE.md needs updating, (2) User explicitly requests CLAUDE.md update or audit, (3) Major refactoring or architectural changes occur, (4) New conventions or patterns are established, (5) Files referenced in CLAUDE.md are deleted/moved. Keeps documentation concise by moving verbose content to docs/ folder with links, removes outdated information, and ensures CLAUDE.md reflects current codebase state.
happy-dom-tests
by iulspop
Generates React component render tests using happy-dom and Testing Library with the "given/should" prose format. Use when writing tests for display components, hooks, user interactions, or accessibility checks.
solid-enforcer
by janjaszczak
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.
mcp-memory-recall
by janjaszczak
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.
mcp-github-ops
by janjaszczak
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.
troubleshooting-rca
by janjaszczak
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.
refactor
by iulspop
Plans and executes safe refactoring with tests as a safety net. Use when restructuring code, extracting functions, renaming across files, or simplifying complex logic without changing behavior.
better-writer
by iulspop
Rewrites text to be clearer, simpler, and more engaging using Scott Adams' writing principles and persuasive techniques. Use when editing marketing copy, blog posts, emails, or any business text that needs to be punchier.
task-planning-shrimp
by janjaszczak
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.
mcp-apify
by janjaszczak
Use Apify Actors for scraping/data acquisition pipelines. Use when data collection from websites is required and needs repeatable runs.
name
by iulspop
Suggests clear, descriptive names for functions and variables following consistent naming conventions. Use when naming new code constructs, renaming for clarity, or reviewing naming in code reviews.
commit
by iulspop
Commits staged changes using the conventional commits format with proper type, scope, and description. Use when committing code changes to maintain a clean, standardized git history.
python-backend-fastapi
by janjaszczak
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.
structured-delivery
by janjaszczak
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.
e2e-tests
by iulspop
Generates end-to-end tests using Playwright with the "given/should" prose format. Use when writing e2e tests for user flows, page interactions, or integration scenarios that exercise the full application stack.