Product updates, architecture patterns, and practical guides.
Each post digs into one part of the workflow — modeling data on the canvas, wiring routes and access rules, and the decisions behind the project skeleton Nodlume generates.
Featured
Canvas node
to normalized path
to file tree
Design systems//6 min read
Color-blind friendly color palettes for UI and charts
Why most palettes fail 8% of men, the two rules that make one safe, and proven color-blind-safe palettes with hex codes for interfaces and charts.
A practical checklist for planning routes, layouts, loading states, error boundaries, data access, authentication, and navigation before a Next.js App Router project becomes expensive to rearrange.
Choose navigation patterns from the shape of the task, connect them to the route tree, and test whether people can find, compare, complete, and recover across a growing application.
A route tree where a page's path is simply where it sits, navigation drawn as the paths people actually travel, and guards that protect a page however someone arrives at it.
The structure painter is a free canvas where brush strokes on a grid become a route tree — downloadable as a real Next.js App Router skeleton or shell script.
What belongs in a Zustand store and what does not, how to split one into slices, and why the App Router needs a per-request store, not a module-level one.
Why multi-file AI code generation should follow a topological build order, what each step should be shown, and why the walk is sequential, not parallel.
Five free shadcn/ui theming tools — theme generator, dark mode converter, font pairings, type scale, palettes — emitting the tokens your project reads.
Nodlume's Theme tab works like a Tailwind theme generator: eight semantic roles, a modular type scale, and elevation — hand-built, shuffled, or AI-generated.
Build an interface palette around roles, contrast, states, and surfaces—not a collection of attractive swatches that falls apart when applied to a real product.
What a complementary color scheme is, why it fails at equal weight, and the 80/20 rule, contrast checks, and dark-mode adjustments that make it work in a real interface.
Monochromatic, analogous, complementary, split-complementary, triadic, tetradic and square — the angle behind each scheme and which one an interface needs.
How to pick an app or website color scheme — primary, accent, background and status colors — with the tests that catch bad choices and 12 ready-made themes.
Turn spacing, elevation, borders, and radius into a small token system that keeps React interfaces coherent across cards, controls, dialogs, and dense application screens.
Choose Chrome extension permissions by capability, understand host access and install warnings, and keep a Manifest V3 extension no more privileged than its features require.
A free generator for Chrome extension manifests — surfaces, permissions that explain themselves, and match patterns that are validated, never repaired.
How Tauri 2's capability files, plugin crates and builder registrations fit together, why a compiling app still denies its own commands, and how to grant the narrowest permission a desktop feature actually needs.
Where Android grants and iOS usage descriptions live in an Expo or bare React Native app, why declaring a permission is only half of asking for it, and how to write usage descriptions App Review will accept.
How the app directory becomes a navigator tree, what belongs outside it, and the structural decisions that get expensive once an Expo app passes twenty screens.
What an agent actually is — a model, tools, and a loop — how to design one before you write code, and how to pick between the five major TypeScript SDKs.
What separates a coding agent from autocomplete, why code is the best domain for agents, the risks that actually matter, and how to choose a tool that fits.
Vercel ships two ways to build an AI agent — the AI SDK's loop inside your app, and Eve's durable deployed agents. What each one is for, and how they combine.
How Eve's filesystem-first layout works — why a tool's filename is the name the model calls, what a subagent does and does not inherit, and which decisions are worth making before the first deploy.
How createDeepAgent turns a prompt, a tool list and a backend into a long-horizon agent — what subagents inherit, why skills and memory are files, and which backend makes them reachable.
What goes into new Agent({ … }) — the difference between a handoff and an agent as a tool, how needsApproval pauses a run, why guardrails are agents themselves, and where MCP servers plug in.
How an ADK project is shaped — rootAgent in agent.ts, FunctionTool with Zod, sequential, parallel and loop workflows sharing state through outputKey — and the four constraints the docs spell out.
The SDK ships the tools and the loop; what you author is Options. How allowedTools, tools and disallowedTools differ, why delegation needs the Agent tool, and where custom tools, hooks and skills go.
Tools, resources and prompts on McpServer — what each register* call takes, why ResourceTemplate insists on list, and when to pick stdio over Streamable HTTP.
A drag and drop app builder assembles software visually. Here is how the category splits, what each type actually produces, and how to choose between them.
Requirements engineering is the discipline that produces good requirements — elicitation, analysis, modeling, definition, and review, sized for a small team.
The eight decisions that are cheap now and expensive later: scope, routes, data, access, API, tokens, tests, and traceability — plus when planning is done.
Turn form behavior, keyboard paths, loading and error states into explicit application decisions—and acceptance tests—before implementation hides the gaps.
Acceptance criteria written beside the page, component, store, or endpoint they are about — and exported as a real test suite where each case is pending until somebody proves it.
A requirements traceability matrix whose axes you wrote — features down the side, live design nodes across the top — and a report that shows what has a home.
Draw entities and relations on a free canvas and export Mermaid — typed columns, PK/FK markers, crow's-foot cardinality — instead of a screenshot that goes stale.
A visual planning workspace for React applications: pages, components, data models, API routes, and access rules on one connected canvas, exported as a real project.
We'd like to use Google cookies to understand how Nodlume is used and to measure our advertising. Nothing loads until you choose, and declining does not affect anything in the app.