Project instructions describing the technology stack and development standards for an application called M3E. It covers TypeScript, Node.js, React, SQLite, Vite, unit tests, and browser-based end-to-end tests.

Use it as background when working on M3E features, especially local data storage, browser flows, graph interfaces, builds, or automated tests.

It gives coding agents a shared picture of the application’s languages, libraries, storage, build tools, and testing approach before they change code.

How akaghef/M3E configures Kiro

Reuse

Borrowing it

Nothing to install: this file belongs to akaghef/M3E. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/akaghef/M3E/main/.kiro/steering/tech.md

Clone the repo

git clone --depth 1 https://github.com/akaghef/M3E

Made for: Kiro.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/akaghef/m3e/tech/github.svg)](https://agentmods.dev/instructions/akaghef/m3e/tech)

Your own site

<a href="https://agentmods.dev/instructions/akaghef/m3e/tech"><img src="https://agentmods.dev/badge/instructions/akaghef/m3e/tech/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/akaghef/m3e/tech"><img src="https://agentmods.dev/badge/instructions/akaghef/m3e/tech.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 738 This file is loaded in full into every session.

When invoked 738 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.

Model	Per session	Once invoked
Fable 5.1	$0.00738	$0.00738
Opus 5.5	$0.00295	$0.00295
Sonnet 5.5	$0.00148	$0.00148
Haiku 4.5	$0.00074	$0.00074

Measured 5d ago against content hash 2a63f99accae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

M3E tech.md 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 5d 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.

.kiro/steering/tech.md · 88 lines

How it starts

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

Technology Stack

Architecture

M3E beta is a TypeScript application with a Node.js local server and browser viewer. The current architecture favors local-first operation, explicit persistence boundaries, and small feature slices that can be verified with unit and browser-visible checks.

Core Technologies

Language: TypeScript.
Runtime: Node.js for local server, filesystem, SQLite, import/export, sync, and AI proxy work.
Frontend: Browser TypeScript plus React-based workbench surfaces where applicable.
Build: TypeScript compiler and Vite.
Persistence: better-sqlite3 for local workspace data; JSON state remains an important compatibility shape.
Testing: Vitest for unit checks and Playwright for browser-visible flows.

Key Libraries

better-sqlite3 for local SQLite persistence.
@playwright/test for visual and end-to-end verification.
vitest for unit tests.
vite for browser build output.
elkjs, cytoscape, @xyflow/react, @antv/x6, and @joint/core for graph/layout/prototype surfaces.
js-yaml for Markdown/frontmatter-oriented flows.
@langchain/langgraph / langchain for graph runtime experiments.
@supabase/supabase-js for optional cloud sync experiments.

Development Standards

Type Safety

Prefer explicit TypeScript types and shared interfaces from beta/src/shared/.
Avoid broad any and stringly contracts when a local type already exists.
Validate external input at the Node/API boundary before applying it to AppState or persistent storage.

Data Safety

Treat workspace > map > scope > node as the product hierarchy.
Preserve mapId, workspaceId, and runtime data-profile separation.
Save/sync/recovery changes need narrow tests and clear rollback or backup behavior.
Do not infer runtime truth from source alone when a visible viewer/runtime state is relevant.

Code Quality

Follow existing module patterns before introducing new abstractions.
Keep UI behavior, persistence, and synchronization changes in small reviewable slices.
Prefer established libraries for parsing, file watching, database access, rendering, and browser tests.

Read the full file on GitHub · 88 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.

5d ago First seen · 88 lines · 738 tokens per session scan A 2a63f99accae

Subscribe to this mod's changes

M3E tech.md is an instructions file published in the GitHub repository akaghef/M3E (11 stars, last pushed 5d ago), licensed MIT. It adds 738 tokens to every session, about $0.0030 per session on Opus 5.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-10-02.

E2E testing Planning Testing Unit testing

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

M3E: Instructions file for Kiro