spiffy-oss / artguard

Rules encode your framework choices, folder layout and TypeScript style once. Every new chat starts already knowing how your project is built.

Enforce tests, formatting and typing at the prompt level and the agent's pull requests arrive shaped like your team's, not like a tutorial's.

It is plain text checked into .cursor/rules. No runtime, no account, no server - and the file doubles as documentation for humans.

The same rules files increasingly work in Windsurf, Copilot and Claude Code. A convention you write once pays off on every tool you try next.