Loading...
Loading...
Found 6,725 Skills
Write feature specifications that capture requirements and acceptance criteria. Use when (1) writing a new feature spec, (2) documenting functional requirements, (3) defining acceptance criteria for a feature, (4) capturing design goals and constraints for planned work, or (5) structuring a product idea into a formal specification.
Shell script testing expertise using bash test framework patterns from unix-goto, covering test structure (arrange-act-assert), 4 test categories, assertion patterns, 100% coverage requirements, and performance testing
C# code review skill. Analyzes code quality from OOP, SOLID, GoF design pattern, modern C# features, and performance perspectives. Use before pull requests, when optimizing code, or auditing legacy codebases.
Performs comprehensive security audit of any codebase against OWASP Top 10 2025. Use when user asks for OWASP audit, OWASP Top 10 review, OWASP security check, or wants to audit code against OWASP categories. Do not trigger for PR review, npm/pip audit, SOC2 compliance, general security questions, or threat modeling.
Statistical modeling toolkit. OLS, GLM, logistic, ARIMA, time series, hypothesis tests, diagnostics, AIC/BIC, for rigorous statistical inference and econometric analysis.
Compose intellectually sophisticated persuasive essays using tripartite dialectical structure (establish-critique-synthesize), paradox accumulation, conversational register calibration, and strategic humility. Supports three atomic writing primitives (AGONAL α, MAIEUTIC β, APOPHATIC γ) with hypersoft plithogenic composition, plus legacy style modes and hybrid combinations. Triggers on requests for persuasive writing to mixed/skeptical audiences, defending counterintuitive claims, Socratic pedagogical dialogue, editorial first-person essays, or writing that must balance accessibility with depth. Implements recursive thematic anchoring, forced dilemma construction, and transformed return closure. Use when linear argumentation is insufficient and accumulated tension resolves through synthesis.
Use when content must be translated between audiences with different expertise, context, or goals while preserving accuracy but adapting presentation. Invoke when technical content needs business framing (engineering decisions → executive summary), strategic vision needs tactical translation (board presentation → team OKRs), expert knowledge needs simplification (academic paper → blog post, medical diagnosis → patient explanation), formal content needs casual tone (annual report → social media post), long-form needs summarization (50-page doc → 1-page brief), internal content needs external framing (roadmap → public updates, bug tracking → known issues), cross-cultural adaptation (US idioms → international clarity, Gen Z → Boomer messaging), medium shifts (written report → presentation script, detailed spec → action checklist), or when user mentions "explain to", "reframe for", "translate this for [audience]", "make this more [accessible/formal/technical]", "adapt for [executives/engineers/customers]", "simplify without losing accuracy", or "same content, different audience". Apply to technical communication (code → business value), organizational translation (strategy → execution), education (expert → novice), customer communication (internal → external), cross-cultural messaging, and anywhere same core message needs different presentation for different stakeholders while maintaining correctness.
RESTful API design guidelines following the Richardson Maturity Model through to Level 3 (HATEOAS) for Ruby on Rails. This skill should be used when designing, building, reviewing, or refactoring REST APIs to ensure proper resource modeling, HTTP method semantics, hypermedia controls, content negotiation, and API evolvability. Triggers on tasks involving API controllers, serializers, routing, link relations, pagination, error handling, or HTTP caching in Rails.
Use when defining events, fields, and governance for GTM analytics pipelines.
Simple report generation without Google Cloud - uses Gmail App Password or local file export (PDF, Excel, Word-compatible formats)
Create a Geoffrey Moore-style positioning statement that clearly articulates who your product serves, what need it addresses, how it's categorized, what benefit it delivers, and how it differs from al
Bronze/Silver/Gold layer design patterns and templates for building scalable data lakehouse architectures. Includes incremental processing, data quality checks, and optimization strategies.