InnerVault

Library

86,689 resources from 11 public sources. 54 checked by hand; the rest are unreviewed.

Results

3,063 results Clear search and filters
  1. React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

    Stale Agent skill collections on GitHub, vercel-labs MIT1 note

    npx skills add vercel-labs/agent-skills
  2. Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

    Stale Agent skill collections on GitHub, vercel-labs 1 note

    npx skills add vercel-labs/agent-skills
  3. React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

    Stale Agent skill collections on GitHub, vercel-labs MIT1 note

    npx skills add vercel-labs/agent-skills
  4. React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

    Stale Agent skill collections on GitHub, vercel-labs MIT1 note

    npx skills add vercel-labs/agent-skills
  5. Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions…

    Stale Agent skill collections on GitHub, vercel-labs MIT1 note

    npx skills add vercel-labs/agent-skills
  6. Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".

    Stale Agent skill collections on GitHub, vercel-labs 1 note

    npx skills add vercel-labs/agent-skills
  7. Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core…

    Stale Agent skill collections on GitHub, vercel-labs 1 note

    npx skills add vercel-labs/agent-skills
  8. Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    Stale Agent skill collections on GitHub, vercel-labs 1 note

    npx skills add vercel-labs/agent-skills
  9. Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".

    Stale Agent skill collections on GitHub, vercel-labs 1 note

    npx skills add vercel-labs/agent-skills
  10. brainstorming

    Skills

    You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

    Stale Agent skill collections on GitHub, obra MIT1 note

  11. Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Stale Agent skill collections on GitHub, obra MIT1 note

  12. Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

    Stale Agent skill collections on GitHub, obra MIT1 note

  13. Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

    Stale Agent skill collections on GitHub, obra MIT1 note

  14. Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

    Stale Agent skill collections on GitHub, obra MIT1 note

  15. 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

    Stale Agent skill collections on GitHub, obra MIT1 note

  16. Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    Stale Agent skill collections on GitHub, obra MIT1 note

  17. Use when executing implementation plans with independent tasks in the current session

    Stale Agent skill collections on GitHub, obra MIT1 note

  18. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    Stale Agent skill collections on GitHub, obra MIT1 note

  19. Use when implementing any feature or bugfix, before writing implementation code

    Stale Agent skill collections on GitHub, obra MIT1 note

  20. Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

    Stale Agent skill collections on GitHub, obra MIT1 note

  21. Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

    Stale Agent skill collections on GitHub, obra MIT1 note

  22. Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

    Stale Agent skill collections on GitHub, obra MIT1 note

  23. writing-plans

    Skills

    Use when you have a spec or requirements for a multi-step task, before touching code

    Stale Agent skill collections on GitHub, obra MIT1 note

  24. Use when creating new skills, editing existing skills, or verifying skills work before deployment

    Stale Agent skill collections on GitHub, obra MIT1 note

Indexed entries aren't reviewed or tested by InnerVault. Details come straight from each source. Anything that can reach your accounts, files or browser can do damage, so read the source before you install it.