By Abildtoft
Tooling for the workflows that Abildtoft encounters in his daily work
Use this agent to audit UI code for WCAG 2.1 AA accessibility issues, including semantics, ARIA, keyboard navigation, focus handling, screen reader support, and contrast. Use it when accessibility is an explicit requirement or when reviewing forms, dialogs, and other interactive flows; not for general UX or visual consistency review.
Use this agent to review code changes from an architectural perspective, focusing on system boundaries, dependency direction, layering, abstractions, service interfaces, and alignment with existing patterns. Best for structural refactors, new services, or cross-cutting features; not for style-only or narrowly local implementation feedback.
Use this agent to review code for authentication, authorization, CSRF, and session management vulnerabilities. Checks that protected operations have proper auth checks, access control is enforced, and sessions are securely managed.
Use this agent to review recent code against project guidelines, CLAUDE.md conventions, and established patterns. It is best used after writing or modifying code, especially before commits or PRs, and should be pointed at the relevant files or diff scope; not for deep product, accessibility, or performance-specific review.
Use this agent after writing or modifying code to simplify the recent changes for clarity, consistency, and maintainability while preserving behavior. It focuses on the modified files or diff scope and is best for cleanup after a working implementation; not for semantic rewrites or feature changes.
(experimental) Browser operator for live product inspection. Detects available browser MCP tooling (claude-in-chrome, chrome-devtools, playwright) and provides consistent navigation, screenshots, interaction, and evidence capture. Not for code-only analysis.
Create engaging changelogs for recent merges to main branch. Triggers on requests for daily/weekly changelogs, release notes, or summarizing recent changes.
Audit a codebase for agent-nativeness — score how well-optimized it is for AI coding agents across 5 dimensions and generate a prioritized refactoring plan.
Remove AI-generated code slop from a branch. Use when cleaning up AI-generated code, removing unnecessary comments, defensive checks, or type casts. Checks diff against main and fixes style inconsistencies.
Scan the codebase (or a specified scope) for unnecessary, redundant, or duplicative UI text. Identifies labels, descriptions, placeholders, tooltips, and instructions that could be removed because the UI already communicates the same information through its structure.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses Bash, Write, or Edit tools
Uses Bash, Write, or Edit tools
This repository contains Claude Code workflow plugins and support scripts.
| Plugin | Description |
|---|---|
kramme-cc-workflow | General workflow plugin. Includes SIW planning, PR lifecycle skills, verification helpers, review agents, hooks, and supporting scripts. |
kramme-connect-workflow | Connect-specific plugin for Consensus ApS's monorepo work (Angular modernization, Nx extraction, NgRx migration, and Rive docs). |
kramme-cc-workflow)59 skills in skills/ (SIW, PR workflows, Linear workflows, verification, documentation utilities, and session helpers)20 specialized agents in agents/ for review and analysishooks/hooks.json for command safety, non-interactive git enforcement, formatting, and context linksscripts/tests/Detailed documentation is available in kramme-cc-workflow/README.md.
SIW means Structured Implementation Workflow.
It is a local, file-based workflow for planning and implementing non-trivial work in a repository. Instead of relying on an external tracker, SIW keeps specification, issue breakdown, and progress state in versioned Markdown files.
SIW typically manages:
siw/LOG.md for decisions and progress notessiw/OPEN_ISSUES_OVERVIEW.md as the active issue indexsiw/issues/ for issue files with status and implementation contextCommon SIW command flow:
/kramme:siw:init # create or link spec + initialize siw/
/kramme:siw:generate-phases # break spec into phase-based issues
/kramme:siw:issue-implement # implement one issue
/kramme:siw:implementation-audit
/kramme:siw:issues-reindex
Related SIW commands include /kramme:siw:issue-define, /kramme:siw:spec-audit, /kramme:siw:reset, /kramme:siw:reverse-engineer-spec, and /kramme:siw:remove.
Marketplace:
claude /plugin marketplace add Abildtoft/kramme-cc-workflow
claude /plugin install kramme-cc-workflow@kramme-cc-workflow
Local install:
claude /plugin install /path/to/kramme-cc-workflow/kramme-cc-workflow
Install the Connect plugin from marketplace:
claude /plugin install kramme-cc-workflow@kramme-connect-workflow
Local install for the Connect plugin:
claude /plugin install /path/to/kramme-cc-workflow/kramme-connect-workflow
Update marketplace install:
claude /plugin marketplace update kramme-cc-workflow
After installation, common entry points are:
/kramme:siw:init
/kramme:pr:code-review
/kramme:pr:fix-ci
/kramme:verify:run
| Directory | Purpose |
|---|---|
kramme-cc-workflow/ | Main plugin: workflow automation, review agents, hooks, and verification |
kramme-connect-workflow/ | Connect product-specific skills |
MIT
npx claudepluginhub abildtoft/kramme-cc-workflow --plugin kramme-cc-workflowCorca Workflow Framework — consolidated hooks and skill orchestration for structured development sessions
Implementation planning, execution, and PR creation workflows with multi-agent collaboration
Software engineering workflows with skills for planning, implementation, quality review, and structured thinking, plus a suite of specialist agents
Harness-native ECC plugin for engineering teams - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows
Claude harness - A harness for solo developers (Vibecoders) to handle full-cycle contract development.