error-patterns
Error recognition and diagnosis patterns for infrastructure troubleshooting. Use when identifying, categorizing, or resolving errors across platforms.
Discover testing security architecture patterns skills, compare source repositories and read the instructions for each workflow.
Error recognition and diagnosis patterns for infrastructure troubleshooting. Use when identifying, categorizing, or resolving errors across platforms.
Use this skill when reasoning about the distributed system design, service orchestration, or request lifecycle of the X recommendation engine. It is essential for tasks involving the "For You" timeline construc...
Deep knowledge of GitHub Actions, Railway, Supabase, and Postgres platforms. Use when troubleshooting, configuring, or optimizing any of these platforms.
Opinionated constraints for building better interfaces with agents. Combines UI Skills and Vercel Web Interface Guidelines. Use when building UI components, reviewing frontend code, or implementing interactions...
Expert guidance for designing, building, and maintaining n8n workflows across dev/staging/prod environments on Railway with MCP integration. Handles flow authoring, node configuration, error handling, and deplo...
Enforces Specification-Driven Development (SDD). Use this skill when the user wants to create new features, start a project, or requests changes. It ensures no code is written without an approved plan.
Manages project structure, auto-saves artifacts, and performs recovery protocols. Use this skill at the end of tasks or when encountering errors.
Build interfaces with intention. Remember decisions across sessions. Maintain systematic consistency. For dashboards, apps, tools — not marketing sites.
Clean architecture patterns for the 3SC widget host. Defines layer boundaries, dependency rules, composition root patterns, and abstraction strategies.
Use this skill when implementing new features or debugging the core "For You" pipeline. The system has shifted from legacy heuristics toward a unified **Rust-based** pipeline powered by the **Phoenix** transfor...
Resilience patterns for the 3SC widget host. Covers retry policies, circuit breakers, timeouts, fallbacks, and graceful degradation for external dependencies.
Common patterns, structures, and best practices for 42 School projects. Use when starting projects, creating Makefiles, or structuring code.
In-memory caching patterns for the 3SC widget host. Covers cache strategies, invalidation, TTL policies, and when to cache vs when to fetch.
TypeScript strict patterns and best practices. Trigger: When writing TypeScript code - types, interfaces, generics.
Platform/Language agnostic API delivery and correctness auditor. Use when project contains API endpoints to verify contract alignment, endpoint behavior, and test coverage.
Structured escalation with evidence. Surfaces blocking issues for human decision, referencing the Manifest hierarchy.
Transform rough ideas into detailed designs through structured dialogue. Use before implementation to refine requirements.
Dynamic plugin enumeration and capability mapping with delegation priority and explicit routing announcements
Creates comprehensive implementation plans through codebase exploration, research, and iterative clarification. Use when asked to plan, design, architect, or figure out how to implement a feature, refactor, or...
Top 1% development standard for OC Pipeline and federal-grade construction software. Use when Bill asks to build features, fix bugs, write code, create components, or do any software development work. Activates...
Guidelines for iteratively planning tasks and changes before implementation. Use this when the user requests a non-trivial task or when you need to align on a complex implementation strategy.
Create detailed implementation plans with granular tasks. Use before implementing features or complex changes.
Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.
Technical analysis capabilities for APIs, data models, integrations, and security requirements. Use when analyzing technical aspects of systems or documenting technical requirements.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.