global-rules

Enforce TypeScript and Python quality gates across Syntaris coding workflows.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/brianonieal/Syntaris --skill global-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: global-rules
Source: https://github.com/brianonieal/Syntaris/tree/main/.claude/skills/global-rules
Command: npx skills add https://github.com/brianonieal/Syntaris --skill global-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives every Syntaris session a consistent operating standard for code quality, communication, git workflow, and context management, reducing drift, regressions, and rework across turns.

Core Features & Use Cases

  • Coding Standards: Enforces TypeScript strict mode, Python type hints, Tailwind token usage, and project-specific technology bans.
  • Quality Gates: Requires tests before or alongside implementation, zero TypeScript errors, ruff clean Python, and mypy passing.
  • Workflow Discipline: Guides file-by-file edits, long-session memory updates, commit formatting, and safe push behavior.
  • Use Case: A developer opens a new Syntaris task and uses this Skill to verify conventions before editing code, running tests, and closing the gate.

Quick Start

Use the global-rules skill to review Syntaris conventions before making any code changes.

Frequently Asked Questions about global-rules

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

FAQPage Schema
How do I enforce coding standards and quality gates for TypeScript and Python in my project?

Coding standards are enforced by requiring TypeScript strict mode, Python type hints, zero TypeScript errors, ruff clean Python, and passing mypy checks before implementation is accepted.

What's the best way to manage context and memory updates during long coding sessions?

Context management for long sessions is handled through gate-based memory update behavior, guiding file-by-file edits and memory updates to reduce drift and regressions across turns.

How does git workflow discipline prevent bad commits and unsafe pushes?

Git workflow discipline enforces safe push behavior and commit formatting by requiring tests before or alongside implementation and verifying conventions before closing the development gate.

Can I use Tailwind tokens and ban specific technologies across my entire project?

Tailwind token usage and project-specific technology bans are applied universally across project-wide development tasks, code edits, and testing to maintain consistent operating standards.

Do I need tests written before implementation to pass quality gates?

Tests are required before or alongside implementation to pass quality gates, ensuring zero TypeScript errors, ruff clean Python, and mypy passing before any code changes are accepted.