IDESKILL_RULE_STUDIO // TAILORED AI CONFIG GENERATOR
Interactive IDE Rule Builder & Customizer
Select your target AI editor, architectural guardrails, and quality constraints to generate zero-hallucination configuration files in real time.
Quick Stack Presets
1. Target AI IDE / Agent
Generates .cursorrules — Generates .cursorrules for codebase indexing and inline composer rules.
2. Architectural & Security Guardrails
3. Add Custom Directives
.cursorrules
5 rules active
# Cursor AI System Rules & Architectural Guardrails
# Generated via ideSkill.com Customizer
# Target Environment: Cursor
# Config File: .cursorrules
## Core Directives
### Strict Server/Client Boundaries
- Always default to React Server Components (RSC) unless interactivity (useState, useEffect) is strictly required.
- Never import server-only utilities (database clients, admin keys, env secrets) into client components.
- Pass serializable data only across Server/Client component boundaries.
### Strict Runtime Zod Validation
- Validate 100% of incoming API route handler payloads using explicit Zod schemas.
- Never use "any" type or unvalidated casts (`as Type`). Prefer type narrowing and Zod inference.
- Return standard 422 JSON errors with flattened issues when Zod parsing fails.
### Design System Semantic Tokens
- Use designated Tailwind semantic color tokens (bg-surface, text-primary, border-border-line) instead of arbitrary hex colors.
- Maintain dark-mode default contrast ratios conforming to WCAG AA.
### Red-Green-Refactor TDD Protocol
- Follow strict Test-Driven Development (TDD): write unit tests (failing) before writing implementation.
- Maintain minimum 90% branch coverage on newly created utility functions and endpoints.
- Follow Arrange-Act-Assert (AAA) pattern explicitly in all test files.
### ContextZen Memory Architecture
- Adhere strictly to ContextZen memory files: read context/project-overview.md, architecture.md, and code-standards.md before writing code.
- Keep context/progress-tracker.md synchronized after each completed milestone.
## Verification Protocol
- Execute all automated unit tests and type-checks before final task completion.
- Ensure no code regressions or unhandled edge cases are introduced.