Skills are versioned playbooks I load into Cursor so recurring engineering decisions start from a proven pattern instead of a blank chat.
Explore skills I've written58 recurring decisions and workflows with downloadable playbooks — RAG, agents, evals, and infra.In my daily workflow
- Before a non-trivial task, I check whether a skill already exists for it — Next.js integration, SEO audit, GSAP animation, etc.
- I invoke the skill at the start of the session so the agent inherits constraints, file paths, and step order.
- When a workflow repeats twice with the same corrections, I capture the delta as a new skill or update the existing one.
- Skills that touch production get a short eval note: what must never break, and how to verify.
How it makes me work smarter
Without skills, every session re-teaches the same repo conventions. With them, I spend tokens on the actual problem — schema migration, UI polish, eval harness — not on re-explaining where admin actions live or how revalidation works. Skills also make handoffs cleaner: another agent (or future me) gets the same guardrails.
My setup
- Cursor agent skills in `.cursor/skills` and `.agents/skills`
- Project-specific skills co-located with the feature they govern
- SKILL.md format: when to use, workflow steps, and references
- Gallery topics cross-link to skills where a deeper playbook exists
On this portfolio
This site ships with skills for Next.js App Router integration, website optimization, and SEO — the same ones I use when extending the knowledge base, copilot graph, or admin CMS. Browse the Skills page for every playbook I've written, with full markdown and downloads.
