design-guide

Codify architectural guidelines for the 2-Tier and Mega-Agent framework.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/JuelHossain/kalshi-trading-team --skill design-guide-juelhossain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-guide
Source: https://github.com/JuelHossain/kalshi-trading-team/tree/main/ai-env/skills/design-guide
Command: npx skills add https://github.com/JuelHossain/kalshi-trading-team --skill design-guide-juelhossain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies architectural guidelines and coding standards needed to maintain a cohesive 2-Tier Sentient Alpha system and its Mega-Agent pillars across all modules.

Core Features & Use Cases

  • 2-Tier architecture: Enables direct frontend-engine communication with clear separation of concerns.
  • Mega-Agent pillars: SOUL, SENSES, BRAIN, HAND guiding autonomy, safety, and execution.
  • Documentation-driven standards: Folder structures, naming conventions, and safety protocols (Ragnarok Protocol, Autopilot Pulse).
  • Consistent tooling patterns: Frontend patterns (React + Vite, Zustand), Engine patterns (asyncio, aiohttp), and shared typing.

Quick Start

Review repository modules and ensure new components follow 2-Tier structure and Mega-Agent pillars.

Frequently Asked Questions about design-guide

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

FAQPage Schema
How do I enforce 2-Tier architecture and coding standards across frontend and engine modules?

Enforce 2-Tier architecture by codifying folder structures, naming conventions, and safety protocols that align frontend components with engine modules to maintain cohesive system design.

What is the Mega-Agent framework and how does it guide development safety?

The Mega-Agent framework uses SOUL, SENSES, BRAIN, and HAND pillars to guide autonomy and execution, integrating safety patterns like the Ragnarok Protocol and Autopilot Pulse for secure development.

How do I structure a React and Vite frontend with an asyncio engine using design patterns?

Structure React and Vite frontends with Zustand state management while aligning asyncio and aiohttp engine modules using shared typing and consistent tooling patterns to ensure direct communication.

Does this coding standards skill work with Python asyncio and aiohttp backend environments?

Yes, it applies to Python environments by outlining engine patterns for asyncio and aiohttp, ensuring async backend modules follow the 2-Tier structure and Mega-Agent safety protocols.

What's the best way to standardize folder structures for frontend and shared code?

Standardize folder structures by applying documentation-driven guidelines that enforce clear separation of concerns across frontend, engine, and shared code for development, review, and onboarding.

When do I need the Ragnarok Protocol and Autopilot Pulse safety patterns?

Apply the Ragnarok Protocol and Autopilot Pulse safety patterns when enforcing compliance and safety protocols across the 2-Tier architecture to protect autonomous agent execution and review processes.