skills.rest
fmbp1981-hash
fmbp1981-hashCOMMUNITY
Explore all skills by this author →
GitHub

dev-standards

Enforce IntelliX development standards for TypeScript, Git workflow, and component structure.

Updated Dec 13, 2025
Search Tags:#state management#TypeScript#development standards#Git#coding guidelines#security best practices#IntelliX
One-click install
npx skills add https://github.com/fmbp1981-hash/cavendish-gig --skill dev-standards-fmbp1981-hash
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-standards
Source: https://github.com/fmbp1981-hash/cavendish-gig/tree/main/.claude/plugins/intellix-plugin/skills/dev-standards
Command: npx skills add https://github.com/fmbp1981-hash/cavendish-gig --skill dev-standards-fmbp1981-hash

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tanstack/react-query, react-query-devtools, zustand, react-hook-form, zod, next/cache, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures adherence to IntelliX development standards, providing guidelines for coding, versioning, TypeScript usage, naming conventions, and more to maintain code quality and consistency.

Core Features & Use Cases

  • Coding Discipline: Enforces principles like 'Think Before Coding', 'Simplicity First', 'Surgical Changes', and 'Goal-Driven Execution'.
  • Git Workflow: Defines best practices for version control, including trunk-based development, atomic commits, save-point pattern, and pre-commit checks.
  • TypeScript Usage: Enforces strict TypeScript usage with examples and configurations.
  • Naming Conventions: Provides clear guidelines for file naming, component naming, hooks, functions, types, interfaces, and constants.
  • Component Structure: Specifies the required structure of components for maintainability.
  • Server vs Client Components: Distinguishes between server and client components based on functionality.
  • Commits: Defines conventional commit standards for clarity and consistency.
  • Server Actions vs Route Handlers: Explains when to use server actions and route handlers.
  • Data Fetching: Integrates TanStack Query for efficient data fetching and caching.
  • State Management: Outlines best practices for state management using TanStack Query, useState, and Zustand.
  • Form Handling: Demonstrates the use of React Hook Form and Zod for form handling.
  • Security Best Practices: Enforces security best practices for multi-tenant SaaS applications, including data filtering, credential management, and LLM guardrails.
  • TypeScript Configuration: Provides a strict TypeScript configuration for the project.

Quick Start

Activate the dev-standards skill to enforce coding standards, version control practices, and TypeScript configurations for your IntelliX development projects.

Frequently Asked Questions about dev-standards

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

FAQPage Schema
How do I enforce TypeScript strict mode and development standards in a React project?▼

To enforce TypeScript strict mode and development standards, apply a strict TypeScript configuration alongside coding discipline guidelines for naming conventions, component structure, and surgical changes. This ensures type safety and codebase maintainability.

What's the best way to manage state and data fetching using TanStack Query and Zustand?▼

The best way to manage state and data fetching with TanStack Query and Zustand involves using TanStack Query for server-state data fetching and caching, while leveraging Zustand for client-side state management to maintain strict server-client separation.

How do I structure form validation with React Hook Form and Zod in TypeScript?▼

To structure form validation with React Hook Form and Zod in TypeScript, integrate Zod schemas for runtime type validation directly within React Hook Form's resolver. This guarantees parsed data matches your strict TypeScript definitions.

When should I use Next.js server actions versus route handlers for data fetching?▼

Use Next.js server actions for mutations or data submissions tightly coupled to the UI, and route handlers for building external API endpoints. This distinction maintains clear component structure and server-client boundaries.

Do I need pre-commit checks and atomic commits for a trunk-based Git workflow?▼

Yes, trunk-based Git workflows require atomic commits and pre-commit checks to maintain version control stability. These save-point patterns ensure surgical changes are verified before integration, preventing broken builds in the main branch.

What security best practices should I follow for multi-tenant SaaS applications?▼

Security best practices for multi-tenant SaaS applications require strict data filtering, secure credential management, and implementing LLM guardrails. These measures prevent cross-tenant data leaks and protect external AI model integrations.

Related Skills

Explore More Software Engineering Skills→
alinaqialinaqi
705

react-web

Develop React web apps with TypeScript, hooks, React Query, and Zustand using test-first methods.

Community
Advanced
marcd35marcd35

git-commit

Enforce atomic conventional git commits with automated pre-commit checks.

Community
Intermediate
AgentiveCityAgentiveCity
2

nextjs-data-fetching-and-caching

Configure data fetching and caching in Next.js App Router applications.

Official
Intermediate
shynlee04shynlee04

Global Coding Style

Enforce global coding style standards across TypeScript, JavaScript, Python, and Ruby.

Community
Basic