By thekostakis
Defect reporting and submission workflow with dispatch contract support. Reporter skill conducts structured interviews, auto-generates reproduction steps via headless Playwright (visual bugs; plugin bridge script, CI-safe) or code tracing (API bugs), cross-references requirements, and classifies as true defect, story update, or feature request. Supports dispatch from orchestrators with page URL (visual) or API endpoint identity (non-visual). Organizer skill submits to GitHub, Jira, Linear, or GitLab with system-native formatting and requirement traceability.
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
This skill should be used when the user has defect report files in the defects/ directory and wants to submit them to an issue tracker (bugs, story-updates, and feature requests are all submitted from those files). Trigger phrases: "submit defects", "push defects", "submit issues", "push issues", "sync defects to GitHub", "sync to Jira", "create defect issues", "create tickets from defects", "file the bugs", "file the issues", "submit bug reports", "submit pending reports", "push bugs to GitHub", "push bugs to Jira", "push story updates", "push change requests", "organize defects", "upload defects", "import defects into Linear", "create GitLab issues from defects". Also trigger when the user has defect files in defects/ and wants them on GitHub, Jira, Linear, or GitLab. Do NOT trigger for defect reporting or investigation — that is the defect-reporter skill.
This skill should be used when the user wants to report or file something against the *existing* product or spec: a bug, an issue, a problem, a regression, a change to requirements or stories, or a concrete feature/enhancement request for the tracker. The skill classifies as defect, story-update, or feature and produces defect report files. Defect- and issue-like triggers: "report a bug", "report a defect", "report an issue", "file a bug", "file an issue", "file a defect", "log a bug", "log an issue", "defect report", "bug report", "I found a bug", "I have an issue", "there's an issue with", "something's wrong", "something is broken", "this isn't working", "doesn't work", "not working", "it's broken", "we have a problem", "problem with", "ran into a problem", "unexpected behavior", "incorrect behavior", "wrong result", "regression", "used to work", "failing", "failure", "error when", "throws an error", "crash", "glitch", "the layout is broken", "broken on mobile", "this endpoint returns 500", "the button doesn't do anything", "wrong error message". Change-, story-, and spec-update triggers: "change request", "scope change", "requirement changed", "update the story", "story needs updating", "story is wrong", "story is outdated", "spec is wrong", "doesn't match the spec", "not what we specified", "acceptance criteria are wrong", "AC is wrong", "ticket needs updating", "amend the story", "revise the ticket", "requirement is outdated", "misspecified", "we need to change the requirement". Feature- and enhancement-like triggers (concrete add-on to existing product, not greenfield scoping): "feature request", "request a feature", "enhancement request", "small feature", "we should add", "missing capability", "not implemented but should be", "not a bug but we need". Do NOT trigger for greenfield requirements discovery ("gather requirements", "what should we build", full MVP scoping, requirements interview) or for design-only reviews — use requirements-gatherer or design-reviewer. DO trigger when the user is filing a concrete gap, change, or request against existing behavior or documented stories. Visual / UI defects: **headless Playwright** via `scripts/playwright-skill-bridge.mjs` (same pattern as functional-tester) — CI-safe, no Chrome DevTools MCP.
A Claude Code plugin marketplace for product design, project planning, and testing workflows.
A senior product consultant that interviews you to understand what you want to build, then produces a structured requirements.md file. It defines WHAT and WHY, never HOW — no architecture, no tech recommendations, no implementation details.
Supports two modes:
New mode — when no requirements.md exists, runs a full requirements interview from scratch.
Addendum mode — when requirements.md already exists, reads it first, then interviews you about what's new or changing. Produces a separate requirements-addendum-[date].md file. The original is never modified.
Trigger phrases:
What it does:
Reads a reviewed requirements.md or requirements-addendum-*.md and creates structured epics and issues in GitHub or Jira. You trigger this after reviewing and editing the requirements document.
Supports two modes:
Full mode — reads requirements.md, groups features into dependency-ordered epics, creates milestones, labels, and issues from scratch.
Addendum mode — reads a requirements-addendum-*.md file, fetches existing milestones and issues, then creates only what's new or changed:
needs-decision issuesTrigger phrases: "create issues from requirements", "organize into epics", "push to GitHub", "push to Jira", "create tickets"
What it does:
backlog.md file if no GitHub/Jira integration is availableneeds-decision-labeled issuesEstablishes a project's visual design system through plain-language interview or by extracting patterns from example websites. Produces design-guidelines.md (core tokens, permanently in CLAUDE.md context) and a component compendium (design/components/) with detailed per-component specs.
Trigger phrases: "design system", "visual design", "extract design from [site]", "I want it to look like [site]", "design guidelines"
What it does:
visual-design:component-context agent)Off-thread lookup with three behaviors: (1) exact or high-confidence (~90%) fuzzy → the entire matched component spec file (full markdown) + motion guidance, no long briefing; (2) ambiguous fuzzy → auto top 3 full specs + pattern synthesis + motion; (3) no match → inferred guidance + motion from guidelines. Further candidates stay one-line only — never the whole compendium.
Trigger phrases: see the skill description in the plugin (e.g. "load component spec", "which component should I use", "no spec for", "map this UI to components"). Prefer dispatching the agent when implementing so the main session stays lean.
Senior creative director quality gate. Verifies implemented UI against the design system through chrome-devtools-mcp (live browser inspection): visual appearance, CSS/token compliance, accessibility (axe), motion, responsive behavior, and Nielsen’s 10 usability heuristics with a 0–100 UX score. Supports diff mode (compare to a prior design-review-*.md report) and can consume design/review-checklist.md from the consultant.
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 claimnpx claudepluginhub thekostakis/requirements-gatherer --plugin defect-gathererRequirements gathering interview and issue creation workflow. Includes skills: a senior product consultant that interviews users to produce structured requirements; source-sync mode to reverse-engineer or reconcile requirements.md from repo, docs, URLs, and attachments (with drift analysis and explicit approval before overwriting); and an organizer that converts reviewed requirements into GitHub milestones/issues or Jira epics/stories.
Playwright functional test generator with full-stack performance analysis. Headless Playwright only (playwright-skill-bridge.mjs + test suite) — CI-safe, AFK-safe, no Chrome DevTools MCP. Playwright AI agents (Planner, Generator, Healer) for resilient test authoring, accessibility-tree selectors, @axe-core/playwright for WCAG audits, visual regression via toHaveScreenshot, Lighthouse CLI / Lighthouse CI for performance and audit scores. TDD-style fix loop, then Lighthouse + axe + performance deep-dive (report-only with escalation tags). Opus agent with haiku TDD sub-agent; .agent-progress/ logs (optional progress_log_path).
Visual design system toolkit with UX/usability expert review. Consultant skill for establishing design systems via interview or site extraction with page discovery, parallel fingerprinting, fluid responsive detection, and custom component motion discovery; codebase reverse-engineering mode derives tokens and component specs from the repo with chrome-devtools-mcp route inspection (spec at docs/design-system/codebase-reverse-spec-*.md, section-by-section approval, per-file delete confirmation). Component-context skill plus opus component-context agent: minimal return (one full spec + motion) for exact or high-confidence fuzzy; auto top-3 full specs + pattern synthesis + motion when ambiguous; gap inference when no match — never the whole compendium. Design-reviewer skill and agent: headless Playwright quality gate (playwright-skill-bridge.mjs) — CI-safe, no DevTools MCP — Nielsen heuristics UX scoring (0-100), diff mode, review-checklist synergy, functional/behavior-change escalation, Categories A–F in phase files. Opus + haiku mechanical dispatch; .agent-progress/ logs. Update-component-index skill for the component compendium index.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Browser automation and end-to-end testing MCP server by Microsoft. Enables Claude to interact with web pages, take screenshots, fill forms, click elements, and perform automated browser testing workflows.