Nextjs React Tailwind Assistant — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Nextjs React Tailwind Assistant (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Your comprehensive AI companion for building modern Next.js applications with React and Tailwind CSS.
Abstracted from 11 professional Next.js templates:
Visual Effects: Gradients, glows, animations, bento grids, decorative SVGs Component Library: Buttons, cards, badges, inputs, avatars, alerts, tooltips Color Systems: 8 palette strategies (Professional, SaaS, Bold, Minimal, Semantic, Dark Mode) Typography: Font systems, type scales, responsive patterns Layouts: App headers, auth pages, sidebars, overlay navigation Pages: Hero sections, pricing tables, blog layouts
All patterns include accessibility, performance, and dark mode support.
npx @smithery/cli install @username/nextjs-react-tailwind-assistant --client claudegit clone https://github.com/CaullenOmdahl/Nextjs-React-Tailwind-Assistant.git
cd Nextjs-React-Tailwind-Assistantnpm installnpm run buildThis will:
.smithery/index.cjs (1.67 MB).smithery/content/ (5.3 MB)npm run dev # Start development server with hot reload
npm run inspector # Launch MCP inspector for testing
npm run build # Build production bundle
npm run watch # TypeScript watch modesearch_nextjs_docs - Search Next.js documentationsearch_tailwind_docs - Search Tailwind CSS utilities and conceptsget_nextjs_full_docs - Complete Next.js documentation (large)get_tailwind_full_docs - Complete Tailwind documentation (large)get_catalyst_component - Retrieve production-ready componentslist_catalyst_components - Browse available componentslist_patterns - Browse design patternsget_pattern - Get detailed pattern implementationscontent/
├── components/
│ └── catalyst/ # 27 TypeScript React components
├── docs/
│ ├── nextjs/ # Complete Next.js 15+ docs (2.9 MB)
│ └── tailwind/ # Complete Tailwind CSS docs (2.1 MB)
├── patterns/
│ ├── features/ # 6 feature patterns
│ ├── layouts/ # 4 layout patterns
│ └── pages/ # 3 page patterns
└── content-summary.json # Catalog of all contentThe server requires the content/ directory (5.3 MB) to be available at runtime. Smithery deploys from your GitHub repository and includes files listed in package.json "files" array.
Deployment Process:
git add content/
git commit -m "Add documentation and pattern content"git push origin mainnpm installnpm run build (which copies content to .smithery/content/)Note: The server uses process.cwd() + '/content' to locate files. When deployed to Smithery, the content directory from your repository should be available in the working directory.
If you get a 500 error on Smithery:
git ls-files content/ | wc -l # Should show files
du -sh content/ # Should show ~5.3M"files": ["dist", "content", "icon.png", "icon.svg"]npm run build
ls -la .smithery/content/ # Should show content directorycd .smithery && node index.cjs
# Should start without errors"type": "module" in package.json).js extensions for TypeScript files-_. only)../ traversalMIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.