Sponsored by

Find leads on Reddit on auto pilot

Topic: cli

1,462 skills in this topic.

system-design Use when designing system architecture, APIs, components, or data models - provides a structured design workflow with validation and documentation outputs.
NickCrew/Claude-Cortex 13
task-orchestration Use when coordinating complex tasks with orchestration, delegation, or parallel workstreams - provides structured workflows for orchestrate:brainstorm, orchestrate:spawn, and orchestrate:task.
NickCrew/Claude-Cortex 13
test-generation Use when generating tests for new or existing code to improve coverage - provides a structured workflow for analyzing code, creating tests, and validating coverage goals.
NickCrew/Claude-Cortex 13
testing-anti-patterns Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
NickCrew/Claude-Cortex 13
testing-skills-with-subagents Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes
NickCrew/Claude-Cortex 13
tool-selection Use when selecting between MCP tools based on task complexity and requirements - provides a structured selection workflow and decision rationale.
NickCrew/Claude-Cortex 13
tutorial-design Design and write hands-on tutorials with progressive disclosure, exercises, and troubleshooting sections. Use when creating learning content, workshops, or step-by-step guides.
NickCrew/Claude-Cortex 13
using-git-worktrees Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
NickCrew/Claude-Cortex 13
vibe-security This skill helps Claude write secure web applications. Use when working on any web application to ensure security best practices are followed.
NickCrew/Claude-Cortex 13
webapp-testing Toolkit for interacting with and testing local web applications using Playwright. Use when verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
NickCrew/Claude-Cortex 13
agent-loops Complete operational workflow for implementer agents (Codex, Gemini, etc.) making code changes and writing tests. Drives all work through atomic commits — each loop operates on the smallest complete, reviewable change. Defines the Code Change Loop, Test Writing Loop, Lint Gate, and Issue Filing process with circuit breakers, severity levels, and escalation rules. Requires `cortex git commit` for all commits. Includes bundled provider-aware review scripts that keep same-model shell-outs as the last resort, plus a fresh-context Codex fallback for code review and test audit. Use this skill when starting any implementation task.
NickCrew/Claude-Cortex 13
code-explanation Use when explaining code, concepts, or system behavior to a specific audience level - provides a structured explanation workflow with depth control and validation steps.
NickCrew/Claude-Cortex 13
mashup Force-fit patterns from other domains to spark novel concepts.
NickCrew/Claude-Cortex 13
pre-mortem Imagine failure first to surface guardrails and feature mitigations.
NickCrew/Claude-Cortex 13
cqrs-event-sourcing CQRS and Event Sourcing patterns for scalable, auditable systems with separated read/write models. Use when building audit-required systems, implementing temporal queries, or designing high-scale applications with complex domain logic.
NickCrew/Claude-Cortex 13
kubernetes-security-policies Kubernetes security policies, RBAC, and Pod Security Standards for hardened cluster deployments. Use when implementing cluster security, defining network policies, or enforcing security compliance in Kubernetes environments.
NickCrew/Claude-Cortex 13
legacy-modernization Modernize legacy systems using proven migration patterns like strangler fig, feature flags, and incremental refactoring. Use when planning system migrations, modernizing monoliths, or managing technical debt.
NickCrew/Claude-Cortex 13
product-strategy Product vision, roadmap development, and go-to-market execution with structured prioritization frameworks. Use when evaluating features, planning product direction, or assessing market fit.
NickCrew/Claude-Cortex 13
secure-coding-practices Secure coding practices and defensive programming patterns for building security-first applications. Use when implementing authentication, handling user input, managing sensitive data, or conducting secure code reviews.
NickCrew/Claude-Cortex 13
security-testing-patterns Security testing patterns including SAST, DAST, penetration testing, and vulnerability assessment techniques. Use when implementing security testing pipelines, conducting security audits, or validating application security controls.
NickCrew/Claude-Cortex 13
systematic-debugging Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
NickCrew/Claude-Cortex 13
test-review Review test quality and audit test coverage for any module. This skill should be used when reviewing existing tests, auditing test gaps, writing new tests, or when asked to assess test health. It pipelines testing standards into the audit workflow to produce a prioritized gap report. The output is a report, not code — do not write test implementations until the report is reviewed.
NickCrew/Claude-Cortex 13
ui-design-aesthetics Generates high-quality, non-generic UI designs with a focus on performance, progressive disclosure, and distinctive aesthetics.
NickCrew/Claude-Cortex 13
user-journey-mapping Create comprehensive user journey maps that identify pain points, opportunities, and emotional states across touchpoints. Use when mapping user experiences or analyzing conversion flows.
NickCrew/Claude-Cortex 13