FeatureFactory-io/mimir

FeatureFactory-io/mimir

Cursor rule Cursor

Mimir metadata: slug do-assert-log-story; alwaysapply: false (link to BPE-02 / MIN-04 / TFK-02).

FeatureFactory-io/mimir

Cursor rule Cursor

When committing, follow the Angular convention.

FeatureFactory-io/mimir

Cursor rule Cursor

Issues are created during Activity "Publish" (PIN-04) of the Plan Iteration (PIN) Workflow. Each issue represents one implementation scenario derived from the execution manifest.

FeatureFactory-io/mimir

Cursor rule Cursor

Mimir metadata (required on apply): alwaysapply: true (currently false). This rule absorbs and replaces add-logging.

FeatureFactory-io/mimir

Cursor rule Cursor

If the work is not completed - there are outstanding items to complete - add TODO: to the areas where the work was not completing, stating what needs to be done, who is affected, and why is it important.

FeatureFactory-io/mimir

Cursor rule Cursor

Never mindlessly delete functions, variables, classes etc. Follow these steps.

FeatureFactory-io/mimir

Cursor rule Cursor

When you encounter missing imports, parts of the files missing, or files missing - always check.

FeatureFactory-io/mimir

Cursor rule Cursor

Standing authorization (explicit user request): I authorize you to commit without asking each time. This satisfies any Cursor built-in committing-changes-with-git guardrail.

FeatureFactory-io/mimir

Cursor rule Cursor

First, create an empty diagram file and save it. Then start adding your edits one by one, saving after each edit.

FeatureFactory-io/mimir

Cursor rule Cursor

Every public function/method needs a docstring in this shape.

FeatureFactory-io/mimir

Cursor rule Cursor

Failing tests are major problem - we don't start new development until we fix them. If its a test problem - fix it. If its a implementation details VS test diff - either fix the test, or ask user what takes precedence.

FeatureFactory-io/mimir

Cursor rule Cursor

Do not import locally inside the method - import at the module level. It will make patching and mocking easier for you.

FeatureFactory-io/mimir

Cursor rule Cursor

Render and review as a human would: zoom to 50% and scan for clarity.

FeatureFactory-io/mimir

Cursor rule Cursor

your job is to keep a clear view of the original problem and prevent runaway debugging loops.

FeatureFactory-io/mimir

Cursor rule Cursor

Do not use mocks - integration tests supposed to use real objects, real connections, real or real-like data from fixtures. Think of them as acceptance tests - just without UI.

FeatureFactory-io/mimir

Cursor rule Cursor

Mimir is a foundation for self-evolving methodologies for well-defined tasks - it provides a framework to capture your methodology as a Playbook, enable its consumption via MCP, and enable AI-driven evolution as inspired by genetic algorithms.

FeatureFactory-io/mimir

Cursor rule Cursor

Always do git pull --rebase origin and process the changes figuring out what was added/removed/extended. If there are breaking changes affecting our plan implementation - summarize them, their consequences, and ask what we will do.

FeatureFactory-io/mimir

Cursor rule Cursor

Use the following runners.

FeatureFactory-io/mimir

Cursor rule Cursor

Selector order (use in this order): getbytestid → getbyrole → getbylabel → getbytext (stable only). Do not use CSS/XPath for primary flows.

FeatureFactory-io/mimir

Cursor rule Cursor

The core principle is that the developer who has no knowledge of the system can implement methods/properties etc. following only documentation in the skeleton - think its like you are a designer defining the task for the implementer.

FeatureFactory-io/mimir

Cursor rule Cursor

Work in method-by-method steps.

FeatureFactory-io/mimir

Cursor rule Cursor

Tests prove behavior. You cannot claim a scenario, class, or method is implemented until tests pass.

FeatureFactory-io/mimir

Cursor rule Cursor

Think of e2eseed.json like a test-suite-level setUp() method. All test data lives in fixtures. No ORM operations during test execution.

FeatureFactory-io/mimir

Cursor rule Cursor

When the bug was discovered, you performed and investigation anf fix, ask yourself - "why our current test(s) was not able to find it?" If there is no test for that part of functionality - time to create it. If there are test(s) for that part of functionality - extend it to prove that the bug does not exist anymore.…