paulund
161 verified skills311 total stars
marketing-reply-drafter
Use when drafting replies to social media posts on X or LinkedIn that add genuine value to the conversation. Produces 2-3 reply options with different angles for direct copy-paste.
testing2
standards-php
Use when writing or fixing PHP code, implementing classes, traits, or interfaces, applying PSR standards, or working with PHP 8.3+ patterns like readonly properties, enums, named arguments, match expressions, and union types.
development2
standards-tdd
Use when building features or fixing bugs using test-driven development, when the user mentions "red-green-refactor", wants integration-style tests, or asks for test-first development.
development2
standards-typescript
TypeScript strict-mode best practices. Auto-load when editing *.ts or *.tsx files. Covers type safety patterns, Zod integration, Prisma types, and React typing conventions.
development2
standards-wordpress
Use when developing WordPress themes, plugins, customizing Gutenberg blocks, implementing WooCommerce features, or optimizing WordPress performance and security.
tools2
writing-humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
testing2
standards-webhook
Use when developing outgoing webhooks for applications and services.
development2
standards-wordpress
Use when developing WordPress themes, plugins, customizing Gutenberg blocks, implementing WooCommerce features, or optimizing WordPress performance and security.
tools2
standards-webhook
Use when developing outgoing webhooks for applications and services.
development2
writing-humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
testing2
marketing-copywriting
Use when writing marketing copy for landing pages, feature sections, headlines, CTAs, product descriptions, or any web page where the goal is to convert visitors into users or customers.
development2
marketing-email-sequence
Use when creating email sequences, drip campaigns, welcome flows, onboarding emails, trial nurture sequences, or re-engagement campaigns. Produces complete sequences with subject lines, preview text, timing, and email body copy.
data-ai2
ops-improve-codebase-architecture
Use when the user wants to improve software architecture, find refactoring opportunities, consolidate tightly-coupled modules, reduce shallow abstractions, or make a codebase more testable and AI-navigable. Language-agnostic. Produces GitHub issues labeled per the `ops-triage` scheme, ready for an AFK agent.
development2
ops-improve-codebase-architecture
Use when the user wants to improve software architecture, find refactoring opportunities, consolidate tightly-coupled modules, reduce shallow abstractions, or make a codebase more testable and AI-navigable. Language-agnostic. Produces GitHub issues labeled per the `ops-triage` scheme, ready for an AFK agent.
development2
plan-bug
Interview the user about a bug and file it as a `planned + afk` GitHub issue ready for autonomous implementation. Use when the user wants to log a bug, report a defect, or file a bug ticket. Trigger phrases - "/plan-bug", "log a bug", "file a bug".
business2
quality-gate
Use when the user wants to run the project's lint + types + build sequence as a gate before pushing, opening a PR, or merging. Invoked by chained dev skills between phases. Trigger phrases - "/quality-gate", "run the quality gate", "check it builds".
development2
dev-implement
Use when the user wants to implement a single AFK GitHub issue end-to-end with TDD. Stops after the implementation lands on the branch — does NOT open a PR or run the quality gate. Trigger phrases - "/dev-implement", "implement this issue", "ship issue N".
development2
ops-backlog-health
Use when the user wants a periodic health pass over the backlog — close stale blockers, surface drifted-priority items, flag long-running in-progress issues, and unblock issues whose blockers were closed. Designed to run on a schedule (e.g. weekly) alongside /ops-triage. Trigger phrases - "/ops-backlog-health", "backlog health pass", "scrub the backlog".
content-media2
pr-open
Use when the user wants to open a pull request for an already-pushed branch that implements a specific issue. Idempotent — returns the existing PR if one is already open for the branch. Trigger phrases - "/pr-open", "open the pr", "create pr for this branch".
testing2
plan-bug
Interview the user about a bug and file it as a `planned + afk` GitHub issue ready for autonomous implementation. Use when the user wants to log a bug, report a defect, or file a bug ticket. Trigger phrases - "/plan-bug", "log a bug", "file a bug".
business2
quality-gate
Use when the user wants to run the project's lint + types + build sequence as a gate before pushing, opening a PR, or merging. Invoked by chained dev skills between phases. Trigger phrases - "/quality-gate", "run the quality gate", "check it builds".
development2
pr-fix
Use when the user wants to action external review feedback or fix CI failures on an open pull request. Single-purpose — does not handle merge conflicts (use merge-main) or open PRs (use pr-open). Trigger phrases - "/pr-fix", "fix the pr", "address review comments", "fix ci".
testing2
pr-verify
Use when the user wants to verify a PR's feature works at runtime by booting the dev server, exercising the affected UI via Chrome DevTools MCP, and posting a screenshot summary back to the PR. Idempotent — skips if `verified` or `verify-failed` is already on the PR. Trigger phrases - "/pr-verify", "verify this PR", "runtime check the pr".
tools2
dev-implement
Use when the user wants to implement a single AFK GitHub issue end-to-end with TDD. Stops after the implementation lands on the branch — does NOT open a PR or run the quality gate. Trigger phrases - "/dev-implement", "implement this issue", "ship issue N".
development2
pr-security-review
Use when the user wants a security-focused review pass on a PR with findings actioned as commits on the same branch. Trigger phrases - "/pr-security-review", "security review and fix".
testing2
ops-backlog-health
Use when the user wants a periodic health pass over the backlog — close stale blockers, surface drifted-priority items, flag long-running in-progress issues, and unblock issues whose blockers were closed. Designed to run on a schedule (e.g. weekly) alongside /ops-triage. Trigger phrases - "/ops-backlog-health", "backlog health pass", "scrub the backlog".
content-media2
pr-review
Use when the user wants to read a PR's diff, run a code-review pass, and action the findings as commits on the same branch. Trigger phrases - "/pr-review", "review and action this PR".
development2
pr-open
Use when the user wants to open a pull request for an already-pushed branch that implements a specific issue. Idempotent — returns the existing PR if one is already open for the branch. Trigger phrases - "/pr-open", "open the pr", "create pr for this branch".
testing2
pr-security-review
Use when the user wants a security-focused review pass on a PR with findings actioned as commits on the same branch. Trigger phrases - "/pr-security-review", "security review and fix".
testing2
pr-fix
Use when the user wants to action external review feedback or fix CI failures on an open pull request. Single-purpose — does not handle merge conflicts (use merge-main) or open PRs (use pr-open). Trigger phrases - "/pr-fix", "fix the pr", "address review comments", "fix ci".
testing2
pr-verify
Use when the user wants to verify a PR's feature works at runtime by booting the dev server, exercising the affected UI via Chrome DevTools MCP, and posting a screenshot summary back to the PR. Idempotent — skips if `verified` or `verify-failed` is already on the PR. Trigger phrases - "/pr-verify", "verify this PR", "runtime check the pr".
tools2
ai-pr-learnt
Use at the end of a sprint or week to extract lessons from PR review comments. Scans pull request reviews and inline comments from the last 7 days across all your repos, picks out corrections, decisions, and validated patterns, and saves them to the right place so Claude gets smarter over time.
testing2
ai-learnt
Use when the user says "learnt", "remember that", "teach claude", "update the rules", "save that lesson", or at the end of a session where Claude was corrected or a pattern was validated. Extracts lessons from the current session and saves them to the right place so Claude gets smarter over time. Always invoke this skill — don't just write memories ad-hoc.
testing2
ai-grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
testing2
ai-ship
Pick the next ready AFK GitHub issue, implement it with TDD, run the full Next.js quality gate, call /simplify, create a PR, call /review + /security-review, and verify the app at runtime with Chrome DevTools MCP. Use when the user wants to process the backlog, implement the next issue, or run the dev loop. Trigger phrases - "/ship", "ship the next issue", "work through the backlog".
tools2
dev-api
Use when designing, building, documenting, or maintaining RESTful APIs in this project. Enforces the project's style guide, response envelopes, pagination, field naming, and release readiness.
development2
dev-inertia
Use when building Inertia.js pages and components, including page props, forms, shared data, navigation, partial reloads, and deferred props.
development2
ai-to-prd
Turn an idea or spec into a parent PRD plus vertical-sliced GitHub issues ready for the /ship loop, with marketing requirements captured alongside. Use when the user wants to plan a feature, break down work, or convert an idea into issues. Trigger phrases - "/plan", "plan this feature", "break this into issues".
data-ai2
marketing-reply-drafter
Use when drafting replies to social media posts on X or LinkedIn that add genuine value to the conversation. Produces 2-3 reply options with different angles for direct copy-paste.
testing2
dev-docker
Use when writing or modifying Docker Compose files, configuring services, healthchecks, and container dependencies.
development2
dev-pre-commit
Use when setting up pre-commit hooks, configuring Husky, adding lint-staged, or enabling commit-time formatting, type checking, or testing. Installs and wires up Husky v9, lint-staged with Prettier, and optionally typecheck and test scripts.
development2
dev-improve-codebase-architecture
Use when the user wants to improve software architecture, find refactoring opportunities, consolidate tightly-coupled modules, reduce shallow abstractions, or make a codebase more testable and AI-navigable. Language-agnostic. Produces GitHub issues labeled per the `github-triage` scheme, ready for an AFK agent.
development2
dev-php
Use when writing or fixing PHP code, implementing classes, traits, or interfaces, applying PSR standards, or working with PHP 8.3+ patterns like readonly properties, enums, named arguments, match expressions, and union types.
development2
dev-typescript
TypeScript strict-mode best practices. Auto-load when editing *.ts or *.tsx files. Covers type safety patterns, Zod integration, Prisma types, and React typing conventions.
development2
dev-webhook
Use when developing outgoing webhooks for applications and services.
development2
saas-prd
Use when generating PRDs for standard SaaS features, planning feature requirements, or documenting decisions for authentication, billing, teams, email flows, legal, notifications, API, and other table-stakes SaaS functionality. Use this before starting implementation to document the decisions that vary per project.
development2
git-commit-push-pr
Use when the user wants to commit staged or unstaged changes, push a branch, and open a pull request in one step.
tools2
git-github-release
Use when the user wants to publish a new GitHub release, cut a version tag, or ship a new version using semver.
tools2
ops-monitoring
Review monitoring data and logs for critical issues or anomalies. Use during on-call, post-deployment, or scheduled health checks. Trigger phrases - "/ops-monitoring", "check monitoring", "review logs".
testing2
marketing-content-strategy
Use when planning a content strategy, defining content pillars, building a content calendar, deciding what to write about, or aligning content output with business goals. Produces a structured, actionable content plan.
development2
marketing-linkedin-content
Use when writing LinkedIn posts from an idea, work experience, observation, or topic the user provides. Produces 2-3 variations with different hooks for direct copy-paste into LinkedIn.
business2
saas-go-to-market
Use when planning a go-to-market strategy for a SaaS product, defining positioning and messaging, choosing channels, planning a launch, or building a 90-day marketing plan. Produces a structured GTM document with positioning, channels, launch phases, and metrics.
development2
simplify
Identify and remove unnecessary complexity in the codebase. Use when code feels over-engineered, before refactoring, or as a cleanup step after implementation. Trigger phrases - "/simplify", "simplify this", "clean up".
development2
ai-pr-learnt
Use at the end of a sprint or week to extract lessons from PR review comments. Scans pull request reviews and inline comments from the last 7 days across all your repos, picks out corrections, decisions, and validated patterns, and saves them to the right place so Claude gets smarter over time.
testing2
ai-ship
Pick the next ready AFK GitHub issue, implement it with TDD, run the full Next.js quality gate, call /simplify, create a PR, call /review + /security-review, and verify the app at runtime with Chrome DevTools MCP. Use when the user wants to process the backlog, implement the next issue, or run the dev loop. Trigger phrases - "/ship", "ship the next issue", "work through the backlog".
tools2
git-merge-main
Merge origin/main into the current branch and resolve all conflicts. Use when the user wants to sync their branch with main, pull in upstream changes, or says "merge in main", "sync with main", "rebase from main", or "update from main". Always invoke this skill for merge/sync workflows — don't just run git merge manually.
data-ai2
ai-grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
testing2
dev-docker
Use when writing or modifying Docker Compose files, configuring services, healthchecks, and container dependencies.
development2
dev-nextjs
Next.js 15 App Router best practices. Auto-load when working in app/, src/app/, components/, server actions, or route handlers. Trigger on user request or when writing any Next.js-specific code.
development2
dev-typescript
TypeScript strict-mode best practices. Auto-load when editing *.ts or *.tsx files. Covers type safety patterns, Zod integration, Prisma types, and React typing conventions.
development2
dev-pre-commit
Use when setting up pre-commit hooks, configuring Husky, adding lint-staged, or enabling commit-time formatting, type checking, or testing. Installs and wires up Husky v9, lint-staged with Prettier, and optionally typecheck and test scripts.
development2
dev-webhook
Use when developing outgoing webhooks for applications and services.
development2
git-github-release
Use when the user wants to publish a new GitHub release, cut a version tag, or ship a new version using semver.
tools2
marketing-content-strategy
Use when planning a content strategy, defining content pillars, building a content calendar, deciding what to write about, or aligning content output with business goals. Produces a structured, actionable content plan.
development2
git-commit-push-pr
Use when the user wants to commit staged or unstaged changes, push a branch, and open a pull request in one step.
tools2
github-triage
Triage GitHub issues through a label-based state machine. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
data-ai2
marketing-email-sequence
Use when creating email sequences, drip campaigns, welcome flows, onboarding emails, trial nurture sequences, or re-engagement campaigns. Produces complete sequences with subject lines, preview text, timing, and email body copy.
data-ai2
marketing-x-content
Use when writing X/Twitter posts, threads, or long-form articles from an idea, news item, article URL, or topic the user provides. Produces 2-3 variations with different hooks and formats for direct copy-paste into X.
development2
marketing-linkedin-content
Use when writing LinkedIn posts from an idea, work experience, observation, or topic the user provides. Produces 2-3 variations with different hooks for direct copy-paste into LinkedIn.
business2
ops-monitoring
Review monitoring data and logs for critical issues or anomalies. Use during on-call, post-deployment, or scheduled health checks. Trigger phrases - "/ops-monitoring", "check monitoring", "review logs".
testing2
saas-pricing-strategy
Use when making SaaS pricing decisions, structuring pricing tiers, choosing a value metric, planning a price increase, or designing a pricing page. Produces a pricing recommendation with tier structure, value metric rationale, and pricing page guidance.
testing2
review
Run a comprehensive code review on the current PR or codebase. Use when a PR is ready for review, after implementation, or when the user asks for a review. Trigger phrases - "/review", "review this".
development2
qa
Validate a PR or feature against acceptance criteria and test for regressions. Use before merging to ensure requirements are met. Trigger phrases - "/qa", "run QA", "test this".
testing2
saas-go-to-market
Use when planning a go-to-market strategy for a SaaS product, defining positioning and messaging, choosing channels, planning a launch, or building a 90-day marketing plan. Produces a structured GTM document with positioning, channels, launch phases, and metrics.
development2
saas-prd
Use when generating PRDs for standard SaaS features, planning feature requirements, or documenting decisions for authentication, billing, teams, email flows, legal, notifications, API, and other table-stakes SaaS functionality. Use this before starting implementation to document the decisions that vary per project.
development2
dev-ship
Pick the next ready AFK GitHub issue, implement it with TDD, run the full Next.js quality gate, call /dev-simplify, create a PR, call /dev-review + /dev-security-review, and verify the app at runtime with Chrome DevTools MCP. Use when the user wants to process the backlog, implement the next issue, or run the dev loop. Trigger phrases - "/dev-ship", "ship the next issue", "work through the backlog".
tools2
dev-ship
Pick the next ready AFK GitHub issue, implement it with TDD, run the full Next.js quality gate, call /dev-simplify, create a PR, call /dev-review + /dev-security-review, and verify the app at runtime with Chrome DevTools MCP. Use when the user wants to process the backlog, implement the next issue, or run the dev loop. Trigger phrases - "/dev-ship", "ship the next issue", "work through the backlog".
tools2
simplify
Identify and remove unnecessary complexity in the codebase. Use when code feels over-engineered, before refactoring, or as a cleanup step after implementation. Trigger phrases - "/simplify", "simplify this", "clean up".
development2
design-interface
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
development2
qa
Validate a PR or feature against acceptance criteria and test for regressions. Use before merging to ensure requirements are met. Trigger phrases - "/qa", "run QA", "test this".
testing2
marketing-seo-audit
Use when auditing a website for SEO issues, diagnosing ranking problems, reviewing technical SEO health, or checking on-page optimisation. Produces a prioritised list of findings with specific actions.
development2
github-triage
Triage GitHub issues through a label-based state machine. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
data-ai2
marketing-content-repurposer
Use when repurposing a blog post, article, newsletter, video transcript, or long-form content into social media posts for X, LinkedIn, or both platforms. Takes existing content and creates platform-optimised social posts that stand alone without requiring the reader to have seen the source.
testing2
dev-nextjs
Next.js 15 App Router best practices. Auto-load when working in app/, src/app/, components/, server actions, or route handlers. Trigger on user request or when writing any Next.js-specific code.
development2
dev-tdd
Use when building features or fixing bugs using test-driven development, when the user mentions "red-green-refactor", wants integration-style tests, or asks for test-first development.
development2
git-merge-main
Merge origin/main into the current branch and resolve all conflicts. Use when the user wants to sync their branch with main, pull in upstream changes, or says "merge in main", "sync with main", "rebase from main", or "update from main". Always invoke this skill for merge/sync workflows — don't just run git merge manually.
data-ai2
dev-wordpress
Use when developing WordPress themes, plugins, customizing Gutenberg blocks, implementing WooCommerce features, or optimizing WordPress performance and security.
tools2
dev-laravel
Use when building or modifying Laravel applications, including routes, controllers, models, migrations, jobs, actions, and API resources.
development2
ai-learnt
Use when the user says "learnt", "remember that", "teach claude", "update the rules", "save that lesson", or at the end of a session where Claude was corrected or a pattern was validated. Extracts lessons from the current session and saves them to the right place so Claude gets smarter over time. Always invoke this skill — don't just write memories ad-hoc.
testing2
ai-to-prd
Turn an idea or spec into a parent PRD plus vertical-sliced GitHub issues ready for the /ship loop, with marketing requirements captured alongside. Use when the user wants to plan a feature, break down work, or convert an idea into issues. Trigger phrases - "/plan", "plan this feature", "break this into issues".
data-ai2
dev-api
Use when designing, building, documenting, or maintaining RESTful APIs in this project. Enforces the project's style guide, response envelopes, pagination, field naming, and release readiness.
development2
design-interface
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
development2
dev-improve-codebase-architecture
Use when the user wants to improve software architecture, find refactoring opportunities, consolidate tightly-coupled modules, reduce shallow abstractions, or make a codebase more testable and AI-navigable. Language-agnostic. Produces GitHub issues labeled per the `github-triage` scheme, ready for an AFK agent.
development2
dev-inertia
Use when building Inertia.js pages and components, including page props, forms, shared data, navigation, partial reloads, and deferred props.
development2
dev-laravel
Use when building or modifying Laravel applications, including routes, controllers, models, migrations, jobs, actions, and API resources.
development2
dev-php
Use when writing or fixing PHP code, implementing classes, traits, or interfaces, applying PSR standards, or working with PHP 8.3+ patterns like readonly properties, enums, named arguments, match expressions, and union types.
development2
marketing-seo-audit
Use when auditing a website for SEO issues, diagnosing ranking problems, reviewing technical SEO health, or checking on-page optimisation. Produces a prioritised list of findings with specific actions.
development2
dev-wordpress
Use when developing WordPress themes, plugins, customizing Gutenberg blocks, implementing WooCommerce features, or optimizing WordPress performance and security.
tools2
dev-tdd
Use when building features or fixing bugs using test-driven development, when the user mentions "red-green-refactor", wants integration-style tests, or asks for test-first development.
development2
marketing-content-repurposer
Use when repurposing a blog post, article, newsletter, video transcript, or long-form content into social media posts for X, LinkedIn, or both platforms. Takes existing content and creates platform-optimised social posts that stand alone without requiring the reader to have seen the source.
testing2
marketing-copywriting
Use when writing marketing copy for landing pages, feature sections, headlines, CTAs, product descriptions, or any web page where the goal is to convert visitors into users or customers.
development2
saas-launch-checklist
Use when auditing launch readiness for a SaaS product, doing a pre-launch review, or checking what is missing before going live. Produces a categorised checklist with status for each item and clear distinction between must-have blockers and post-launch additions.
development2
review
Run a comprehensive code review on the current PR or codebase. Use when a PR is ready for review, after implementation, or when the user asks for a review. Trigger phrases - "/review", "review this".
development2
saas-launch-checklist
Use when auditing launch readiness for a SaaS product, doing a pre-launch review, or checking what is missing before going live. Produces a categorised checklist with status for each item and clear distinction between must-have blockers and post-launch additions.
development2
marketing-x-content
Use when writing X/Twitter posts, threads, or long-form articles from an idea, news item, article URL, or topic the user provides. Produces 2-3 variations with different hooks and formats for direct copy-paste into X.
development2
security-review
Run a focused security audit on the current PR or codebase. Use when reviewing code that handles auth, payments, user input, or sensitive data. Trigger phrases - "/security-review", "security check".
development2
security-review
Run a focused security audit on the current PR or codebase. Use when reviewing code that handles auth, payments, user input, or sensitive data. Trigger phrases - "/security-review", "security check".
development2
saas-pricing-strategy
Use when making SaaS pricing decisions, structuring pricing tiers, choosing a value metric, planning a price increase, or designing a pricing page. Produces a pricing recommendation with tier structure, value metric rationale, and pricing page guidance.
testing2
pr-review
Use when the user wants to read a PR's diff, run a code-review pass, and action the findings as commits on the same branch. Trigger phrases - "/pr-review", "review and action this PR".
development2
dev-commit-push-pr
Use when the user wants to commit staged or unstaged changes, push a branch, and open a pull request in one step.
development2
dev-merge-main
Merge origin/main into the current branch and resolve all conflicts. Use when the user wants to sync their branch with main, pull in upstream changes, or says "merge in main", "sync with main", "rebase from main", or "update from main". Always invoke this skill for merge/sync workflows — don't just run git merge manually.
development2
ops-triage
Triage GitHub issues through a label-based state machine. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
data-ai2
standards-api
Use when designing, building, documenting, or maintaining RESTful APIs in this project. Enforces the project's style guide, response envelopes, pagination, field naming, and release readiness.
development2
ops-triage
Triage GitHub issues through a label-based state machine. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
data-ai2
standards-pre-commit
Use when setting up pre-commit hooks, configuring Husky, adding lint-staged, or enabling commit-time formatting, type checking, or testing. Installs and wires up Husky v9, lint-staged with Prettier, and optionally typecheck and test scripts.
development2
standards-laravel
Use when building or modifying Laravel applications, including routes, controllers, models, migrations, jobs, actions, and API resources.
development2
dev-simplify
Identify and remove unnecessary complexity in the codebase. Use when code feels over-engineered, before refactoring, or as a cleanup step after implementation. Trigger phrases - "/dev-simplify", "simplify this", "clean up".
development2
dev-pr
Use when the user wants to action PR review feedback, resolve merge conflicts on a PR branch, fix CI failures on an open pull request, or update an existing PR. Trigger phrases - "/pr", "fix the pr", "address review comments", "resolve ci failures", "update my pr".
development2
dev-review
Run a comprehensive code review on the current PR or codebase. Use when a PR is ready for review, after implementation, or when the user asks for a review. Trigger phrases - "/review", "review this".
development2
learn-pr-learnt
Use at the end of a sprint or week to extract lessons from PR review comments. Scans pull request reviews and inline comments from the last 7 days across all your repos, picks out corrections, decisions, and validated patterns, and saves them to the right place so the agent gets smarter over time.
testing2
learn-learnt
Use when the user says "learnt", "remember that", "teach agent", "update the rules", "save that lesson", or at the end of a session where the agent was corrected or a pattern was validated. Extracts lessons from the current session and saves them to the right place so the agent gets smarter over time. Always invoke this skill — don't just write memories ad-hoc.
testing2
plan-to-prd
Turn an idea or spec into a parent PRD plus vertical-sliced GitHub issues ready for the /ship loop, with marketing requirements captured alongside. Use when the user wants to plan a feature, break down work, or convert an idea into issues. Trigger phrases - "/plan", "plan this feature", "break this into issues".
business2
plan-grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
testing2
dev-security-review
Use when reviewing code that handles auth, payments, user input, or sensitive data. Trigger phrases - "/dev-security-review", "security check".
development2
standards-typescript
TypeScript strict-mode best practices. Auto-load when editing *.ts or *.tsx files. Covers type safety patterns, Zod integration, Prisma types, and React typing conventions.
development2
plan-design-interface
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
development2
standards-pre-commit
Use when setting up pre-commit hooks, configuring Husky, adding lint-staged, or enabling commit-time formatting, type checking, or testing. Installs and wires up Husky v9, lint-staged with Prettier, and optionally typecheck and test scripts.
development2
standards-php
Use when writing or fixing PHP code, implementing classes, traits, or interfaces, applying PSR standards, or working with PHP 8.3+ patterns like readonly properties, enums, named arguments, match expressions, and union types.
development2
standards-inertia
Use when building Inertia.js pages and components, including page props, forms, shared data, navigation, partial reloads, and deferred props.
development2
standards-docker
Use when writing or modifying Docker Compose files, configuring services, healthchecks, and container dependencies.
testing2
standards-tdd
Use when building features or fixing bugs using test-driven development, when the user mentions "red-green-refactor", wants integration-style tests, or asks for test-first development.
development2
standards-nextjs
Next.js 15 App Router best practices. Auto-load when working in app/, src/app/, components/, server actions, or route handlers. Trigger on user request or when writing any Next.js-specific code.
development2
release-github-release
Use when the user wants to publish a new GitHub release, cut a version tag, or ship a new version using semver.
tools2
dev-commit-push-pr
Use when the user wants to commit staged or unstaged changes, push a branch, and open a pull request in one step.
development2
dev-merge-main
Merge origin/main into the current branch and resolve all conflicts. Use when the user wants to sync their branch with main, pull in upstream changes, or says "merge in main", "sync with main", "rebase from main", or "update from main". Always invoke this skill for merge/sync workflows — don't just run git merge manually.
development2
dev-pr
Use when the user wants to action PR review feedback, resolve merge conflicts on a PR branch, fix CI failures on an open pull request, or update an existing PR. Trigger phrases - "/pr", "fix the pr", "address review comments", "resolve ci failures", "update my pr".
development2
dev-review
Run a comprehensive code review on the current PR or codebase. Use when a PR is ready for review, after implementation, or when the user asks for a review. Trigger phrases - "/review", "review this".
development2
dev-security-review
Use when reviewing code that handles auth, payments, user input, or sensitive data. Trigger phrases - "/dev-security-review", "security check".
development2
dev-simplify
Identify and remove unnecessary complexity in the codebase. Use when code feels over-engineered, before refactoring, or as a cleanup step after implementation. Trigger phrases - "/dev-simplify", "simplify this", "clean up".
development2
learn-learnt
Use when the user says "learnt", "remember that", "teach agent", "update the rules", "save that lesson", or at the end of a session where the agent was corrected or a pattern was validated. Extracts lessons from the current session and saves them to the right place so the agent gets smarter over time. Always invoke this skill — don't just write memories ad-hoc.
testing2
learn-pr-learnt
Use at the end of a sprint or week to extract lessons from PR review comments. Scans pull request reviews and inline comments from the last 7 days across all your repos, picks out corrections, decisions, and validated patterns, and saves them to the right place so the agent gets smarter over time.
testing2
plan-design-interface
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
development2
plan-grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
testing2
plan-to-prd
Turn an idea or spec into a parent PRD plus vertical-sliced GitHub issues ready for the /ship loop, with marketing requirements captured alongside. Use when the user wants to plan a feature, break down work, or convert an idea into issues. Trigger phrases - "/plan", "plan this feature", "break this into issues".
business2
release-github-release
Use when the user wants to publish a new GitHub release, cut a version tag, or ship a new version using semver.
tools2
standards-api
Use when designing, building, documenting, or maintaining RESTful APIs in this project. Enforces the project's style guide, response envelopes, pagination, field naming, and release readiness.
development2
standards-docker
Use when writing or modifying Docker Compose files, configuring services, healthchecks, and container dependencies.
testing2
standards-inertia
Use when building Inertia.js pages and components, including page props, forms, shared data, navigation, partial reloads, and deferred props.
development2
standards-laravel
Use when building or modifying Laravel applications, including routes, controllers, models, migrations, jobs, actions, and API resources.
development2
standards-nextjs
Next.js 15 App Router best practices. Auto-load when working in app/, src/app/, components/, server actions, or route handlers. Trigger on user request or when writing any Next.js-specific code.
development2
laravel
Use when building or modifying Laravel applications, including routes, controllers, models, migrations, jobs, actions, and API resources.
development1
code-review
Use when reviewing code, pull requests, or auditing code quality and best practices.
development1
learnt
Extract lessons from the current session and save them to the right place so Claude gets smarter over time. Use whenever the user says "learnt", "remember that", "teach claude", "update the rules", "save that lesson", or at the end of a session where Claude was corrected or a pattern was validated. Always invoke this skill — don't just write memories ad-hoc.
testing1
github-actions-claude
Create GitHub Actions workflows that run Claude Code skills or prompts on a schedule or trigger. Use this skill when the user wants to automate a Claude Code task in CI, migrate a scheduled Claude task to GitHub Actions, or create a new workflow that uses claude-code-action.
development1
docker
Use when writing or modifying Docker Compose files, configuring services, healthchecks, and container dependencies.
testing1
humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
testing1
inertia
Use when building Inertia.js pages and components, including page props, forms, shared data, navigation, partial reloads, and deferred props.
development1
laravel-sail
Use when working with Laravel Sail, including docker-compose configuration, service management, and running commands inside containers.
devops1
laravel-testing
Use when writing or modifying Pest tests for Laravel applications, including feature tests, unit tests, and factories.
testing1
api
Use when designing, building, documenting, or maintaining RESTful APIs — including endpoint design, OpenAPI specifications, security, and release readiness.
development1
merge-main
Merge origin/main into the current branch and resolve all conflicts. Use when the user wants to sync their branch with main, pull in upstream changes, or says "merge in main", "sync with main", "rebase from main", or "update from main". Always invoke this skill for merge/sync workflows — don't just run git merge manually.
data-ai1