NikiforovAll

Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.

Analyze a Claude Code session for "wrong-turn" moments (corrections, retries, waste, reversals, dead-ends) and produce an interactive HTML dashboard with copy-able recommendations (CLAUDE.md rules, docs, scripts, hooks, memory entries, sub-skills, etc.) that would help future agents reach the goal faster. Defaults to reflecting on the current in-context session; optionally accepts a session ID or JSONL path. Use when the user invokes /reflect or asks to learn from this session.

Summarize WHAT WAS SHIPPED in a Claude Code session as a self-contained HTML slide deck — the elevator pitch (problem, solution, decisions, artifacts, verification, gaps), not a play-by-play of tool calls or debugging detours. Defaults to the current in-context session; optionally accepts a session ID or JSONL path. Renders directly in the reflect aesthetic — no delegation. Use when the user invokes /reflect-solution or asks for a recap deck of what changed.

Visualize a Claude Code session as a quest/skill tree — a navigable SVG graph where nodes are turns and edges show flow, with distinct visual encoding for normal flow, dead-ends, corrections, retries, reversals, and backtracking. Sibling to /reflect (which produces an incidents+recommendations dashboard); this one shows the journey itself. Defaults to the current in-context session; optionally accepts a session ID or JSONL path. Use when the user invokes /reflect-tree or asks to map a session as a tree/graph/journey.

Analyze a task and produce an Architecture Decision Record with implementation steps.

Analyze a task, propose an agent team composition with roles and responsibilities, and create the team after user confirmation. Use when the user says "team stack", "create a team", "set up agents for this", or describes a complex task that would benefit from multiple agents working together.

This skill should be used when users want to discover, browse, or audit cc-handbook marketplace plugins. Shows all available plugins with installation status, versions, and component breakdown (skills, agents, commands, MCP/LSP servers, hooks). Trigger phrases include "discover plugins", "list handbook plugins", "what plugins are available", "browse marketplace".

This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository.

This skill should be used when investigating .NET project dependencies, understanding why packages are included, listing references, or auditing for outdated/vulnerable packages.

This skill should be used when running .NET tests selectively with a build-first, test-targeted workflow. Use it for running tests with xUnit focus.

Use when user explicitly requests planning with files, or asks for persistent tracking of a complex task.

Drive the claude-code-kanban browser dashboard from this Claude session. Use this skill when the user mentions "kanban" together with "session" — e.g. "open this session in kanban", "show kanban", "focus current session in kanban", "pin/unpin a session in kanban", "preview this file in kanban", or asks to peek/view a kanban session.

Run code quality checks on the claude-code-kanban project. Use this skill whenever the user wants to check code formatting, linting, or overall code quality for the public/app.js and public/style.css files. Trigger on phrases like "check quality", "lint", "format check", "style check", "quality gates", or any mention of code quality/standards.

This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and optionally publish to npm. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".

Helps with deployment tasks and scripts

A skill with nested file structure for testing

This skill should be used when the user wants to run code quality checks (linting, formatting, type checking, tests) on the lazyopencode project. Use this skill when asked to "run quality gates", "check the code", "run tests", "lint the code", or verify code quality before committing.

Implementation guide for Keycloak.AuthServices .NET library — authentication (JWT Bearer, OIDC, RFC 8414), authorization (RBAC, resource protection, Authorization Server, organizations, multi-tenancy), Admin REST API SDK, Protection API SDK, and developer experience tooling (.NET Aspire, templates, OpenTelemetry). Trigger phrases include Keycloak.AuthServices, ProtectedResource, Admin SDK, Protection API, organization, RFC 8414, token introspection.

Keycloak identity and access management (IAM) administration guidance — realm management, client configuration, authentication flows, authorization policies, security hardening, and troubleshooting. Use when configuring Keycloak, setting up SSO, managing realms/clients, troubleshooting authentication issues, or implementing RBAC. Trigger phrases include "Keycloak", "SSO", "OIDC", "SAML", "identity provider", "IAM", "realm", "access management".

Update GitHub star counts for suggested marketplaces in DEFAULT_SUGGESTED_MARKETPLACES. Use this skill when asked to "update stars", "refresh marketplace stars", or "sync star counts".

This skill should be used when the user wants to run code quality checks (linting, formatting, type checking, tests) on the lazyclaude project. Use this skill when asked to "run quality gates", "check the code", "run tests", "lint the code", or verify code quality before committing.

Review code for quality, security, and best practices. Use when asked to review code, find bugs, suggest improvements, or check for security issues.

Use when creating, updating, reviewing, or validating Demo Time act files and companion slides for this repository, especially .demo/*.yaml files, code highlight chunks, scene flow, and alignment with slides and src samples.

Scaffold a new post in the nikiforovall.blog Jekyll repo. Copies _posts/_template.md to the right year folder, creates the matching assets folder, and primes the user on the asset/media conventions. Use whenever the user wants to "start a new post", "draft a blog post", "new blog entry", "write up X for the blog", or mentions creating content under nikiforovall.github.io / nikiforovall.blog.

Access curated Fabric AI prompts for content processing, research, and writing.

This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and optionally publish to npm. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".

Query the DIAL AI model catalog, inspect a specific model's details/capabilities, or check rate-limit usage via the local `dial` CLI shipped with the pi-dial package. Trigger when the user asks about DIAL models, "what openweight/Anthropic/GPT model is available", token quotas / rate limits, or wants to look up a model id served via EPAM's DIAL proxy.

This skill should be used when the user wants to run code quality checks (linting, formatting, type checking, tests) on the company_intel project. Use this skill when asked to "run quality gates", "check the code", "run tests", "lint the code", or verify code quality before committing.