A blueprint-first framework and Agent Skill for Claude. Before any production code, your AI agent writes the plan a senior team would: product, architecture, security, privacy law, accessibility and every UI state. Then it stops and waits for your approval.

Install · See it work · 17 launch traps · What's inside · Cite

They're decisions nobody made. The demo works and the tests pass. Then:

Bansat makes every one of those decisions explicit before the first commit, and checks them again before launch.

Bansat (بنسټ) is Pashto for "foundation": the part you lay before you build.

flowchart TB subgraph NEW ["Plan"] direction LR A["Your idea"] --> B["Intake<br/>20-question screen"] --> C["Risk tier<br/>Low · Medium · High"] --> D["docs/BLUEPRINT.md"] --> G1{"G1<br/>You approve"} end subgraph SHIP ["Build and ship"] direction LR P["9 build phases"] --> G2{"G2<br/>Data-ready"} --> G3{"G3<br/>Launch gate"} --> L["Launch"] --> G4{"G4<br/>30-day review"} end NEW --> SHIP

Loading

The gates are the point:

Already built something? The retrofit track triages the live risks within 48 hours, reverse-engineers the blueprint from your code, and turns every gap into a fix with a deadline:

flowchart LR E["Existing or live app"] --> T["Day-0 triage<br/>11 checks in 48 h"] --> R["As-is blueprint<br/>from the code"] --> GR["Gap register<br/>with deadlines"] --> S["Fix sprints<br/>R1 → R4"]

Loading

Install in 60 seconds

Claude Code (terminal or VS Code). Install it once and use it in every project:

macOS / Linux

git clone https://github.com/bewithkhan/bansat ~/.claude/skills/bansat

Windows (PowerShell)

git clone https://github.com/bewithkhan/bansat "$HOME.claude\skills\bansat"

Start a new Claude Code session and type /bansat. To update, run git pull in that folder. To share it with your team, copy the folder into your repo at .claude/skills/bansat/ and commit it.

Claude apps (web and desktop): add it as a skill in your Claude settings. See Use skills in Claude.

Any other agent: SKILL.md follows the open Agent Skills format, so skills-compatible agents can load it as it is. For Cursor, Copilot, Lovable, Bolt or anything else that reads a rules file, give the agent reference/bansat-framework.md and paste its Part 12.1 agent rules into AGENTS.md, .cursor/rules or your project knowledge.

/bansat I want to build a revision app with an AI tutor for students in the UK and Nigeria

Bansat restates the idea and asks at most five questions, only where a wrong guess would be costly. It then writes docs/BLUEPRINT.md and a summary like this one (abridged):

These are the failures that get vibe-coded apps fined, breached or rejected by the app stores. Bansat checks every one before you collect real data (G2), and again before launch (G3). The full table, with fixes and tests, is in §9.26 of the framework.

If you read one thing in this repo, read this table. Then check your own app against it.

Viral compliance threads get some of this wrong. Bansat sticks to what the law actually says:

One Markdown file: 15 parts and 4 appendices, about 2,800 lines. Claude reads only the parts each project needs.

PRD template Asking the AI Bansat

Product, architecture, security, privacy and UX in one plan Product only Patchy ✅

Gates that block code, data and launch until you approve ❌ ❌ ✅ G0–G4

Laws cited to the section, and checked on a stated date ❌ Unverified ✅ 4 Nov 2026

Code samples tested before release ❌ Untested ✅

A track for apps that are already live ❌ ❌ ✅ Day-0 triage

Every UI state designed and tested on every screen ❌ Happy path only ✅ 17 states

The same standard on every project, team and tool Copy and paste Per chat ✅ One skill, one file

Tested, not just written

The code in the framework was run before release:

Laws change. Re-check anything you rely on before launch; see the disclaimer.

Is this legal advice?

No. It summarises the law and regulator guidance as of 4 November 2026, cites the sections, and says when to get a qualified review: health, children, biometrics, worker monitoring or large-scale tracking.

It scales with risk. A low-risk project fills in only the essentials: intake, the core product spec, the stack, cookies and third-party requests, the launch traps, UI states and the launch gate. High-risk projects get everything, because that's where mistakes cost the most.

No. The framework is one Markdown file you can fill in by hand or with any AI agent. Claude Code just does the most for you: it screens your idea, writes the blueprint and holds the gates.

The engineering half applies everywhere, and the laws table has pointers for other markets. Open an issue with your country's law and a link to an official source.

Yes. The text and templates are CC BY 4.0, so you can use and adapt them commercially as long as you keep the credit line. The code samples are MIT.

It lives in your repo as docs/BLUEPRINT.md and changes in the same pull request as the code. Live projects get a monthly review and a quarterly launch-trap audit.

Use GitHub's Cite this repository button, or:

Khan, M. T. (2026). Bansat (بنسټ): A blueprint-first framework for building software (Version 2.0) [Computer software]. GitHub. https://github.com/bewithkhan/bansat

@misc{khan2026bansat, author = {Khan, Muhammad Tufail}, title = {Bansat: A blueprint-first framework for building software}, year = {2026}, note = {Version 2.0}, howpublished = {\url{https://github.com/bewithkhan/bansat}} }

Contributing

Bansat gets better with every project it meets. Contributions are welcome:

Keep the credit line in anything you copy or adapt (CC BY 4.0).

Muhammad Tufail Khan: PhD researcher in AI and IoT for healthcare at the University of the West of Scotland, based in Glasgow.

Text and templates: CC BY 4.0, full text in LICENSE. You can use, adapt and share them, including commercially, if you keep this credit: "Bansat (بنسټ) by Muhammad Tufail Khan, https://github.com/bewithkhan/bansat, CC BY 4.0".

Code samples: MIT (see LICENSE-CODE).

NOTICE sets out which licence covers what, with the credit line.

Disclaimer

Bansat summarises laws and regulator guidance as of 4 November 2026. It is not legal advice. Check the current rules before you launch, and get a qualified review for high-risk processing.

If Bansat saves you from one bad launch, star the repo so the next builder finds it before theirs.

Built by Muhammad Tufail Khan · LinkedIn · GitHub