ReddRadar
Topic: ai-assisted-development
271 skills in this topic.
-
workflow-orchestrator
Execute 5-phase workflow for complex features. Includes fasttrack mode for pre-approved specs. DO NOT use for simple bug fixes.
nguyenthienthanh/aura-frog 14
-
api-design-patterns
Comprehensive REST and GraphQL API design patterns with versioning, pagination, error handling, and HATEOAS principles. Use when designing APIs, defining endpoints, or architecting service contracts requiring production-grade patterns.
NickCrew/Claude-Cortex 13
-
api-gateway-patterns
API Gateway patterns for routing, authentication, rate limiting, and service composition in microservices architectures. Use when implementing API gateways, building BFF layers, or managing service-to-service communication at scale.
NickCrew/Claude-Cortex 13
-
async-python-patterns
Python asyncio and concurrent programming patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.
NickCrew/Claude-Cortex 13
-
code-quality-workflow
Use when assessing or improving code quality, maintainability, performance, or security hygiene - provides workflows for analysis, code review, and systematic improvements with validation steps.
NickCrew/Claude-Cortex 13
-
your-skill-name
Brief description of what this skill does and provides. Use when [clear trigger condition that indicates this skill should activate]. Keep under 200 words.
NickCrew/Claude-Cortex 13
-
database-design-patterns
Database schema design patterns and optimization strategies for relational and NoSQL databases. Use when designing database schemas, optimizing query performance, or implementing data persistence layers at scale.
NickCrew/Claude-Cortex 13
-
design-system-architecture
Build scalable design systems with design tokens, component APIs, and documentation. Use when creating or evolving component libraries.
NickCrew/Claude-Cortex 13
-
dev-workflows
Use when running builds, executing tests, or improving developer experience workflows - provides structured guidance for build/test execution and DX improvement.
NickCrew/Claude-Cortex 13
-
doc-completeness-audit
Audit documentation completeness by mapping what a doc set should cover against what it actually covers. Produces a prioritized gap report by topic, not just by file. This skill should be used after shipping features, before releases, or when users report missing documentation.
NickCrew/Claude-Cortex 13
-
doc-health-audit
Orchestrate a full documentation health audit across five dimensions: structural health, semantic accuracy, topic completeness, prose quality, and information architecture. Runs each phase in dependency order with phase gating. This skill should be used for pre-release audits, periodic health checks, or comprehensive documentation assessments.
NickCrew/Claude-Cortex 13
-
documentation-production
Use when generating, updating, or organizing documentation (component/API docs, project indexes, diagrams, tutorials, learning paths) - provides structured workflows and references for docs generation, indexing, diagrams, and teaching.
NickCrew/Claude-Cortex 13
-
helm-chart-patterns
Helm chart development patterns for packaging and deploying Kubernetes applications. Use when creating reusable Helm charts, managing multi-environment deployments, or building application catalogs for Kubernetes.
NickCrew/Claude-Cortex 13
-
mermaid-diagramming
Mermaid diagram creation covering flowcharts, sequence diagrams, ERDs, state machines, Gantt charts, and architecture views. Use when creating or updating technical diagrams in documentation.
NickCrew/Claude-Cortex 13
-
multi-llm-consult
Consult external LLMs (Gemini, OpenAI/Codex, Qwen) for second opinions, alternative plans, independent reviews, or delegated tasks. Use when a user asks for another model's perspective, wants to compare answers, or requests delegating a subtask to Gemini/Codex/Qwen.
NickCrew/Claude-Cortex 13
-
python-performance-optimization
Python performance optimization patterns using profiling, algorithmic improvements, and acceleration techniques. Use when optimizing slow Python code, reducing memory usage, or improving application throughput and latency.
NickCrew/Claude-Cortex 13
-
python-testing-patterns
Python testing patterns and best practices using pytest, mocking, and property-based testing. Use when writing unit tests, integration tests, or implementing test-driven development in Python projects.
NickCrew/Claude-Cortex 13
-
reference-documentation
Create exhaustive technical references, API documentation, and searchable reference materials. Use when building API docs, configuration references, or complete technical specifications.
NickCrew/Claude-Cortex 13
-
release-prep
Use when preparing a production release or release candidate - provides a checklist-driven workflow for validation, versioning, build optimization, documentation updates, and deployment readiness.
NickCrew/Claude-Cortex 13
-
session-management
Use when loading, saving, or reflecting on session context - provides structured workflows for session lifecycle management and reflection outputs.
NickCrew/Claude-Cortex 13
-
skill-creator
Guide for creating effective skills. Use when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
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
-
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