Showing 41971–42000 of 77200 skills
Plans capacity, performance, and resilience from measured or explicitly estimated demand. Use for scalability decisions, growth planning, service targets, bottleneck forecasts, queue or cache sizing, and Now/Next/Scale plans. Do not use to debug a known slow path or implement a feature.
Kartik-Doye/Ravengard-AI-Recruiter
Improves performance by defining a metric and workload, profiling first, controlling noise, changing one major variable, and comparing equivalent conditions. Use for latency, throughput, memory, CPU, rendering, query, bundle, or startup problems.
Kartik-Doye/Ravengard-AI-Recruiter
Builds an implementation sequence from repository evidence using dependencies, invariants, vertical slices, rollback points, parallel work, irreversible decisions, and conscious deferrals. Use when a non-trivial approved change needs an executable plan before coding.
Kartik-Doye/Ravengard-AI-Recruiter
Edit prose into a clear, specific, source-grounded version that preserves the author's meaning and voice. Use for humanizing stiff writing, removing generic phrasing, matching a supplied voice sample, diagnosing robotic prose, or drafting from the user's notes. Do not optimize for AI-detector scores or claim to prove authorship.
Kartik-Doye/Ravengard-AI-Recruiter
Implements an approved plan one coherent slice at a time with fresh inspection, risk-appropriate verification, diff review, and clean handoff state. Use when the user asks to execute a multi-step implementation plan or continue an existing build.
Kartik-Doye/Ravengard-AI-Recruiter
Reviews a change against intent, design, correctness, complexity, security, tests, maintainability, and repository conventions. Use for code, diffs, pull requests, or implementation reviews that should produce only evidence-backed actionable findings.
Kartik-Doye/Ravengard-AI-Recruiter
Deploys software through the target platform's real release model, sequencing configuration, secrets, data, and code safely, then verifying the immutable release and public behavior. Use when the user asks to deploy, release, publish, roll back, or prove a version is live.
Kartik-Doye/Ravengard-AI-Recruiter
Researches version-sensitive technical questions using repository truth, installed sources, official documentation, standards, and upstream evidence. Use when an API, library, platform, security rule, or current implementation detail must be verified rather than recalled.
Kartik-Doye/Ravengard-AI-Recruiter
Finds root causes through reproduction, minimization, telemetry, competing hypotheses, discriminating experiments, causal chains, and counterfactual validation. Use when a bug, intermittent failure, or unexplained system behavior needs diagnosis.
Kartik-Doye/Ravengard-AI-Recruiter
Sets up new projects or improves existing projects with development best practices, tooling, documentation, and workflow automation. Use when user wants to start a new project, improve project structure, add development tooling, or establish professional workflows.
mhattingpete/claude-skills-marketplace
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
supreme12343/Stai-Project
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
supreme12343/Stai-Project
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
supreme12343/Stai-Project
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
supreme12343/Stai-Project
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
supreme12343/Stai-Project
Use when executing implementation plans with independent tasks in the current session
supreme12343/Stai-Project
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
supreme12343/Stai-Project
Use when implementing any feature or bugfix, before writing implementation code
supreme12343/Stai-Project
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
supreme12343/Stai-Project
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
supreme12343/Stai-Project
Use when you have a spec or requirements for a multi-step task, before touching code
supreme12343/Stai-Project
Use when creating new skills, editing existing skills, or verifying skills work before deployment
supreme12343/Stai-Project
Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when reviewing a change for keyboard, contrast, or screen-reader support. standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS/Android).
supreme12343/Stai-Project
Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature. Use when an agent or LLM feature misbehaves and the failing layer is unknown, or before shipping an agent stack.
supreme12343/Stai-Project
Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics. Use when choosing between coding agents, or when a change to an agent setup needs measured pass rate, cost, and time rather than an impression.
supreme12343/Stai-Project
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.
supreme12343/Stai-Project
Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol. Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet.
supreme12343/Stai-Project
Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.
supreme12343/Stai-Project
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
supreme12343/Stai-Project
Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.
supreme12343/Stai-Project