Sovereign Stack Recipes

Enforces standardized patterns for ShellPlate across testing, UI, API routing, and database interactions.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/ClawStackStudios/ClawChives --skill sovereign-stack-recipes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Sovereign Stack Recipes
Source: https://github.com/ClawStackStudios/ClawChives/tree/main/.crustagent/vibecheck/skills/stack-recipes
Command: npx skills add https://github.com/ClawStackStudios/ClawChives --skill sovereign-stack-recipes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized set of patterns and best practices for developing and maintaining the ShellPlate codebase, ensuring consistency and preventing sprawl.

Core Features & Use Cases

  • Testing: Enforces colocation of tests and specific testing frameworks (Vitest, supertest).
  • UI/Components: Dictates component architecture, styling with Tailwind CSS, and conditional class management.
  • API/Routing: Defines service layer separation, security middleware, and error handling patterns.
  • Database: Promotes raw SQL with prepared statements and outlines migration procedures.
  • Use Case: A new developer joins the team and needs to understand how to correctly implement a new feature, including writing tests, styling components, and defining API endpoints according to established standards.

Quick Start

Follow the testing patterns for Vitest and supertest to write unit and integration tests for your new feature.

Frequently Asked Questions about Sovereign Stack Recipes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain coding standards for Vitest and Tailwind CSS in a new project?

To maintain coding standards, you must colocate tests using Vitest and style components with Tailwind CSS, applying conditional class management and specific testing frameworks to ensure consistency across the codebase.

What's the best way to structure API routing and database interactions for a new feature?

The best way to structure API routing is to enforce service layer separation and security middleware, while database interactions should use raw SQL with prepared statements to maintain standardized development patterns.

Do I need to use raw SQL with prepared statements for database migrations?

Yes, you need to use raw SQL with prepared statements for database interactions, and you must follow the outlined migration procedures to ensure all new feature development adheres to codebase standards.

How does conditional class management work with Tailwind CSS components?

Conditional class management with Tailwind CSS works by dictating specific component architecture and styling utilities, ensuring UI components follow standardized patterns across all new feature development and refactoring.

When should I not use supertest for integration testing?

You should not bypass supertest when writing integration tests, because the established coding standards strictly require adherence to specific testing frameworks like Vitest and supertest to prevent codebase sprawl.