Addy Osmani
- 47 skills
- 0 followers
- 69k repo stars
- last week last updated
- ▌ Debugging And Error Recovery 2 · addyosmaniGuides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than guessing.
- ▌ Observability And Instrumentation 2 · addyosmaniInstruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
- ▌ Factory Spec 2 · addyosmaniTurn a ready-to-spec queue item into an approved plan through explicit human gates. Use when an item needs scope decided before code exists, when planning a feature, or before starting a migration. Runs interactively - not for unattended routines.
- ▌ Factory Triage 2 · addyosmaniClassify incoming issues into the live GitHub label queue, reproduce where cheap, and write an auditable QUEUE.md snapshot. Use when triaging a backlog, running the scheduled triage routine, or deciding what the factory should pick up next.
- ▌ Factory Verify 2 · addyosmaniVerify an open factory PR before human review - re-runs gates, checks the test proves the fix, checks scope and test tampering. Use when reviewing a factory PR, running the PR review routine, or asked to independently check a change.
- ▌ Factory Monitor 2 · addyosmaniScheduled health sweep that closes the factory loop - reads CI failures, recent commits, dependency and security advisories, and live queue labels, then files issues and writes an immutable run record. Use for the nightly or weekly monitor routine.
- ▌ Factory Implement 2 · addyosmaniClaim one live GitHub queue item, implement it end to end, run fail-closed gates and independent verification, then open a draft PR. Use for one ready-to-implement issue or the implementation routine.
- ▌ Factory Spec · addyosmaniTurn an ambiguous factory issue into human-approved product, behavior, design, and implementation slices. Use interactively before implementation.
- ▌ Factory Tune · addyosmaniReview factory evidence and propose tighter or looser constraints without editing the charter. Use for a periodic constraint review.
- ▌ Factory Status · addyosmaniShow the factory control room from live GitHub labels, open PRs, recent run records, gate health, and charter limits.
- ▌ Factory Triage · addyosmaniClassify GitHub issues into the factory's live label queue and write an auditable snapshot. Use for backlog triage or a scheduled triage run.
- ▌ Factory Verify · addyosmaniIndependently verify a factory pull request, including fail-closed gates, negative test proof, scope, and load-bearing review.
- ▌ Factory Monitor · addyosmaniInspect factory health, stale work, CI, security advisories, and recent run evidence without implementing fixes.
- ▌ Factory Implement · addyosmaniClaim and implement one ready GitHub issue, run fail-closed gates, obtain independent verification, and open a draft pull request.
- ▌ Adverse Review · addyosmani bundleMulti-agent adversarial code review. Spawns three reviewer subagents (Auditor, Adversary, Pragmatist) on a single model, runs a cross-examination round, then deterministically synthesizes a single ranked report. Use this for non-trivial PRs, security-sensitive changes, refactors that touch many files, or any change where one perspective has obvious blind spots. Trigger phrases include "adverse review", "adversarial review", "multi-perspective review", "review my changes from multiple angles", "panel review". NOT suitable for trivial diffs (typos, dependency bumps, formatting).
- ▌ Clarity · addyosmani bundleDraft, rewrite, or review reader-facing prose so it is specific, useful, and recognizably the author's without inventing facts or performing humanness. Use for essays, articles, newsletters, documentation, talks, launch copy, and other important prose that feels generic, hollow, or AI-shaped. Supports co-write, rewrite, review, and lint modes.
- ▌ Web Quality Audit · addyosmaniComprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
- ▌ Core Web Vitals · addyosmaniOptimize Core Web Vitals (LCP, INP, CLS) for better page experience and search ranking. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".
- ▌ Best Practices · addyosmaniApply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".
- ▌ Accessibility · addyosmaniAudit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
- ▌ Performance · addyosmaniOptimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".
- ▌ SEO · addyosmaniOptimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".
- ▌ Constraint Driven Development · addyosmani bundleEstablishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.
- ▌ Idea Refine · addyosmani bundleTransforms vague ideas into structured, actionable concepts through guided divergent and convergent thinking, producing a markdown one-pager.
- ▌ Interview Me · addyosmaniExtracts the user's true intent through one-question-at-a-time interviews, surfacing hidden assumptions before any plan or code is written.
- ▌ Using Agent Skills · addyosmaniDiscovers and invokes agent skills by mapping tasks to development phases, with core operating behaviors for assumption surfacing, confusion management, and scope discipline.
- ▌ Code Simplification · addyosmaniSimplify code by reducing complexity while preserving exact behavior, making it easier to read, understand, modify, and debug.
- ▌ Context Engineering · addyosmaniOptimizes agent context setup by structuring rules, specs, source files, error output, and conversation history to improve output quality.
- ▌ Shipping And Launch · addyosmaniProvides a structured pre-launch checklist, staged rollout plan, monitoring setup, and rollback strategy for safe production deployments.
- ▌ CI CD And Automation · addyosmaniAutomates CI/CD pipeline setup, quality gates, test runners, and deployment strategies for GitHub Actions.
- ▌ Documentation And Adrs · addyosmaniRecords architectural decisions and documentation to capture the context, constraints, and trade-offs behind codebase choices.
- ▌ Security And Hardening · addyosmaniHardens code against vulnerabilities by applying threat modeling, OWASP Top 10 prevention patterns, and secure coding practices for web applications.
- ▌ Code Review And Quality · addyosmaniConducts multi-axis code review across correctness, readability, architecture, security, and performance before merging any change.
- ▌ Frontend UI Engineering · addyosmaniBuild production-quality user interfaces that are accessible, performant, and visually polished, with guidance on component architecture, state management, design system adherence, and accessibility.
- ▌ Spec Driven Development · addyosmaniCreates structured specifications before writing code to clarify requirements, surface assumptions, and define success criteria, reducing rework and miscommunication.
- ▌ Test Driven Development · addyosmaniDrive development with tests by writing a failing test before implementing code, and reproduce bugs with tests before fixing them.
- ▌ API And Interface Design · addyosmaniDesign stable, well-documented interfaces that are hard to misuse, including REST APIs, GraphQL schemas, module boundaries, and component props.
- ▌ Doubt Driven Development · addyosmaniSubjects every non-trivial decision to a fresh-context adversarial review before it stands, prioritizing correctness over speed for high-stakes or unfamiliar code.
- ▌ Performance Optimization · addyosmaniMeasures application performance first, identifies bottlenecks, and applies targeted fixes for frontend and backend systems.
- ▌ Deprecation And Migration · addyosmaniGuides the process of deprecating old systems, APIs, or features and migrating users to replacements, including decision frameworks, migration patterns, and removal strategies.
- ▌ Source Driven Development · addyosmaniGrounds every implementation decision in official documentation, ensuring authoritative, source-cited code free from outdated patterns.
- ▌ Incremental Implementation · addyosmaniDelivers changes incrementally by building in thin vertical slices, testing and verifying each piece before moving to the next.
- ▌ Git Workflow And Versioning · addyosmaniStructures git workflow practices for committing, branching, resolving conflicts, and organizing work across multiple parallel streams.
- ▌ Planning And Task Breakdown · addyosmaniDecompose work into small, verifiable tasks with explicit acceptance criteria, ordered by dependencies and sliced vertically for reliable implementation.
- ▌ Debugging And Error Recovery · addyosmaniProvides a structured triage process for debugging test failures, build errors, runtime bugs, and production incidents, including steps to reproduce, localize, fix, and guard against recurrence.
- ▌ Browser Testing With Devtools · addyosmaniTests and debugs web applications in real browsers using Chrome DevTools MCP, enabling DOM inspection, console error capture, network analysis, performance profiling, and visual verification with live runtime data.
- ▌ Observability And Instrumentation · addyosmaniAdds logging, metrics, tracing, and alerting to make production behavior visible and diagnosable.