57 skills (repositories by addyosmani) · sorted by popularity
Review code changes before merging across correctness, readability, architecture, security, and performance. Get findings that distinguish required fixes from optional suggestions, with concrete ways to simplify code and checks on test coverage.
Add logs, metrics, traces that follow requests across services, and actionable alerts to production features. This skill guides signal design, request identification, response instructions, and checks that the collected data can explain failures.
Develop and fix code by first writing a failing test, then making it pass and improving the implementation. The skill follows the project's testing tools and checks both the intended behavior and existing functionality.
Make working code easier to read and maintain while preserving its behavior. The skill identifies tangled conditions, unclear names, duplication, and unnecessary abstractions, then guides small refactoring steps checked against existing tests and project conventions.
Plan the retirement of old APIs, features, and systems, then move their users to replacements in stages. The skill also guides database schema changes through additive steps that keep old and new application code compatible during rollout.
Find and fix slow page loads, API responses, and database queries using measurements. Compare results before and after each change, discard changes without clear gains, and add checks or monitoring to catch future slowdowns.
Prepare a production release with checks for code quality, security, performance, accessibility, and infrastructure. Plan monitoring, gradual feature exposure, and rollback steps, then use release metrics and reliability limits to guide rollout decisions.
Review web application security across user input, authentication, external services, dependencies, personal data, and AI features. Identify threats, apply protective controls, and verify changes with checks covering access permissions, sensitive information, and untrusted model output.
Implement larger changes as small, working pieces. Each piece goes through testing, verification, and a focused commit, with guidance on choosing boundaries, hiding unfinished features behind switches, and keeping changes easy to roll back.
Check project dependency versions and consult the relevant official documentation before writing framework-specific code. Produce implementations with source links, identify deprecated APIs, and flag unverified approaches or conflicts between documentation and existing project patterns.
Turn clear requirements into small implementation tasks with acceptance criteria, verification steps, dependencies, and estimated scope. Produce a written plan and ordered task list, with checkpoints and opportunities for parallel work identified before coding begins.
Build responsive interfaces that follow an existing design system and support accessible interaction. Covers component structure, state management, keyboard controls, and loading, empty, and error states, with checks across screen sizes and assistive tools.
Clarify an unclear request through one question at a time, with the agent sharing its best guess for each answer. Produce a user-confirmed statement covering the desired outcome, audience, timing, success criteria, constraints, and exclusions.
Choose the right engineering skills for a task and decide their order, from clarifying requirements to deployment. This guide also defines shared practices for stating assumptions, resolving uncertainty, keeping scope focused, and verifying completed work.
Design APIs and interfaces between modules with clear inputs, outputs, naming, and errors. The skill guides compatible extensions, input validation, and retry handling so callers can use interfaces consistently without accidentally repeating state-changing operations.
Test browser interfaces through Chrome DevTools MCP, a connection that lets an agent inspect a live browser. Check screenshots, errors, network traffic, accessibility, and performance to diagnose problems and verify fixes.
Set up automated checks and deployment workflows with GitHub Actions. Covers tests, type checks, builds, security audits, preview deployments, staged releases, and rollback plans, with guidance for diagnosing failures and reducing pipeline runtime.
Define project quality standards in CONSTRAINTS.md, connect measurable targets to checks, and inspect changes for weakened safeguards. It helps teams choose thresholds and catch skipped tests, suppressed warnings, unfinished code, or lowered standards during agent development.
Organize the information an AI coding agent needs for each task. This skill guides project rules, relevant file selection, conversation summaries, and session handoffs so the agent can follow existing conventions and retain key decisions.
Investigate failing tests, broken builds, and unexpected behavior through a structured debugging process. Reproduce the failure, narrow down its source, fix the root cause, and add a regression test that catches the same problem.
Challenge important design and implementation decisions with a separate reviewer that does not inherit the working session's context. Identify hidden assumptions and failure cases, then assess each finding against the artifact and its requirements.
Organize code changes into focused commits and manageable branches, prepare pull requests, and maintain release versions and changelogs. The skill also covers separate working directories for parallel work and checks before committing.
Turn a rough idea into a concrete concept through guided discussion. Explore alternatives, compare user value and feasibility, and produce a Markdown brief covering the recommended direction, assumptions to test, minimum scope, and explicit exclusions.
Document why software decisions were made, which alternatives were considered, and what trade-offs remain. Create architecture decision records, README guidance, API documentation, and changelogs that help future contributors and AI agents understand the project.