enterprise-web-code
Enterprise-ready web development for Next.js 16, React, and TypeScript incorporating Kaizen (continuous improvement) and Monozukuri (meticulous craftsmanship) principles. Use this skill when building web applic...
发现 devops architecture patterns 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Enterprise-ready web development for Next.js 16, React, and TypeScript incorporating Kaizen (continuous improvement) and Monozukuri (meticulous craftsmanship) principles. Use this skill when building web applic...
Create comprehensive implementation plans for engineers with minimal codebase knowledge. This skill should be used when breaking down features into detailed, step-by-step implementation guides following TDD pri...
Ruthlessly critical plan reviewer that catches gaps, ambiguities, and missing context. Read-only - cannot modify files. Use when reviewing Prometheus plans or any implementation specs before execution. Simulate...
Strategic planner that creates detailed implementation plans without writing code. Operates in Interview Mode to gather requirements, then produces self-contained plans in .sisyphus/plans/. Use when user needs...
AAA-caliber engineering council for building production-quality games. Use when implementing game systems, writing game code, designing data architecture, building UI components, creating tutorials, optimizing...
Guide for building software with Clean Architecture, DDD, SOLID principles, and hexagonal/onion patterns. Use when designing new features, refactoring code, reviewing architecture, or when user mentions clean c...
Fundamental coding principles (DRY, KISS, YAGNI, SOLID, HHH). Use when starting any development task, evaluating implementation approaches, or reviewing code quality. Always active as foundation for all develop...
SOLID principles and architecture design patterns. Use when starting new features, refactoring code, conducting architecture reviews, or applying object-oriented design principles.
Ralph Loop integration patterns for iterative AI development. Use when starting Ralph loops, managing iterations, or recovering from context compaction. Covers TDD, debugging, context management, and memory per...
On-demand audit and analysis of agent orchestration flows via Sentinel Protocol
Analyze repository through 8 philosophical dimensions for MVV extraction
Code implementation standards, patterns, and best practices. Use when writing code, implementing features, following coding conventions, or need guidance on code structure, naming, error handling, and testing.
Software architecture design patterns and technical solution design. Use when designing data models, API structures, state management, component architecture, or translating requirements into technical solution...
Specification-Driven Development methodology from GitHub spec-kit. Use when users ask to create specifications, plan features, define requirements, write user stories, decompose tasks, establish project constit...
Guide for creating structured plans with numbered steps and quality gates
Design multi-service architectures with RAW workflows as components
Key algorithms in OpenAPI LSP - Solver (Union-Find equivalence classes), Root Discovery (glob-based workspace scanning), Nominal Propagation (fixed-point iteration within SCCs), and Kosaraju's SCC algorithm. Re...
Bounded Context에 새로운 presentation 레이어를 추가하거나 수정할 때 사용하세요.
새로운 Bounded Context(도메인)를 DDD, Clean Architecture, CQRS 패턴에 맞게 추가합니다. 새로운 도메인이나 모듈을 추가할 때 사용하세요.
Bounded Context에 새로운 infrastructure 를 추가하거나 수정할 때 사용하세요.
Bounded Context에 새로운 application 레이어를 추가하거나 수정할 때 사용하세요.
Minimal reference skill used to validate parsing and loading.
This skill provides high-level overview about the network topology and functions to be achieved in the project. Use for understanding the project contexts outside of the codebase.
Rapidly create professional REST APIs with proper documentation, security, and best practices. Use when user needs to build APIs quickly, generate API boilerplate, create API documentation, or implement standar...
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。