productivity▌

MySQL development best practices for schema design, query optimization, and database administration. \n \n Covers schema design with InnoDB as default engine, appropriate data types (DECIMAL for financial data, utf8mb4 charset), and primary key strategies including AUTO_INCREMENT and UUID storage \n Indexing strategies including B-tree, FULLTEXT, and covering indexes with guidelines on column selectivity and composite index ordering \n Query optimization using EXPLAIN analysis, prepared statemen

Enterprise-grade Nest.js architecture guidance covering modules, dependency injection, testing, databases, and authentication. \n \n Diagnoses and resolves dependency injection issues, circular dependencies, and module configuration problems with proven solutions from 500+ real GitHub issues and Stack Overflow threads \n Covers full request lifecycle: middleware, guards, interceptors, pipes, and exception filters with correct execution order and async handling \n Provides testing strategies for

Generates comprehensive README.md files for projects with professional structure and formatting. \n \n Analyzes entire project workspace to create contextually accurate, well-organized documentation \n Follows proven open-source README patterns with clear sections for setup, usage, and key features \n Uses GitHub Flavored Markdown and admonition syntax for enhanced readability and visual hierarchy \n Balances detail with conciseness, avoiding unnecessary sections and excessive emoji while mainta

Analyze codebases for architectural friction and propose module-deepening refactors as testability improvements. \n \n Explores codebases organically to surface shallow modules, tightly-coupled components, and untested seams rather than following rigid heuristics \n Applies John Ousterhout's \"deep module\" principle: small interfaces hiding large implementations for better testability and AI navigability \n Generates multiple radically different interface designs (minimalist, flexible, caller-o

One-time setup that gathers design context and persists it to your AI config file. \n \n Scans your codebase to discover existing design patterns, brand assets, tech stack, and design tokens before asking questions \n Asks targeted UX questions about users, brand personality, aesthetic preferences, and accessibility needs, skipping what's already clear from exploration \n Synthesizes findings into a Design Context markdown section saved to .impeccable.md in your project root for all future sessi

This skill enables precise extraction of tables from PDF documents using camelot - the gold standard for PDF table extraction. Handle complex tables with merged cells, borderless tables, and multi-page layouts with high accuracy.

This skill enables AI agents to perform a comprehensive usability evaluation of apps, websites, or digital interfaces using Jakob Nielsen's 10 Usability Heuristics, the industry-standard framework for identifying usability problems.

Five specialized agents for ideation, design thinking, innovation strategy, problem-solving, and storytelling. \n \n Five named agents (Carson, Maya, Victor, Dr. Quinn, Sophia) each with distinct methodologies: brainstorming coach, design thinking facilitator, innovation strategist, creative problem solver, and storyteller \n Brainstorming agent covers 36 techniques across 7 categories; storytelling agent provides 25 proven story frameworks; problem-solving agent uses TRIZ, Theory of Constraints

Expert project planning, execution, and delivery across traditional and agile methodologies. \n \n Covers full project lifecycle: initiation, planning, execution, monitoring, risk management, and closure with structured deliverables like charters, WBS, Gantt charts, and risk registers \n Supports hybrid approaches combining Waterfall, Agile, Scrum, Critical Path Method, and Earned Value Management for different project contexts \n Handles cross-functional team coordination, stakeholder communica

This is the main browser automation strategy skill for nontrivial web work. It teaches the agent when to stay on public-web tools, when to use the live browser session, and when to fall back to a separate browser or raw-fetch path.