Loading...
Loading...
Found 1,140 Skills
Evaluate product bets and shape pitches using Shape Up's appetite model and Bezos's Type 1/Type 2 decision framework. Use when asked to assess a product bet, evaluate initiative risk, decide resource allocation, or shape a pitch for a new feature or project.
Prioritize features and backlog items using RICE scoring and Linear's enablers vs blockers lens. Use when asked to rank features, prioritize a backlog, decide what to build next, or evaluate feature requests against each other.
Apply preferred toolchain and technology stack defaults: pnpm, Next.js, TypeScript, Convex, Vercel, Tailwind, shadcn/ui, Zustand, TanStack, Vitest. Use when setting up new projects, choosing dependencies, discussing stack decisions, or evaluating alternatives.
Run SEO and GEO audits on URLs covering technical SEO, content quality, E-E-A-T signals, and AI citation readiness. Use when evaluating search performance or diagnosing ranking issues.
Audit and assess a codebase for programmatic SEO readiness at 1000+ page scale. Use when starting a pSEO project, evaluating an existing codebase for pSEO gaps, or when the user asks to audit, assess, or review their site for programmatic SEO scalability.
Create and maintain a control-system metalayer for autonomous code-agent development in any repository. Use when you need explicit control primitives (setpoints, sensors, controller policy, actuators, feedback loop, stability and entropy controls), repo command/rule governance, and a scalable folder topology that lets agents operate safely and keep improving over time.
Use this skill to build, run, deploy, evaluate, and troubleshoot Go agents with Google's Agent Development Kit (`google.golang.org/adk`), including llmagent config, tools/integrations, callbacks/plugins, sessions/state/memory, workflows, streaming, MCP/A2A, and runtime/deployment patterns.
Software design principles and patterns. This skill should be used when making architectural decisions, designing classes or modules, or evaluating code structure. Use proactively when discussing SOLID principles, coupling, cohesion, connascence, refactoring structure, class design, module boundaries, dependency injection, or the Four Rules of Simple Design. (user)
Use when ANY runtime debugging is needed — setting breakpoints, inspecting variables, evaluating expressions, analyzing threads, or reproducing crashes interactively with LLDB
Use when starting a Next.js Pages Router to App Router migration, evaluating migration feasibility, or auditing codebase readiness. Run this BEFORE any other migration skill.
Use when evaluating AI tools and agentic workflows against workflow gaps, when conducting quarterly landscape scans, or when assessing integration feasibility of new tools for startup workflows.
Knowledge base for designing, reviewing, and linting agentic AI infrastructure. Use when: (1) designing a new agentic system and need to choose patterns, (2) reviewing an existing agentic architecture ADR or design doc for gaps/risks, (3) applying the lint script to an ADR markdown file to get structured findings, (4) looking up a specific agentic pattern (prompt chaining, routing, parallelization, reflection, tool use, planning, multi-agent collaboration, memory management, learning/adaptation, MCP, goal setting, exception handling, HITL, RAG, A2A, resource optimization, reasoning techniques, guardrails, evaluation, prioritization, exploration/discovery). All rules and guidance are grounded in the PDF "Agentic Design Patterns" (482 pages).