Sponsored by

Find leads on Reddit on auto pilot

Topic: tui

201 skills in this topic.

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
claude-consult Consult Claude specialist agents during implementation for codebase understanding, pattern checking, security review, debugging help, and more. Use this skill whenever you're unsure about conventions, stuck on a failure, or need expert input before writing code. Does not replace the formal review gates in agent-loops — this is for mid-implementation consultation.
NickCrew/Claude-Cortex 13
backlog-md Task tracking system for agents via Backlog.md CLI. Use when creating deferred issues during implementation, filing audit findings, working assigned tasks, or managing project work. Optimized for agent workflows: structured issue filing, priority/labeling system, and task completion tracking.
NickCrew/Claude-Cortex 13
assumption-buster Flip, remove, or exaggerate assumptions to unlock new solution angles.
NickCrew/Claude-Cortex 13
brainstorming Rapid ideation skill adapted from obra/superpowers to kick off cortex sessions. Use when defining scope, aligning on goals, or exploring solution space before coding.
NickCrew/Claude-Cortex 13
compliance-audit Regulatory compliance auditing across GDPR, HIPAA, PCI DSS, SOC 2, and ISO frameworks with automated evidence collection and gap analysis. Use when conducting compliance assessments, preparing for certifications, or implementing regulatory controls.
NickCrew/Claude-Cortex 13
doc-maintenance Systematic documentation audit and maintenance. This skill should be used when documentation may be stale, missing, or misorganized — after feature work, refactors, dependency upgrades, or as a periodic health check. It prescribes folder structure for docs/ and manual/, dispatches haiku subagents for codebase/doc scanning, and routes doc creation to specialized agents (reference-builder, technical-writer, learning-guide) with docs-architect as quality gate.
NickCrew/Claude-Cortex 13
doc-quality-review Assess documentation quality across readability, consistency, audience fit, and prose clarity. Produces a scored review with actionable findings. This skill should be used before releases, during doc reviews, or when documentation feels unclear or inconsistent.
NickCrew/Claude-Cortex 13
event-driven-architecture Event-driven architecture patterns with event sourcing, CQRS, and message-driven communication. Use when designing distributed systems, microservices communication, or systems requiring eventual consistency and scalability.
NickCrew/Claude-Cortex 13
feature-implementation Use when implementing a feature or multi-file code change - provides structured implementation flow with persona selection, validation, and testing guidance.
NickCrew/Claude-Cortex 13
incident-response Incident triage, cascade prevention, and postmortem methodology. Use when handling production incidents, designing resilience patterns, or conducting chaos engineering exercises.
NickCrew/Claude-Cortex 13
microservices-patterns Comprehensive microservices architecture patterns covering service decomposition, communication, data management, and resilience strategies. Use when designing distributed systems, breaking down monoliths, or implementing service-to-service communication.
NickCrew/Claude-Cortex 13
repo-cleanup Use when a repository needs cleanup of dead code, build artifacts, unused dependencies, outdated docs, or stale tests - provides safe cleanup workflows, validation steps, and reporting templates for code, deps, docs, tests, and sprint archives.
NickCrew/Claude-Cortex 13
sharing-skills Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository
NickCrew/Claude-Cortex 13
template-skill A template for creating new skills. Use when initializing a new skill to ensure proper structure and metadata.
NickCrew/Claude-Cortex 13
threat-modeling-techniques Threat modeling methodologies using STRIDE, attack trees, and risk assessment for proactive security analysis. Use when designing secure systems, conducting security reviews, or identifying potential attack vectors in applications.
NickCrew/Claude-Cortex 13
using-superpowers Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Skill tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists
NickCrew/Claude-Cortex 13