ivklgn
- 22 skills
- 0 followers
- 9 hours ago last updated
- ▌ Create Landing · ivklgn bundleCreate or improve a complete landing page from a plain-language business description. Use when someone asks to make, fix, or improve a landing, sales, or conversion page. Researches the business, asks only essential questions, builds an Astro site, checks it in a real browser, and reports readiness in plain words. Not for a single UI component, an audit-only request, one image, or deployment-only work.
- ▌ Update Node Deps · ivklgn bundleAudit and update Node.js/JavaScript project dependencies using native package-manager commands (npm, pnpm, yarn, bun). Auto-applies patch updates silently, asks before minor, and confirms each major individually. Cross-checks changelogs via Context7 and security advisories before each batch. Use when the user asks to update dependencies, bump packages, check outdated packages, or audit security in a JS/TS project.
- ▌ New Skill · ivklgnCreate a new ai-kit skill end to end — ground in the repo's Archcore rules, collect the brief from the user, draft with skill-creator, apply ai-kit conventions, then hand off to review-and-release. Use when the user says "/new-skill", "давай новый скилл", "add a skill to ai-kit", or describes a capability they want packaged as a skill in this repository.
- ▌ Reset Permissions · ivklgn bundleReset accumulated permissions in .claude/settings.local.json. Use when the user says "/reset-permissions" or asks to clear, reset, or clean up Claude Code permissions. Supports full reset (default) or selective reset keeping read-only permissions (--keep-read).
- ▌ Test Health Check · ivklgn bundleProve that a unit, integration, or end-to-end test genuinely guards its stated behavior by running a few targeted fault probes (reachability, sensitivity, oracle validity, reliability) around the code under test — instead of trusting coverage. Use during active test development or test review — after writing or changing a test, when verifying a test actually catches real bugs, when a test "passes but might not test anything", when a suite feels untrustworthy, or to health-check the tests affected by the current branch. Supports an isolated git-worktree mode scoped to affected cases so production code is never touched.
- ▌ Update Golang Deps · ivklgn bundleAudit and update Go module dependencies using native go toolchain commands (go list, go get, go mod tidy) plus govulncheck for security. Auto-applies patch updates silently, asks before minor, and confirms each major individually. Cross-checks release notes via gh/Context7 and vulnerabilities before each batch. Handles v2+ module path changes (gopkg.in/, github.com/.../v2). Use when the user asks to update dependencies, bump modules, check outdated modules, or audit security in a Go project.
- ▌ Compatibility Audit · ivklgn bundleAudit whether a change is compatible with everything around it, across four boundaries — the contract it exposes to consumers, how cleanly it fits the conventions and abstractions of the place it lives, whether the change was carried through everywhere it had to be, and whether it survives its runtime environment. Scope is either the current git changes (working tree, staged, or branch vs merge base) or an explicit path — a module, package, class, function, file, schema, or config. Language-, domain- and artifact-agnostic — works the same for a new API endpoint, a Go package refactor, a single class, a frontend component, a database migration, or a devops/CI configuration. Emits a per-axis verdict (OK/RISK/FAIL) with evidence-backed findings and a compatible / conditionally compatible / incompatible ruling plus a migration path. Use when asked whether a change will break anyone, whether a piece of code still fits its surroundings, before merging a refactor, when extracting or upgrading a shared package, when
- ▌ Load Branch Changes · ivklgn bundleLoad current git branch changes (diff, commits, changed files) into session context. Use when the user invokes /load-branch-changes to review, understand, or focus on the current branch's changes compared to the base branch.
- ▌ Explain Branch Changes · ivklgn bundleExplain the current git branch's changes in plain product language for a non-technical audience — no file paths, no code references, no jargon. Reads the branch diff, commits, and available docs, then produces a short human briefing about what changed and why it matters. Use when the user invokes /explain-branch-changes, asks what a branch does in simple terms, needs a product summary of changes for a PM / designer / stakeholder / support, or says things like 'объясни ветку простыми словами', 'что поменялось для пользователей', 'explain this branch to a non-developer'. Works with any codebase, language, and project structure. NOT for code review or technical diff analysis — use load-branch-changes for that.
- ▌ Simplify Code Comments · ivklgnKeep code comments signal-only in any programming language — never write comments that restate the code, and delete existing noise comments instead of rewriting them. Use when writing or generating code (to avoid producing filler comments), when asked to clean up, simplify, or remove comments, or when reviewing code for comment noise. Preserves doc comments (JSDoc, docstrings, javadoc, rustdoc, godoc), "why" comments, ticket/ADR anchors, and deprecation notices.
- ▌ Review And Release · ivklgnSync README with current agents/skills, validate plugin conventions, sync the Codex plugin directory (plugins/ai-kit), bump version, and commit. Use when the user says "/review-and-release" or wants to prepare a release after adding, removing, or changing agents or skills.
- ▌ Jsdoc · ivklgnWrite, fix, or review JSDoc documentation for JavaScript and TypeScript code. Detects whether the project uses typed JSDoc (plain JS with checkJs), TypeScript (docs without type duplication), or a doc generator (TypeDoc, JSDoc CLI), and documents accordingly. Use when adding JSDoc comments, documenting a public API, fixing doc/signature drift, or setting up doc generation.
- ▌ Recap · ivklgnRe-orient inside a long session — produce a dense five-slot status (goal, done, current step, open items, next step) written in the language of the session, plus an optional drill-down into any single item. Reads only what is already in context plus one git call, and never explores the codebase. Use when the user asks where we are, what we were doing, what the status is, where we stopped, what is left, to catch up or be reminded, or invokes recap; and when returning to a session whose earlier part is no longer fresh.
- ▌ Ask Me · ivklgnTurn the current plan into a numbered list of what only the human can supply — decisions, facts only they know, credentials or access, data from systems the agent can't reach, and real-world or interactive actions — each with why the agent is blocked, which step it unblocks, the default if unanswered, and the exact reply shape. Works only from what is already in context; calls no tools and never explores the codebase. Use when the user asks what you need from me, what's blocked on me, give me my part, what are your questions, or says ask me what you need, or invokes ask-me; and proactively once the plan reaches a step that depends on a person.
- ▌ Can I Use · ivklgnCheck browser support for web platform features (CSS, JS APIs, HTML) against the project's actual browser targets. Resolves the project's browserslist config, queries caniuse/MDN compatibility data, reports Baseline status, and recommends fallbacks or progressive enhancement. Use when asking "can I use X", choosing between modern and legacy approaches, reviewing code for unsupported features, or auditing browser compatibility.
- ▌ Humanizer · ivklgn bundleRemove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.
- ▌ SEO Audit · ivklgn bundleManual, strategic SEO review and methodology — no tooling required. Use when the user wants to audit, diagnose, or improve SEO and ranking, or mentions "SEO audit," "technical SEO," "why am I not ranking," "on-page SEO," "meta tags review," "E-E-A-T," or "SEO health check." Covers crawlability, on-page, content quality, and keyword strategy, ending in a prioritized report. For an automated, crawler-driven scan with a health score, use the audit-website skill instead.
- ▌ Audit Website · ivklgn bundleAutomated technical website audit via the squirrelscan CLI: crawls a live or local site and checks 230+ rules across SEO, performance, security, technical, content, and 16 other categories, returning an LLM-optimized report with a health score, broken links, meta-tag analysis, and actionable fixes (with an optional confirm-first fix loop). Use for a fast, tool-driven scan of a website or webapp. For manual SEO strategy and content review without a crawler, use the seo-audit skill instead.
- ▌ Code Reviewer · ivklgn bundleAnalyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues.
- ▌ Review Golang · ivklgn bundleRun a comprehensive Go code review on git-changed files using the golang-pro agent with Context7 library docs
- ▌ 12 Factor Apps · ivklgn bundlePerform 12-Factor App compliance analysis on any codebase. Use when evaluating application architecture, auditing SaaS applications, or reviewing cloud-native applications against the original 12-Factor methodology.
- ▌ Nextjs Developer · ivklgn bundleUse when building Next.js applications with App Router, server components, or server actions. Invoke to configure route handlers, implement middleware, set up API routes, add streaming SSR, write generateMetadata for SEO, scaffold loading.tsx/error.tsx boundaries, or deploy. Triggers on: Next.js, App Router, RSC, use server, Server Components, Server Actions, React Server Components, generateMetadata, loading.tsx, Next.js deployment, Vercel, Next.js performance.