Klaus L. Hougesen
Community@klh · copenhagen
Jack of many trades, design, developer, hacker, bizdev
Agent Skills by Klaus L. Hougesen
Showing 52 vetted skills indexed across 2 GitHub repositories.
klhklh-testing-patterns
Provides Jest testing patterns, factory functions, and TDD workflow guidance for unit tests.
klhklh-project-memory
Creates and maintains structured project memory files tracking bugs, decisions, facts, and work history.
klhklh-systematic-debugging
Diagnose bugs through a four-phase root cause analysis methodology.
klhall-skills
Guides agent output verbosity, efficiency, and formatting rules for any user request.
klhklh-find-bugs
Review local branch changes for bugs, security vulnerabilities, and code quality issues.
klhklh-agents-md
Creates and maintains concise AGENTS.md files that reference local agent skills.
klhklh-dispatch
Detects task type and routes work to the appropriate klh-* skill.
klhklh-lit-dev
Build Lit web components with TypeScript decorators, Zod validation, and Playwright testing.
klhklh-cli-speed-tools
Replace standard CLI tools like ls, grep, find, and cat with faster modern alternatives.
klhklh-settings-audit
Generates recommended Claude Code settings.json permissions by detecting a repository's tech stack.
klhklh-zod-validation
Implements Zod schema validation patterns for TypeScript API inputs and data.
klhklh-core-components
Enforces design tokens and core component usage when building UI layouts.
klhklh-openapi-directory-first
Look up authoritative OpenAPI specs for public APIs before relying on training data.
klhklh-all-skills
Guides agent output verbosity, efficiency, and formatting rules for any user request.
klhklh-code-simplifier
Simplifies recently modified code for clarity and maintainability while preserving functionality.
klhskill-lookup
Search, retrieve, and install Agent Skills from the prompts.chat registry via MCP tools.
klhidea-refine
Frame raw ideas into structured concepts through a three-phase ideation process.
klhdebugging-and-error-recovery
Guide root-cause debugging for failing tests, broken builds, and runtime errors.
klhusing-agent-skills
Map development tasks to phase-specific engineering workflow skills.
klhtest-driven-development
Write failing tests before implementing behavioral changes across codebases.
klhplanning-and-task-breakdown
Break specifications into ordered tasks with acceptance criteria and dependencies.
klhsystematic-debugging
Diagnose bugs through a four-phase root cause analysis methodology.
klhcode-documenter
Generate and validate docstrings, JSDoc, and OpenAPI specs for Python, TypeScript, and Node.js projects.
klhincremental-implementation
Deliver incremental, testable multi-file code changes that keep the repository buildable.
Frequently Asked Questions About Klaus L. Hougesen
FAQPage SchemaWhat tasks can I accomplish with Klaus L. Hougesen's skills?▼
You can run test-driven development cycles, trace bugs to root causes, validate inputs with Zod schemas, scaffold Lit web components, review branch changes for vulnerabilities, simplify TypeScript/React code, generate Claude Code settings.json allowlists, and maintain AGENTS.md and project memory documentation.
Who should use the klh skill collection?▼
Frontend and full-stack engineers working in TypeScript, JavaScript, Node.js, and React codebases benefit most, especially teams practicing TDD, maintaining design systems with Lit components, or standardizing Claude Code and AGENTS.md configuration across repositories.
How do I install and run these skills?▼
Use the skill-lookup or find-skills entries to search the prompts.chat registry, retrieve install commands, and add skills via MCP. The klh-dispatch skill acts as a single entry point that detects task type and routes to the matching klh-* skill automatically.
What prerequisites do the klh skills require?▼
Skills target Node.js and TypeScript environments with Jest, Playwright, Zod, and Lit for component work. Configuration skills like settings-audit and project-memory require a Claude Code setup with CLAUDE.md or AGENTS.md files in the repository.
How does the systematic-debugging skill differ from find-bugs?▼
Systematic-debugging applies a four-phase root-cause methodology to failing tests and unexpected behavior, enforcing no fixes before cause identification. Find-bugs instead audits local git branch changes for bugs, security vulnerabilities, and code-quality issues before merge.