gas-optimization
Gas optimization techniques and patterns for efficient Solidity smart contracts. Use when optimizing contract gas costs or reviewing code for efficiency improvements.
Gas optimization techniques and patterns for efficient Solidity smart contracts. Use when optimizing contract gas costs or reviewing code for efficiency improvements.
Test coverage analysis and improvement strategies for Solidity contracts. Use when analyzing or improving test coverage.
MoonBit code generation best practices. Use when writing MoonBit code to avoid common AI mistakes with syntax, tests, and benchmarks.
Monetization expert that analyzes codebases to discover features, calculate service costs, model usage patterns, and create data-driven pricing with revenue projections. Use when: (1) Analyzing app features and their costs, (2) Modeling user consumption and usage patterns, (3) Calculating ARPU, LTV, and revenue projections, (4) Setting optimal tier limits based on usage percentiles, (5) Creating pricing tiers with adequate margins, (6) Implementing payment systems (Stripe, etc.), (7) Break-even and profitability analysis, (8) Subscription and billing systems.
Analyze and optimize code performance with profiling and benchmarking. Use when asked to improve performance or diagnose slowness.
This skill should be used for multi-perspective analysis through parallel cursor-agent sessions. Triggers include "analyze from multiple angles", "what are the gaps/patterns/friction", "explore before deciding", pre-refactor landscape mapping, or skill/architecture auditing. Each agent gets a DIFFERENT prompt, results aggregated.
Analyze features and their dependencies. Use when mapping feature relationships, detecting blockers, optimizing build order, or identifying critical paths.
Create Jupyter notebooks for FF Analytics following project conventions. Use this skill when the user requests analysis notebooks for player evaluation, roster health, trade scenarios, market trends, or projection quality analysis. Guides through notebook structure, DuckDB connections, mart queries, visualization standards, and freshness banner patterns.
This skill should be used when the user asks to "analyze costs", "optimize infrastructure spending", "reduce operational expenses", "monitor API costs", "audit cloud resources", "optimize database queries", or needs comprehensive cost analysis and optimization recommendations.
Analyze and prioritize technical debt with refactoring recommendations. Use when evaluating code quality or planning debt reduction.
Performance auditing for web applications. Analyzes bundle size, React rendering, database queries, network patterns, and assets. Provides actionable recommendations with effort estimates.
This skill should be used when the user asks about "code complexity", "cyclomatic complexity", "cognitive complexity", "code metrics", "maintainability index", "code coverage", or when measuring code quality quantitatively. Provides metrics thresholds and measurement techniques.
Performance analysis and optimization opportunities. Use when application feels slow or before optimization work.
Performance benchmarking techniques and analysis. Use when measuring performance.
Architecture review using "A Philosophy of Software Design" principles. Modes: red-flags, depth, complexity, fcis, performance, split, comments, naming, consistency, tactical, review.
Create detailed implementation plans with diagrams and dependency graphs. Use when planning features, refactoring, or multi-step development work before writing code.
Generates implementation plans with code reuse analysis, architecture design, and complexity estimation during the /plan phase. Use when planning feature implementation, analyzing code reuse opportunities, or designing system architecture after specification phase completes. Integrates with 8 project documentation files for constraint extraction. (project)
Provides expert code quality analysis, technical debt assessment, and maintainability evaluation. Use this skill when the user needs code review, tech debt inventory, refactoring prioritization, or code health assessment. Triggers include requests for code quality review, technical debt audit, maintainability analysis, or when asked to evaluate codebase health. Produces detailed consultant-style reports with findings and prioritized recommendations — does NOT write implementation code.
Deliver a complete, user-centered critique of a product or flow, identifying issues, risks, and improvements across the entire experience.. Use when When a user requests a UX/UI audit or heuristic review of a product..