oreum-ai

oreum-ai/smartstack

Cursor rule Cursor

SmartStack — points Cursor at the portable brain and core rules.

oreum-ai/smartstack

Cursor rule Cursor

You are working in a repo that uses SmartStack. Read AGENTS.md at the repo root — it is the full brain — and follow its session protocol and golden rules. Load only what the task needs from ai-rules/ (see the context-budget skill); do not rescan the whole repo.

oreum-ai/smartstack

Skill Claude CodeCodex

At the start of any task, and whenever you're about to read files to gather context. Keeps you from burning tokens by scanning the whole repo when a targeted read would do.

oreum-ai/smartstack

Skill Claude CodeCodex

The moment something breaks: a crash, a failed request, a wrong value, a red test, a confusing bug. This is the skill that makes the error ledger pay off.

oreum-ai/smartstack

Skill Claude CodeCodex

Before merging or shipping any non-trivial change, and whenever you want a thorough multi-lens review of a diff. Orchestrates the specialist agents so nothing important is missed.

oreum-ai/smartstack

Skill Claude CodeCodex

When code works but is hard to read, duplicated, or fragile — and you want to improve its structure without changing behavior. Not for features; for making existing code cleaner and safer to change.

oreum-ai/smartstack

Skill Claude CodeCodex

Installing SmartStack into a repo for the first time, onboarding a new AI tool, or repairing/extending the system itself.

oreum-ai/smartstack

Skill Claude CodeCodex

When a change is finished and you're ready to commit, push, or release. The final gate that makes sure you ship working, safe code — and that project memory is updated so the next session inherits your work.

oreum-ai/smartstack

Skill Claude CodeCodex

Before writing any high-risk logic: authentication, authorization, money/billing, core domain rules, data integrity, anything irreversible. Required there because a silent bug is dangerous or expensive.

oreum-ai/smartstack

Skill Claude CodeCodex

To add tests to code that already exists (vs tdd, which writes tests first for new risky logic). Use it to backfill coverage before a release, after a bug, or when a risky path has no protection.