Loading...
Loading...
Found 372 Skills
Apply Edward de Bono's Six Thinking Hats methodology to software testing for comprehensive quality analysis. Use when designing test strategies, conducting test retrospectives, analyzing test failures, evaluating testing approaches, or facilitating testing discussions. Each hat provides a distinct testing perspective: facts (White), risks (Black), benefits (Yellow), creativity (Green), emotions (Red), and process (Blue).
Go-specific code review with 6-phase methodology: Context, Automated Checks, Quality Analysis, Specific Analysis, Line-by-Line, Documentation. Use when reviewing Go code, PRs, or auditing Go codebases for quality and best practices. Use for "review Go", "Go PR", "check Go code", "Go quality", "review .go". Do NOT use for writing new Go code, debugging Go bugs, or refactoring -- use golang-general-engineer, systematic-debugging, or systematic-refactoring for those tasks.
Mom Nagging Mode — Chinese-style mom nagging drives AI to explore every possible solution. The underlying behavioral constraints remain unchanged (three red lines, methodology, 7-item checklist), with the narration switching from big tech PUA to mom's constant nagging. Triggers on: '/pua:mama', '/pua mama', '妈妈模式', '妈妈唠叨', 'mama mode', '唠叨模式'. Similar to /pua:yes, this is a narration style switch that does not alter core behaviors.
Calculate construction costs using DDC CWICR resource-based methodology. Break down costs into labor, materials, equipment with transparent pricing.
PluginEval quality methodology — dimensions, rubrics, statistical methods, and scoring formulas. Use this skill when understanding how plugin quality is measured, when interpreting a low score on a specific dimension, when deciding how to improve a skill's triggering accuracy or orchestration fitness, when calibrating scoring thresholds for your marketplace, or when explaining quality badges to external partners like Neon.
Go testing patterns for production-grade code: subtests, test helpers, fixtures, golden files, httptest, testcontainers, property-based testing, and fuzz testing. Covers mocking strategies, test isolation, coverage analysis, and test design philosophy. Use when writing tests, improving coverage, reviewing test quality, setting up test infrastructure, or choosing a testing approach. Trigger examples: "add tests", "improve coverage", "write tests for this", "test helpers", "mock this dependency", "integration test", "fuzz test". Do NOT use for performance benchmarking methodology (use go-performance-review), security testing (use go-security-audit), or table-driven test patterns specifically (use go-test-table-driven).
Discover where your audience actually pays attention online using Rand Fishkin's behavioral intelligence methodology—beyond demographics to actionable media affinity data. Use when: **Find where to reach your audience** beyond Google and Facebook ads; **Discover podcasts, YouTube channels, and publications** your audience follows; **Identify influencers and accounts** with real audience overlap; **Plan PR and media outreach** with data-backed target lists; **Improve ad targeting** on YouTube,...
Unbounce platform help — landing page builder, Smart Traffic AI optimization, Smart Copy AI copywriting, A/B testing, popups, sticky bars, Dynamic Text Replacement, AMP pages, REST API. Use when landing page built in Unbounce isn't converting, Smart Traffic not improving conversions, A/B test setup in Unbounce, popup or sticky bar not triggering, Unbounce page loads too slowly, choosing between Build vs Experiment vs Optimize plan, connecting Unbounce to CRM or email tool, or Dynamic Text Replacement not working. Do NOT use for general funnel strategy (use /sales-funnel) or general CRO methodology (use /sales-vwo).
Product Requirement Prompts (PRP) methodology for AI-assisted development with validation loops and autonomous execution
Jeffrey Emanuel's comprehensive markdown planning methodology for software projects. The 85%+ time-on-planning approach that makes agentic coding work at scale. Includes exact prompts used.
Perform 12-Factor Agents compliance analysis on any codebase. Use when evaluating agent architecture, reviewing LLM-powered systems, or auditing agentic applications against the 12-Factor methodology.
Expert sales strategy and operations guidance for B2B SaaS companies. Use when designing sales processes, implementing qualification frameworks (MEDDIC, BANT, SPICED), territory planning, forecasting, quota setting, compensation design, or optimizing pipeline velocity. Covers sales methodology, org structure, tech stack selection, win rate analysis, and deal acceleration strategies.