gitops-principles-skill
Comprehensive GitOps methodology and principles skill for cloud-native operations. Use when (1) Designing GitOps architecture for Kubernetes deployments, (2) Implementing declarative infrastructure with Git as single source of truth, (3) Setting up continuous deployment pipelines with ArgoCD/Flux/Kargo, (4) Establishing branching strategies and repository structures, (5) Troubleshooting drift, sync failures, or reconciliation issues, (6) Evaluating GitOps tooling decisions, (7) Teaching or explaining GitOps concepts and best practices, (8) Deploying ArgoCD on Azure Arc-enabled Kubernetes or AKS with workload identity. Covers the 4 pillars of GitOps (OpenGitOps), patterns, anti-patterns, tooling ecosystem, Azure Arc integration, and operational guidance.
ultrathink
First-principles deep thinking for significant problems. Use when you need to question assumptions, craft elegant solutions, and challenge beliefs.
constitution
Develop, refine, and maintain project constitutional principles - uses Socratic questioning to eliminate ambiguity and ensure perfect clarity on design values and non-negotiables
check-constitutional-alignment
Verify feature requests align with project constitutional principles - applies decision framework systematically and provides clear align/reject/revise recommendation with detailed reasoning
functional-introspection-principle
Apply functional introspection principles to self-analysis.
codex-law-enforcement
Enforce the four Codex Laws governing all agent interactions: CONSENT, INVITATION, INTEGRITY, GROWTH.
zfc
Zero Framework Cognition Principles
paul-graham-wisdom
Apply Paul Graham's principles when exploring ideas, evaluating opportunities, building products, or making important decisions. Use this skill when brainstorming, validating ideas, planning ventures, thinking through problems, or needing a framework for clear thinking. Triggers include "evaluate this idea", "should I pursue this", "help me think through", "is this worth doing", "startup idea", "opportunity analysis", or any creative/strategic thinking task.
solid-principles
Apply and validate SOLID principles in object-oriented design
testing-philosophy
Apply testing philosophy: test behavior not implementation, minimize mocks, AAA structure, coverage for confidence not percentage. Use when writing tests, reviewing test quality, discussing TDD, or evaluating test strategies.
ousterhout-principles
Apply Ousterhout's software design principles: detect shallow modules, information leakage, and complexity red flags. Use when reviewing code, designing modules, refactoring, or discussing architecture.
naming-conventions
Apply universal naming principles: avoid Manager/Helper/Util, use intention-revealing names, domain language, verb+noun functions. Use when naming variables, functions, classes, reviewing names, or refactoring for clarity. Language-agnostic principles.
promptup
Transform vague requirements into production-grade prompts using evidence-based principles. Diagnose prompt issues, define boundaries, and iterate to quality.
debugging-complex-multi-layer-systems
A reasoning pattern for diagnosing and fixing bugs that span multiple abstraction layers in complex systems.
development-philosophy
Personal development philosophy emphasizing experiment-driven, fail-fast approach. Activate when planning implementations, reviewing code architecture, making design decisions, or when user asks to apply development principles. Guides against over-engineering and towards solving real problems with simple solutions. (project, gitignored)
least-astonishment
Principle of Least Astonishment (POLA) - ensure code changes behave as users and developers expect. Activate when making code changes, refactoring, modifying APIs, renaming functions/variables, changing file structure, or reviewing proposed implementations. Guides predictable, convention-following changes.
rust-guidelines
Pragmatic Rust conventions to keep code readable, testable, and performant for this project.
quality-standards
Defines code quality benchmarks, standards compliance, and best practices for maintaining high-quality codebases
Page 1 of 3 · 41 results