Author Profile: Bokazan

Skills published by Bokazan with real stars/downloads and source-aware metadata.

Total Skills

14

Total Stars

0

Total Downloads

0

RSS Feed

Skills Performance

Comparison chart based on real stars and downloads signals from source data.

browser-testing-with-devtools

0

Stars
0
Downloads
0

build-check

0

Stars
0
Downloads
0

code-review-and-quality

0

Stars
0
Downloads
0

code-simplification

0

Stars
0
Downloads
0

debugging-and-error-recovery

0

Stars
0
Downloads
0

deprecation-and-migration

0

Stars
0
Downloads
0

documentation-and-adrs

0

Stars
0
Downloads
0

git-workflow-and-versioning

0

Stars
0
Downloads
0

Published Skills

Coding

browser-testing-with-devtools

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.

Repository SourceNeeds Review
Security

build-check

Run the complete build verification pipeline (lint, tests, security audit, architecture review, QA, changelog)

Repository SourceNeeds Review
Security

code-review-and-quality

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.

Repository SourceNeeds Review
Coding

code-simplification

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.

Repository SourceNeeds Review
General

debugging-and-error-recovery

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.

Repository SourceNeeds Review
Coding

deprecation-and-migration

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.

Repository SourceNeeds Review
Coding

documentation-and-adrs

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.

Repository SourceNeeds Review
Coding

git-workflow-and-versioning

Disciplined version control — trunk-based development, atomic commits, descriptive messages, pre-commit hygiene. Use on every code change.

Repository SourceNeeds Review
General

idea-refine

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".

Repository SourceNeeds Review
General

incremental-implementation

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.

Repository SourceNeeds Review
General

planning-and-task-breakdown

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.

Repository SourceNeeds Review
General

shipping-and-launch

Ship with confidence — pre-launch checklist, feature flag strategy, staged rollout, monitoring setup, and rollback planning. Use before any production deployment.

Repository SourceNeeds Review
Coding

spec-driven-development

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.

Repository SourceNeeds Review
Coding

test-driven-development

Red-Green-Refactor cycle for features, Prove-It pattern for bugs. Use during BUILD and VERIFY phases. Tests describe behavior, not implementation.

Repository SourceNeeds Review
Author Bokazan | V50.AI