Lumenari vs Writing your own prompts
DIY prompting is free, totally fine, and what most people start with. Lumenari is for the moment you realize you've been re-writing the same prompt for six months and would rather have it dialed in by someone else. The decision is honestly about the value of your time — at what hourly rate does it stop being worth your weekend to author your own prompts. For some people that's $20/hour, for some it's $300/hour. The answer determines which path is right for you, and most people pick wrong in both directions at different times in their journey.
| Función | Lumenari | Writing your own prompts |
|---|---|---|
| Price | $14–$29 CAD per kit | Free |
| Time to first useful output | ~2 minutes | Hours to days, iterating |
| Customization ceiling | Edit anything inside the kit | Unlimited |
| Maintenance burden | Updates included | You |
| Reusability across tools | 4 formats per kit | Author each per tool |
| Learning effect | Read the kit, learn the patterns | Earn the patterns directly |
| Best fit | Outcomes-focused users | Prompt-engineering power users |
| Companion files | memory.md, voice presets, quick starts | Whatever you author |
Dónde gana Lumenari
- Pre-tested patterns — every kit has been run through real workflows before shipping, with documented failure modes already caught. The constraint blocks in particular are earned from real mistakes, not invented in the abstract.
- Four delivery formats — same kit works in Claude, ChatGPT, Cursor, Gemini, custom GPTs. Authoring your own means writing each format yourself if you want cross-AI portability, which most DIY prompters skip and later regret.
- Role-specific depth — kits include the supporting files (memory.md, voice presets, quick-start prompts) most people never get around to authoring. The SKILL.md is 20% of the value; the supporting files are the other 80% that most DIY attempts skip.
- Updates — when the model improves or a new failure mode shows up in customer reports, the kit gets refreshed. DIY prompts go stale silently and you find out via a frustrating output six months in.
- Recommendation wizard finds the right kit without you having to know the catalog. DIY means you also have to design the prompt taxonomy — what counts as one prompt vs three vs a whole role.
- Honest learning resource — read the SKILL.md, see how the patterns are layered, and you'll write better DIY prompts going forward. Many customers buy two or three kits, internalize the structure, then DIY the rest.
- Removes the meta-work — most DIY prompters spend more time tuning the prompt than using it. The kit collapses that overhead so you can spend your hours on outcomes instead of prompt iteration.
Dónde gana Writing your own prompts
- Free. No payment, no signup, no vendor relationship. The most flexible option by definition.
- Total customization — every constraint, persona, format exactly as you want it. No compromise with someone else's design decisions, no patterns you don't agree with.
- Builds the skill — the more you prompt, the better you get at the meta-skill of prompt engineering. That's a transferable capability that compounds over years.
- No dependency on a vendor's catalog or pricing. Your prompts live on your disk forever, regardless of what any company does.
- Tuned to your exact context — your codebase, your voice, your industry, your specific clients. A general-purpose kit can't capture the level of specificity a DIY prompt can.
- Forces you to actually understand your own workflow — the act of authoring a prompt is itself useful diagnostic work for figuring out what you actually want the AI to do.
Preguntas comunes
Isn't DIY just better in the long run?
For a power user who'll spend 50+ hours on prompt engineering anyway — probably yes, and you'll come out with prompts more tightly tuned to your exact context than any general-purpose kit can manage. For someone whose job isn't prompt engineering and who'd rather spend that time on outcomes (closing deals, shipping code, writing listings) — Lumenari is the shortcut. The honest decision is whether you want to be good at prompt engineering or good at your actual job.
Can I learn from Lumenari kits and then build my own?
Yes — the kits are open files. Read the SKILL.md, see the structure, internalize the patterns, then iterate on your own. Many customers buy two or three kits for the roles they work in most and then go DIY for the rest. The kits double as a working education in the SKILL.md format, which is hard to teach in the abstract but obvious once you've seen a few done well.
What if I only need one prompt, not a whole kit?
Honestly, DIY. Lumenari kits earn their price when you reach for them five or ten times across a role. For a one-off task — a single email, a one-time outline, a single migration — write your own prompt and ship. The kit math doesn't work for genuinely one-off use cases.
How long does it take to author a really good prompt from scratch?
For a single one-shot prompt, 15-30 minutes if you know what you're doing. For a full SKILL.md with constraints, patterns, examples, and supporting files for a specific role — usually 4-8 hours of focused work plus another 4-8 hours of iteration over the next few weeks as you find the failure modes. That's the time you're saving when you buy a kit instead of authoring one.
What if my role isn't in the Lumenari catalog?
Then DIY is the right answer for now. Use the closest adjacent kit as a structural template, modify it for your specifics, and you'll be ahead of authoring from scratch. The catalog is also still scaling toward 100+ kits — if your role isn't covered today, it may be in a quarter or two.
Mira el catálogo tú mismo.
20+ kits, 6 bundles, cuatro formatos por kit.