Ben Warzeski
Community@muselesscreator
Ben Warzeski's skill registry provides UI engineering lifecycle skills covering planning, implementation, testing, review, validation, and repo knowledge management for frontend codebases.
Agent Skills by Ben Warzeski
Showing 24 vetted skills indexed across 1 GitHub repositories.
muselesscreatorcleanup-unit-tests
Diagnoses failing unit tests and applies fixes to mocks, assertions, and snapshots.
muselesscreatorupdate-learnings
Re-analyzes changed repository files and updates stored flat-file learnings incrementally.
muselesscreatorask-ui
Answers questions about code, plans, or branch changes with file:line evidence.
muselesscreatorpr-review-ui
Reviews UI pull requests with parallel specialist agents covering accessibility, performance, and security.
muselesscreatorcleanup-ui
Runs lint fix, type-check, and dead code removal on changed files in a UI branch.
muselesscreatorclean-branch
Removes .cursor permission files and non-code noise from a git branch before rebasing.
muselesscreatorplan-ui
Generates structured UI implementation plans with file placements, patterns, and test impact analysis.
muselesscreatorload-savepoint
Loads the latest savepoint handoff file for the current repo and branch to resume prior work.
muselesscreatorcleanup-e2e-tests
Diagnoses and fixes failing Cypress E2E tests including intercepts, selectors, and wait patterns.
muselesscreatorwalkthrough
Generates a narrated, chapter-based visual timeline explaining a diff, branch, PR, or feature.
muselesscreatortest-context
Loads stored test pattern learnings and scans local test files to produce structured test context.
muselesscreatoranalyze-task
Gathers repo learnings, branch state, and tooling constraints into a task-context artifact.
muselesscreatorcommit-branch
Stages and commits working tree changes with a Conventional Commits message derived from the actual diff.
muselesscreatorwrite-unit-tests
Writes unit tests for components, hooks, and utilities following repo test conventions.
muselesscreatorimpl-ui
Implements UI features by orchestrating disposable worker agents from a written implementation brief.
muselesscreatorwrite-e2e-tests
Writes Cypress end-to-end tests for user flows following repository conventions.
muselesscreatoranalyze-patterns
Analyzes a codebase for reusable patterns and produces cited examples with file and line references.
muselesscreatorartifact
Persists request results to timestamped artifact files for reuse by follow-on agents.
muselesscreatorsavepoint
Summarizes the current conversation into a handoff file for a fresh session.
muselesscreatoranalyze-cycle
Analyzes completed work cycles and proposes evidence-backed edits to the skills that ran them.
muselesscreatorvalidate-ui
Validates a UI implementation against its stated requirements and reports gaps and unrequested changes.
muselesscreatorsynthesize-patterns
Synthesizes cross-repo engineering patterns from analyze-patterns learnings files into universal principles and trade-off analyses.
muselesscreatororch-ui
Orchestrates multi-step UI work cycles by running each step in an isolated subagent.
muselesscreatorlearn-repo
Analyzes a repository's code patterns and writes structured markdown learnings to a local directory.
Frequently Asked Questions About Ben Warzeski
FAQPage SchemaWhat tasks can I accomplish with muselesscreator's skills?▼
The skills cover the full UI development cycle: planning features, implementing components, writing and repairing unit and Cypress E2E tests, validating implementations against specs, reviewing UI pull requests, cleaning lint and type errors, committing with Conventional Commits, and analyzing codebase patterns.
Who are these skills designed for?▼
Frontend and UI engineers working in established repositories who need structured assistance with feature planning, test coverage, PR review, and code cleanup. They assume an existing project with defined test conventions, design systems, and tooling constraints rather than greenfield setups.
How do the UI lifecycle skills work together in practice?▼
The orch-ui skill coordinates a feature cycle: analyze-task gathers constraints, plan-ui produces an implementation plan, impl-ui builds via isolated subagents, validate-ui checks against requirements, cleanup-ui fixes lint and types, and commit-branch commits with a generated Conventional Commits message.
What prerequisites or dependencies do these skills require?▼
Skills expect an existing repository with established test patterns, lint and type-check configuration, and optionally a wiki or learnings directory. Several skills depend on repo learnings stored at ~/.claude/repo-learnings/{repo}/, created by learn-repo or update-learnings, and test-context supports the test-writing skills.
How do the skills preserve context across sessions?▼
The savepoint skill writes a handoff file capturing goal, state, decisions, key files, and next steps; load-savepoint restores it in a fresh session. The artifact skill persists outputs like logs and analyses to files so follow-on work reads results instead of recomputing them.