Dominik Bláha
Community@DNepovim · Prague
Software Engineer
Agent Skills by Dominik Bláha
Showing 15 vetted skills indexed across 1 GitHub repositories.
frontend-design
Generate production-grade frontend interfaces with distinctive typography, color, motion, and layout.
using-git-worktrees
Creates isolated git worktrees with directory selection, ignore verification, and baseline test validation.
test-driven-development
Enforces red-green-refactor test-driven development workflow before writing implementation code.
systematic-debugging
Diagnose bugs through a four-phase root cause investigation process before proposing fixes.
using-superpowers
Enforces skill discovery and invocation before any AI response or action.
dispatching-parallel-agents
Dispatch concurrent agents to investigate independent failures across separate problem domains.
executing-plans
Executes written implementation plans task-by-task with verification checkpoints and review gates.
finishing-a-development-branch
Guides completion of development branches through structured merge, PR, keep, or discard options.
brainstorming
Guides collaborative design dialogue to turn ideas into approved specs before implementation.
writing-plans
Generates detailed implementation plans with bite-sized TDD tasks from feature specifications.
requesting-code-review
Dispatches a code-reviewer subagent to evaluate git diffs against requirements before merging.
receiving-code-review
Guides verification and implementation of code review feedback with technical rigor.
writing-skills
Create and test agent skills using test-driven development with subagent pressure scenarios.
verification-before-completion
Enforces running verification commands and checking output before claiming work is complete.
subagent-driven-development
Executes implementation plans by dispatching fresh subagents per task with two-stage review.
Frequently Asked Questions About Dominik Bláha
FAQPage SchemaWhat tasks can I accomplish with Dominik Bláha's skills?▼
You can run test-driven development cycles, systematically debug failures, create isolated git worktrees, write and execute implementation plans, request and respond to code reviews, verify work before completion, and generate polished frontend interfaces.
Who are these skills designed for?▼
Software engineers and developers who want disciplined engineering practices: TDD before implementation, evidence-based verification before claiming completion, structured code review handling, and parallel task dispatch for independent work items.
How do the skills fit into a development session?▼
Start with brainstorming and writing-plans before touching code, isolate work via git worktrees, implement with test-driven-development, debug systematically, then request code review and run verification-before-completion before merging or opening a PR.
Are these skills open source and what do they cost?▼
The frontend-design skill references complete terms in its bundled LICENSE.txt; other skills carry no explicit license in their frontmatter. No pricing or paid tier is indicated in the manifest, so review each skill's license file before redistribution.
What prerequisites or dependencies do these skills require?▼
Skills are invoked through a Skill tool, and using-superpowers mandates invoking it before any response. Git-based skills require a git repository; executing-plans requires a written implementation plan; verification skills require runnable test or verification commands.