React product UI
typescript.mdcreact.mdctailwind.mdcConstrain types, component boundaries, and styling expression together.
Rule Atlas / Adoption Paths / Generated Catalog
The site first explains what each `.mdc` rule is for, which stack it supports, and how rules combine. Architecture, data flow, and references become evidence layers rather than the homepage identity.
Each family represents an adoption context: quality, languages, frameworks, mobile apps, backend services, and engineering infrastructure.
clean-codecodequalitygitflowLanguagesLanguage-level constraints for Python, Java, Go, TypeScript, C++, C#, PHP, and Ruby.typescriptpythongoFrontend frameworksModern frontend practice for React, Vue, Svelte, Next.js, Tailwind, and Medusa.reactvuetailwindBackend servicesAPI, layering, and server-side constraints for Node Express, Spring, and FastAPI.node-expressspringfastapiMobile appsDevice and cross-platform rules for Android, iOS, WeChat Mini Program, and NativeScript.androidioswechat-miniprogramEngineering infrastructureDatabase and Docker rules for data, containers, and delivery foundations.databasedockerA file can match language, framework, and engineering rules at the same time. Readers should understand that model before copying rules.
typescript.mdcreact.mdctailwind.mdcConstrain types, component boundaries, and styling expression together.
python.mdcfastapi.mdcdocker.mdcConstrain language style, API shape, and containerized delivery together.
android.mdcgitflow.mdccodequality.mdcConstrain platform code, collaboration flow, and quality baseline together.
Rule Catalog
Proof layer
Root `.mdc` files define the real public surface.
Validation and catalog generation scripts convert curated rules into runtime assets and localized shells.
Homepage, academy, architecture, and research each serve a distinct explanatory role.
Further reading