core-development

core-development is a cursor rule for Cursor from boparaiamrit/skills-by-amrit. It costs 561 tokens per session, scanned A, original, MIT.

A set of coding rules applied whenever code is created or changed. The rules cover types, error handling, logging, configuration, function size, naming, comments, and duplicated code.

In plain words
What is it for?
Guiding code generation and edits across TypeScript and Python projects, including type choices, logging, configuration, validation, error paths, and code structure.
Why use it?
It gives development work consistent quality and safety checks, reducing silent failures, hardcoded settings, weak validation, and difficult-to-maintain code.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Guiding code generation and edits across TypeScript and Python projects, including type…

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/boparaiamrit/skills-by-amrit/core-development
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/boparaiamrit/skills-by-amrit

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for core-development

README.md
[![agentmods](https://agentmods.dev/badge/rules/boparaiamrit/skills-by-amrit/core-development.svg)](https://agentmods.dev/rules/boparaiamrit/skills-by-amrit/core-development)
Your own site
<a href="https://agentmods.dev/rules/boparaiamrit/skills-by-amrit/core-development"><img src="https://agentmods.dev/badge/rules/boparaiamrit/skills-by-amrit/core-development.svg" alt="Measured on agentmods" height="20"></a>
Per session 561 This file is loaded in full into every session.
When invoked 561 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00561 $0.00561
Opus 5 $0.00280 $0.00280
Sonnet 5 $0.00112 $0.00112
Haiku 4.5 $0.00056 $0.00056

Measured 7d ago against content hash 6f8273002351, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

core-development scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

cursor-rules/core-development.mdc · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Core Development Rules

Code Quality Standards

ALWAYS

  • Type safety — Use proper types. No any in TypeScript without explicit justification. Use type hints in Python.
  • Error handling — Handle all error paths explicitly. No empty catch blocks. No silent failures.
  • Logging — Use the project's logging framework. Never use console.log for production code (use logger.info, logger.error, etc.).
  • Configuration — Externalize all configuration values. No hardcoded API keys, URLs, ports, or magic numbers.
  • Functions — Keep functions under 50 lines. Each function does ONE thing (Single Responsibility).
  • Naming — Use descriptive, self-documenting names. Avoid abbreviations. Match existing codebase conventions.
  • Comments — Comment the WHY, not the WHAT. Code should be self-explanatory for the "what."
  • DRY — Don't Repeat Yourself. If you write the same logic twice, extract it.

NEVER

  • Leave console.log debugging statements in production code
  • Use any type without a comment explaining why
  • Catch errors silently: catch(e) {}
  • Hardcode values that should be configurable
  • Skip input validation on user-facing endpoints
  • Copy-paste code blocks (extract shared logic)
  • Leave TODO/FIXME without an associated issue number
  • Introduce new dependencies without justification

Architecture Principles (SOLID)

  1. Single Responsibility — Each class/module has one reason to change
  2. Open/Closed — Open for extension, closed for modification (use interfaces/abstract classes)
  3. Liskov Substitution — Subtypes must be substitutable for their base types
  4. Interface Segregation — Many specific interfaces over one general-purpose
  5. Dependency Inversion — Depend on abstractions, not concretions

Testing Requirements

  • Every new feature needs tests covering happy path AND error paths
  • Tests must be independent (no shared mutable state between tests)
  • Test names describe the behavior: should return empty array when no items match
  • Mock external dependencies, not internal logic
  • Test coverage should not decrease with new changes

Read the full file on GitHub · 56 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 56 lines · 561 tokens per session scan A 6f8273002351

Subscribe to this mod's changes

core-development is a cursor rule published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 561 tokens to every session, about $0.0028 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.