Instruction file imported from pointdotcom-marketing/geo-ip-lp (.cursor/rules/02-standards.mdc). Copyright stays with the author.

Code Standards

Name: 02-standards
Author: pointdotcom-marketing

Quality

Clear, idiomatic, maintainable; descriptive names; strict typing.
Small, composable functions; avoid over-engineering.
Focused diffs; follow existing patterns; fix linter warnings.

Safety (scale with risk)

Always: Handle errors, null/undefined; validate inputs.
User-facing/APIs: Validate schemas (Zod/Yup), sanitize output.
Auth/payments: Add XSS/CSRF/injection guards, secrets hygiene.
Clean up I/O resources (files, sockets, connections).

Testing (scale with scope)

Refactors/utilities: Add unit tests covering happy + edge cases.
New features/APIs: Add integration tests; mock externals.
Bug fixes: Add regression test.
Simple UI tweaks: Manual verification OK; skip tests if trivial.
Keep tests fast & deterministic (prefer bunx/bun).

Example

Fix typo in button text → no test needed.
Add API endpoint → validate input schema, add unit + integration tests, handle timeouts.

{ "ocm": "1", "id": "pointdotcom-marketing-geo-ip-lp-02-standards-rule", "kind": "skill", "name": "02-standards", "description": "Code standards—quality, safety, testing; scale rigor with task complexity.", "publisher": "pointdotcom-marketing", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github-cursor-rules" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Code standards—quality, safety, testing; scale rigor with task complexity." ], "primary": false, "metadata": { "source": { "provider": "github-cursor-rules", "repository": "https://github.com/pointdotcom-marketing/geo-ip-lp", "path": ".cursor/rules/02-standards.mdc", "ref": "f28376570dacbd3872c84f18376ea053ec9400a6", "url": "https://github.com/pointdotcom-marketing/geo-ip-lp/blob/f28376570dacbd3872c84f18376ea053ec9400a6/.cursor/rules/02-standards.mdc", "key": "pointdotcom-marketing/geo-ip-lp/.cursor/rules/02-standards.mdc" } }, "instructions": "# Code Standards\n\n## Quality\n- Clear, idiomatic, maintainable; descriptive names; **strict typing**.\n- Small, composable functions; avoid over-engineering.\n- Focused diffs; follow existing patterns; fix linter warnings.\n\n## Safety (scale with risk)\n- **Always:** Handle errors, null/undefined; validate inputs.\n- **User-facing/APIs:** Validate schemas (Zod/Yup), sanitize output.\n- **Auth/payments:** Add XSS/CSRF/injection guards, secrets hygiene.\n- Clean up I/O resources (files, sockets, connections).\n\n## Testing (scale with scope)\n- **Refactors/utilities:** Add unit tests covering happy + edge ", "cost": { "context_tokens": 244 } }

02-standards

About

Code Standards

Quality

Safety (scale with risk)

Testing (scale with scope)

Example

Use it

Manifest

Reviews