Explore skills
Showing 29641–29670 of 77079 skills
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
mouadja02/skills
Stars: 13Claude CodeCodexRefactors code surgically without changing behavior: extract functions, rename, break up large functions and classes, reduce complexity, and remove code smells. Use when code is hard to understand or extend, or the user asks to clean up, refactor, or improve existing code.
mouadja02/skills
Stars: 13Claude CodeCodexProduces a concrete plan before a multi-file refactor: scope, sequence, risks, and verification for each step. Use when the user asks to plan, sequence, or safely execute a refactor across several files, before any code changes are made.
mouadja02/skills
Stars: 13Claude CodeCodexUse when completing tasks, implementing major features, or before merging to verify work meets requirements
mouadja02/skills
Stars: 13Claude CodeCodexInteractive onboarding that learns your communication style, audiences, and data sources to configure personalized status briefings. Paste in examples of updates you already write, answer a few questions, and roundup calibrates itself to your workflow. Use the first time Roundup is used, or to recalibrate its style and sources.
mouadja02/skills
Stars: 13Claude CodeCodexUse when designing new API endpoints, defining module boundaries or contracts between teams, creating component prop interfaces, or changing an existing public interface. Covers naming, versioning, error shapes, and designing surfaces that are hard to misuse.
mouadja02/skills
Stars: 13Claude CodeCodexTests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
mouadja02/skills
Stars: 13Claude CodeCodexUse when setting up a project's CI pipeline, adding or changing automated checks, configuring deployment pipelines, or debugging CI failures. Covers quality gates, pipeline stages, and what to verify automatically on every change.
mouadja02/skills
Stars: 13Claude CodeCodexConducts a multi-axis code review (correctness, readability, architecture, security, performance) before merging. Use before merging any change, after finishing a feature or bug fix, when reviewing code another agent or person wrote, or when asked to review a diff or pull request.
mouadja02/skills
Stars: 13Claude CodeCodexUse when working code feels heavier than it needs to be — deeply nested logic, long functions, unclear names, duplication after a merge, or a review that flagged complexity. Reduces complexity while preserving behavior exactly. Not for code you do not yet understand, or code you are about to rewrite.
mouadja02/skills
Stars: 13Claude CodeCodexEstablishes 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.
mouadja02/skills
Stars: 13Claude CodeCodexUse when starting a coding session, setting up a project for AI-assisted development, switching between parts of a codebase, or when agent output quality degrades — hallucinated APIs, wrong patterns, ignored project conventions. Structures what the agent loads and when.
mouadja02/skills
Stars: 13Claude CodeCodexGuides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
mouadja02/skills
Stars: 13Claude CodeCodexUse when replacing an old system, API, or library, sunsetting a feature, consolidating duplicate implementations, removing dead code nobody owns, or deciding whether to maintain a legacy system versus migrate off it. Covers deprecation timelines, migration paths, and safe removal.
mouadja02/skills
Stars: 13Claude CodeCodexUse when making an architectural decision, choosing between competing approaches, adding or changing a public API, shipping a user-facing behavior change, or repeatedly explaining the same thing. Captures the why — context, constraints, alternatives — as ADRs and project docs. Not for restating obvious code.
mouadja02/skills
Stars: 13Claude CodeCodexSubjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production auth, security-sensitive logic, a high-stakes migration, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.
mouadja02/skills
Stars: 13Claude CodeCodexUse when building or modifying user-facing interfaces: new components and pages, responsive layouts, interactivity and state management, or fixing visual and UX issues. Covers component architecture, styling, accessibility, and state boundaries.
mouadja02/skills
Stars: 13Claude CodeCodexUse on every code change — commit structure, branching, history hygiene, and versioning. Apply when committing work, opening or splitting a branch, writing commit messages, cutting a release, or recovering from a bad history state.
mouadja02/skills
Stars: 13Claude CodeCodexReverse-engineers and debugs macOS and iOS binaries with Hopper Disassembler and LLDB: ObjC/Swift symbols, dyld loading, framework internals, and crash investigation from disassembly. Use when private API behavior or a runtime crash needs to be understood at the binary level.
mouadja02/skills
Stars: 13Claude CodeCodexUse when refining a vague idea through divergent expansion, convergent focus, and assumption stress-testing before planning or implementation.
mouadja02/skills
Stars: 13Claude CodeCodexDelivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
mouadja02/skills
Stars: 13Claude CodeCodexProfiles macOS and iOS apps with Instruments and xctrace: choosing templates such as Time Profiler, launching binaries with arguments, recording traces, and exporting results. Use when a Mac or iOS app needs CPU, memory, or responsiveness profiling.
mouadja02/skills
Stars: 13Claude CodeCodexExtracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
mouadja02/skills
Stars: 13Claude CodeCodexBehavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
mouadja02/skills
Stars: 13Claude CodeCodexProfiles native macOS and iOS apps from the command line only: xctrace recording, Time Profiler samples, hotspot ranking, and symbolication with atos and vmmap. Use for headless or SSH-based performance analysis without opening the Instruments GUI.
mouadja02/skills
Stars: 13Claude CodeCodexInstruments 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.
mouadja02/skills
Stars: 13Claude CodeCodexUse when performance budgets or SLAs exist, users or monitoring report slowness, Core Web Vitals fall below thresholds, a change may have caused a regression, or a feature handles large datasets or high traffic. Measure-first workflow: profile, fix the proven bottleneck, re-measure. Not for speculative optimization.
mouadja02/skills
Stars: 13Claude CodeCodexUse when a task feels too large or vague to start, a spec needs breaking into implementable units, work must be parallelized across agents or sessions, or implementation order is unclear. Produces ordered tasks with acceptance criteria. Skip when the spec already contains well-defined tasks.
mouadja02/skills
Stars: 13Claude CodeCodexUse when building anything that accepts user input, implementing authentication or authorization, storing or transmitting sensitive data, integrating external APIs, or adding file uploads, webhooks, or callbacks. Covers input validation, secrets, authz checks, and PII and payment handling.
mouadja02/skills
Stars: 13Claude CodeCodexUse when deploying to production, releasing a significant user-facing change, migrating data or infrastructure, or opening a beta. Covers the pre-launch checklist, staged rollout, monitoring, and rollback planning for deployments that carry risk.
mouadja02/skills
Stars: 13Claude CodeCodex