kenlck
- 36 skills
- 0 followers
- 3 hours ago last updated
- ▌ Grill With Docs · kenlck bundleGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
- ▌ Sdd · kenlck bundleDeliver one tracker work package labeled `ready-for-seo-agent` through acceptance → delivery → evidence.
- ▌ SEO · kenlck bundleCodebase-driven SEO + GEO (Generative Engine Optimization) audit. Gathers site facts into SEO.md, scores the site against a fixed rubric, and writes a dated report with a prioritized improvement plan.
- ▌ Tdd · kenlck bundleTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
- ▌ SEO Strategy · kenlck bundleResearch and maintain an evidence-backed SEO/GEO thesis, opportunity portfolio, and execution-ready roadmap.
- ▌ Drain Tickets · kenlck bundleDrain ready-for-agent GitHub tickets via do-work subagents — parallel or sequential, one PR or PR-per-ticket.
- ▌ To SEO Issues · kenlck bundleConvert an approved SEO/GEO strategy into independently executable tracker work packages.
- ▌ Weekly Report · kenlck bundleProduce a weekly engineering report for a branch — activity, per-country changes, per-developer signals, risks, and week-over-week trend.
- ▌ Bug Fix · kenlck bundleStructured bug fixing with reproduction, root cause analysis, fix design, regression risk analysis, and quality review. Only invoke this skill when the user explicitly asks to use it by name (e.g. "use bug-fix", "run bug-fix") or clearly requests a structured/systematic bug fixing process. Do not invoke for general bug reports, error messages, or broken behavior — handle those directly without this skill.
- ▌ Codemap · kenlck bundleBuild and maintain a persistent structural index of a Java, Go, Python, or Rust codebase under .codemap/ (graph.json + MAP.md), so other skills explore via the map instead of grep + read loops. Tree-sitter based; supports polyglot repos. Use when starting work in an unfamiliar non-TS/JS repo, when the user asks to build/refresh/update the codemap, after large refactors, or before any exploration phase that would otherwise scan source files. For TypeScript/JavaScript repos, use the sibling `ts-codemap` skill — it has higher fidelity (path aliases, re-export flattening, JSX).
- ▌ Simplify · kenlckSimplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
- ▌ Polish UI · kenlckPerforms a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
- ▌
- ▌ TS Codemap · kenlck bundleBuild and maintain a persistent structural index of a TypeScript/JavaScript codebase under .codemap/ (graph.json + MAP.md), so other skills explore via the map instead of grep + read loops. Uses ts-morph for high-fidelity TS/JS parsing (tsconfig path aliases, re-export flattening, JSX). Use when the user asks to build, refresh, or update the codemap on a TS/JS repo, when starting work in an unfamiliar TS/JS repo, or before any exploration phase that would otherwise scan source files. For Java/Go/Python/Rust repos, use the language-agnostic `codemap` skill instead.
- ▌ Code Review · kenlckReview changed code for bugs, simplicity, security, and convention adherence using parallel reviewer agents. Use when the user asks to review code, review a PR, check quality, or wants a second pair of eyes before merging.
- ▌ Feature Dev · kenlck bundleOptimized guided feature development with deep requirement drilling, codebase understanding, and design-quality frontend implementation. Use this skill whenever the user wants to build or implement a feature — whether they say "let's build X", "add feature Y", "implement Z", "I want to create", "can we add", or any variation. This is the go-to skill for any non-trivial software feature work. Prefer this over a plain coding response whenever the feature has more than one moving part.
- ▌ Prd To Plan · kenlckTurn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
- ▌ Write A Prd · kenlck bundleCreate a PRD with an embedded Design Direction section through user interview, codebase exploration, and design intent capture. Use when building or revamping any feature with frontend or UI work — landing pages, components, UI redesigns — where design intent needs to be locked in before implementation. Extends the standard PRD process with structured design thinking: audience, tone, aesthetic direction, and the one memorable differentiator.
- ▌ Feature Dev Auto · kenlck bundleAutonomous feature development with goal-loop verification. Front-loads all decisions through interactive stages, then drives implementation unattended against verifiable goals — re-architecting, diagnosing, and self-correcting until green or escalation thresholds hit. Use for substantial feature work with a verifiable end state ("until tests pass / type-check clean / acceptance criteria hold").
- ▌ Feature Dev Next · kenlck bundleRight-sized guided feature development with three presets (Quick / Standard / Deep) covering everything from one-line tweaks to risky new modules. Invoke for any non-trivial feature work.
- ▌ Grill Me Standards · kenlckInterview the user to extract coding standards and project context, grounded in what the codebase already does. Use when user wants to generate a CLAUDE.md, CODING_STANDARDS.md, or otherwise capture conventions from an existing codebase.
- ▌ Code Review Parallel · kenlckReview multiple pull/merge requests across GitHub, GitLab, and Azure DevOps in parallel. Thin orchestrator over the single-PR code-review skill — one agent per PR, consolidated summary, optional PR comments. Use when the user wants to review several PRs/MRs at once (release sweep, multi-repo audit, batch review).
- ▌ Prepare Implementation Plan · kenlck bundleTurn an ADO user story — or a rough idea — into a verifiable, code-grounded blueprint a TDD executor can build from. Use when the user wants work planned before coding.
- ▌ Do Work · kenlck bundleDo work on ready-for-agent GitHub issues — claim, TDD, draft PR with FE/BE artifacts. Use when the user says do-work, wants the next ready issue implemented, or a loop/automation should drain the ready-for-agent queue.
- ▌ Do SEO Work · kenlck bundleDeliver one ready-for-seo-agent GitHub work package through claim, SEO Delivery Discipline, evidence, and tracker lifecycle updates. Use when the user says do-seo-work, asks to execute the next ready SEO/GEO issue, names a ready SEO package to deliver, or wants a loop or automation to drain the ready-for-seo-agent queue one package at a time.
- ▌ Review Operability · kenlck bundleOperability review for logs, metrics, traces, correlation, health signals, configuration, diagnostics, alertability, deployment safety, rollback signals, and runbooks. Use for observability, production-readiness, or operations questions.
- ▌ Review Test Quality · kenlck bundleTest quality review for meaningful assertions, isolation, determinism, negative cases, and unit, integration, contract, and end-to-end balance. Use for test-strategy, flaky-test, or coverage-confidence questions.
- ▌ Audit Software Fleet · kenlck bundleAudit multiple local or Git-hosted software repositories as one system. Use for fleet health reviews, cross-repository architecture, normalized audit evidence, offline HTML reporting, or explicit policy gates. Reporting-only; use other workflows for remediation.
- ▌ Review Tech Lifecycle · kenlck bundleTechnology lifecycle review for runtime, framework, build-tool, plugin, dependency, and API support status, deprecation, compatibility, and migration pressure. Use for end-of-life, upgrade-readiness, or obsolete-technology questions.
- ▌ Review Codebase Design · kenlck bundleCodebase design review for internal module boundaries, dependency direction, coupling, cohesion, domain modelling, layering, complexity, duplication, and observed patterns. Use for maintainability, modularity, or within-repository architecture questions.
- ▌ Review System Integration · kenlck bundleSystem integration review for cross-repository contracts, versioning, shared data, service boundaries, dependency direction, synchronous and messaging chains, failure propagation, cycles, and coordinated-release risk. Use for system maps, integration, or fleet-architecture questions.
- ▌ Review Application Security · kenlck bundleApplication security review for attack paths and controls around identity, untrusted data, secrets, cryptography, injection, exposure, sensitive data, and exploitable dependencies. Use for secure-code, OWASP, or vulnerability-risk questions.
- ▌ Review Software Reliability · kenlck bundleSoftware reliability review for failure handling, timeouts, retries, idempotency, concurrency, resource safety, transactions, consistency, degradation, and recovery. Use for resilience or fault-tolerance questions.
- ▌ Review Delivery Supply Chain · kenlck bundleDelivery and supply-chain review for CI/CD, reproducible builds, pinning, provenance, SBOMs, artifact and container integrity, licences, and release controls. Use for pipeline, artifact, SLSA, or software-supply-chain questions.
- ▌ Review Engineering Governance · kenlck bundleEngineering governance review for ownership, standards, repository hygiene, documentation, dependency policy, exceptions, release discipline, change controls, maintainership, and policy consistency. Use for stewardship, governance, or engineering-control questions.
- ▌ Review Performance Efficiency · kenlck bundlePerformance and efficiency review for hot paths, I/O, database access, batching, caching, frontend loading, resource use, build cost, and scaling constraints. Use for latency, throughput, bundle-size, or efficiency questions.