mission-control-coding-standards

Enforce Mission Control coding standards for TypeScript modules using the src/modules pattern.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/ProfFroggo/froggo-mission-control --skill mission-control-coding-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mission-control-coding-standards
Source: https://github.com/ProfFroggo/froggo-mission-control/tree/main/.claude/skills/froggo-coding-standards
Command: npx skills add https://github.com/ProfFroggo/froggo-mission-control --skill mission-control-coding-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mission Control coding standards ensure a consistent, scalable codebase across modules, reducing onboarding time and bugs.

Core Features & Use Cases

  • TypeScript-first conventions (no JavaScript in src)
  • Module pattern and folder structure: src/modules/{name}/ with module.json, index.ts, and views
  • API Routes: consistent error handling using try/catch and standardized responses
  • Zustand Stores: persist middleware and UI state management practices
  • Styling: TailwindCSS usage and Tailwind-based design tokens
  • Database & ENV: consistent DB access patterns and ENV variable usage
  • Testing: Vitest-based unit tests and colocated test files

Quick Start

Review this skill's guidelines and start applying the TypeScript, module pattern, and testing conventions to all new and existing Mission Control modules.

Frequently Asked Questions about mission-control-coding-standards

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

FAQPage Schema
How do I enforce consistent TypeScript module structure across my codebase?

Apply Mission Control coding standards to enforce a consistent src/modules/{name}/ pattern with module.json, index.ts, and views, ensuring scalable TypeScript-first conventions across your codebase.

What's the best way to standardize API route error handling in TypeScript?

Standardize API route error handling using try/catch blocks and consistent response formats as outlined by Mission Control coding standards, applied to all TypeScript modules following the src/modules pattern.

How do I structure Zustand stores for state management consistency?

Structure Zustand stores using persist middleware and UI state management practices defined by Mission Control coding standards, applied to TypeScript modules within the src/modules directory structure.

Can I use JavaScript files in src when following these coding standards?

No, Mission Control coding standards enforce TypeScript-first conventions, requiring TypeScript exclusively within the src directory and prohibiting JavaScript files to maintain consistency.

How do I set up Vitest unit tests for TypeScript modules?

Write Vitest-based unit tests colocated with your source files inside the src/modules/{name}/ directory structure, following Mission Control coding standards for consistent testing practices.

Do I need TailwindCSS to follow these module coding standards?

Yes, Mission Control coding standards specify TailwindCSS usage and Tailwind-based design tokens for styling, ensuring consistent visual conventions across all TypeScript modules.