"You are spawning universes every time you prompt. Some of you are making very shitty universes which are very generic."
The Core Thesis
Why "Nano Apps"?
The word is deliberate. Not "micro." Not "macro." Nano.
A nano app solves one problem, solves it deeply, and refuses to bloat. The constraint is the feature. When you limit scope to a single-purpose tool, every line of code serves the mission. There is no feature committee, no backlog of compromises. The constraint breeds creativity β you must find elegant solutions within a tight box rather than throwing complexity at the problem.
This is not minimalism for its own sake. It is a design philosophy rooted in respect for the user's attention. Every feature you add is a tax on comprehension. Nano apps pay zero tax.
Offline-First: A Philosophical Choice
Ankura apps work on file://. You can double-click index.html from your desktop β no server, no internet, no build step, no deploy pipeline. This is not a technical limitation. It is a philosophical stance.
When your tool works offline, you are saying: your data never leaves your machine. There is no analytics endpoint phoning home. There is no cloud dependency that can be revoked, rate-limited, or monetised against you.
file:// compatibility is the most democratic deployment target on Earth. It works on a $100 laptop in a village with no internet. It works in an air-gapped corporate environment. It works 10 years from now when whatever cloud service would have shut down.
Zero Dependencies: The Courage to Own Every Line
No React. No Vue. No Tailwind. No npm. No build tool. No transpiler.
Every line of JavaScript is vanilla ES5-compatible code running in an IIFE. Every CSS rule is hand-written. When you own every line, you understand every line. There is no supply chain to audit. There is no node_modules black hole.
Zero dependencies means zero excuses.
The Naming Philosophy
Sanskrit + English: Bridging Worlds
Every app carries a Sanskrit name paired with an English word. Each Sanskrit root encodes the app's essence:
| Sanskrit Root | Meaning | App | Why |
|---|---|---|---|
| Vaak (ΰ€΅ΰ€Ύΰ€ΰ₯) | Speech, utterance | Vaak-Smith | Prompting is speech directed at an intelligence. The "smith" forges it into a weapon. |
| Yatra (ΰ€―ΰ€Ύΰ€€ΰ₯ΰ€°ΰ€Ύ) | Journey, pilgrimage, travel | Yatra-Monitor | Tracks travel journeys β train tickets parsed from PDFs into a navigable dashboard. |
| Yukti (ΰ€―ΰ₯ΰ€ΰ₯ΰ€€ΰ€Ώ) | Wisdom, strategy | GenAI-Yukti-Deck | Each card is a yukti β a named strategic device for prompt engineering. |
| Tula (ΰ€€ΰ₯ΰ€²ΰ€Ύ) | Balance, the scales | Tula-Bench | A balance for weighing AI tool quality through calibrated sentiment. |
| Ankura (ΰ€ ΰ€ΰ₯ΰ€ΰ₯ΰ€°) | Sprout, seedling | Ankura Array | The whole project is a seedling β small tools that grow from simple roots. |
The naming convention forces the creator to distil the app's essence into a single concept before writing a single line of code. If you can't name it in one word, you haven't understood it yet.
Vaak-Smith β The Prompt Engineering Cockpit
Core Belief: Prompting is worldbuilding, not form-filling.
A prompt is not a form. A prompt is a universe you are creating for an AI to inhabit. Every word constrains possibilities. A vague prompt leaves the AI in a vast, generic space. A worldbuilt prompt teleports the AI into a tight, rich, well-defined universe.
The 7 Principles
- Audience-First β Good writing is about what people hear, not what you say. The AI needs to know who it is talking to.
- Atomic Units β Start with ground truths. Set the physics of the universe before building anything inside it.
- Worldbuilding β Each prompt creates a universe. The Worldbuilder framework makes this explicit.
- Grounding with Examples β One concrete inputβoutput pair outperforms ten paragraphs of abstract instruction.
- Cognitive Hospitality β Simple language produces better AI outputs. Reduce cognitive load for the receiver.
- Single Leverage Point β Not all sections are equal. Each framework marks one β‘ leverage point.
- Frame Shift β Start in the audience's existing world, then gradually redirect. (Future exploration.)
Frameworks Are Thinking Scaffolds, Not Templates
Each framework enforces a particular order of thought. Google Standard forces persona first. Vivek-Kram forces you to articulate where you're stuck. The Worldbuilder forces audience and ground truths before the task. The order matters because it shapes how you think, not just what you write.
Yatra-Monitor β The Travel Intelligence Dashboard
Core Belief: Your data should work for you, not a corporation.
IRCTC ticket PDFs are locked vaults of your own travel history. Yatra-Monitor cracks them open using pdf.js (CDN with local fallback for offline), extracting raw text and applying a layered regex strategy with graceful fallbacks. A paste-text fallback ensures the parser works even in strict file:// environments without pdf.js.
Every parsing step is logged in a visible, timestamped, severity-coded Parse Log β the user is a collaborator, not a consumer. The schema-driven grid turns opaque data into a searchable, sortable thinking tool. A QR preview renders the PDF page to canvas for visual verification β no QR decoding library needed. Two-tier storage keeps PDF binaries in IndexedDB and parsed metadata in localStorage.
GenAI-Yukti-Deck β The Prompt Hack Deck
Core Belief: Prompt engineering is a learnable craft, not magic.
The deck externalises prompt engineering knowledge as playable cards with names like "The False Memory" and "The $100 Bet." The Pipeline Protocol (L1βL4) ensures correct ordering regardless of selection sequence. The {{VAR}} template system turns cards into micro-programs. Gamification as pedagogy: play β internalise β apply.
Tula-Bench β The AI Tool Evaluator
Core Belief: You can't improve what you can't measure with feeling.
Continuous atomic capture: every notable AI moment logged in 3 seconds. The 5-point sentiment scale (π β π) captures gut reactions, not sanitised survey responses. The Smart Summary reads your data and speaks back in English: opinionated, actionable intelligence, not just charts.
Zero config. Maximum signal. Zero friction.
Design Principles β The Laws of This Universe
- Constraint breeds creativity β Nano, not micro, not macro.
- Offline-first is a feature, not a bug β If it requires internet, it doesn't ship.
- Every app must work on
file://β The most democratic deployment target. - Zero dependencies means zero excuses β Own every line. Understand every line.
- Sanskrit names encode intent β If you can't name the essence in one word, you haven't understood it.
- One problem, solved deeply β Depth over breadth, always.
- Data never leaves the machine β No analytics. No telemetry. No cloud. No exceptions.
- User as collaborator β Show your work. Expose the logs. Make data editable.
- Concrete beats abstract β One example outperforms ten descriptions.
- Respect attention β Every feature is a tax on comprehension. Pay zero tax.