using-toolkit

v2026.09.24

Use when starting any conversation, receiving a new task, or when uncertain which skill applies - establishes how to find and use all 64 toolkit skills, requiring Skill tool invocation before ANY response including clarifying questions

GitHub
Install command
npx skhub add pixel-process-ug/using-toolkit
Markdown
SKILL.md
<EXTREMELY-IMPORTANT> If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.

IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.

This is not negotiable. This is not optional. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT>

Overview

Master catalog and dispatch system for all 64 toolkit skills. Ensures proper skill identification at conversation start.

How to Access Skills

In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded and presented to you — follow it directly. Never use the Read tool on skill files.


Phase 1: Skill Identification

Before ANY action: scan catalog, identify ALL matching skills (even 1% relevance), invoke via Skill tool.


Phase 2: Skill Prioritization

Invoke in order: (1) Process (brainstorming, planning) → (2) Specialist (frontend, backend, architect) → (3) Quality (TDD, review) → (4) Docs → (5) Design → (6) Ops → (7) Terminal (verification).


Phase 3: Skill Execution

Rigid skills: Follow exactly. Flexible skills: Adapt to context. Always invoke verification-before-completion before claiming done.


Available Skills (64 Total)

Core Skills (6)

SkillWhen to Use
using-toolkitSession start — establishes skill usage
self-learningStarting work on unfamiliar projects, or when corrected
resilient-executionWhen an approach fails — ensures retry with alternatives
circuit-breakerAutonomous loops, repeated operations, stagnation detection
auto-improvementSelf-improving system, tracks effectiveness, learns from errors
verification-before-completionBefore claiming ANY task is complete

Process & Workflow Skills (9)

SkillWhen to Use
planningBefore ANY implementation — forces structured planning
brainstormingBefore creative work — exploring ideas, features, designs
task-managementBreaking work into tracked steps during implementation
executing-plansExecuting approved plan documents step by step
subagent-driven-developmentMulti-task execution with two-stage review gates
dispatching-parallel-agentsRunning multiple independent tasks concurrently
autonomous-loopRalph-style iterative autonomous development loops
ralph-statusEnd of every autonomous loop iteration — structured progress reporting
task-decompositionHierarchical task breakdown, dependency mapping, parallelization

Quality Assurance Skills (17)

SkillWhen to Use
code-reviewAfter completing tasks, before committing
test-driven-developmentWriting any new code (RED-GREEN-REFACTOR)
systematic-debuggingInvestigating bugs, errors, unexpected behavior
testing-strategyChoosing testing approach for a project
security-reviewReviewing for vulnerabilities, auth, input validation
performance-optimizationOptimizing speed, reducing load times
acceptance-testingValidating implementation meets spec acceptance criteria
llm-as-judgeEvaluating subjective quality (tone, UX, readability, aesthetics)
senior-frontendReact/Next.js/TypeScript specialist with >85% test coverage
senior-backendAPI design, microservices, event-driven architecture
senior-architectSystem design, scalability, trade-off analysis, ADRs
senior-fullstackEnd-to-end development across the full stack
clean-codeSOLID, DRY, code smells, refactoring patterns
react-best-practicesReact hooks, context, suspense, server components
webapp-testingPlaywright-based web testing, screenshots, browser logs
senior-prompt-engineerPrompt design, optimization, chain-of-thought
senior-data-scientistML pipelines, statistical analysis, experiment design

Documentation Skills (5)

SkillWhen to Use
prd-generationGenerating Product Requirements Documents
tech-docs-generatorGenerating or updating technical documentation
writing-skillsCreating new skills, commands, or agent definitions
spec-writingWriting specifications with JTBD methodology and acceptance criteria
reverse-engineering-specsGenerating implementation-free specs from existing codebases

Design Skills (3)

SkillWhen to Use
api-designDesigning API endpoints and generating specs
frontend-ui-designComponent architecture, responsive design, accessibility
database-schema-designData modeling, migrations, indexing

Operations Skills (7)

SkillWhen to Use
deploymentSetting up CI/CD pipelines and deploy checklists
using-git-worktreesCreating isolated development environments
finishing-a-development-branchCompleting work on a branch, preparing to merge
git-commit-helperConventional commits, semantic versioning, changelogs
senior-devopsCI/CD, Docker, Kubernetes, infrastructure-as-code
mcp-builderMCP server development, tools, resources, transport layers
agent-developmentBuilding AI agents, tool use, memory, planning

Creative Skills (6)

SkillWhen to Use
ui-ux-pro-maxFull UI/UX design intelligence with styles, palettes, fonts, UX guidelines
ui-design-systemDesign tokens, component libraries, Tailwind CSS, responsive patterns
canvas-designHTML Canvas, SVG, data visualization, generative art
mobile-designReact Native, Flutter, SwiftUI, platform HIG compliance
ux-researcher-designerUser research, personas, journey maps, usability testing
artifacts-builderGenerate standalone artifacts, interactive demos, prototypes

Business Skills (3)

SkillWhen to Use
seo-optimizerTechnical SEO, meta tags, structured data, Core Web Vitals
content-research-writerResearch methodology, long-form content, citations
content-creatorMarketing copy, social media, brand voice

Document Processing Skills (3)

SkillWhen to Use
docx-processingWord document generation, template filling
pdf-processingPDF generation, form filling, OCR, merge/split
xlsx-processingExcel manipulation, formulas, charts

Frameworks & Languages Skills (3)

SkillWhen to Use
laravel-specialistLaravel development — Eloquent, Blade, Livewire, queues, Pest
php-specialistModern PHP 8.x — PSR standards, static analysis, Composer
laravel-boostLaravel Boost performance optimization — caching, queries, N+1

Productivity Skills (1)

SkillWhen to Use
file-organizerProject structure, file naming, directory architecture

Communication Skills (1)

SkillWhen to Use
email-composerProfessional email drafting, tone adjustment

Decision Table: Choosing the Right Skill

User Request ContainsPrimary SkillSupporting Skills
"build", "implement", "create feature"planningbrainstorming, tdd, code-review
"fix", "bug", "error", "broken"systematic-debuggingtdd, resilient-execution
"test", "coverage", "spec"test-driven-developmenttesting-strategy, acceptance-testing
"review", "check", "audit"code-reviewsecurity-review, clean-code
"plan", "how should we"planningbrainstorming, task-decomposition
"deploy", "CI/CD", "pipeline"deploymentsenior-devops
"API", "endpoint", "REST", "GraphQL"api-designsenior-backend
"React", "Next.js", "component"senior-frontendreact-best-practices, frontend-ui-design
"Laravel", "Eloquent", "Blade", "Livewire"laravel-specialistphp-specialist, laravel-boost
"PHP", "Composer", "PSR"php-specialistlaravel-specialist
"database", "schema", "migration"database-schema-designsenior-backend
"design", "UI", "UX"ui-ux-pro-maxui-design-system, frontend-ui-design
"mobile", "iOS", "Android"mobile-designui-ux-pro-max
"document", "docs", "README"tech-docs-generatorprd-generation
"spec", "requirements", "PRD"spec-writingprd-generation
"autonomous", "loop", "ralph"autonomous-loopralph-status, circuit-breaker
"performance", "optimize", "slow"performance-optimizationlaravel-boost
"security", "vulnerability", "auth"security-reviewsenior-backend
"SEO", "meta tags", "search engine"seo-optimizercontent-research-writer
"email", "draft", "compose"email-composercontent-creator
"PDF", "Word", "Excel"pdf-processing / docx-processing / xlsx-processing—
"agent", "AI", "tool use"agent-developmentmcp-builder
"MCP", "server", "transport"mcp-builderagent-development

Workflow Patterns

PatternSkill Chain
"Build feature X"brainstorming -> planning -> executing-plans -> code-review -> verification
"Fix bug Y"systematic-debugging -> TDD -> code-review -> verification
"Write new code"test-driven-development (always)
"Run autonomously"autonomous-loop -> ralph-status -> circuit-breaker
"Write specs"spec-writing (JTBD methodology)
"Understand legacy code"reverse-engineering-specs -> spec-writing (audit)
"Check acceptance criteria"acceptance-testing (backpressure chain)
"Validate subjective quality"llm-as-judge (rubric-based evaluation)
"Document the API"tech-docs-generator or api-design
"Create a PRD for Z"prd-generation
"Set up CI/CD"deployment
"How should we test?"testing-strategy
"Design the database"database-schema-design
"Build a UI component"frontend-ui-design
"Check for security issues"security-review
"Make it faster"performance-optimization
"Done with this branch"finishing-a-development-branch
"Design a UI"ui-ux-pro-max -> ui-design-system -> frontend-ui-design
"Build mobile app"mobile-design -> planning -> tdd
"Optimize SEO"seo-optimizer
"Write marketing copy"content-creator
"Process documents"docx-processing / pdf-processing / xlsx-processing
"Compose email"email-composer
"Build an AI agent"agent-development -> planning -> tdd
"Set up infrastructure"senior-devops -> deployment
"Decompose complex task"task-decomposition -> dispatching-parallel-agents
"Build Laravel feature"laravel-specialist -> planning -> tdd -> code-review
"Optimize Laravel app"laravel-boost -> performance-optimization -> verification
"Write PHP code"php-specialist -> tdd -> clean-code

Anti-Patterns

  • Never skip skill check for "simple" tasks — always check catalog
  • Never invoke skills from memory — use Skill tool for current version
  • Never read skill files with Read tool — use Skill tool
  • Never skip verification — always invoke verification-before-completion last
  • Never respond before checking skills — skill check is ALWAYS first

Anti-Rationalization Guards

If you think "This is just simple / I need context first / Let me explore first / This doesn't need a skill / I remember this skill / The skill is overkill / I'll do one thing first" — STOP. Check for skills FIRST. No exceptions.


Integration Points

Key integrations: self-learning (project context), verification-before-completion (terminal checkpoint), circuit-breaker (stall safety), auto-improvement (effectiveness tracking), planning (most common first skill), resilient-execution (failure recovery).


Core Rules

Plan before coding. TDD always. Verify completion with evidence. Review before merge. Use subagents for parallel work. Self-learn continuously. Try 3 approaches before escalating. Report RALPH_STATUS in loops. Protect config files. Write specs with acceptance criteria.


Skill Types

Rigid (TDD, debugging, planning, verification, code-review, autonomous-loop, circuit-breaker, spec-writing, acceptance-testing): Follow exactly. Flexible (brainstorming, tech-docs, api-design, frontend, database, performance, security-review, prd-generation, laravel-specialist, php-specialist): Adapt to context.


Find Missing Skills

npx skills find [query] to search, npx skills add <owner/repo@skill> -g -y to install. Prefer 1K+ weekly installs from reputable sources.


Skill Type

RIGID — Skill checking is mandatory. Every task begins with a catalog scan. No exceptions. No rationalization.

Discovery
Tags

No tags published for this skill.

Version
Latest version metadata

Version

v2026.09.24

Published

Sep 24, 2026

Category

Uncategorized

License

MIT

Source path

templates/skills/using-toolkit

Default branch

main

Latest commit

cc7fcb7

Tree SHA

7a49a40