post-kit: Instructions file for Kiro

.kiro/steering/architecture.md

post-kit architecture.md is an instructions file for Kiro from Huzaifa-ali/post-kit. It costs 1,394 tokens per session, scanned A, original, MIT.

Project architecture instructions for a desktop application built with Tauri, FastAPI, and a web frontend. They require each system layer, module, file, function, and line to have a clear single purpose.

In plain words
What is it for?
Use them when adding or reorganising modules, deciding where application logic belongs, and checking whether a file or function does too many jobs.
Why use it?
They reduce tangled code and unclear boundaries by making responsibilities explicit. This helps keep a growing application easier to understand and maintain.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is Huzaifa-ali/post-kit's own configuration. It tells Kiro how to work on post-kit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything post-kit configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Huzaifa-ali/post-kit. 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/Huzaifa-ali/post-kit/master/.kiro/steering/architecture.md
Clone the repo
git clone --depth 1 https://github.com/Huzaifa-ali/post-kit

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.

agentmods badge for post-kit architecture.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/huzaifa-ali/post-kit/architecture/github.svg)](https://agentmods.dev/instructions/huzaifa-ali/post-kit/architecture)
Your own site
<a href="https://agentmods.dev/instructions/huzaifa-ali/post-kit/architecture"><img src="https://agentmods.dev/badge/instructions/huzaifa-ali/post-kit/architecture/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.

agentmods 80×15 button for post-kit architecture.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/huzaifa-ali/post-kit/architecture"><img src="https://agentmods.dev/badge/instructions/huzaifa-ali/post-kit/architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,394 This file is loaded in full into every session.
When invoked 1,394 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.01394 $0.01394
Opus 5.5 $0.00558 $0.00558
Sonnet 5.5 $0.00279 $0.00279
Haiku 4.5 $0.00139 $0.00139

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

Security

Grade A, and why

post-kit architecture.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 16d 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/architecture.md · 143 lines

How it starts

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

Project Architecture — Single Responsibility at Every Level

How top-tier open source projects stay maintainable: every piece has one job, clear boundaries, and obvious names.

The Principle

Single responsibility applies at every level:

  • System level: each layer has one job (Tauri=shell, FastAPI=logic, Frontend=display)
  • Module level: each module owns one feature completely
  • File level: each file has one purpose
  • Function level: each function does one thing
  • Line level: each line is readable without context

If you can't explain it in one sentence, it's too complex. Split it.

System Architecture

┌─────────────────────────────────────────────────────┐
│ Tauri Shell                                          │
│ Job: Launch backend, show webview, handle OS events  │
└─────────────────────┬───────────────────────────────┘
                      │ spawns
┌─────────────────────▼───────────────────────────────┐
│ FastAPI Backend                                      │
│ Job: All application logic, serve HTML, expose API   │
├──────────────────────────────────────────────────────┤
│ ┌──────────┐ ┌──────────┐ ┌──────────┐             │
│ │ Modules  │ │   Core   │ │ Adapters │             │
│ │ (features│ │ (shared) │ │ (AI CLI) │             │
│ └──────────┘ └──────────┘ └──────────┘             │
└─────────────────────┬───────────────────────────────┘
                      │ reads/writes
┌─────────────────────▼───────────────────────────────┐
│ Filesystem (post-kit)                                │
│ Job: Source of truth — posts, config, engine         │
└─────────────────────────────────────────────────────┘

Module Rules

Every module follows this structure:

modules/<name>/
├── router.py    # HTTP in/out. Thin. Calls service.
├── service.py   # Logic. Thick. The brain.
└── models.py    # Pydantic schemas. The contract.
File Allowed to import NOT allowed to import
router.py FastAPI, own service, own models Other modules, database directly
service.py core/bridge, core/database, core/events FastAPI, other modules
models.py Pydantic, stdlib Anything else

Read the full file on GitHub · 143 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. 16d ago First seen · 143 lines · 1,394 tokens per session scan A 706c720bb765

Subscribe to this mod's changes

post-kit architecture.md is an instructions file published in the GitHub repository Huzaifa-ali/post-kit (4 stars, last pushed 17d ago), licensed MIT. It adds 1,394 tokens to every session, about $0.0056 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-11.

Related

Other instructions, from other repositories

data-scientist copilot-instructions.md

Repository instructions for a data-science workflow in GitHub Copilot, covering datasets, statistics, and analysis files.

realnghon/data-scientist · 373 tokens

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,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens