Agent skill · writing content · jeremylongshore
prism-stack
Use when asked for framework-specific best practices, implementation guidelines for React/Vue/Svelte/Next.js, or stack-specific patterns. Examples: "React best practices", "Vue component patterns", "Next.js performance
Why this skill is useful
Adds specific implementation guidelines and best practices for React, Vue, Svelte, and Next.js that the AI wouldn't reliably generate on its own.
What it needs
Requires python3 installed locally. About 1k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
prism-stack — Framework Best Practices Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. When to use User asks about framework-specific patterns, component architecture, or stack guidelines. Workflow 1. Detect stack from project files (package.json, imports, config files) 2. Search stack knowledge base: 3. Cross-reference version — confirm guidelines match the detected major version 4. Output framework-specific guidelines with code examples Output format Anti-patterns Never apply guidelines from the wrong framework version (e.g., Vue 2 patterns on Vue 3) Never mix framework idioms (e.g., React hooks inside Vue components) Never skip version detection — always confirm before outputting guidelines Never output framework-agnostic advice when stack-specific guidance is available Delivery If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/prism-stack