Total Skills
14
Skills published by Bokazan with real stars/downloads and source-aware metadata.
Total Skills
14
Total Stars
0
Total Downloads
0
Comparison chart based on real stars and downloads signals from source data.
browser-testing-with-devtools
0
build-check
0
code-review-and-quality
0
code-simplification
0
debugging-and-error-recovery
0
deprecation-and-migration
0
documentation-and-adrs
0
git-workflow-and-versioning
0
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that renders in a browser — DOM inspection, console errors, network analysis, performance profiling, accessibility verification.
Run the complete build verification pipeline (lint, tests, security audit, architecture review, QA, changelog)
Multi-dimensional code review — correctness, readability, architecture, security, performance. Use before merging any change, after completing a feature, or when evaluating code produced by another agent.
Reduces code complexity while preserving exact behavior. Applies Chesterton's Fence principle — understand before removing. Use after implementing features, or on request via /code-simplify.
Systematic debugging with structured triage. Use when tests fail, the build breaks, runtime behavior is wrong, or a bug report arrives. Stop the line, preserve evidence, find the root cause.
Safely removes code that no longer justifies its maintenance cost and migrates users to replacements. Use when sunsetting APIs, removing features, or transitioning to new implementations.
Document decisions, not just code. Write Architecture Decision Records for significant technical choices. Use when making architectural decisions, choosing between approaches, or when the same thing needs explaining repeatedly.
Disciplined version control — trunk-based development, atomic commits, descriptive messages, pre-commit hygiene. Use on every code change.
Refines ideas iteratively through structured divergent and convergent thinking. Use when starting with a vague concept or when you need to stress-test a direction before committing to a spec. Trigger with "idea-refine" or "ideate".
Builds features as thin vertical slices — each increment is implemented, tested, verified, and committed before moving to the next. Use during the BUILD phase to execute planned tasks one at a time.
Decomposes work into small, verifiable tasks with acceptance criteria and dependency ordering. Use when you have a spec and need to break it into implementable units, or when a task feels too large or vague to start.
Ship with confidence — pre-launch checklist, feature flag strategy, staged rollout, monitoring setup, and rollback planning. Use before any production deployment.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
Red-Green-Refactor cycle for features, Prove-It pattern for bugs. Use during BUILD and VERIFY phases. Tests describe behavior, not implementation.