Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/ai-agency/tonone/skills/prism-stack

prism-stack

Verified

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"

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)
    grep -r "\"react\"\|\"vue\"\|\"svelte\"\|\"next\"\|\"nuxt\"\|\"astro\"" package.json 2>/dev/null | head -5
    
  2. Search stack knowledge base:
    python3 -m prism_agent.uiux search --domain stacks --query "{stack_name}" --limit 5
    
  3. Cross-reference version — confirm guidelines match the detected major version
  4. Output framework-specific guidelines with code examples

Output format

┌─ Stack Guidelines — {stack_name} {version} ─────────────────────────┐
│ Category         │ Guideline                          │ Severity      │
├──────────────────┼────────────────────────────────────┼───────────────┤
│ {category}       │ {guideline}                        │ Critical      │
│ {category}       │ {guideline}                        │ High          │
│ {category}       │ {guideline}                        │ Medium        │
└──────────────────┴────────────────────────────────────┴───────────────┘

Code example:
{code_block}

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.

brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall