Explore skills
Showing 24811–24840 of 71536 skills
nexscope-ai/eCommerce-Skills
Stars: 1.4kClaude CodeCodexnexscope-ai/eCommerce-Skills
Stars: 1.4kClaude CodeCodexnexscope-ai/eCommerce-Skills
Stars: 1.4kClaude CodeCodexnexscope-ai/eCommerce-Skills
Stars: 1.4kClaude CodeCodexnexscope-ai/eCommerce-Skills
Stars: 1.4kClaude CodeCodexnexscope-ai/eCommerce-Skills
Stars: 1.4kClaude CodeCodexnexscope-ai/eCommerce-Skills
Stars: 1.4kClaude CodeCodexnexscope-ai/eCommerce-Skills
Stars: 1.4kClaude CodeCodexnexscope-ai/eCommerce-Skills
Stars: 1.4kClaude CodeCodexnexscope-ai/eCommerce-Skills
Stars: 1.4kClaude CodeCodexnexscope-ai/eCommerce-Skills
Stars: 1.4kClaude CodeCodexnexscope-ai/eCommerce-Skills
Stars: 1.4kClaude CodeCodexnexscope-ai/eCommerce-Skills
Stars: 1.4kClaude CodeCodexGenerates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexSafely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexAudits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexEnforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexExtracts and records architectural decisions from diffs, conversation context, and explicit choices. Supports automatic extraction from staged changes, deduplication against prior decisions, and persistent ADR-format logging with spec traceability. Use after a significant design or architecture choice, before committing a diff that embeds implicit decisions, or when the same question keeps resurfacing.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexGenerates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input). Seeds corpus from existing fixtures and runs initial pass. Use when implementing or changing a parser, or any code that ingests user input, webhook payloads, API responses, or file formats.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexAssesses production readiness or audits a codebase against its specs. Supports quick static mode, deep 17-dimension audit, or single-dimension focus. Use before a production launch, after a major refactor, when inheriting a codebase, or when someone asks how done the project is.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexCloses a large backlog of findings (a gap analysis, an audit, or 10+ bugs) in prioritized waves. Loops through triage, dependency analysis, parallel fix streams, a test gate, and re-audit until the target is met. Use after a gap analysis, audit, or review produces 10+ findings, or to burn down a large bug or tech-debt backlog.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexImplements snapshot/golden file tests with temporal normalization so tests don't break daily. Use when implementing tests that compare output against expected snapshots.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexAnalyzes large tasks for independent subtasks that can be safely parallelized. Produces a DAG-based dispatch plan with dependency ordering and maximum parallelism. Use when a task has 5+ subtasks touching independent files, or the user asks to speed up or parallelize the work.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexRuns the Implement→Review→Test→Fix cycle until the work is actually clean, with evidence. Use after any non-trivial implementation and before claiming it is done.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexCaptures reusable knowledge after work is done — learnings from feedback or failures, resolved bugs (symptom, root cause, prevention), and recurring code patterns — into the project's persistent memory file. Use after feedback, a non-trivial bug fix, a failed attempt, or the third repetition of a pattern.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexDocuments rollback procedures before making risky changes. Covers what's changing, verification steps, rollback procedures, and blast radius assessment. Use before database migrations, breaking API changes, infrastructure or DNS changes, large dependency upgrades, or any change where undo is not obvious.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexPerforms deployment with pre-flight checks, atomic replacement, post-deploy verification, provenance (proving the environment serves the exact commit you pushed), and automatic rollback. Use before any deployment to staging, preview, or production.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexStrips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails). Counts measurable tells first (keyword saturation, tricolons and anaphora, the "not X, it's Y" reflex, fragment-for-emphasis, bolded thesis lines, listicle-ization, signpost phrases, filler vocabulary, em-dashes, engineered-quotable closers), then applies a "doing work or reflex?" test to each instance so genuine voice survives. Use when asked to de-slop text or make it sound human, when text reads as machine-written, and as the final pass on prose the agent drafted.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexKeeps specification documents and code in agreement. Audit mode finds every divergence when an implementation is claimed complete; sync mode detects spec drift in staged changes and updates the spec after user approval, so each commit is a reconciled snapshot of spec, tests, and code. Use when an implementation is claimed complete against a spec, before committing changes that may drift from the spec, or after approving decisions that must flow back into it.
ash1794/vibe-engineering
Stars: 163Claude CodeCodexdgiot/dgiot
Stars: 4.8kClaude CodeCodex