xoai/stack-nextjs-fullstack
tools/sage-claude-plugin/skills/stack-nextjs-fullstack/SKILL.md
Integration patterns for Next.js + Tailwind CSS + Prisma + Auth.js — the seams between frameworks
$ install --global
skillsauthnpx skillsauth add xoai/sage stack-nextjs-fullstackInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 26, 2026, 2:10 AM94.6s1 file scanned
SKILL.md
- name:
- stack-nextjs-fullstack
- description:
- Integration patterns for Next.js + Tailwind CSS + Prisma + Auth.js — the seams between frameworks
- version:
- 1.0.0
- type:
- composite
- layer:
- stack
- sage:
- >=1.0.0
- detected:
- [next, tailwindcss, prisma]
- tags:
- [next,tailwindcss,prisma]
stack-nextjs-fullstack
Layer 3 — Stack Composition
Integration patterns for the most common Next.js fullstack combination: Next.js App Router + Tailwind CSS + Prisma ORM + Auth.js.
Philosophy
Individual framework docs tell you how each tool works in isolation. They don't tell you how they work TOGETHER. Where does the Prisma client go in a Next.js project? How does Auth.js middleware interact with App Router layouts? What happens when Tailwind's utility classes meet server components?
These integration points — the seams between frameworks — are where most bugs live. Each framework team documents their own tool. Nobody documents the gaps between tools. That's what this pack does.
What's Included
| Type | Files | Coverage | |------|-------|----------| | Integration patterns | 4 | Prisma + Next.js, Auth.js + Next.js, Tailwind + Next.js, Full-stack project structure | | Anti-patterns | 3 | Prisma client instantiation, auth in wrong layer, Tailwind in server components | | Constitution | 1 | 5 stack integration principles |
Prerequisites
This pack requires web, react, and nextjs to be
installed. It activates when the codebase-scan detects Next.js, Tailwind CSS,
and Prisma in the project dependencies.
What This Pack Does NOT Cover
- How Prisma works (queries, migrations, schema) — that's Prisma's docs
- How Auth.js providers work (OAuth, credentials) — that's Auth.js's docs
- How Tailwind utility classes work — that's Tailwind's docs
- This pack covers the integration BETWEEN them, not each one individually
Related Skills
xoai/sage-self-learning
tools
VerifiedTrustedCommunity
Captures agent mistakes, corrections, and discovered gotchas so they are not repeated. Use when: (1) a command or operation fails unexpectedly, (2) the user corrects the agent, (3) the agent discovers non-obvious behavior through debugging, (4) an API or tool behaves differently than expected, (5) a better approach is found for a recurring task. Also searches past learnings before starting tasks to avoid known pitfalls. Activate alongside the sage-memory skill — they share the same MCP backend but serve different purposes (sage-memory = codebase knowledge, sage-self-learning = agent mistakes and gotchas).
17SKILL.mdUpdated May 20, 2026
xoai/sage-ontology
development
VerifiedTrustedCommunity
Typed knowledge graph stored in sage-memory. Use when creating or querying structured entities (Person, Project, Task, Event, Document), linking related objects, checking dependencies, planning multi-step actions as graph transformations, or when skills need to share structured state. Trigger on "remember that X is Y", "what do I know about", "link X to Y", "show dependencies", "what blocks X", entity CRUD, cross-skill data access, or any request involving structured relationships between things.
17SKILL.mdUpdated May 20, 2026
xoai/sage-memory
tools
VerifiedTrustedCommunity
Integrates sage-memory into Sage workflows. Teaches the agent when to remember (store findings during work), when to recall (search memory at session start and task start), and how to learn (structured knowledge capture via sage learn). Use when the user mentions memory, remember, recall, learn, capture knowledge, onboard to codebase, or when starting any session where sage-memory MCP tools are available.
17SKILL.mdUpdated May 20, 2026
xoai/sage-self-learning
tools
VerifiedTrustedCommunity
Captures agent mistakes, corrections, and discovered gotchas so they are not repeated. Use when: (1) a command or operation fails unexpectedly, (2) the user corrects the agent, (3) the agent discovers non-obvious behavior through debugging, (4) an API or tool behaves differently than expected, (5) a better approach is found for a recurring task. Also searches past learnings before starting tasks to avoid known pitfalls. Activate alongside the sage-memory skill — they share the same MCP backend but serve different purposes (sage-memory = codebase knowledge, sage-self-learning = agent mistakes and gotchas).
17SKILL.mdUpdated May 20, 2026