Hey everyone, If you’ve ever used AI coding assistants for full-stack work, you’ve probably dealt with this frustration: AI spits out a backend endpoint, but the frontend types don’t match, routes break, or config gets out of sync. I built shaft-rules to fix exactly that. It’s a stack-agnostic ruleset (works with Cursor, Claude Code/Dev, Aider, Continue, Cline, etc.) that strictly enforces this 5-step cycle for every feature: sync-contract (API contract as single source of truth) backend-impl frontend-impl (with auto-generated types) config-sync validate-harmony (end-to-end checks) Super quick install (1 min), customizable, README has pt-br too. Quick example prompt: “Implement user login feature using shaft-rules full cycle: contract → backend (NestJS) → frontend (Next.js + Zod) → config → validation” Outcome: consistent layers, fewer manual fixes, cleaner PRs. I made this because I was tired of fixing AI-generated mess — hope it helps others too. Anyone using similar rulesets? What do you think is missing? How do you handle backend/frontend desync with AI tools? Repo: https://github.com/razectp/shaft-rules Open to feedback/ideas — if you try it, feel free to open issues! submitted by /u/Fit_Cauliflower2535
Originally posted by u/Fit_Cauliflower2535 on r/ClaudeCode