post-kit: Instructions file for Kiro

.kiro/steering/frontend.md

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

Frontend coding instructions for HTML, Tailwind CSS version 4, and plain JavaScript. They emphasise accessible semantic HTML, one responsibility per file or function, and keeping CSS configuration in CSS rather than JavaScript.

In plain words
What is it for?
Use them when building or reviewing pages, templates, JavaScript modules, and Tailwind styles in the post-kit project.
Why use it?
They reduce hard-to-maintain page structure and mixed responsibilities. They also give consistent rules for accessible markup, styling, and small frontend modules.

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/frontend.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 frontend.md

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

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

Measured 16d ago against content hash 1a9d508950fd, 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 frontend.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/frontend.md · 194 lines

How it starts

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

Frontend — HTML, Tailwind CSS v4, Vanilla JS

Write frontend code like Stripe's dashboard, Linear's UI, or Cal.com: minimal, fast, readable. No cleverness.

Single Responsibility

  • One JS file = one concern (chat.js handles chat, editor.js handles editing — never both)
  • One HTML template = one page
  • One component partial = one reusable piece
  • One function = one action (fetch data OR render DOM — not both in the same function)

The test: Can you name the file/function in 2-3 words that fully describe it? If not, it does too much.

HTML — Semantic, Accessible, Clean

<!-- Good — semantic, readable -->
<main class="flex-1 p-6">
  <section data-page="library">
    <header class="mb-6">
      <h1 class="text-xl font-semibold text-primary">Library</h1>
    </header>
    <article class="post-card" data-post-id="{{ post.id }}">
      ...
    </article>
  </section>
</main>

<!-- Bad — div soup -->
<div class="main">
  <div class="section">
    <div class="header">
      <div class="title">Library</div>
    </div>
  </div>
</div>

Rules:

  • Semantic elements: <nav>, <main>, <section>, <article>, <aside>, <header>, <footer>
  • Every <img> has alt. Every <input> has <label>. Every button is keyboard-accessible.
  • data-* attributes for JS hooks. Never select by styling classes.
  • No inline styles. No inline scripts.

Tailwind CSS v4 — CSS-First, Token-Based

Configuration lives in CSS (not JavaScript)

/* app.css — the ONLY place design tokens are defined */
@import "tailwindcss";

@theme {
  /* Colors — OKLCH for perceptual uniformity */
  --color-surface: oklch(0.13 0.01 260);
  --color-surface-raised: oklch(0.18 0.01 260);
  --color-text-primary: oklch(0.93 0 0);
  --color-text-secondary: oklch(0.65 0 0);
  --color-accent: oklch(0.65 0.19 265);
  --color-border: oklch(0.28 0.01 260);
  --color-status-draft: oklch(0.75 0.15 85);
  --color-status-approved: oklch(0.65 0.15 250);
  --color-status-published: oklch(0.70 0.15 145);

  /* Typography */
  --font-sans: "Inter", system-ui, sans-serif;
  --font-mono: "JetBrains Mono", monospace;

  /* Shadows */
  --shadow-card: 0 2px 8px oklch(0 0 0 / 0.25);
}

Read the full file on GitHub · 194 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 · 194 lines · 1,693 tokens per session scan A 1a9d508950fd

Subscribe to this mod's changes

post-kit frontend.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,693 tokens to every session, about $0.0068 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

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

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens