Straktur

10 posts

Straktur banner
Straktur

Straktur

@straktur

Internal tools starter kit for AI builders. Auth, tables, forms, RBAC - production-ready. Works with Claude Code, Cursor, Codex, Gemini.

เข้าร่วม Ocak 2026
2 กำลังติดตาม1 ผู้ติดตาม
ทวีตที่ปักหมุด
Straktur
Straktur@straktur·
straktur.com — Build internal apps with AI. On a foundation that won't break. 🏗️ Not another SaaS starter kit. Straktur is a Next.js boilerplate for CRMs, dashboards, admin panels, and ops tools. How it works: 1️⃣ Clone & run — up in 5 minutes 2️⃣ Describe your feature in plain English 3️⃣ Ship it — production-ready code, every time The secret? Every feature your AI builds follows the same architecture. Same patterns. Same UI. No spaghetti. Whether it's your 1st feature or your 50th. 🔐 Auth & RBAC 📊 DataTables, inline editing, detail pages 🏢 Multi-tenancy 🧩 69 custom components 🤖 Architecture optimized for AI coding tools One-time purchase. No per-user fees. Own your code.
English
1
0
0
79
Straktur
Straktur@straktur·
DataTable with server-side sorting, filtering, search, and pagination Your AI coding agent generates this in minutes because it copies the pattern that already works.
English
0
0
0
13
Straktur
Straktur@straktur·
More demos coming this week. Get early pricing on straktur.com
English
0
0
0
5
Straktur
Straktur@straktur·
Polish: → Linear-style active filter highlight → DatePicker timezone bug (dedicated post coming - it's a classic .toISOString() trap 👀) → EntityHeader breadcrumb flicker on detail→detail jumps → EditableNumber: 2 decimals + comma separator for pl-PL → Sticky columns no longer bleed scrolled content
English
1
0
0
27
Straktur
Straktur@straktur·
4 weeks of shipping in Straktur Boilerplate 🚢 24 commits · 72 files · +2.9K lines PDF viewer, date range filter, role-based nav, a nasty timezone bug fixed, and a bunch of polish. Here's what's new 👇
Straktur tweet media
English
1
0
0
49
Straktur
Straktur@straktur·
You're building a CRM. You click into a client. You want to see their orders right there on the page. You tell your AI: "add an orders table to the client detail page." Because Straktur has a clear pattern for this, your AI already knows what to do: → Full sorting and search — not a basic list → Pagination that fits the space → "Add new order" button — scoped to this client → Same polished look as every other table in your app You didn't configure any of this. It's just how Straktur works. That's the difference between a boilerplate and a foundation. A boilerplate gives you building blocks. A foundation teaches your AI how to use them.
Straktur tweet media
English
0
0
0
75
Straktur
Straktur@straktur·
Most boilerplates give you components. We obsess over the tiny decisions that save you hours later. Example: JavaScript formats 0.23 as 23%. But your database stores 23.00 as 23%. Without handling this? Your app shows 2300% instead of 23%. 🫠 In Straktur, it's one config line. Set it once → every percentage column in every table just works. Forever. This is what we mean by "production-ready." Not more components - fewer surprises.
Straktur tweet mediaStraktur tweet media
English
0
0
0
53
Straktur รีทวีตแล้ว
Marcin Perlak
Marcin Perlak@marcinperlak·
I described a "Deals" feature in CRM demo app in plain English. 10 minutes later - full module with filters, search, inline editing, and multi-tenancy. No boilerplate wrestling. The trick isn't better prompts — it's giving AI the right architecture to follow. Full demo 👇
English
1
1
0
131