Add comprehensive guides for various Epic Stack skills

[rubenpenap]

Summary

This PR adds 11 comprehensive skill guides (SKILL.md files) to .cursor/skills/ that document Epic Stack best practices and patterns. Each guide includes when to use it, patterns, conventions, common mistakes, and references.

Guides added:

• epic-auth: Authentication, sessions, OAuth, 2FA, and passkeys
• epic-caching: Caching with cachified, SQLite cache, and LRU cache
• epic-database: Prisma, SQLite, and LiteFS
• epic-deployment: Deployment with Fly.io, multi-region setup, and CI/CD
• epic-forms: Forms with Conform and validation with Zod
• epic-permissions: RBAC system and permissions
• epic-react-patterns: React patterns, performance optimization, and code quality
• epic-routing: Routing with React Router and react-router-auto-routes
• epic-security: Security practices including CSP, rate limiting, and session security
• epic-testing: Testing with Vitest and Playwright
• epic-ui-guidelines: UI/UX guidelines, accessibility, and component usage

These guides serve as comprehensive references to help developers understand and implement Epic Stack best practices and conventions.

Test Plan

No tests required because:

• Only documentation files are added (docs/skills/*/SKILL.md)
• No functional code changes
• No changes to business logic
• Does not affect application execution

Suggested verification steps:

1. Verify all 11 SKILL.md files exist in docs/skills/
2. Check markdown formatting is correct
3. Review that references to codebase files are accurate
4. Confirm Cursor can properly read these skills

Checklist

• Tests updated (N/A - documentation only)
• Docs updated (The added files are the new documentation)

Screenshots

N/A - Only documentation files were added.

[cr101]

Thank you for putting this together.

Do you think it would be better to place the skill folders inside a .github/skills/ directory at the root of the repository instead to ensure that AI agents (Cursor , Claude Code, VS Code Copilot, and other emerging agentic frameworks) can find and use the custom instructions?

[rubenpenap]

Hey Cris! Thanks for the suggestion, that makes a lot of sense

I initially placed the skills under .cursor mainly because the folder already existed and felt like a natural starting point. That said, I totally agree that .github/skills/ at the repo root is probably a better, more discoverable convention for agents across Cursor, Claude Code, Copilot, and others.

Happy to move them there if you think that’s the right call, no problem at all on my side. Let me know what you prefer and I’ll adjust it.

[cr101]

please place the skills in .github/skills/ Thank you

[kentcdodds]

Is there no standard place to put these? Will putting them in .github/skills/ work for cursor, vscode, claude code, etc?

[rubenpenap]

There’s no official standard yet for where AI agent rules/skills should live, but the emerging convention is to keep shared, tool-agnostic instructions in .github/ (e.g. .github/skills/ or .github/ai/). This makes them discoverable by multiple agents and avoids editor/vendor lock-in.

@kentcdodds Kent, could you confirm whether you’d prefer this to live under .github/ (e.g. .github/skills/), or if you’d suggest a better location? I’m happy to adjust it to match whatever you think works best.

[sergiodxa]

.github/skills doesn't seem tool-agnostic, that looks like what GH Copilot uses.

From what I understand, any SKILL.md in any part of the repo should work, right? You could have docs/skills/ folder even

[kentcdodds]

I like docs/skills personally

[rubenpenap]

The change is ready 👍

[kentcdodds]

Right now we delete the docs directory when initializing the project. I think we should probably not do that anymore in general, and we'll definitely not want to do that for these skills. Could you remove that bit in the init script?

[rubenpenap]

The change is ready 🔥

[kentcdodds]

Awesome! Let's see how it goes 🤞

[kentcdodds]

Thanks a ton for putting these together!