e2e
Generate and verify E2E tests for a feature. Explores live app, creates test plan, generates tests, runs and fixes until passing.
Installable AI agent skills for prompt engineering developer workflows in Claude Code, Cursor, and Windsurf.
This collection is built for teams that treat prompt engineering as an engineering discipline, not ad-hoc tweaking. It covers design patterns, evaluation loops, regression checks, and versioned workflows that keep agent behavior stable as products evolve. MCP may show up as a supporting integration in some setups, but the core is repeatable prompt quality and reliable execution in production.
Once the install path is clear, move into the solution, CLI, or editorial surface that best matches this collection. That keeps platform, framework, and operations demand narrowing into a more verifiable high-intent journey.
A practical bridge into command behavior, sync rules, and what operators should validate after installation.
CLI documentation proves the site has operational depth beyond discovery wrappers.
A scenario page for users who already know the workflow problem they need to solve.
High-intent solution pages are safer recovery surfaces than broad skill detail expansion.
Generate and verify E2E tests for a feature. Explores live app, creates test plan, generates tests, runs and fixes until passing.
Guides PRD, ADR, Design Doc, and Work Plan creation. Use when: planning features, writing specs, or creating technical documents.
TypeScript SDK patterns for Opik. Use when working in sdks/typescript.
Generate customizable widget plugins for the prompts.chat feed system
Do not reset back to the generic directory. Move sideways through these adjacent high-intent collections to narrow the shortlist toward the install path that best matches your team.
A high-trust collection that lets the site lead with official and strongly verified ecosystems instead of random long-tail repos.
Trusted-brand collections are the fastest way to rebuild authority after pruning.
A workflow-first collection that explains why related skills belong together and what job they solve.
Workflow collections add first-party judgment that generic skill detail pages struggle to communicate.
A platform-specific collection for one of the clearest demand clusters in the product ecosystem.
Platform collections let the site recover with narrower, more trustworthy topical intent.
A clean surface for editor-specific demand with explicit workflow intent.
Editor-specific demand should land on curated surfaces, not random repo coverage.
This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.
Use the collection to shortlist tools, then open the installation docs before browsing more repositories. That is the fastest path to install and validate a real setup.
Start with the official and trusted tools collection. It concentrates first-party and well-established ecosystem tools before you branch into broader workflow bundles.
Yes. Choose a skill from the collection, open the install guide, and run `npx killer-skills add owner/repo`. The CLI handles the native file format for supported IDEs.
These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.
A use-case page for users searching for repeatable automation patterns instead of one-off tools.
Workflow automation demand is easier to satisfy with curated intent clusters than with flat directory coverage.
A high-trust collection that lets the site lead with official and strongly verified ecosystems instead of random long-tail repos.
Trusted-brand collections are the fastest way to rebuild authority after pruning.