ReddRadar
Topic: ai-assisted-development
271 skills in this topic.
-
internal-comms
A set of resources to help write all kinds of internal communications, using company-specific formats. Use when asked to write internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
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
-
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
-
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
-
prompt-engineering
Optimize prompts for LLMs and AI systems with structured techniques, evaluation patterns, and synthetic test data generation. Use when building AI features, improving agent performance, or crafting system prompts.
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
-
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches superpowers:code-reviewer subagent to review implementation against plan or requirements before proceeding
NickCrew/Claude-Cortex 13
-
requirements-discovery
Stakeholder interviews, PRD structure, and scope definition for software requirements elicitation. Use when gathering requirements, defining project scope, or structuring product requirement documents.
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
-
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
-
socratic-questioning
Guide discovery through questioning techniques and pattern recognition for Clean Code, GoF design patterns, and architectural decisions. Use when coaching developers, facilitating design discussions, or helping teams discover solutions.
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
-
template-skill
A template for creating new skills. Use when initializing a new skill to ensure proper structure and metadata.
NickCrew/Claude-Cortex 13
-
your-skill-name
Brief description of what this skill does (1-2 sentences). Use when [specific trigger condition]. Keep under 200 words total.
NickCrew/Claude-Cortex 13
-
terraform-best-practices
Terraform infrastructure-as-code best practices for scalable and maintainable cloud infrastructure. Use when writing Terraform modules, managing infrastructure state, or implementing infrastructure automation at scale.
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
-
token-efficiency
Compressed communication using symbols and abbreviations. Use when context is limited or brevity is needed.
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
-
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
-
ux-review
Multi-perspective UX review combining usability, accessibility, and interaction design analysis.
NickCrew/Claude-Cortex 13
-
verification-before-completion
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
NickCrew/Claude-Cortex 13
-
workflow-bug-fix
Systematic approach to identifying, fixing, and validating bug fixes. Use when fixing bugs, resolving issues, or addressing errors.
NickCrew/Claude-Cortex 13
-
workflow-feature
Complete feature development workflow from design to deployment. Use when implementing new features or functionality.
NickCrew/Claude-Cortex 13
-
workflow-feature-development
Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.
NickCrew/Claude-Cortex 13